Effective September 1, 2026. This is a first-pass policy covering how Fondra is actually built today — have it reviewed by counsel before relying on it for a live launch.
Fondra is built for hosts running events, weddings, parties, reunions, who want their guests' photos and videos without running their own upload infrastructure. When a host creates an event, the host is the data controller for the media guests upload to that event: the host decides what the event is for, who can join, and what happens to the media afterward. Fondra acts only as a data processor, relaying uploads on the host's instructions into storage the host controls. If you're a guest, your relationship for that media is with the host, not with Fondra.
Guest-uploaded photos and videos go directly from the guest's browser into the host's own Google Drive — our server hands the browser a direct upload link and never receives the file's bytes at all, not even in memory. We do not keep a copy anywhere.
What we do store, in our own database:
Sign-in is handled by Firebase Authentication (Google). We support signing in with a Google account or with a passwordless email link. We don't receive or store your Google password in either case.
We use Firebase Analytics (built on Google Analytics) to understand how the site is used, e.g. which pages get visited and roughly how many people sign up. This uses cookies and similar identifiers in your browser. It is not used to profile guests uploading to a specific event. Analytics cookies only run if you accept them in the cookie banner shown on your first visit — see "Cookies" below.
Today, Fondra collects the basic usage data already described on this page — account data, event metadata, upload records, and Analytics cookies if you accept them — for one real purpose: to operate and improve the service. That's it.
In the future, we may explore using this data to personalize your experience, and may explore advertising to help support the free tier. Neither of these is happening today. If we ever introduce targeted advertising specifically, that will require its own real, separate, explicit opt-in — the same kind of active consent already used for Analytics cookies (see "Cookies" below) — not something this policy grants in advance.
We also maintain internal records of account-level usage for registered Fondra host accounts — specifically: signup date, your Party Points balance and purchase history, how many events your account has created, when you last signed in, and which core features (event creation, buying points, etc.) your account has used. This exists for the same purpose as the rest of this section — operating and improving the service — scoped to your own account only. It never includes anything about guests on someone else's event; that data relationship stays between the host and their guests, per "Who does what with your data" above.
We don't sell personal data, and we don't share it with anyone else beyond what's needed to run the service described above.
Account and event metadata is kept while your account or event is active. If you delete your account, we delete the account and event records tied to it, other than what we're required to retain for tax or legal reasons. Media itself lives in the host's Drive under the host's own retention choices, not ours, since we never held a copy.
You can ask to see, correct, or delete the account data we hold about you. For media you uploaded to someone else's event, that request goes to the host, since they control that Drive folder — we can help you identify who to contact.
Fondra isn't directed at children under 13, and we don't knowingly collect account data from them. Event hosts are responsible for getting appropriate consent before inviting minors to upload to an event.
If this policy changes materially, we'll update the date above and, where required, let account holders know directly.
Questions about this policy, or a data request: [email protected].