Privacy Policy

What we collect

Altra collects the data needed to operate a private-beta planner workspace and keep each planner's work isolated.

• Account and workspace details, including name, email, studio, invite-code status, roles, and settings.
• Couple portal membership, invitation, notification, action, response, upload, and activity records for planners who enable the portal for a Wedding.
• Wedding data, including couples, dates, responsibility profiles, tasks, timelines, budgets, decisions, notes, and workflow status.
• Vendor, contact, file, calendar, inbox, Playbook, and Altra Assistant data that planners add, import, connect, upload, or ask Altra to process.
• AI interactions, prompts, drafts, review decisions, action receipts, and support records needed to explain or troubleshoot beta behavior.
• Limited product analytics through Vercel Analytics, plus security, deployment, and diagnostic logs from our infrastructure providers.

How we use data

We use planner data to provide the product, support beta onboarding, secure access, and improve reliability during the private beta.

• Authenticate planners, enforce invite-gated signup, protect planner routes, and maintain tenant isolation.
• Authenticate invited couple members, enforce Wedding-scoped membership, and provide the action, timeline, file, budget, and concierge views their planner enables.
• Run planner workflows such as Wedding setup, vendor work, files, budgets, timelines, calendar, inbox, and the Altra Assistant.
• Draft, summarize, classify, recommend, or prepare actions that the planner can review before anything is sent or committed.
• Investigate support requests, prevent misuse, preserve audit context, and diagnose incidents or failed workflows.
• Improve beta quality using aggregate or de-identified patterns where practical, not by selling planner data.

AI and planner review

Altra's AI features assist planners, but they do not replace planner judgment or approval.

• The Altra Assistant may use workspace, Wedding, vendor, calendar, inbox, file, and prior interaction context to produce drafts or recommendations.
• Planner-facing review remains required before outbound email, couple-facing communication, vendor actions, budget moves, or other committed actions.
• AI outputs can be incomplete or incorrect. Planners are responsible for reviewing, editing, and approving the final content they use.

Integrations and processors

The private beta uses a small set of infrastructure, AI, search, and integration processors to operate the app.

• Vercel for hosting, deployment logs, and Vercel Analytics.
• Supabase for authentication, database, storage, and server-side access controls.
• OpenAI for AI drafting, summarization, classification, and orchestration features.
• Google OAuth APIs for Google sign-in and planner-authorized calendar, contacts, or inbox workflows.
• Firecrawl and Exa for vendor discovery and enrichment workflows when those features are used.
• The configured email provider or connected Google account for planner-approved outbound email workflows.

Uploaded files, contacts, inbox, and calendar data

Planner-imported operational data is used to power the workspace features the planner chooses to use.

• Uploaded files are stored for the planner workspace and used for Wedding, vendor, and support workflows.
• Imported contacts and vendor records are used to build planner-owned vendor libraries, enrichment queues, and Wedding vendor workflows.
• Connected inbox and calendar data is used only for the planner-authorized features that need it, such as drafts, summaries, reminders, and schedule context.
• When a planner enables couple commitment detection, Altra may process the newest unquoted portion of Wedding-matched email to identify an explicit request for a known couple email. Couples do not connect Gmail for this feature.
• Raw email bodies are processed transiently for commitment detection and are not stored in the couple action ledger. Altra stores bounded evidence, extraction results, HMAC-derived message identifiers, outcomes, and audit metadata needed to prevent duplicate processing and explain an action.
• Private planner records, emails, files, and Wedding details should not be exposed to other planners except through explicit product features that are designed for couple collaboration or internal Altra directory review.

Export, deletion, and support

Private beta planners can request support-assisted export or deletion using support@meetaltra.com.

• Workspace export is available in Settings > Workspace and returns planner-scoped JSON for support-assisted portability.
• Deletion requests are handled by support during beta until self-serve account deletion is released.
• Before deletion, support will verify account ownership and offer export unless the planner asks to skip it.
• Incident or privacy requests should be sent to support@meetaltra.com and include the planner account email, workspace name, affected Wedding or vendor when known, browser/device, and timestamp.

Beta changes

Altra is an invite-only private beta. Features, processors, and data practices may change as the product matures, and this policy will be updated when the beta surface changes materially.