Skip to content

Privacy Policy

What we collect, why, and how long we keep it.

Template — lawyer review required

This is a starter draft, not legal advice. Have a qualified lawyer review this — especially the biometric-data and privacy sections — before public launch, and replace every [PLACEHOLDER] with your real business details.

1. What we collect

To run a scan you sign in with Google. Through our sign-in provider, Supabase, we receive your email address and the basic profile details Google shares at sign-in (such as your name and profile picture). For each scan we collect the two photos you upload (one front-facing, one side profile) and the face points placed on them, automatically or by you. We never collect your date of birth: the age question is checked in your browser, and only a yes/no flag is kept there. When you use the site, our providers also keep standard technical records, such as your IP address, browser type and the time of each request: Supabase for your sign-in sessions, and Railway and Vercel in their server logs. Our server’s logs may record your account ID with a scan, but never your photos.

2. How we use it

We use your photos to produce your facial analysis (measuring proportions, and producing the scores, observations and cosmetic guidance on your results page), to produce features you ask for, such as hairstyle suggestions, and to show them back to you with your results. We use your email address to run your account and, only if you opt in, to send you updates. We use your data for nothing else, and we do not sell it.

3. How long we keep it

Each scan’s two photos are saved automatically in a private storage bucket tied to your account. They are never made public, and they are shown only to you, through links that expire after two minutes. The face points placed on them are saved with them. Your scan result is saved with your account too: the scores, the measurements taken from your face, the skin and grooming observations, the written analysis, your action plan and your checklist progress. We keep all of this until it is deleted, by you or at your request (see section 6); nothing expires automatically. Deleting a scan’s photos (or all of your photos) removes the files and the face points taken from them; the results, scores, measurements and hairstyle suggestions stay. We do not use your photos to train or improve any model.

If you request hairstyle suggestions, we also save the face-shape assessment from your front photo and the suggested hairstyles with that scan, so you can reopen them even after its photos are deleted. To enforce generation limits, we keep per-scan counts of generation attempts, including failed attempts. These counts stay with the scan when its photos are deleted. We also keep timestamped attempt records linked to your account: for hourly limits on hairstyle suggestions and action plans, and for a daily limit on scan attempts, where each attempt counts toward a limit over 24 hours. If a scan attempt fails because of a problem on our side, we mark it as given back, and it no longer counts toward that limit. Records older than one day are removed when we next check your account’s limits. If no further check occurs, those records remain until your account is deleted.

4. Third-party processing

We use these service providers, each only to run LooksLab for you. Anthropic (the AI models): every scan sends your front and side photos, with measurements computed from them, to produce your analysis; your front photo is sent again if you ask for hairstyle suggestions; and the text of your results, with no photos, is sent to write your action plan and, if you use Hebrew, to translate the written analysis. Anthropic processes this data under its commercial API terms: by default it does not train its models on it, and it deletes it after the limited retention period those terms set. Supabase (sign-in, database and photo storage) holds your account, photos and results on our behalf. Railway runs our application server: it receives your photos to run the analysis and any hairstyle suggestions you ask for. The working copies there are deleted when the request finishes, and any that an interrupted request leaves behind are deleted automatically within about an hour. Vercel hosts the website and never receives your photos. Google handles sign-in. The open-source code that checks your photo inside your browser is delivered by our own website, so no other provider is involved. No one else receives your photos, and we will update this policy before any feature sends them to another provider. Some of these providers process data outside your country, including in the United States.

5. Biometric data notice

A photo of your face may be considered biometric data under some laws (e.g. Illinois’ BIPA, the EU’s GDPR, and similar state/national laws). [PLACEHOLDER: confirm applicable biometric-privacy obligations for your jurisdiction(s) with a lawyer before launch — this may require explicit consent language, a retention schedule, or additional disclosures beyond this starter draft.]

6. Your rights

You can delete the photos for any scan, or all of your photos, at any time, from your results or your scan history. You can also delete your account yourself from My scans. Account deletion removes your account and its saved content from the site’s active storage and database: your photos and face points, results, scores and measurements, hairstyle suggestions, action plan and progress, email preferences and generation-limit records. This cannot be undone. The exceptions are explained below.

Each Google account gets one free scan, and deleting your account does not reset that allowance. If your account used its free scan, we retain a code derived from your Google account ID. This record contains only the code, indicating that the free scan was used. It contains no email address, name, photo, result or date. We use it only to recognise the same Google account if it signs in again and prevent another free scan. We do not store your Google account ID in this record.

Some copies are kept outside the site’s active storage and database. Deleting your account does not remove them immediately, and they are not all kept for the same length of time: each follows its provider’s own retention. The logs of our application server, at Railway, can include your account ID and scan IDs, and its request records can include your IP address. Supabase’s service logs of database requests and sign-ins can include your account ID, email address and IP address. Our database provider may also keep backup copies under its own retention policy. Vercel’s logs of requests to the website can include your IP address. The photos and text sent to Anthropic, and its generated responses, are handled under its commercial API terms. API inputs and outputs are normally deleted within 30 days of receipt or generation. Content flagged by its automated safety systems as violating its Usage Policy may be retained for up to two years, and related safety classification scores for up to seven years. Longer retention may apply for legal compliance, Usage Policy enforcement, or particular features or agreements.

For access, correction or any other request, write to [PLACEHOLDER: contact email] and we’ll respond promptly.

7. Marketing emails

Your Google sign-in gives us your email address, which we use to run your account. We do not email you unless you opt in. If you check “Email me when they launch” on your results page, we record that choice with your email address and email you when tracking and progress features launch. It is off by default, and you can withdraw at any time by unchecking it, or through the unsubscribe link in any email we send you.

8. Age requirement

LooksLab is for users who are 18 or older, or the age of majority in their jurisdiction if that is greater. We do not knowingly collect data from anyone below that age — see our Terms of Service.

Separately, we do not accept images of anyone under 18, whoever uploads them. If we learn that a photo we processed depicted a minor, we delete the associated data and may disable the account that submitted it.

9. Storage in your browser

LooksLab also keeps a small amount of data in your own browser. None of it is used for analytics or advertising: the site loads no analytics, advertising or tracking scripts, and the only cookie it sets itself remembers your language choice, for up to a year. Google and Supabase may set their own cookies on their sign-in pages. The open-source code for the in-browser photo checks is part of the site itself; the site loads no code from other providers.

In localStorage, which persists until you clear it: your sign-in session, if you sign in with Google — this is managed by Supabase, our authentication provider, and refreshed automatically; your language choice; and a flag recording that you confirmed you are 18 or older. If you take part in our invitation-only placement study, the study page also keeps there the points you mark, the label from your invitation link, a random ID for your device, and each photo’s file name and a fingerprint of it (never the photo itself). These stay on your device until you clear them, and reach us only if you send them yourself.

In sessionStorage, which your browser discards when you close the tab: your most recent scan result, so the results page can show it and survive a reload; a note of whether that result came from a new scan or was reopened from your scan history; and, once a new scan’s score animation has played, a note saying so, so it does not replay on a reload.

The photo you upload is not stored in your browser at all. It is held in memory for the length of your visit and released when you leave the page.

You can clear all of this at any time through your browser's site-data controls. Doing so signs you out, resets your language to the default, and asks the age question again.

10. Who we are, and how to contact us

[PLACEHOLDER: controller legal entity name, company number, and registered address]

Privacy questions or requests: [PLACEHOLDER: contact email].