How SnapIdentify handles your information
SnapIdentify processes an image to provide the identification you request. This policy explains what the site receives, which service processes it, and what you should avoid uploading.
Uploaded images
Images are sent to the SnapIdentify server for file validation, rotation, resizing, and metadata removal. The normalized image is processed in memory. SnapIdentify does not intentionally write the image to local application storage or create a public image URL.
Google Gemini processing
SnapIdentify sends the normalized image, the selected identifier type, and any optional context to the Google Gemini API. Google processes that information to generate the identification result. The API key remains on the server and is not sent to your browser.
When the site uses unpaid Gemini API quota, Google states that submitted content and generated responses may be used to provide, improve, and develop Google products and machine-learning technologies. Human reviewers may also read, annotate, or process API input and output. Do not upload sensitive, confidential, private, or personally identifying information. Review the Gemini API terms and the Google Privacy Policy for details.
When the Gemini project uses an active paid billing account, Google applies its paid-service data terms. Limited logging may still occur for safety, abuse prevention, service operation, and legal requirements.
Age requirement
The Gemini-powered identifier is for adults aged 18 or older. Do not use the upload tool if you are under 18. Do not upload photographs of children or material intended to identify a child.
Optional context
You may provide a country or broad region, environment, approximate size, and a short observation. Do not submit a street address, account credentials, medical records, financial details, private documents, or other sensitive data.
Technical and security information
The server may process an IP-derived request key, request time, response status, and limited error details to enforce rate limits, detect abuse, and maintain the service. Application logs are not intended to contain raw uploaded image bytes or the Gemini API key.
Contact messages
The contact form collects the name, email address, topic, subject, and message you submit. When the form is configured with a Formspree endpoint, that information is sent to Formspree so SnapIdentify can review and answer the inquiry. Formspree may apply its own spam, security, and delivery processing.
Blog and public pages
Reading a public page or blog post does not require an account. Blog images are public files and should never contain private or confidential information.
Cookies and analytics
SnapIdentify does not require an account or advertising cookies to process an image. This policy will be updated before analytics, advertising, account history, or consent-dependent tracking is introduced.
Your choices
You can omit all optional context. You can also crop faces, addresses, license plates, documents, private locations, and other identifying details before uploading. The safest choice is not to submit an image that contains information you would not want an external AI provider to process.