Scope
This notice describes the current Facehunch test application at facehunch.com. The fictional sample is separate from the API test. The account and checkout flow uses Stripe test mode and fictional reports; real payments and paid searches remain disabled.
Images and API results
Selecting an image creates a preview in your browser. Starting the consented API test sends that image through Facehunch’s server to FaceCheck. Facehunch does not persist those uploads or API results in an application database. The server uses a protected provider key; that key is not sent to your browser.
A signed, expiring job token lets the browser poll its search and request cleanup. The application asks FaceCheck to remove the search input after completion or cancellation. Network or provider failures can prevent confirmed cleanup. Closing the browser does not guarantee the cleanup request completes.
Third-party processing
FaceCheck processes the submitted image under its own policies. Review the provider’s current terms and privacy information on FaceCheck before uploading. Test mode changes search coverage and billing behaviour; it does not mean the image stays on your device.
Cloudflare serves the application and processes requests. Operational request information may be handled by the hosting platform for delivery, security and diagnostics. This notice does not promise that all infrastructure logs are disabled or instantly deleted.
Website analytics
Google Tag Manager loads Google Analytics 4 and our Matomo instance at tracking2.lindoai.com to measure page visits and navigation. These services may use analytics cookies and process device, browser and network information. Pageview URLs exclude query strings and fragments. We do not send uploaded photos, search results, email addresses or signed job tokens as analytics event data.
Results and external links
Source links lead to third-party websites with their own policies. Removing your search input does not remove source images or change a provider’s index. Sample saved items demonstrate the interface and are not a durable archive of API findings.
Your choices
Use the fictional example if you do not want to submit an image. Upload only images you are entitled to share, and avoid unrelated sensitive information. Read photo removal for the different removal routes. Contact hello@sopranos.dev to request removal of your test account and associated report records.
Test accounts and checkout
We store your verified account email, account creation time, and test report references in a dedicated Cloudflare D1 database. Email sign-in uses a single-use four-digit code sent through Cloudflare Email Service. Codes expire after five minutes and allow five attempts. We store a keyed hash of each code, not the code itself. An HttpOnly session cookie keeps you signed in for up to seven days. Signing out revokes that session. No password is needed. Google sign-in, when available, shares your verified email and Google account identifier; we do not request access to Gmail or contacts.
The preparation and Stripe checkout flow does not upload your selected photo. It stays in your browser. Stripe receives a test checkout amount and opaque account and report identifiers; we do not send it your selected photo or account password. Information you enter directly on Stripe is processed by Stripe. Use only test card details. We retain the Stripe test session reference and confirmation time so your sample reports remain available when you sign in. Accounts and report references remain until test data is reset or you request removal.
The separate API example workspace can send a photo to FaceCheck only when you explicitly start its consented API test. This is independent of the sample report checkout.