Privacy
Drafted 5 October 2026. Last updated November 21, 2026.
This page says what we hold, where it sits, and who else can see it. It is written from the software itself rather than from a template, so where it is specific it is specific on purpose, and where something is not built yet it says so.
The short version
- Your guests never give us an account, a password, an email address or a phone number.
- We do not use your guests' photos, their names, or anything else from your event to train machine-learning models, and we do not hand them to anyone else to train on.
- Photos sit in a private bucket. Nothing about your event is a public web page, and the address of your guest page is a random secret that we never publish.
- The copies your guests can see have had their location data stripped out. Only you can reach an original.
- Optional first-party usage statistics help us improve the product. Separately, account holders may opt in to purchase measurement with Meta. There are no advertising pixels. Upload diagnostics help us investigate problems.
- The guest-list tester on the home page stores nothing at all.
What we hold about you, the host or the planner
Your account is an email address. That is the whole identity: there is no name field, no phone number and no postal address anywhere in it, because signing in is a link we email you or a Google sign-in, and neither needs more than that.
If you rate One Code yourself, from your own console after your event, we hold the stars you gave, the short comment if you wrote one, whether you ticked the box allowing us to quote you, and the name you chose to be quoted under. That rating is tied to your account because it is yours to change. Nothing you write there is published anywhere unless you tick that box. Customer feedback is kept separate from historical guest feedback.
If you choose to tell us how you first heard about One Code, we keep one current answer with your account. Only authorized One Code operators can view the aggregate report. This is separate from campaign statistics and does not subscribe you to marketing. You can change or remove your answer under Your events. If you skip or remove it, we keep that preference so the question stays closed. Deleting your account removes the answer and preference.
Gift settings include the recipient name, message and external links you choose to show guests. One Code does not collect or hold gift money or verify payment completion. We keep the latest 50 gift-setting changes for each event, including the acting account and previous destinations, to help investigate unauthorized changes. This private history is removed when the event is deleted.
About the event itself, we hold what you type in:
- Who is holding the event, the date, the time and the timezone.
- Your colors and fonts, and the invitation image if you upload one so we can read the palette from it.
- Venue details, parking, dress code, wifi and anything else you add to the information page.
- The program, and the menu if you use it.
- Your guest list, which is the part below.
What we hold about your guests
This is the unusual part, and it is worth being plain about: your guests do not give us their details. You do. When you import your list, we hold for each person their first name, last name, nickname and preferred display name where you have given them, which household or group they belong to, their table, and their seat.
We also build one derived value from those names: a lowercase, accent-stripped search key. That is what makes a guest typing “jose” find “José”, and “Bob” find “Robert” where you have recorded the nickname. It is not shared and it is not used for anything else.
If a guest uploads a photo or a video, we additionally hold:
- The file, and two smaller copies of it that we make.
- A fingerprint of the file, computed in their browser, so that retrying after a dropped connection does not create a duplicate.
- Its type, size and dimensions, how long a video runs, and the time the camera recorded if the file says so.
- The name they typed when they uploaded, if they typed one.
- A hash of a random token their own browser generated. The token itself stays in their browser. We store only the hash, and we use it to let them delete their own upload and to stop one device flooding the gallery. It is not an account and it does not identify a person to us.
If a guest leaves a note in the guestbook we hold the name and message they wrote, or the audio clip they recorded.
We no longer ask event guests to rate One Code. Historical guest feedback contains stars, an optional comment and a hash of a random browser token. Those records do not contain a name, email address, phone number or IP address. They remain private to the One Code team and are kept separate from customer feedback. No guest account is required to use the event page.
Who decides what happens to your guests' details
This matters more here than in most privacy policies, because the people whose details we hold are mostly not the people who signed up. So, plainly: the host decides. You chose to collect your guest list, you decided who is on it and what it says, and you decide when it is deleted. We hold it and act on your instructions. In the language of data protection law, you are the controller of your guest list and we are processing it for you.
What that means for a guest who wants something changed or removed: the host can do it immediately, and that is usually the fastest route. We can do it too, and if a guest writes to us about their own name or their own photograph we will act on it rather than sending them away. What we will not do is hand an event’s guest list to somebody because they say they are on it, because we have no way of knowing that they are.
What your guests are actually told
We would rather you knew exactly how much and how little a guest sees, because you are the one who has to answer for it at the door. A guest is never asked to create an account, never asked for an email address or a phone number. Optional usage statistics are off until they choose to allow them under Usage statistics. When they open the upload screen, one line sits on it permanently and cannot be dismissed: it names you, and it tells them that the photos they upload are shared with you and your guests, and that they can delete their own at any time. The Usage statistics control also links to this privacy notice.
Before the seat finder, which is where a guest types their name, they are told nothing at all. That is a gap we know about rather than a decision we are defending, and it is why the obligation in our terms to tell your guests about your guest list sits with you. If your guests should be told something, say it on your invitation or on your signs, where they will actually read it.
Where this sits, geographically
Everything described on this page is held with companies based in the United States, and your event’s data is processed there. If you or your guests are outside the United States, that is a transfer out of your country, and you should treat it as one. We are not going to print a list of transfer mechanisms we have not put in place. If you are buying from outside the US and this matters to you, ask us before you buy and we will tell you honestly where we stand.
Photos, and the location data inside them
A phone can write the exact spot a photo was taken into the file. That matters at an event, because a guest sharing a picture with the room is not knowingly sharing their location with it.
For a photo with a working gallery preview, we keep these separate copies:
- The original, exactly as the camera made it, location data and all. Only you and anyone you give admin access to can ever reach it. It is never handed to a guest.
- A display copy, about 1600 pixels on its longest side. This is the one guests see in the gallery.
- A thumbnail, about 480 pixels.
The display copy and thumbnail are normally made in the guest’s browser. If those previews are missing, our server can process the private original to create them. Both paths re-encode the image and exclude the original location metadata from the copies guests see. If a preview cannot be created, the upload status says so; the original can remain saved privately for the host without appearing in the gallery.
The original and any preview copies live in a private bucket that is never public. Anything shown on a page is fetched through a short-lived signed link, and the address of your guest page is itself a random 96-bit secret that we do not publish or allow search engines to index.
We do not train anything on your event
We do not use your guests’ photos, your guest list, your guests’ names, your guestbook messages, or anything else from your event to train, fine-tune, or evaluate machine-learning models. We do not sell that content, we do not license it, and we do not pass it to anybody else for them to train on.
This is not conditional on a setting you have to find and switch off. It is how the product works.
The guest-list tester on the home page
Anyone can drop a spreadsheet on the home page and see how we would read it, without an account. That file is held in memory for as long as it takes to answer, and then it is gone.
It is not written to a disk. It is not written to a database. Its contents are not logged, not emailed, not kept in a queue, and not used to train anything. We do not keep the file name, the file itself, or any of the names in it. If the parse fails we do not even log why, because an error log containing your guest list is still your guest list.
The one thing that endpoint does remember is a count of how many files have recently come from your network address, held in memory on the server for a few minutes, so that one person cannot hammer it. That count contains no part of your file and disappears on its own.
Who else processes this, and what they hold
We do not run our own servers. These are the companies that handle data on our behalf, and this list is what the code actually calls, not a generic list.
| Company | What it does for us | What it holds |
|---|---|---|
| Supabase | Our database, and the system that signs you in. | Your account email address. Your event's settings, guest list, program, menu and information page. The details we keep about each photo, but not the photo files themselves. |
| Cloudflare R2 | Where the photo and video files themselves are stored. | Uploaded originals and any smaller preview copies. The bucket is never public. |
| Vercel | Hosting. Every page and request is served from their network. | Processes application requests and, when needed, photo files to create safe gallery previews. Stores ordinary server logs, including network addresses and requested URLs, for a limited period. We do not intentionally write photo contents or guest-list contents into those logs. |
| Stripe | Takes the payment. | Your card details, which they collect on their own page. We never see or store a card number. We keep only their reference for the payment, the amount, the currency, whether it succeeded, and when. |
Sign-in emails, including the link you use to log in, are sent through Supabase. Fonts are served from our own domain rather than fetched from a third party, so simply opening a page here does not tell anyone else that you did.
Reading your column headings with an AI service
This is built and it is not switched on. When you import a guest list, we would send the column headings and a short description of the kind of values in each column, for example “whole numbers, 1 to 2 digits”, to our AI service provider, so that it can work out which column is which. The contents of your rows are never sent. This column-mapping service is disabled, so no AI provider is called for that import, and imports are read by our own rules about what headings usually mean.
One honest limit on that promise. We read the first row of your file as the headings, so if your file has no heading row and starts straight into your guests, the first guest’s details sit in the place a heading would. We check for the two shapes that matter most and refuse to send them, so an email address or a phone number in that position is never sent. A name is not something we can recognize mechanically, so a file whose first row is a person could send that one person’s name as though it were a column heading. Giving your file a heading row avoids it, and a file with no heading row usually fails the import for a different reason before this point is reached.
A related feature we considered and have not built: letting you photograph or upload a seating chart and having an AI service read the whole thing into a guest list. There is no such feature here. That would mean sending your guests’ actual details, which is a different question from sending the word at the top of a column, and we are not asking you for that.
These are our AI service provider’s terms as we verified them against their own published pages on 5 October 2026. Their commercial terms state they may not train models on customer content, so what we send would not train a model. Their stated default is that inputs and outputs are deleted within thirty days.
The figure that actually matters is different and larger, and we would rather tell you now than in a footnote later. Content that our AI service provider’s automated abuse-detection systems flag is retained by them for up to two years, and their own documentation says that retention survives even a zero-data-retention arrangement. So if something we sent happened to trip an automated classifier, it could sit with them for up to two years, and no agreement available to us would change it.
That is the reason we send headings and never rows. A column heading that has been flagged and kept for two years is the word “Table”. A guest list that has been flagged and kept for two years is your guests. We also send what we send inside the request itself rather than uploading anything to their file storage, which has no automatic expiry at all.
Optional AI program suggestions
In Program tools, hosts can explicitly request AI suggestions for a pasted program excerpt. When enabled, the AI option sends only the excerpt you choose to our AI service provider after you confirm sharing it. Remove guest lists, contact details, access codes and private notes first. We do not automatically send your saved event, guest list or photographs.
One Code does not store the raw excerpt. Suggestions stay in your tab until you approve selected titles, times and locations for your guest program. The approved fields, import receipt and event-level AI attempt budget are stored with your event. Reusable planner styles and generic checklists belong to your account; other events do not automatically receive them or inherit completed checks.
Our AI service provider processes the excerpt under its commercial data policy. Its default retention is up to 30 days, with exceptions for legal requirements and policy enforcement; flagged inputs and outputs may be kept for up to two years. Its commercial inputs and outputs are not used for training by default. We do not submit your excerpts as provider feedback. We have not arranged zero retention for this feature. Provider retention policy and training policy, checked 20 October 2026.
How long we keep things
We do not delete your photos on a timer. There is no expiry date on your event, no clock counting down after it, and nothing in this product that removes anything because time has passed. Your event stays where it is until you ask us to remove it.
When you import a guest list we keep a snapshot of that import, so that if the import went wrong you can roll it back. That snapshot contains the guest names from the file you uploaded, and it stays until the event is deleted.
The primary event owner can request permanent deletion from Your events or the event's Settings. This removes the guest list, schedule, menu, uploaded artwork, photos, videos and other event content. Export what you want to keep before confirming; deletion cannot be undone and does not request a refund.
Once accepted, the event is unavailable to guests and cleanup continues in the background. Your events shows progress and any delay. Files are removed before their content records. Uploads already in progress may require further cleanup checks. We retain limited cleanup records for repeated late-upload checks, and retain payment and necessary security records separately. Deleting an event does not delete your account.
You can download available photos and videos from your event's photos screen and export your guest list from Guest list. Contact us if you need help accessing or removing your data.
To have your event or your photos deleted, or to ask what we hold about you, email aa@onecode.events.
Usage statistics and upload diagnostics
When you allow usage statistics, we collect the screen category, approximate active foreground time, furthest scroll percentage, coarse viewport and browser-engine categories, broad traffic source, recognized campaign names after the additional campaign choice, and actions such as choosing a seat or opening a registry. A random tab-session identifier helps avoid counting every page as a different session. These are sampled browser measurements, not attendance, attention or verified people.
We do not collect typed names, search queries, keystroke content, screenshots, screen recordings, full referring URLs or photo contents for analytics. Usage observations are not joined to your guest list, ratings or account. If you choose to allow usage and campaign statistics, a recognized campaign name can also be stored with a newly created checkout and its payment record. This lets us count paid events by campaign without attaching the anonymous tab-session identifier to the payment. Only authorized One Code operators can read product usage reports. We use site and event activity to improve the service; event hosts and planners do not have access to these reports.
Upload diagnostics run when an upload is attempted, independently of the optional usage choice. They contain a random attempt identifier, processing and transfer stages, retry count, coarse file-size category, elapsed time and an allowlisted error category. Selection diagnostics also count how many files were selected, prepared and refused before queuing; they contain no filenames. They help explain interruptions without storing filenames or free-form errors. A device that closes or loses connectivity may be unable to send its last update.
Observation records are scheduled for deletion after 30 days, with a daily cleanup job. An outage can delay cleanup. Turning optional statistics off stops future usage reporting; it does not identify and remove previously collected observations. Deleting an event also removes its observation records. Our operational records and payment records have the separate retention purposes described elsewhere on this page.
Optional purchase measurement with Meta
Separately from our first-party usage statistics, account holders can allow optional purchase measurement at checkout or in Account privacy. It starts off and is never required to buy or use an event. Turning on usage statistics does not enable it.
After you opt in, eligible future purchases may be reported to Meta with the purchase amount, currency, successful-payment time, an opaque report identifier, our website address and a hashed version of your account email. Hashing lets Meta match the email to an account; it does not make the information anonymous. Meta may use it for advertising measurement and personalization under its Business Tools terms. Meta states that it may retain event data for up to two years.
We do not send guest lists, guest names, event titles, invitations, programs, menus, photos or videos through this measurement. There is no advertising pixel, browser fingerprint or advertising cookie in this integration. Past purchases are not enrolled when you turn it on.
Turning the choice off cancels unsent reports and stops reports for future checkouts. A report already being sent may finish, and reports already delivered cannot be recalled through this control. Browser Do Not Track and Global Privacy Control signals keep optional reporting off when we receive them. Your event remains available if reporting fails. If we cannot save a browser opt-out, we ask you to retry checkout before reusing any previously consented payment link.
Cookies and what is kept in your browser
If you have an account, signing in sets a cookie that keeps you signed in. That is a working part of the site and there is no version of it that is optional.
Guest browsers store a random upload token to recognize their own photos. Older browsers may retain a cookie from the retired guest feedback feature; it is no longer issued or used to collect ratings. Upload identifiers are not used to join historical ratings to uploads or to a guest name.
There are no advertising cookies or third-party browser tracking scripts. Separately opted-in purchase reporting to Meta is described above. Your optional usage choice is stored in localStorage; allowing it creates a random session identifier in sessionStorage for that tab. Campaign measurement additionally requires the current explicit usage-and-campaign choice. Existing usage-only choices do not enable it automatically. The current choice lets us keep recognized campaign and commercial names in localStorage for up to 24 hours across tabs in this browser. Older tab-only campaign choices remain tab-only until you choose to allow the updated statistics. Turn it off under Usage statistics at the bottom of the page. Turning it off clears the campaign stored for this browser and the current tab and stops sending it with future checkout requests; it does not rewrite an already-created checkout or erase records already sent. Campaign names recorded with a checkout remain with those checkout/payment records. No browser session identifier, advertising click identifier or raw URL is sent to Stripe for this measurement. Browser Do Not Track and Global Privacy Control signals keep optional collection off.
Network addresses
Some security controls use hashed network addresses alongside device limits, with larger budgets for shared venue networks. The guest-list tester also uses a short-lived in-memory network counter. Raw network addresses are not stored in our usage observations. Hosting providers may process network addresses in their request logs.
Children
This is not a service children sign up for, and we ask that nobody under 18 creates an account. Being accurate about that rather than firm: it is a term of use, not a check. We do not ask your age, we have no age field and we do not verify anybody’s age, because signing in is a link we email you and that is all we collect. If you tell us an account belongs to a child we will close it.
Children are photographed at events, and that is the part worth being careful about. A photo of a child uploaded by a guest is treated exactly like every other upload: it goes to a private bucket, the location is stripped out of every copy anybody can see, it is never on a public web page, and it is reachable only by someone holding your event’s secret link. The host can hide it from the gallery, the guest who uploaded it can delete it outright, and if you ask us to remove a specific photograph we will remove it. We are precise about that difference on purpose: hiding is not deleting. Authorized hosts can delete a photo from Photos, and you can also contact us about removal.
We do not knowingly build any profile of a child, we do not use a face in a photograph to identify anybody, and nothing about any guest, child or adult, is used to train a model. If you are a parent and a photograph of your child is in an event gallery, the quickest route is the host, because it is their event and they can take it down in seconds. Ours works too.
If this page changes
If we change what we do with your event in a way that matters, we will change this page and the date at the top of it. We are not going to quietly start training on your photos and update a clause.
See also our terms and our refund policy.