Privacy Policy
DRAFT — REQUIRES LEGAL REVIEW BEFORE PUBLISHING. This document was scaffolded from common multi-jurisdiction templates by an AI assistant. It MUST be reviewed and amended by a qualified privacy lawyer in your jurisdiction(s) of operation before being made public or relied upon by users. Do not publish as-is.
PhotoTool ("we", "us", "our", or "the Service") respects your privacy and is committed to handling your personal information transparently and lawfully. This Privacy Policy explains what data we process when you use the Service, why we process it, and the rights you have over that data.
If you do not agree with this Privacy Policy, please do not use the Service.
1. Who we are
PhotoTool is a browser-based tool that helps users prepare photos that meet the technical requirements of the United States Department of State's biometric photo programs — including the Diversity Visa (DV) Lottery program and the US Passport application. PhotoTool is not a US Government service, is not affiliated with the US Department of State, and does not guarantee acceptance of any photo submitted to the DV Lottery program, the US Passport application, or any other government program.
For privacy-related questions or to exercise your rights, contact: privacy@phototool.example.
2. The data we process
2.1 The photo you upload
When you use the Service, you upload a digital photograph of a face — yours or someone else's whom you are authorised to act for. The photograph is biometric data in many jurisdictions because it depicts identifiable facial features.
We process the photograph for the sole purpose of:
- analysing whether it meets US State Department biometric photo requirements (face position, lighting, glasses, background, sharpness, dimensions, etc.) for the document type you select (DV Lottery or US Passport);
- producing a corrected version of the photograph if you choose to proceed.
What happens to the photograph:
- Your browser sends it to our API, which forwards it to Google's Gemini API for the analysis and, if you proceed, for the correction (Section 4.1). Our API handles it in memory only; it does not write the photograph to disk, to a database or to its logs.
- The corrected image — produced by Gemini or, if Gemini is unavailable, by a fallback that runs in your browser — is sent to our watermarking function and held in a cache (Upstash Redis, Section 4.8) under a random token for up to 30 minutes, so that we can show you a watermarked preview and, once you have paid, serve the clean download. The cache entry is deleted as soon as the paid download is served and expires automatically otherwise.
- Your original upload is not stored by us. The face-geometry measurements from the local check are computed in your browser and are not sent anywhere; the analysis results Google returns (including the head-size and eye-level figures it measures) pass through our API to your browser and are not stored.
We do not use your photograph to train any machine-learning model. We do not share, sell, rent, or disclose your photograph to any third party except as described in Section 4 (sub-processors strictly necessary to provide the Service).
2.2 Technical metadata
When you visit the Service, your browser transmits standard request headers (IP address, user-agent string, referrer) to Vercel, which hosts the Service and runs our API (Section 4.4). Vercel records this request metadata and the log lines our API functions write for a limited period; we keep no server-side logs of our own beyond those.
2.3 Local storage on your device
PhotoTool uses your browser's localStorage for a small number of functional purposes:
- recording your consent to this Privacy Policy and the Terms of Service (versioned);
- recording your dismissal of the local-storage notice;
- remembering the document type you selected (US Passport or DV Lottery);
- if you use the "DS-260 Unlock" workflow, keeping a log of the requests you dispatched from this device (the form fields you entered), on your device only;
- storing administrator-only configuration if you log in as an administrator (training examples, email-routing settings).
- if you log in as an administrator, our server also sets a session cookie (
pt_admin_session; HttpOnly, Secure, SameSite=Strict, expires after 24 hours) containing a signed token with the administrator username — the only cookie the Service itself sets.
PhotoTool uses Google Analytics 4 (measurement ID G-ESEEZ7LH7W) only after you opt in during the consent step. Until you opt in, the Google Analytics script is not loaded at all: your browser makes no request to Google Analytics and no analytics cookie is set. We use Google Consent Mode v2 in its "basic" form — analytics_storage defaults to denied and the tag is inserted only once you grant it. Your choice is stored on your device as part of the consent record above, so on later visits the script is loaded only while that opt-in stands. You may withdraw or change this consent at any time from the consent banner in the Service: withdrawing sets analytics_storage back to denied at once (a script already loaded in the current page stays until you leave the page but no longer uses cookies) and the script is not loaded on your next visit. We do not use advertising identifiers or cross-site tracking.
2.4 Email contents (DS-260 unlock requests only)
If you use the optional "DS-260 Unlock" workflow, the form details you submit (full name, case number, date of birth, your email address and the reason for the request) are sent to our server-side email endpoint, which passes them to Resend, an email delivery provider (Section 4.3), to deliver the email to the Kentucky Consular Center at your direction (or to a test address configured by an administrator). Your email address is set as the reply-to address of that email. We do not retain these details on our servers; your own browser keeps a copy of the request in its localStorage (Section 2.3).
2.5 Children
The Service is not directed at users under the age of 16. If you are under 16, do not use the Service. If we learn that we have processed the personal data of a child under 16 without verifiable parental consent (where required), we will delete it.
3. Where the processing happens
In your browser:
- Local face-mesh detection and the geometric measurements run in JavaScript on your device.
- The fallback background removal (used only if the AI correction is unavailable) runs in JavaScript on your device.
- Resizing, EXIF-handling, and JPEG export all run on your device.
On our API (functions run by Vercel, Section 4.4): receiving your photograph and forwarding it to Google's Gemini API; applying the preview watermark to the corrected image and placing it in the cache; checking the payment status with Stripe or OpenNode before releasing the clean download; sending the DS-260 email through Resend. Our functions keep data in memory only and do not write it to disk.
At Google: the AI analysis and the AI image correction run on Google's servers (Section 4.1). This is unavoidable because the AI model runs there.
In the cache: the corrected image is held in Upstash Redis (Section 4.8) under a random token for up to 30 minutes. It is the only copy of your image stored by us or on our behalf outside your browser; Google's handling of the photograph during and after the AI call is governed by its Gemini API terms (Section 4.1). It is deleted as soon as you download the clean image after payment and expires automatically otherwise, and it can only be retrieved with the token held in your browser session together with a confirmed payment reference.
Closing the tab discards your browser's copies of the original and corrected images. It does not shorten the cache period, but the token needed to retrieve the cached image is discarded with the tab.
4. Sub-processors and third parties
We rely on a small number of third-party services to provide the Service. Each is named below with its role and a link to its own privacy policy.
4.1 Google Gemini API (Google LLC)
- Role: Performs AI photo analysis and AI image correction.
- Data shared: Your photograph (sent by our API as base64-encoded image bytes), and a text prompt describing the analysis or correction task.
- Retention: Google retains and uses prompts and images according to the Gemini API Additional Terms (ai.google.dev/gemini-api/terms). Which terms apply depends on whether our project is on Google's paid tier: under Google's current terms, content submitted through the unpaid tier may be used by Google to improve its services, while content submitted through the paid tier is not. [Tier to be confirmed in the Google AI Studio dashboard and stated here before publication.]
- Privacy policy: policies.google.com/privacy
- Geographic processing: Google operates a global infrastructure; your photograph may be processed on Google servers in the United States or other countries.
4.2 Content delivery networks (Google Fonts, IMG.LY)
- Role: Google Fonts serves the icon font; IMG.LY's CDN (
staticimgly.com) serves the background-removal model used only by the fallback correction. The face-detection model that runs in your browser is served from our own website, not by a third party. - Data shared: Standard HTTP request headers from your browser (IP, user-agent). Your photograph is not transmitted to any of them.
- Privacy policies: policies.google.com/privacy, img.ly/privacy-policy
4.3 Resend (used only for DS-260 Unlock email dispatch, if you choose)
- Role: Email delivery provider, operated by Plus Five Five, Inc. Our server-side endpoint hands the unlock-request email to Resend, which delivers it to the Kentucky Consular Center on your behalf. The sending credentials are held on our server; nothing is sent from your browser to Resend directly.
- Data shared: The recipient address, the subject line (which contains your case number), the message body (your full name, case number, date of birth and the reason you entered), your email address as the reply-to address, and our sender address.
- Retention: Resend keeps the message and its delivery record according to its own policy; we keep no server-side copy.
- Privacy policy: resend.com/legal/privacy-policy
4.4 Hosting and API functions (Vercel Inc.)
- Role: Vercel serves PhotoTool's static files and runs our API functions (the photo analysis and correction relay, watermarking, payment checks, email dispatch and the security-report sink).
- Data shared: Standard request headers and metadata for every request (IP address, user-agent, referrer, requested path, status code, timing), and the log lines our functions write: request method, path and status, error messages returned by the providers in this section, and Content-Security-Policy violation reports sent by your browser (page URL and blocked resource). Payment references (the Stripe PaymentIntent id or the OpenNode charge id) appear in requested paths. Request bodies — including your photograph and the DS-260 email — are handled in memory and are not written to the logs.
- Retention: Vercel keeps request and function logs for the period set by its log-retention policy for our plan; we keep no separate copy.
- Privacy policy: vercel.com/legal/privacy-notice
4.5 Google Analytics (Google LLC) — opt-in only
- Role: Anonymous usage analytics (page views, session counts, approximate geography by country/region, and a few events in the photo flow) to help us improve the Service.
- Data shared: A pseudonymous client ID (
_gacookie), your IP address (Google Analytics 4 uses it to derive approximate location and does not log or store it), user-agent, the page URL you visited, and these event details: whether your photo was uploaded or taken with the in-app camera, the document type, whether it passed our checks and how many checks failed, and, if you buy, the payment method and amount. Your photograph and face measurements are not transmitted to Google Analytics. - Lawful basis: GDPR Art. 6(1)(a) — your consent. Not loaded by default: the Google Analytics script is inserted only after you opt in via the consent gate (Google Consent Mode v2, basic implementation —
analytics_storagestaysdeniedand no request is made to Google Analytics until then). - Measurement ID:
G-ESEEZ7LH7W. - Privacy policy: policies.google.com/privacy
4.6 Stripe (Stripe, Inc. and its affiliates) — card payments
- Role: Processes card payments (and the wallet methods Stripe offers in its payment form) for the corrected photo.
- Data shared: Your card details and any billing details Stripe asks for are entered in Stripe-hosted form fields and go directly from your browser to Stripe; they never reach our servers. Because Stripe's script runs in your browser, Stripe also receives standard request data from your browser (IP address, user-agent). Our server sends Stripe only the amount and currency to create the payment. We receive a payment reference (the PaymentIntent id) and its status, which we check once with Stripe before releasing the clean download.
- Retention: Stripe keeps the payment record under its own policy. We store no payment record; the payment reference is held in your browser for the session.
- Privacy policy: stripe.com/privacy
4.7 OpenNode (OpenNode, Inc.) — Bitcoin and Lightning payments
- Role: Creates and settles Bitcoin (on-chain) and Lightning Network charges as an alternative to card payment.
- Data shared: Our server sends OpenNode the amount in US dollars, the currency, a description of the item and our webhook address. OpenNode returns a charge id, a Lightning invoice, a Bitcoin address and the amount in satoshis, which we display to you. Your wallet pays OpenNode directly; OpenNode sees the payment and, for on-chain payments, so does the public Bitcoin network. We receive only the charge id and its status (processing, paid or expired), by webhook and by polling. We do not receive your wallet address.
- Retention: OpenNode keeps the charge record under its own policy. We store a "paid" flag keyed by the charge id in the cache (Section 4.8) for one hour so the download can be released without asking OpenNode again.
- Privacy policy: opennode.com/privacy-policy
4.8 Upstash (Upstash, Inc.) — short-lived cache
- Role: Hosts the Redis cache our API uses between the correction step and the download.
- Data stored: (a) The corrected image, without the preview watermark, under a random token (
phototool:correction:<token>) with a 30-minute expiry (1,800 seconds); it is deleted the moment the paid download is served. (b) For Bitcoin payments, a "paid" flag under the OpenNode charge id (btc:paid:<charge id>) with a one-hour expiry. No names, email addresses, IP addresses or account data are stored. The token is random, and a cache entry can be fetched only with the token and a confirmed payment reference. - Privacy policy: upstash.com/trust/privacy.pdf
5. Your rights
You have rights over your personal data that vary by jurisdiction. Some of those rights apply to data we never hold a lasting copy of (because processing happens in your browser, or because the only server-side copy — the cached corrected image — expires within 30 minutes); for those, the right is fulfilled by closing the tab or by waiting for the cache to expire.
To exercise any of these rights, contact privacy@phototool.example with proof of identity sufficient to confirm you are the subject of the data.
5.1 European Economic Area and the United Kingdom (GDPR / UK GDPR)
If you are in the EEA or the UK, you have the rights to:
- be informed about how your data is processed (this Policy);
- access any personal data we hold about you (Art. 15);
- have inaccurate data corrected (Art. 16);
- have your data erased (Art. 17);
- restrict processing (Art. 18);
- data portability (Art. 20);
- object to processing (Art. 21);
- withdraw consent at any time (Art. 7) — this does not affect the lawfulness of processing already carried out;
- lodge a complaint with your local supervisory authority (Art. 77). For the EU, the European Data Protection Board lists them at edpb.europa.eu/about-edpb/our-members_en; for the UK: ico.org.uk.
Lawful basis under GDPR for processing your photograph:
- Article 6(1)(a) — your consent, given via the consent gate before upload;
- Article 9(2)(a) — your explicit consent to the processing of biometric data, given via the same consent gate.
International transfers. When your photograph is sent to Google for AI analysis, it may be transferred outside the EEA/UK to the United States. Google participates in the EU-US Data Privacy Framework and offers Standard Contractual Clauses; we rely on those mechanisms, and the same applies to Google Analytics data if you opt in (Section 4.5). The sub-processors that hold user data on our behalf — Vercel Inc., Upstash, Inc., Stripe, Inc., OpenNode, Inc. and Plus Five Five, Inc. (Resend) — are United States companies, so the cached corrected image, payment references and the DS-260 email may likewise be processed in the United States; we rely on the transfer mechanisms each offers (Standard Contractual Clauses and, where the provider is certified, the EU-US Data Privacy Framework). The content-delivery networks in Section 4.2 (IMG.LY GmbH, Germany; Google Fonts, Google LLC) receive only standard request headers.
5.2 California (CCPA / CPRA)
If you are a California resident, you have the rights to:
- know what personal information is collected, used, shared, or sold;
- delete personal information collected from you;
- correct inaccurate personal information;
- opt out of the sale or sharing of personal information for cross-context behavioural advertising;
- limit the use and disclosure of sensitive personal information.
We do not sell your personal information and we do not share it for cross-context behavioural advertising. Your photograph is treated as sensitive personal information; we use it only for the photo-validation purpose you uploaded it for.
5.3 Illinois (BIPA)
The Service performs face-geometry analysis on your photograph, which qualifies as the processing of "biometric identifiers" or "biometric information" under the Illinois Biometric Information Privacy Act, 740 ILCS 14.
Specific BIPA disclosures:
- What is collected: Geometric measurements of facial features, derived in real time from your uploaded photograph.
- The specific purpose: To assess whether the photograph meets the technical requirements of the US Department of State biometric photo program you have selected (Diversity Visa Lottery or US Passport).
- The specific term: Geometric measurements are derived in your browser and discarded when the browser tab closes. We do not store biometric identifiers on any server we control. The maximum retention period is therefore the duration of your browser session. The corrected photograph itself (an image, not a geometric template) is cached for up to 30 minutes as described in Section 2.1.
- Disclosure: We do not sell, lease, trade, or otherwise profit from your biometric identifiers or biometric information. We share them only with Google's Gemini API for the purpose stated above (Section 4.1) — Google acts as a service provider performing AI analysis, not as an independent recipient. The photograph itself also passes through our API functions on Vercel and, once corrected, is cached with Upstash (Sections 4.4 and 4.8); neither derives or stores facial geometry.
- Written consent: Your acceptance of the consent gate at upload time, recorded with version stamps and timestamp in your browser's
localStorage, constitutes your written release for BIPA purposes.
If you do not consent to biometric processing, do not click the consent box and do not proceed past the upload step.
5.4 Other jurisdictions (universal)
The rights of access, rectification, deletion, objection, and complaint are recognised in substantially the same form by, among others, the South African POPIA, Kenyan DPA 2019, Nigerian DPA 2023, Egyptian PDPL, Indian DPDP Act 2023, Japanese APPI, Singaporean PDPA, Thai PDPA, and the ASEAN and APEC frameworks. If you are subject to any of these regimes and wish to exercise your rights, contact privacy@phototool.example.
5.5 Mainland China (PIPL)
The Service is not intended for users physically located in mainland China. We have not performed a cross-border data transfer impact assessment under the Personal Information Protection Law (PIPL). If you are in mainland China, do not use the Service.
6. Retention
- Your original photograph: held in memory by your browser and by our API functions while they handle the request; we do not store it. Google processes it to perform the analysis and correction under its Gemini API terms (Section 4.1). Closing the tab discards your browser's copy.
- The corrected image: held in the Upstash Redis cache under a random token for up to 30 minutes (1,800 seconds). It is deleted as soon as the paid download is served and expires automatically otherwise.
- Geometric measurements from the local check: your browser session only.
- Payment records: kept by Stripe or OpenNode under their own policies. We store no payment record. For Bitcoin payments, a "paid" flag keyed by the OpenNode charge id is kept in the cache for one hour.
- Your consent record: retained on your device until you clear your browser storage or withdraw consent. We do not have a copy.
- Your document-type preference (US Passport or DV Lottery): on your device until you clear browser storage.
- DS-260 unlock requests: the email is kept by Resend and by the recipient under their own policies; we keep no server-side copy. Your own browser keeps a log entry of the request until you clear your browser storage.
- Administrator data (training examples, email-routing settings): retained only on the administrator's device.
- Request and function logs: kept by Vercel for the period set by its log-retention policy. They never contain your photograph.
Apart from the short-lived cache described above, we run no database, object store or other server-side persistence layer that holds user data.
7. Security
The Service keeps no lasting store of your photograph; the only server-side copy is the 30-minute cache of the corrected image, reachable only with a random token and a confirmed payment reference. The principal security measures are:
- TLS encryption in transit between your browser, our API and every third party.
- Provider credentials (Google, Resend, Stripe, OpenNode, Upstash) held only in server-side environment variables, never in the browser.
- Payment card data handled only by Stripe, in Stripe-hosted fields.
- HTTP security headers, including a Content Security Policy, on every page.
- Source-code review and dependency auditing.
- A documented data-flow inventory (internal).
- Separation of administrator credentials from regular user flows.
We do not claim absolute security; no internet-based service can. The residual risk is concentrated in transit-time exposure, which TLS mitigates, and in the short-lived cache, which is bounded by its 30-minute expiry and its random tokens.
8. Changes to this Policy
We may update this Privacy Policy from time to time. The version number and effective date at the top of the document will be incremented when we do.
If a material change occurs, the consent gate in the Service will require you to re-confirm acceptance of the updated Policy before you continue using the Service. Stored consents at older policy versions will be invalidated automatically.
Change log:
- v1.2 (2026-10-05): Named Vercel as host; moved DS-260 email dispatch from the former browser-side mail relay to Resend; added Stripe, OpenNode and Upstash as sub-processors; corrected retention to the 30-minute server-side cache of corrected images; the Google Analytics script is now loaded only after you opt in; listed the document-type preference kept in local storage and the transfer position of each sub-processor.
- v1.1 (2026-05-11): Added optional Google Analytics 4 (opt-in via consent gate, Consent Mode v2). Updated Section 2.3 and added sub-processor 4.5.
- v1.0: Initial draft.
9. Contact
For privacy questions, data subject requests, or any other matter under this Policy, contact: privacy@phototool.example.
End of draft. The placeholders for the effective date and the contact mailbox / final domain (phototool.example → real domain) must be filled before publication. A privacy lawyer should review the BIPA, GDPR, CCPA, and PIPL sections in particular.