Photos stay on-device.
Camera images and video are processed in browser memory. The scan flow does not upload them or save them to your report.
Privacy
How your camera data and reports are handled.
Launch draft · October 18, 2026
Reports keep measurements.
We save derived measurements, capture checks, experimental references, focus points, versions, and report ownership so you can revisit a completed scan.
You choose who you scan.
Use the camera only with the person’s permission. Get their agreement before saving their report to your account.
What the camera accesses
The scanner asks your browser for camera permission. Images, video, and visible landmark overlays are processed on your device. Captured frames are held in memory for the scan and hairline confirmation; they are not included in requests to the report API. Leaving the scanner stops the camera and releases the scan view.
The browser downloads the face-landmark model and supporting files from this website's own origin. The model then runs on your device; your camera images are not sent to a remote analysis service.
What a saved report contains
Saved data includes normalized facial measurements, additional feature geometry, estimated head pose, expression and lighting flags, measurement availability and warnings, your selected aesthetic preset, experimental reference values or ranges, reference eligibility, tier status, coverage, focus points, model and analysis versions, completion time, and the free-scan, credit, subscription, or test allowance used. A report is linked to its guest session or signed-in account.
These measurements are personal information even without an image. The product does not use them to identify who a face belongs to or match faces across accounts. You can delete individual reports from your account. Deleting a report does not restore a used free scan or credit.
Leaderboard and Battle
Creating a leaderboard profile saves a display name, chosen preset, and personal best. If you choose to appear publicly, other visitors can see your display name, score, tier, rank, and the time of that best result. Reports, photos, contact details, and private ownership identifiers are not published. You can hide or remove your profile from the leaderboard.
Battle history saves the two player names, preset, round scores, category comparisons, and links to the private scan reports. Only the owning browser session or account can open or delete those matches. Deleting a scan clears its linked leaderboard best and Battle round. Deleting a match leaves its individual scan reports in your scan history.
Guest profiles and matches are tied to the remembered browser session. When sign-in is connected, signing in on that browser links saved data to the account. A display name is not a verified real-world identity; clearing browser data can lose unlinked guest data. Someone-else and Battle scans do not update the owner’s personal ranking.
Guest sessions and cookies
A secure guest cookie remembers your browser and links it to a server usage record. This helps enforce one completed free report per remembered browser. Clearing browser data or switching devices can lose access to a guest report or bypass that best-effort allowance. Signing up does not provide another free scan.
When you sign in on the browser used for a guest scan, the app can link that report to your account. Authentication cookies keep you signed in. Request-protection cookies and tokens help protect account and payment actions.
Accounts and billing
Cloudflare D1 stores verified email addresses, account balances, reports, profiles and Battle history. Resend delivers one-time login codes to your email address. The app verifies those codes and manages sessions directly. Login codes expire after ten minutes and are stored as keyed hashes. Opaque session tokens are kept in HttpOnly cookies, with only their hashes stored in D1; sessions expire after 30 days and are revoked when you sign out. Expired challenges and sessions are removed during subsequent login requests. The same flow creates an account on your first login. Your email address is private and is not shown on the leaderboard. The app stores protected rate-limit identifiers rather than raw email addresses in its abuse-prevention records.
When payments are configured, Stripe hosts checkout and the billing portal. Look Maximize stores the payment identifiers and entitlement information needed to track purchased credits and subscription access. Card details are entered in Stripe’s checkout. Your email address is attached to your Stripe customer record for account and billing support.
Storage and service availability
The local development version can store guest records and reports on the application server. A configured hosted deployment uses its database. Accounts and payments show an unavailable state when their required services have not been connected. This notice does not claim that a local development session is a live production account.
Before public launch
This is a launch draft describing the implemented data flow. The operator’s identity, contact channel, retention periods, account-deletion process, hosting regions, and any additional production services must be finalized before accepting public accounts or payments. No operator contact details have been invented for this preview.
Read how scoring works for measurement limitations and the draft terms for use and billing rules.