Privacy
The short, human version.
Fetti needs enough information to run an invitation, coordinate guests, and keep an event’s shared memories available. This page explains the main categories in plain language so a host or guest can understand the product before signing in or uploading anything.
What Fetti stores
Depending on how you use the service, this can include account and profile details, event settings, RSVP and guest records, comments, poll answers, subscriber requests, and photos or videos that hosts or guests upload. Event data is stored in Fetti’s hosted database, and uploaded media is stored in the service’s storage layer. A host controls whether an event is discoverable and open to public discovery.
Browser preferences and sign-in
Your browser may keep non-critical preferences such as guest-preview mode, followed hosts, and local event drafts in local storage. Sign-in uses a magic link or a configured one-time code flow. Treat every code as private: Fetti support will never ask you to forward one.
Analytics and choices
Product analytics may receive broad usage events and technical context so Fetti can understand reliability and feature adoption. Analytics should not contain magic-link codes, private credentials, or the contents of user-generated messages. Public pages can be read without an account; account and host controls require sign-in.
Account deletion and questions
When signed in, open Account to manage your profile or request account deletion. Deleting an account removes the account and events it owns; a comment or RSVP left on another host’s event may remain without a link to the deleted account. For a privacy request or a question about a specific event, email hello@fetti.me and include the relevant URL. This plain-language page is a summary, not a substitute for a legal notice required in your jurisdiction.