Temporary field notes, or saved account records.

Anonymous photos and identification results become unavailable to your browser 24 hours after an identification is created. We retain the private photos and model result versions without a scheduled expiry so authorized operators can investigate recognition failures and review service performance. This does not create an account collection or a public photo link. Optional notes, location details and chat are removed during cleanup after the 24-hour access period. Deleting a specimen also removes its retained results and schedules unused photos for deletion. After browser access expires, you can contact support to request deletion using your task or result ID.

Signing in migrates eligible, unexpired records from the current anonymous browser session into your account history, up to the current plan limit shown on the pricing page. New signed-in identifications are automatically kept in history. Favorites are separate bookmarks: removing a favorite does not delete the record. Account photos, notes, chat and result versions are retained for up to 10 years unless you delete the specimen or account. Google sign-in uses your verified email address and stable Google account identifier to create or access your account. We verify the Google credential on the server and do not retain it. Google receives the sign-in request; we do not request access to your Gmail, Drive, or contacts. Email sign-in sends a one-time code through our configured email provider (Brevo or Resend). The provider receives your email address and code to deliver the message, but no specimen photos or notes. Codes expire after 10 minutes, allow at most five incorrect attempts, and work only in the browser that requested them. We store a keyed hash of the code rather than the code itself; sign-in attempt records are removed after 31 days. A verified email opens the existing account with that email, including its saved records and plan.

Location is optional. The service does not request GPS coordinates. You can permanently delete a specimen from its result or history page. This removes its readable results, chat, notes and versions, removes it from history and favorites, and schedules unused photos for cleanup.

An anonymous browser cookie applies daily limits and separates temporary records. A separate signed-in account cookie grants access to saved records on another device. Clearing browser data or using another device does not restore anonymous records, and an anonymous cookie cannot open records after they are claimed by an account.

When identification is enabled, prepared photos and the information you submit are sent to the configured AI provider to generate a result or reply. This site uses Google Gemini through OpenRouter. When identification is paused, no new analysis or reply is sent. Avoid including faces, addresses or other personal information in your photos and notes.

The server removes photo metadata before storing prepared images. It uses essential anonymous and, when signed in, account session cookies. Account session tokens expire after 30 days. Quota records and technical usage records can remain after content expires; deleting a result does not reset your allowance.

Tool choices and optional observations are stored with the specimen. Minimal product events record the tool and workflow stage, without photo contents, location or free-text notes, and expire after 90 days. Support messages are visible only to their owner and authorized support operators.

On public pages, we record anonymous visit sources such as Google, Bing and ChatGPT. A separate random visitor cookie lasts 30 days and lets us keep the first visit source for the same browser. We store the source, referring domain, UTM source label, public landing path and visit timestamps for up to 90 days. We do not store full referring URLs, search queries, other URL parameters, IP addresses or account details in these records. Signed-in visits and private pages are excluded from source attribution. Daily business statistics also count visits to public pages after sign-in, using the same random visitor cookie to count each browser once per Beijing calendar day. These daily records contain a hashed browser identifier, timestamps and the source category, referring domain, UTM source label and attribution method of that browser's first public visit each day, not an email address or account profile, and are removed after 90 days. If a browser or app does not provide a source, we mark it as direct or unknown.

We measure the sign-in process using a random, short-lived flow ID: opening sign-in, choosing Google or email, submitting verification, successful sign-in, new account creation and fixed error codes. The ID can travel in the sign-in URL and tab storage for up to 30 minutes. These first-party records contain no email address, verification code, Google credential, IP address, account ID, specimen details or return URL, and are removed after 90 days. Authorized administrators can see aggregate conversion and failures; this does not enable Clarity recording on private pages.

We use Google Analytics to understand visits to the website and which pages people use. Google receives visit information, including browser and device information, and may set analytics cookies. The page-view addresses we configure remove query parameters, fragments, private record identifiers and share tokens. We do not add email addresses, specimen photos, notes or chat messages to analytics events.

We use Microsoft Clarity on public pages to understand clicks, scrolling and navigation through heatmaps and session recordings. Page text, specimen photos, identification results, notes and conversations may appear in recordings. We do not apply additional content masking. Clarity automatically masks input boxes and dropdown controls. We exclude account, billing, history, collection and share pages from recording, and skip visits containing sensitive sign-in or order parameters. We send Clarity a denied cookie-storage signal and do not provide custom user identifiers. Microsoft receives interaction and technical visit data for this analysis.

When paid plans are enabled, Stripe handles checkout, payment methods and invoices. We store customer, order, subscription and event references to manage your plan; we do not store payment-card numbers. Billing records may remain for reconciliation after you delete specimen content. Successful invoice amounts, currency, payment times and refund records are retained for business reporting, including renewals. Different currencies and test payments are reported separately.

Private recovery snapshots have a seven-day retention period. Deletion records are retained separately so a restore does not make deleted content available again. A restored backup revokes existing login sessions. Recovery copies are unavailable through public photo URLs.