Trust
Security
Most tools like this ask you to trust a privacy policy. We'd rather you trust an architecture. Here's exactly what happens to your photo, in plain language.
Most processing never leaves your device
Cropping, zooming, rotating, positioning against the guide overlay, and checking your photo against the compliance rules all run as computation inside your own browser, using on-device machine-learning models for face and background detection that download to your browser once and then run locally. For the free tier, and for the paid tier in the United States, United Kingdom, Canada, and China, your original photo is never transmitted to any server at all.
The one exception: AI enhancement
For the paid upgrade, on countries where digital enhancement is legally permitted, one step does touch a server. Here is exactly what that involves:
- After your payment is verified, your browser sends the photo once, over an encrypted (HTTPS/TLS) connection, to a serverless function we run.
- That function forwards the image, in memory, to Replicate — a hosted image-processing API we use specifically for this step — and waits for the enhanced result.
- The result streams straight back to your browser.
At no point in that round trip is your photo written to a disk or a database. There is no database in this product at all — we have nowhere to put it even if we wanted to.
Nothing is stored, so there's nothing to lose
We don't create accounts, so there's no password database and no user profile tied to your identity. We don't persist your photo on our servers at any stage of any flow, free or paid. That means there's no backup of your photo sitting somewhere waiting to be breached, leaked, or subpoenaed after the fact, because it was never kept in the first place.
No biometric templates or faceprints, ever
Face-landmark detection is used only to help position an initial crop guide as a convenience — the coordinates it produces exist transiently in your browser's memory during your session and are used purely for that one geometric purpose. We never generate, store, or transmit a biometric template, faceprint, or any other persistent representation of your face.
Payments never touch our servers
Checkout is handled entirely by Stripe. Your card number, expiry, and security code are entered directly into Stripe's own hosted checkout page — they never pass through our servers, and we never see or store them.
Named sub-processors
These are the only outside companies that ever handle data on our behalf, and each is scoped to one narrow purpose:
Stripe
Payment processing for the one-time paid-tier upgrade.
Handles your card details directly; we never see or store them. Captures your email for the receipt.
Their privacy policy →Replicate
Hosted image-inference API used for the AI enhancement/upscale step only.
Used only for paid-tier orders on countries where enhancement is legally permitted. Receives the photo in memory for that single request; we do not use it to store a photo library.
Their privacy policy →Beyond these two, our hosting infrastructure (Vercel) automatically logs standard technical data, such as IP address and request timestamps, for security and reliability, the same way almost any web host does. These logs are about the request, not your photo's content, and are not linked to anything you upload.
Encryption in transit
Every network request this service makes — checkout, the enhancement call, and everything else — happens over HTTPS/TLS. There isn't a plaintext path anywhere in the flow.
A note on “online passport photo” warnings
A concern we take seriously, not one we wave away
Australia's Department of Foreign Affairs and Trade (DFAT) has publicly warned travelers about certain online passport-photo services and mobile apps, largely because of concerns about photos being uploaded to servers and retained by unknown third parties. That is a legitimate concern about a real category of product.
Here is how this service's architecture differs from what those warnings are typically about:
- Most of our processing happens on your device, not a server.
- We don't create an account or a persistent profile tied to you.
- We don't build a photo library, gallery, or history of any kind.
- Nothing about your photo is retained once your session ends, or once an enhancement request completes.
- The named sub-processors above are the only third parties that ever touch image data, and only for the one narrow step described.
This page is a factual description of that architecture, not a claim of endorsement by DFAT, any other passport authority, or any government.