Privacy Policy

Altessa LLC ("we", "our", "us"), operating as Altessa, provides wedding planning software to couples preparing for their wedding day. This Privacy Policy describes how we collect, use, and share information when you use Altessa at altessa.studio (the "Service").

Information we collect

When you create an account, we collect your email address and any name you provide, the date and version of the Terms of Service you accepted, and, if you choose to tell us, how you heard about Altessa. When you use the Service, we store the wedding planning information you enter, including dates, venues, vendor details, guest lists, budgets, layouts, and any files you upload such as vendor contracts or floor plans.

If you purchase Altessa, our payment processor Stripe collects your billing information. We never see or store your full card number.

We automatically receive limited technical information when you visit the Service, including IP address, browser type, device information, and pages visited, for security purposes. We also collect product-usage information such as the pages and features you interact with, to understand how Altessa is used and improve it (see Analytics and session recordings below).

Signup and purchase events for ad measurement. When you sign up, request a free planning tool by email, or make a purchase, we record that event and may send it to Meta to measure our own advertising, as described in Advertising and measurement below.

First-touch attribution. On your first visit we note, in your browser, the website that referred you, the page you first landed on, any campaign (UTM) tags in the link, and any Facebook click identifier (fbclid). When you create an account, the referrer, landing page, and campaign tags are saved to your account; the click identifier is used only for ad measurement and is not stored with your account.

Approximate signup location. When you create an account, we record an approximate location derived by our hosting provider, Vercel, from your connection: country, region, city, and coordinates rounded to about 10 km. We do not store your IP address for this.

How we use information

We use the information to operate the Service, authenticate your account, process payments, communicate with you about your account and product updates, prevent abuse, measure our own advertising, and improve Altessa.

Internal use. We review aggregated usage and account activity, such as signups, purchases, feature use, and where new accounts come from, to run and improve Altessa.

Service providers

We share information with the following third parties to operate the Service:

• Supabase: database, authentication, and file storage. Receives everything stored in your account.
• Vercel: web hosting, cookieless page-view analytics (Vercel Web Analytics), and the approximate location described above. Receives your requests to the Service, including IP address and browser details.
• Stripe: payment processing. Receives your email address, account ID, and billing details.
• Sentry: error and crash reporting (always on; see Error monitoring below). Receives technical details about errors, including browser and device information.
• PostHog: product analytics (cookieless in the United States unless you accept; cookies and session recordings only with your consent). Receives usage events and your account ID. The assistant integration also sends PostHog one server-side event per request (the tool, the assistant, whether it worked, a guest count range, and whether room dimensions were given) under an anonymous identifier that changes daily, never your account ID.
• Microsoft Clarity: heatmaps and session recordings (loads only with your consent). Receives masked recordings of page use.
• Meta (Facebook) Pixel and Conversions API: measures whether our own advertising led to a signup or purchase. Receives the events and identifiers described in Advertising and measurement below.
• Klaviyo: email. Receives your email address, first name, plan, and planning details such as wedding date, planning stage, approximate guest count and budget range, and how you use Altessa, so we can send account and planning emails. When a wedding guest asks for a copy of their RSVP, Klaviyo also receives that guest's email address and reply so it can send the copy.
• Google: sign-in with Google, optional Google Calendar sync, and web fonts. Receives your Google account email when you choose Google sign-in, the deadlines you choose to add to your calendar, and your IP address and browser details when fonts and the sign-in script load.
• Anthropic: artificial intelligence analysis of venue floor plans you choose to import. Receives the floor plan image and the room and guest-count details you enter, never your name or email address.

Except for Meta, as described in Advertising and measurement, these providers process information on our behalf under contract and are not permitted to use it for their own purposes. We do not sell your wedding planning data, and we do not share your wedding planning data with advertisers or vendors.

Google user data

If you sign in with Google, we receive your Google account email address and name to create and secure your account. Google also sends a link to your profile photo, which Altessa does not use.

If you connect Google Calendar, Altessa requests one permission: https://www.googleapis.com/auth/calendar.events. We use it only to add the dated planning deadlines on your timeline to your Google Calendar as all-day events, when you choose to sync. Altessa does not read, change, or delete your existing events or calendars. The access token is used for that sync and is not stored. We store only a reference linking each Altessa deadline to the event it created, and when it was synced, so a repeat sync does not create duplicates.

We do not use Google user data for advertising, we do not sell it, and we do not transfer it to anyone except as needed to provide the sync. No one at Altessa reads it unless you ask us to, for security, or as required by law. You can disconnect Altessa at any time at myaccount.google.com/permissions.

Altessa's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Advertising and measurement

We run a small amount of advertising on Meta platforms (Facebook and Instagram) and use the Meta Pixel and the Meta Conversions API to learn whether those ads led to a signup, an email request for a free planning tool, or a purchase.

The Meta Pixel is a script from Meta that runs in your browser. It sends page views and those events to Meta, and once you select "Accept" it may set Meta cookies. The Conversions API sends the same events from our servers. Server events can include a hashed (unreadable) form of your email address and account ID, your IP address and browser details, the page address, Meta's browser identifiers, and the purchase amount. Meta may use this information under its own terms and privacy policy, including to improve its advertising services.

Under California law, disclosing personal information to an ad platform in this way counts as "sharing" for cross-context behavioral advertising. We never share your wedding planning data, your guests, or your vendor details with Meta or any advertiser.

You can opt out of this sharing in three ways:

• Use the button on Your Privacy Choices.
• Select "Decline" in our cookie banner.
• Turn on Global Privacy Control in your browser. We honor it automatically.

After you opt out, the Meta Pixel does not load in that browser and we do not send signup, lead, or purchase events to Meta for you. If you are signed in, the opt-out is saved to your account and applies on every device.

Analytics and session recordings

We use PostHog and Microsoft Clarity to understand how people use Altessa so we can improve it. In the United States and everywhere outside the European Economic Area and the United Kingdom, PostHog runs in a cookieless mode unless you select "Accept" in our cookie banner, including after you select "Decline": it collects product-usage events (such as which pages and features you visit and the campaign link you arrived through), approximate location derived from your IP address, and device and browser information, but sets no cookies, stores no persistent identifier in your browser, and does not record your session. Microsoft Clarity does not load at all unless you accept.

If you select "Accept", PostHog and Clarity may set cookies and use related browser storage so we can recognize you on a return visit, and may record masked session replays and heatmaps that show how a page was used. To protect your wedding planning information, PostHog recordings mask all text and all form inputs, so the content you type is not captured. If you select "Decline", or later change your choice to Decline, Clarity stops recording and its cookies are deleted from your browser, and PostHog returns to the cookieless mode described above, with its cookies and stored identifier removed and no session recording.

Error monitoring

We use Sentry to receive automatic reports when the Service encounters an error, so we can diagnose and fix problems. Sentry runs for error monitoring only. It does not record your session, replay your activity, or track your behavior across the Service. Because it is limited to keeping the Service working correctly, we run it on the basis of our legitimate interest in the Service's reliability and security, independent of the consent choices described here.

Cookies and consent

We use a strictly necessary authentication cookie set by Supabase to keep you signed in. The Service cannot function without it, so it is always present. We also store small first-party values in your browser's local storage to remember your cookie choice, your privacy choices, a referral or campaign link you arrived through, and similar functional settings.

United States and other regions. When you first visit Altessa, a banner lets you Accept or Decline. Before you answer, PostHog runs cookieless as described above, Microsoft Clarity and the Meta Pixel do not load, and signup and purchase events are sent to Meta for ad measurement. If you accept, Clarity and the Meta Pixel load, and PostHog, Clarity, and the Meta Pixel may set cookies and use related browser storage. If you decline, Clarity and the Meta Pixel stay off, PostHog stays cookieless, and you are opted out of sharing with Meta.

European Economic Area and United Kingdom. If your device is set to a European or Icelandic time zone, nothing described above loads until you select "Accept": no PostHog, no Clarity, no Meta Pixel, and no signup, lead, or purchase events are sent to Meta. If you decline, none of them load.

Everywhere, a browser that sends Global Privacy Control is treated as opted out of sharing with Meta. Sentry and Vercel Web Analytics run for every visitor and do not set analytics or advertising cookies. We remember your choice in local storage under the key altessa_cookie_consent. You can change your choice at any time on Your Privacy Choices, where you can also opt out of sharing.

Email

We send email through Klaviyo. When you create an account, you will receive planning tips and product email from Altessa, along with account emails and planning emails such as the Monday planning summary. Every marketing email includes an unsubscribe link, and you can turn off the Monday planning email in Settings.

Guest information

Couples add their guests' information, such as names, addresses, email addresses, and RSVPs, to plan their wedding. Altessa uses guest information only to run the Service for that couple and never markets to guests. Wedding websites that couples publish through Altessa (addresses beginning with altessa.studio/w/) show only what the couple chooses to publish. When a guest RSVPs on a wedding website and asks for a copy, the confirmation email goes only to the address the guest enters. We do not run analytics, session recording, advertising measurement, or a cookie banner on those pages.

Wedding members

An account owner can invite one additional planner to their wedding. A second planner can see and edit all of the wedding's planning data, including the guest list, budget, vendors, and files.

Assistant integrations (ChatGPT, Claude, and other MCP clients)

If you use Altessa from ChatGPT, Claude, or another assistant that supports the Model Context Protocol (MCP), the Altessa MCP server receives only the tool inputs your assistant sends, such as a guest count, a ceremony time, a city, or a guest list. It does not receive the rest of your conversation, your name, or your email address; your conversation is handled by your assistant's provider under its own privacy policy.

The server stores the plan it makes under a random link that anyone with the link can view. The plan includes the tool inputs it was made from, such as guest names, so share the link only with people you want to see it. The server also stores the name of the assistant that asked for the plan and a timestamp. If you save a plan to your Altessa account, it is copied into your wedding and treated like the rest of your planning data. Unclaimed plans may be deleted after 180 days.

For each request, the server sends PostHog one server-side event with the tool used, the assistant, whether the request worked, a guest count range, and whether room dimensions were given. When it creates a shareable plan, it sends a second event with the tool, the assistant, and the plan's link. These events use an anonymous identifier that changes daily. They contain no guest names and nothing that identifies you or your account.

Nothing is sold through the integration. To have a shared plan deleted, email hello@altessa.studio with its link.

Legal bases for processing (EEA and UK users)

Where the GDPR or UK GDPR applies, we process your information on the following legal bases: to perform our contract with you (operating the Service, processing payments, authentication); to comply with legal obligations; based on your consent for analytics and advertising, including PostHog, Microsoft Clarity, the Meta Pixel, and the Meta Conversions API, which you may withdraw at any time as described under Cookies and consent; and based on our legitimate interests in securing and maintaining the Service, including error monitoring, where those interests are not overridden by your rights.

Data retention

We retain your information for as long as your account is active. When you delete your account, your data is removed from the app right away, deleted from our systems within 30 days, and deleted from backups within 90 days. Plans made through the assistant integration that nobody saves to an account may be deleted after 180 days.

Your rights

You can download a copy of your data and delete your account yourself in Settings: Download my data gives you every record you've entered, your guest list and budget as spreadsheets, and links to your uploaded files, and Delete my account permanently is in the Danger zone. Account deletion is permanent and removes your wedding planning data, files, and account record: your data is removed from the app right away, deleted from our systems within 30 days, and deleted from backups within 90 days. When you delete your account we also ask Klaviyo to delete your email profile and PostHog to delete your analytics profile. Stripe keeps its payment records, because tax law requires them. If you left a review that we approved and you agreed to share, it stays on the site under your first name and last initial, no longer linked to your account. If you joined someone else's wedding as a partner or planner, deleting your account removes your access and your own account; the wedding stays with its owner. You can also email us at hello@altessa.studio to request access to, correction of, export of, or deletion of your data, and we will respond to verified requests as required by law.

If you are a resident of California, the EEA, or the United Kingdom, you may have additional rights under applicable law, including the right to access, the right to deletion, the right to object to or restrict processing, the right to data portability, and the right to lodge a complaint with a supervisory authority. California residents have the right to know what personal information we collect and to opt out of the sale or sharing of personal information. We do not sell personal information. We share limited signup and purchase events with Meta as described in Advertising and measurement, and you can opt out on Your Privacy Choices, by selecting Decline, or with Global Privacy Control. We will not discriminate against you for exercising these rights.

Security

We use industry-standard security practices including encrypted connections (HTTPS), encrypted data at rest via Supabase, and Row-Level Security policies that restrict each user's access to their own data. No system is perfectly secure; if we become aware of a breach affecting your information we will notify you as required by law.

Children

Altessa is not intended for use by anyone under 18. We do not knowingly collect information from children. If you believe a child has provided us with information, please contact us and we will delete it.

International users

Altessa is operated from the United States. Your information is transferred to and processed in the United States.

Changes to this policy

We may update this Privacy Policy from time to time. If we make material changes we will notify you by email or by a notice in the Service before the change takes effect.

Contact

Questions about this policy can be sent to hello@altessa.studio or by mail to Altessa LLC, 680 N Lake Shore Dr, Suite 110 #3280, Chicago, IL 60611.

See also our Terms of Service and Your Privacy Choices.