Privacy notice

This marketing website.

The sample demo uses bundled images and predefined results. It does not access your camera, request your location, upload photographs, or create an account. Saved demo cards are stored in session storage in this browser tab so they remain available when you navigate between pages or reload. Reset demo clears saved cards. If browser storage is unavailable, the demo keeps cards in memory until the page is closed or reloaded.

Fonts, photographs, and visual libraries are served with this website. The site includes no analytics or advertising scripts and sets no application cookies. The hosting provider receives ordinary network information when serving pages. External links and email applications have their own handling of information.

The contact form creates an email link locally. A message is sent only if you open the draft and send it in your email application. Messages sent to the operator are handled by the email provider.

Information in this preview

Your explorer name, optional profile photo, interests, discoveries, images and preferences are saved on your device. Cloud builds also store your account and uploaded records in Supabase. Before optional profile setup or guest creation, we ask for an age range and the Terms and Privacy acknowledgments. Cloud choices record your account identifier, age range, policy version, server acknowledgment time and processing choices. We do not ask for your legal name or full birthday. Google, Apple or email sign-in can provide account identifiers, an email and a profile image.

When you identify a photo

Online recognition sends a compressed subject crop and a small preview of the surrounding photo, image fingerprints, selected category, capture time, active themes, and optional location to Supabase. OpenAI assesses identity, estimated encounter scarcity and signs of screens or prints in the selected photograph. A requested second angle can also be assessed by OpenAI. Optional embedding search sends the subject crop to Voyage AI. Exact location remains in private server evidence; the model receives locality and nearby-place hints rather than exact coordinates. Promising new identities may receive a bounded text-only web lookup; supported findings are saved to the shared catalog for reuse. Your profile photo and explorer name are not sent with recognition. Photo AI permission is requested before the upload, separately from device permissions. Chapter suggestions separately send a title to OpenAI and may use a destination web lookup; avoid private information in titles.

Embeddings, caches, and training

A visual embedding is a numerical representation used to compare an image with known reference images. A recognition cache remembers an identification result so the same request may not need another vision call. Neither mechanism trains a new model. This preview does not add submitted photos or their embeddings to a shared reference library. It does not opt in to provider model training. If contributions are introduced, we will provide a separate, optional choice with its purpose, retention, and withdrawal details before collection. Profile photos and location will be excluded, and minors will not be eligible.

Optional camera and location

Camera access is requested when you choose to capture; the system photo picker opens only when you choose a photo. Location is off by default and needs both your choice and device permission. Foreground location is collected while the camera is open; there is no background tracking. Precise coordinates need a separate choice. Supabase receives permitted location for private encounter checks; shared card responses and rendered share cards omit coordinates and venue names. Nearby-place lookup requires a separate opt-in and sends an approximate search area to OpenStreetMap through Overpass. Location does not prove authenticity or origin. Turning location off stops future collection on this device; earlier records remain until removed or retained under the schedule below.

Providers and other recipients

Supabase hosts online recognition when enabled. OpenAI and Voyage AI can process selected photo crops as described above. OpenAI API data is not used to train models by default unless the API account explicitly opts in. Disabling response storage does not eliminate provider security or abuse-monitoring retention. Actual provider handling depends on their terms and our service configuration. Sample photographs, fonts, and the welcome film are bundled with the app; some social or external images and links can contact their hosts, which receive ordinary network information such as an IP address. The app has no advertising or cross-app tracking integration, and we do not sell personal information.

Optional card inscriptions

If you choose to seal a message or drawn signature, the card service stores its text or numeric handwriting strokes, card identity, finish, service-owner identifier, author name and sealing time in Supabase. The inscription cannot be edited through the app. It is not legal signature verification and is not submitted for model training. It is included when you share or export the card. Contact us about access or deletion; sealed content does not override applicable privacy rights.

Sharing is your choice

Cloud profiles and discoveries start private. When you choose a broader audience, shared content is held for a safety review. A separate permission is requested before shared text, including names, chapter titles, notes and postcard messages, goes to OpenAI for automated moderation. It covers future shared text until withdrawn in Settings. Photos and drawings require a separate media and child-safety review process. Unknown or failed reviews do not release content to other users. Shared destinations receive the card, photo or link you send, potentially including your name and inscription. JSON exports omit saved coordinates, venue names, private receipts, image data and device paths. Copies already sent to other people cannot be recalled.

Retention and security

Native persisted app state and auth sessions use AES-GCM encryption with a key stored in the device keystore. Photo files are separate and rely on operating-system file protection. Browser app records use IndexedDB; browser auth uses session storage. Browser storage is not a secure vault against same-origin malicious scripts. Signing out does not delete collections. Cloud maintenance can remove expired recognition caches, clear precise capture-evidence locations after 30 days and remove usage events after 90 days; these jobs must be enabled by the operator. Saved discoveries and photos remain until deletion. Uncollected cloud artifacts, backups and provider security records require separate operator retention controls.

Your choices and requests

AI photo processing is requested immediately before the first online identification or angle check; chapter AI processing is requested before sending a chapter title. Either can be declined and withdrawn in Settings. Withdrawal stops future server requests after the change is saved; it cannot recall an in-flight request. Disable location in Settings and revoke camera or location permission in device settings. Settings includes account deletion and export. Cloud deletion removes owned storage objects through the storage service and deletes account-linked records; linked Apple authorization must be revoked first. If deletion fails, the app reports the failure. Contact the operator for access, correction, deletion, an appeal of a content decision or applicable state privacy rights. Do not email passwords or sensitive photos.

Age and updates

Findmore is intended for US users aged 13 and older. An under-13 answer blocks setup before guest creation. Users under 18 confirm parent or guardian permission. On supported iOS versions, Apple age-range and regulatory signals are checked where applicable; an unavailable signal is not treated as verified adulthood. A required parental approval for a significant change blocks continuation until the proper approval is available. The manual age declaration and permission checkbox are not verified parental consent. Existing users must review changed policies. If you believe a child under 13 has submitted information, contact us so it can be investigated and removed.

Website early-access waitlist

When you join the Findmore waitlist, we collect your email address to manage early access and send a test link and setup instructions. This is separate from creating an app account. Signup requests are delivered to hello@findmore.app using our Google Workspace mailbox when email delivery is configured. We do not use waitlist emails for unrelated marketing. In local development previews, signups are saved only on the developer’s computer and the form states that email delivery is not active. You can ask us to remove your signup by emailing hello@findmore.app. Participation in the app test, rather than simply joining the list, qualifies for the limited Early Explorer badge.