Privacy
This is a plain-language description of what Attind stores, why, and who else touches it. It covers both hosts, who have an account, and guests, who usually do not.
What we collect from hosts
A host account holds a name, an email address and an authentication credential, plus whatever the host chooses to put into an occasion: its title and date, the invitation content, a cover image, the guest list, seating, registry items, checklist tasks and the timeline. We do not ask for anything the planning itself does not need, and there is no profiling of hosts for advertising.
Signing in with Google, Facebook, Apple or Microsoft
If you sign in with one of these providers, we receive your name, your email address and, where the provider has one, your profile picture, and we use them only to create your account, sign you in and address you in the app. The provider also issues sign-in tokens, which we store with your account and do not use to read your contacts, calendar, files or anything else. If you ask Apple to hide your email, we only ever see the relay address it gives us. We never post on your behalf, and nothing received from a provider is sold, shared for advertising or used to train AI models. Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. You can revoke Attind's access at any time in your provider's account settings.
What we collect from guests
Guests do not need an account. When a guest opens an invitation and responds, we store the answer the host asked for: attendance, the names in the party, dietary requirements if the host enabled them, a message, and a contact address where one was given. That information belongs to the host's occasion. A guest can edit their own response using the same link, and can ask the host, or us, to have it removed.
Cookies and measurement
We set a session cookie so a signed-in host stays signed in, and a language cookie so the app keeps opening in the language you chose. Neither is used for advertising. We measure page views and real page-speed data at an aggregate level to find slow pages, and that measurement does not build a profile of an individual visitor across other websites. We also count how the product is used, such as which onboarding steps are finished and when invitations go out, using PostHog in the EU. That measurement sets no cookie, never receives names, email addresses or guest answers, and connects events to an account only through its internal id.
Who else processes the data
Attind is hosted on Vercel and stores its data in a managed Postgres database. Transactional email, such as an RSVP confirmation or a reminder, is sent through Resend. If a host turns on guest payments, the payment itself is handled by Stripe and card details never reach Attind. Each of these providers processes the data only to deliver the part of the service it is responsible for. Counts of how the product is used go to PostHog, hosted in the EU.
Keeping and deleting
An occasion and everything attached to it lives for as long as the host keeps it. To delete an occasion or your whole account, including any sign-in linked from Google, Facebook, Apple or Microsoft, write to us through the contact page from the email address on the account and say what you want deleted. Deleting an occasion deletes its guests, responses, seating and registry with it. Deleting an account also deletes the occasions it owns and the data received from the sign-in provider. We confirm when it is done, normally within 30 days. Demo occasions created to try the product out are disposable by design.
This page describes how the product actually behaves. It is a summary for hosts and guests, not a substitute for the full terms.