Legal
Privacy Policy
Last updated: 17 November 2026
Who we are
RealTime.Photos is a live event photo sharing platform operated by Nanjing Zhiyin Trading Co., Ltd., reachable at hello@realtime.photos.
This policy explains how we process personal data in two distinct contexts: (1) data we collect about event owners, the event organisers, agencies, companies and photographers who hold an account with us, and (2) data processed on behalf of event owners about their event guests. For guest data, the event owner is the data controller and RealTime.Photos acts as its data processor — a relationship governed by our Data Processing Agreement.
The short version
Guests don't need an account. We never ask guests for a name, email, or login. Selfies taken to find photos are used for that one search and never stored. Faces in event photos are processed on the event owner's behalf, as described in Face recognition below, and deleted with the event.
Event owner accounts require only your name and email address to operate. We store the minimum needed to run your account and manage your events.
All event data is automatically deleted. On standard plans, photos, face data, and event records are purged within a fixed window of your event's first photo (see Data retention below). Custom plans and Custom events follow the retention terms agreed with us instead. In every case, biometric face data is deleted no later than 12 months after the first photo is uploaded, regardless of plan.
We do not sell your data. We never sell, rent, or share personal data with third parties for advertising or marketing purposes.
Data we collect
Event owner accounts. When you create an account or sign in, we collect your name and email address via our authentication provider (Clerk). We use this to identify your account, send transactional communications (such as payment receipts and data deletion warnings), send occasional emails about new features in the service you use, and manage your events. You can unsubscribe from those emails with the link in each one.
Event guests. Guests browse galleries without an account, email, or login, and we never ask them for identifying details. Like counts are stored against photo IDs with no user identifier attached. Sort preferences, liked photo IDs and, after a selfie search, a reference to the face groups it found (with a signed token that proves it, valid for up to 30 days) stay in your browser's storage, so you can reopen your photos without a new selfie. The selfie itself is never stored. Faces that appear in event photos are processed on the event owner's behalf, as described in Face recognition below.
Demo and contact requests. If you submit a demo request or contact form, we collect your name and email address to respond to your inquiry, processed via Formspree.
Website analytics. We use Vercel Analytics and Vercel Speed Insights, cookieless tools that collect no personally identifiable information, to understand general traffic patterns (such as pages visited) and page performance.
Lawful basis for processing
Under the GDPR and equivalent applicable law, we rely on the following lawful bases for processing event owner account data:
- Contract performance (Article 6(1)(b)): Processing your name and email to operate your account, send transactional emails (receipts, deletion warnings), and provide the service you signed up for.
- Legitimate interest (Article 6(1)(f)): Cookieless website analytics to understand and improve the platform; occasional emails about new features and changes to the service you use, sent to account holders only, with an unsubscribe link in every one; responding to demo and contact requests; keeping a short record of deleted events to handle support and billing questions and to limit free trials to one per account; displaying customer names and logos in marketing materials (subject to opt-out — see our Terms of Service, Marketing Use section).
- Legal obligation (Article 6(1)(c)): Retaining financial and billing records as required by applicable tax and accounting law (typically 7 years in Spain).
Providing your name and email address is a contractual requirement to create and use an event owner account — without it, we cannot provide the service. You are under no statutory obligation to provide this data.
For the processing of guest personal data (including biometric face data), the event owner is the data controller and is responsible for establishing a lawful basis for each purpose it switches on (face recognition, Social connections, Audience expressions), including an Article 9(2) basis for biometric special-category data. This is set out in our Data Processing Agreement.
Face recognition
RealTime.Photos uses Amazon Rekognition (operated by Amazon Web Services) to detect and match faces in event photos. Because this involves biometric data — a special category under GDPR Article 9 — we are fully transparent about how it works:
- When a photo is uploaded, faces are detected. Faces that are too small or low quality are automatically ignored.
- Similar face identifiers are grouped into clusters. Each cluster has a representative image crop — a small region of a photo showing the face. Clusters carry no names or identities.
- When a guest takes a selfie to find their photos, the image is sent securely to the face recognition service for matching. The selfie is discarded immediately after the result is returned — it is never stored in any database, file system, or log.
- Numerical face representations (embeddings) used for matching are stored in a per-event index and deleted permanently when the event data is purged.
Face clusters are used to help guests find photos of themselves, to produce anonymous event statistics and, with the guest's consent, to show who they appeared with. They are never used to find out who someone is, for surveillance, or for any purpose beyond the event.
Event statistics and Audience expressions. During photo processing, Rekognition also returns per-face quality signals (sharpness, head angle), which are kept with each detected face to power the event owner's clean-up tools. On Trial and Custom events with face recognition on, it also returns whether each face is smiling, for the event's smile rate. Only on events with Audience expressions on does it also return estimates of age range, gender and facial expression; on every other event these are never requested. If a purpose is switched off, collection stops from the next photo, and what was already collected is kept, hidden from the event owner, until the event is deleted. The raw per-face estimates are folded into running counts for each face cluster, usually within minutes of face recognition finishing, and then permanently deleted, within 48 hours at the latest. Each cluster keeps a summary of those counts (smile rate and, with Audience expressions, estimated gender, average age and expression averages) until the event is deleted. These summaries power the anonymous event totals the event owner sees (people detected, the Networking index, the smile rate and, with Audience expressions, the age, gender and expression distributions) and the guest's own recap. They are never shown to other guests. As Amazon's own documentation puts it, this output is a reading of how a face appears in a photo, not a determination of anyone's internal emotional state.
Consent per purpose. Guest consent is set separately for each purpose the event owner switches on. For each one, the event owner chooses where it is asked: in the gallery, or before the event, for example at registration. "Asked before the event" may be chosen only if every guest agreed; where anyone did not, the event owner must choose "Asked in the gallery" or switch the purpose off. We never assume consent. RealTime.Photos provides ready-to-use consent wording in the dashboard, with one checkbox for each purpose asked before the event, covering the purpose, the retention period and the right to request deletion at realtime.photos/forget-me.
Face recognition (Find my photos). Asked in the gallery, on a consent screen before the selfie, or before the event. Where it is asked before the event, guests use face search in the gallery without a prompt. Face indexing runs when photos are uploaded so that results are ready the moment a guest searches. Guests who decline, or who never use the selfie search, are never shown face-matched results. On Trial and Custom events, face recognition also produces anonymous event totals for the event owner, at every event type, including staff events and graduations: people detected, the Networking index (the average number of people each person appeared with) and the smile rate. Every detected face counts towards these totals, whether or not that guest used face search, and the totals name no one. Where photos record when they were taken, the event owner also sees the smile rate by time of day, in fixed slots of 15 to 60 minutes. A slot with fewer than five people, or where one person makes up more than a third of the faces, shows no figures.
Social connections. Called Networking insights at business events and events for the host's own staff. With their own consent, a guest sees in their recap how many people they appeared with and connected with, and the faces of the people they connected with who also agreed. Their own face appears in the recaps of people they appeared with, on the event's connection map and among top connectors. It reads no expressions, so it is available at every event type, including staff events and graduations. It is asked on the recap card after the selfie, with a tick box, or before the event, but only where face recognition was also asked before the event.
Audience expressions. Expression analysis, estimated age and gender, and the guest's own smile line in their recap. Asked before the event only, never in the gallery: it is read when each photo is uploaded, so there is no later moment to ask. It is never available at events for the host's own staff, such as company parties, incentives and kick-offs, or at graduations, whatever anyone consents to (EU AI Act, Article 5(1)(f)). Where photos record when they were taken, the event owner also sees expressions by time of day, under the same slot rule as the smile rate.
A guest's face is shown to other people only for a purpose that covers them: in the gallery's face row under face recognition, and on the connection map and in other guests' recaps under Social connections. Guests who never use face search are never shown face-matched results.
Leaving a purpose. A guest who has matched their face can leave each purpose in one tap on the card shown after their selfie. "Remove me from the connection map" takes them out of Social connections: their recap line, the connection map, top connectors and other guests' recaps. It also takes them out of Stars of the show, the most-photographed faces shown to the event owner. "Leave out my expressions" takes them out of the event's expression, age and gender statistics and their own smile line. They can also remove all of their face data at realtime.photos/forget-me. Per-cluster summaries, including those kept by time of day, are deleted with the event data at the end of the retention period.
Returning guests. After a selfie, the guest's phone remembers, in its own storage and never on our servers, which face groups the search found and a signed token that proves it, for up to 30 days. When the guest comes back, the gallery asks "Is this still you?". Yes reopens their photos without a new selfie, so no new face is read. No asks for consent and a selfie again.
Minors. Events may include attendees who are below the age at which they can give consent on their own (14 in Spain under Article 7 of the LOPDGDD, or the age set by local law elsewhere). Wherever each consent is asked, the event owner, as data controller, is responsible for obtaining consent from a parent or guardian for those attendees. RealTime.Photos cannot know a person's age before face recognition runs, so it cannot check this itself. On the face recognition consent screen in the gallery, guests confirm that they are 14 or older or have a parent's or guardian's permission.
Event owners (as data controllers) are responsible for obtaining any required consent or other lawful basis from event attendees for the processing of their biometric data, as required by GDPR Article 9(2) or equivalent applicable law.
Text recognition
On events whose plan includes it, Rekognition also reads the text that appears in photos, such as a sponsor's name or a race number. The event owner picks keywords from that text so guests can find photos by them, and sees how often each keyword appears. The detected text is stored with the event and deleted with it. When a guest searches by keyword we count the searches for each keyword, and we never store what the guest typed.
Third-party services
We work with a small number of trusted service providers to operate the platform. Each processes only the data necessary for their specific role. We do not share personal data with third parties for advertising or marketing purposes.
International transfers
Event photos and face recognition run on AWS in Spain, and our database runs on Convex in Ireland. Clerk, Convex, AWS, Vercel, Resend, and Formspree are US companies, and some processing, such as authentication, hosting, and email delivery, takes place in the United States. Dodo Payments, our merchant of record for event purchases, processes payment data as an independent controller under its own privacy policy, which relies on the EU Standard Contractual Clauses for transfers outside the EEA. Where personal data of individuals in the EEA or UK is transferred outside those regions, we protect the transfer using one or more of the following mechanisms:
- Standard Contractual Clauses (SCCs) — EU Commission Decision 2021/914 for EEA-origin transfers; the UK International Data Transfer Addendum to the EU SCCs, issued by the ICO, for UK-origin transfers — incorporated into our agreements with each provider.
- EU-US Data Privacy Framework (DPF) certification, where the provider is currently certified under the framework, which may supplement or substitute the SCCs.
You may request details of the transfer mechanism applicable to any specific provider by contacting us at hello@realtime.photos.
Data retention
Raw per-face biometric attributes (age range, gender, smile, facial expression signals) captured during photo processing are permanently deleted within 48 hours of the last photo upload, and in practice within minutes of face recognition finishing for that upload. They are first folded into a summary for each face cluster (smile rate and, with Audience expressions, estimated gender, average age and expression averages), which is kept until the event is deleted; the 48 hours is an outer limit, not a waiting period. The individual per-photo estimates cannot be reconstructed from the summary.
Returning-guest reference (which face groups a guest's selfie search found, and the signed token that proves it) is kept only on the guest's phone and removed after 29 days, or sooner when the guest clears their browser storage. We hold no copy.
Event data (uploaded photos, face recognition data, and associated records) on Trial, Basic and Pro plans is automatically and permanently deleted within a fixed number of days after the event's first photo was uploaded — between 7 and 60 days, depending on the plan. Events on the legacy Large plan are deleted after 90 days.
Contract-based retention (Custom plans and Custom events). Events on our Custom tier, including every event created under a Custom plan, are not on this automatic day-count schedule. Events on a Custom plan are kept for the plan's term and deleted automatically 30 days after it ends. A Custom event outside a plan is kept for the period agreed with us, and we set its deletion date accordingly. Event owners with a Custom-tier event can request the applicable retention date by contacting us.
Regardless of plan, face recognition biometric data (face embeddings stored in AWS Rekognition) is always purged no later than 12 months after the first photo was added, to limit long-term biometric data storage. Photos and face avatar filters remain fully accessible after biometric data is purged; only selfie-based photo search is affected.
Event owner account data (name and email) is retained for the duration of your account. You can delete your account at any time from your account settings; your account profile and events are then deleted straight away. Records we must keep by law, such as payment records, are retained as described below.
Deleted event records. When you delete an event, or it reaches its deletion date, we delete its photos, face data and everything guests could see. We keep a short record of the event itself: its name, plan and event type, when it was created, paid for and deleted, how many photos it held, and whether you, we or the retention schedule deleted it. It contains no photos and no guest data. We use it to answer support and billing questions about past events and to make sure each account gets one free trial. These records are deleted when you delete your account.
Payment records are retained for the period required by applicable tax and financial reporting law — typically 7 years in Spain — after which they are permanently deleted.
Demo and contact requests are retained for up to 12 months or until the inquiry is resolved, whichever comes first.
Anonymised engagement statistics (gallery page views, interaction counts, upload activity) collected via the analytics system contain no personal data and are not deleted when an event is deleted. They are retained indefinitely as aggregate product analytics and cannot be attributed to any individual.
Your rights
Event guests. Even without an account, you have rights over your biometric data. To request removal of your face data from all active events, use our self-service data removal tool. We search every event that uses face recognition for your face and delete the matching face data we find, usually within a minute. Your photos stay in the gallery; only the face data used to find you is removed. Because we never know who you are, we cannot recognise you in photos uploaded later, so you can use the tool again at any time. You may also email hello@realtime.photos with the event name and date. Where an event has Social connections or Audience expressions, you can leave each one in one tap on the card shown after your selfie, without contacting anyone: "Remove me from the connection map" or "Leave out my expressions". Where an event's anonymous totals have already been calculated, your individual contribution to them (people detected, the Networking index, the smile rate and, with Audience expressions, the age, gender and expression distributions) cannot be reversed; the totals contain no personal identifiers and are not personal data under GDPR.
If you are an event owner with an account, you have the following rights over your personal data:
- Access (Article 15): Request a copy of the personal data we hold about you.
- Rectification (Article 16): Request correction of inaccurate or incomplete data.
- Erasure (Article 17): Request deletion of your personal data, subject to our obligations to retain certain records under applicable law.
- Restriction (Article 18): Request that we limit how we process your data while a dispute is resolved.
- Portability (Article 20): Request your personal data in a structured, machine-readable format so you can transfer it to another service.
- Objection (Article 21): Object to processing based on our legitimate interests. We will stop unless we have compelling grounds that override your interests.
- Withdraw consent: Where processing relies on your consent, withdraw it at any time. Withdrawal does not affect the lawfulness of processing before withdrawal.
To exercise any of these rights, email us at hello@realtime.photos. We will respond within one month of receiving your request and may ask you to verify your identity before processing. For complex or numerous requests, we may extend this period by up to two further months; if so, we will notify you of the extension within the first month.
Right to complain. You have the right to lodge a complaint with a data protection supervisory authority, in particular in the EU member state where you live or work, or where you believe an infringement took place. In Spain, this is the Agencia Española de Protección de Datos (AEPD), reachable at www.aepd.es. UK residents may complain to the Information Commissioner's Office (ICO) at ico.org.uk.
US privacy rights
If you are a resident of California, Virginia, Colorado, Connecticut, or Utah, you have additional rights under applicable state privacy law (CCPA, VCDPA, CPA, CTDPA, and UCPA respectively):
- Right to know what personal information we collect, use, disclose, and sell.
- Right to request deletion of your personal information, subject to certain exceptions.
- Right to correct inaccurate personal information (California, Virginia, Colorado, Connecticut).
- Right to data portability — to receive a copy of your personal information in a portable, usable format.
- Right to opt out of the sale or sharing of personal information and of targeted advertising. We do not sell or share personal information for these purposes — this right is preserved but not currently applicable.
- Right to non-discrimination — we will not deny, degrade, or charge differently for our services because you exercised a privacy right.
To exercise any of these rights, email hello@realtime.photos. We will respond within 45 days (extendable by a further 45 days where reasonably necessary, with notice to you). We will not charge a fee unless requests are excessive or repetitive.
Event guests and attendees
If your photo appears in an event gallery on RealTime.Photos, the business or person that runs that event on our platform (the event owner) is the data controller for your personal data (your image). That is usually the event organiser, or an agency or photographer working for them. RealTime.Photos processes that data only on the event owner's behalf, as set out in our Data Processing Agreement.
To exercise your rights over photos of yourself, including requesting removal, contact the event owner. If you're not sure who that is, or can't reach them, write to us at hello@realtime.photos and we'll pass your request on.
Gallery browsing is anonymous: no name, email, account, or tracking identifier is collected or stored when guests browse a gallery. After a selfie search, your phone may keep a reference to it, as described in Data we collect; we hold no copy. Faces in event photos are processed on the event owner's behalf, as described in Face recognition above.
Automated decision-making
We do not carry out automated decision-making within the meaning of GDPR Article 22 — that is, decisions based solely on automated processing that produce legal effects or similarly significant effects on you.
Face clustering is an automated process, but it produces only a navigational aid (grouping photos by apparent visual similarity) and, for guests who agree, a count of the people they appeared with. It has no legal, financial, or otherwise significant effect on any individual. Event owners review and manage face clusters manually.
Event owner responsibilities
Event owners using RealTime.Photos are responsible for ensuring they have the necessary legal basis to photograph and publish images of event attendees, and that attendees have been informed of face recognition and of each other purpose switched on (a connection map, expression analysis). The print-ready QR card names the ones that are on. By creating an event, you confirm this, consistent with applicable laws in your jurisdiction.
If you invite collaborators to upload or manage an event, they act on your behalf, and you remain responsible for the event.
If a guest requests removal of photos showing them, event owners can hide individual photos from the gallery at any time from the dashboard. Hiding removes a photo from the gallery; to have the file itself deleted, contact us. Event owners who receive formal data subject requests from guests should notify us at hello@realtime.photos so we can provide any necessary technical assistance.
Changes to this policy
We may update this policy as the product evolves. Material changes will be notified to event owner account holders by email at least 14 days before they take effect. The current version is always available at realtime.photos/privacy. Continued use of the platform after the effective date constitutes acceptance of the updated policy.
Contact
For any privacy-related enquiries, to exercise your rights, or to request further information about our data practices, contact us at hello@realtime.photos. RealTime.Photos is operated by Nanjing Zhiyin Trading Co., Ltd.
EU Representative (Article 27 GDPR). For the purposes of Article 27 of the GDPR, our representative in the European Union is Pablo Martín Larriu, reachable at hello@realtime.photos, located in Irún, Gipuzkoa, España, 20304.