The short version
- Your selfie never leaves your phone. It is matched on your device and is not uploaded or stored.
- Photos stay in the photographer's Google Drive. Fozo does not copy them to its servers.
- Face data is used for one thing only: showing people their own photos from one event. We never sell it, rent it or use it for advertising.
- Face data is deleted when the event is deleted, and in any case 12 months after the event is published.
- You can ask us at any time to see, correct or delete your data.
1. Who we are
Fozo ("Fozo", "we", "us") is a web service at fozo.pics that helps photographers share event photos so that each guest can find the photos they appear in. Fozo is operated by [Legal name of the business], [registered address, India].
2. Our role
- Photographers and their events. The photographer (or studio) who creates an event decides which photos are used and who may see them. For the event photos and the face data created from them, the photographer is the controller (GDPR) or Data Fiduciary (India's DPDP Act), and Fozo is the processor that acts on their instructions.
- Accounts, access requests and payments. For Google sign-in details, access requests, billing and our website, Fozo is the controller / Data Fiduciary.
3. Data we process
| Data | Whose | Why | Legal basis (GDPR) | How long |
|---|---|---|---|---|
| Google account name, email, profile picture and user ID | Photographers, admins, guests | Sign-in; showing the photographer who asked for access | Contract (Art. 6(1)(b)) | Until you delete your account or the event is deleted |
| Access requests and approvals (status, dates) | Guests | Letting the photographer approve or remove access | Contract; legitimate interest of the photographer | Until the event is deleted |
| Event details and branding (event title, studio name, logo, phone, email, WhatsApp, Instagram, website) | Photographers | Shown publicly on the event's share page | Contract | Until the event is deleted |
| Face descriptors (lists of 128 numbers describing a face) and small face thumbnails | People who appear in event photos | Grouping faces and showing each guest their own photos | Explicit consent (Art. 9(2)(a)), obtained by the photographer | Event deletion or 12 months after publishing, whichever comes first |
| Photo list (file names and Google Drive file IDs) | Photographers | Loading previews and downloads from Google Drive | Contract | Same as face data |
| Guest selfie | Guests | Finding your photos | Explicit consent | Not stored. Processed on your device and discarded |
| Google Drive access token | Photographers | Reading your chosen Drive folder | Contract | Kept only in your browser's memory; never sent to our database |
| Billing details (name, email, country, plan, transaction ID) | Paying photographers | Subscriptions, invoices and tax | Contract; legal obligation | As long as tax law requires (usually 8 years in India) |
| Technical logs (IP address, browser, time) | All visitors | Security and keeping the service running | Legitimate interest | Kept by our hosting providers for up to 30–90 days |
We do not use face data to identify people by name, we do not match faces across different events, and we do not build profiles or show advertising.
4. Biometric data policy
This section is our written public policy for biometric identifiers and biometric information. It is written to meet Illinois' Biometric Information Privacy Act (BIPA), Texas and Washington biometric laws, GDPR Article 9 and India's DPDP Act.
- What we collect: face descriptors and small face thumbnails created from event photos chosen by the photographer, and, on the guest's own device only, a face descriptor from the guest's selfie.
- Purpose: only to group the faces in one event and show each person the photos they appear in.
- Consent first: no face matching runs until the photographer confirms they have consent from the people photographed, and the guest gives explicit consent before using a selfie.
- Retention and destruction schedule: we permanently destroy an event's face data at the earliest of:
- the photographer deleting the event
- 12 months after the event is published
- a valid deletion request from the person
- No sale: we never sell, lease, trade or otherwise profit from biometric data.
- No disclosure except to our infrastructure provider (Google Cloud / Firebase) to store it, or where required by law or a valid court order.
- Protection: biometric data is stored encrypted at rest and in transit. Only the event's admins and the guests they approve can read it.
5. Consent and photographers' responsibilities
Before scanning photos, photographers must confirm that they have the right to use the photos and that they have told the people photographed, and obtained their consent where required, that face matching will be used to deliver photos. Before taking a selfie, guests must tick a consent box.
You can withdraw consent at any time by contacting the photographer or us (see section 12). We will then delete your face group from the event. Withdrawing consent does not affect processing that happened before.
6. Service providers and international transfers
- Google Firebase / Google Cloud (Authentication, Firestore database, Hosting): stores account data, access requests and published face data.
- Google Drive: the photographer's own storage. Photos are loaded directly from Google.
- Dodo Payments: our Merchant of Record for payments. Dodo is the seller of record, processes your card or UPI details and handles sales tax, VAT and GST. We never see full card numbers. Dodo's own privacy policy applies to payment data.
- Content delivery networks (Google Fonts, gstatic.com, jsDelivr) deliver code and fonts and see your IP address when your browser loads them.
These providers may process data outside your country, including in the United States. For transfers from the EU, UK or Switzerland we rely on the provider's Standard Contractual Clauses and, where applicable, the EU–US Data Privacy Framework. Transfers from India are made as allowed under the DPDP Act.
We do not sell or "share" personal information for cross-context behavioural advertising, as defined by the California Consumer Privacy Act (CCPA/CPRA).
7. Cookies and local storage
Fozo uses no advertising or tracking cookies. Your browser stores only what is strictly needed:
- your sign-in session (Firebase Authentication)
- small preferences such as your currency choice and consent answers
Because these are strictly necessary, no cookie banner is required. If we add analytics later, we will use a privacy-friendly tool without cookies, or ask for consent first.
8. Your rights
Depending on where you live, you can:
- Everyone: ask for access to, a copy of, correction of, or deletion of your data; withdraw consent; and ask us to remove your face from an event.
- EU, UK and EEA (GDPR): also restriction, data portability, objection, and the right to complain to your data protection authority.
- India (DPDP Act 2023): a summary of the data processed and who it was shared with; correction, completion, updating and erasure; grievance redressal; nominating someone to exercise your rights; and the right to complain to the Data Protection Board of India once you have used our grievance process.
- California and other US states: to know, delete and correct; to limit the use of sensitive personal information (we already use it only to provide the service); and not to be discriminated against for using these rights.
Email us (section 12) from the Google account you used with Fozo. We reply within 30 days and may need to confirm it's you. Requests about an event's photos may be passed to the photographer, who controls that event.
9. Children
Fozo accounts are for people aged 18 and over. Guests under 18 should use Fozo with a parent or guardian. For events with children (for example schools and birthday parties), the photographer must obtain verifiable consent from a parent or guardian before using face matching, as required by the DPDP Act, GDPR and COPPA. If you believe a child's data was processed without that consent, contact us and we will delete it.
10. Security and breaches
Data is encrypted in transit (HTTPS) and at rest. Database rules allow only an event's admins and the guests they approve to read its face data. If a personal data breach happens, we will notify the affected people and authorities as the law requires, including the Data Protection Board of India and the relevant EU authority within 72 hours where needed.
11. Changes
If we change this policy in a way that matters, we will update the date at the top and tell signed-in photographers before the change takes effect.
12. Contact and grievance officer
Privacy questions, data requests and complaints:
Grievance Officer / Privacy contact: [Name], [Legal name of the business], [address]
Email: sanatharayash@gmail.com
EU/UK visitors: if required under GDPR Article 27, our EU representative will be listed here.