Your records stay on your phone.

FieldSee has no accounts or ads. This page explains what the FieldSee apps and fieldsee.com send, what we keep, and which service providers receive data, including text-recognition diagnostics.

What stays on your phone

Your records stay on your phone: label photos, the brand, model, and serial numbers you check, documents you add, notes, contacts, and reminders. They live in the app's private storage, and deleting a record or the app deletes them. We never see them.

What the app sends, and why

The first photo of each item, made smaller, once you say yes to Identify with AI. The app asks when it first opens, before it sends anything to the AI, and you can change your answer in Settings. Our server asks an AI model on Amazon Bedrock, run by Amazon Web Services, what the item is and where its label usually is. The photo can show whatever you point the camera at, such as an appliance, a document, or a medicine label. We do not store it, and Amazon does not use it to train models. The text your phone reads from the photo stays on the phone. A photo whose text shows a password, a key, or an access code, a payment card or bank account number, or an identity document is never sent, and neither is one whose text the phone could not read.
A brand and model, when the app looks up a manual. Our server searches the web for the owner's manual and the support page; the search engines see our server, not your phone.
Longer voice requests, as text. Your speech becomes text on your phone when it can; otherwise Apple's or Google's speech service does it, under their terms. Short commands are handled on the phone. A longer request is sent as text, with what the screen shows, so our server can work out what you asked. We do not store it.

Turn off Identify with AI in Settings and every photo stays on your phone; voice then understands only short commands. Settings, under What leaves the phone, says the same.

The headset app

FieldSee for Meta Quest 3 and 3S does not upload camera images, recognized text, or saved records to FieldSee or Google. Its records stay on the headset, in the app's private storage, and deleting a record or the app deletes them. Google's text-recognition SDK sends diagnostic and usage metrics as described below.

Read a label uses the headset's passthrough camera, only while that screen is open and only after you allow it. Each picture is read on the headset, in memory, and thrown away; only the model, the serial number, and the maker it reads are kept, and only when you save them. It does not read identity documents or payment cards.
Stickers: with scene access, which you allow when the app opens, the headset looks for printed FieldSee stickers so a record can show beside its sticker. That data stays on the headset.
Your phone: records you mark Show on glasses in the phone app go straight from your phone to your headset over your home Wi-Fi, after a one-time pairing code. They never pass through a server.

The headset app keeps its own technical log on the headset, with counts and states but no record text, so problems can be found. FieldSee does not upload this log automatically. Meta's own terms and privacy policy cover the headset itself and the Meta Horizon Store.

Google text-recognition diagnostics

The Android phone and headset apps use Google ML Kit to read text on the device. ML Kit does not send its input images, recognized text, or results to Google. It does send diagnostic and usage metrics, including device and app information, an identifier for the app installation, processing times, image format and dimensions, and feature events and errors. Google uses these metrics to operate and improve ML Kit and detect misuse. The metrics travel over HTTPS. See Google's ML Kit privacy terms and Android data disclosure for details.

What we keep

Our server keeps short technical logs: the time, the type of thing it identified and, for equipment only, its brand (never the name of a medicine), the kind of voice command, the brand and model searched, and the network address of each request. We use them to keep the service working and to stop abuse, and they are overwritten as they rotate. Network addresses are also used briefly, in memory, to limit how many requests one address can make.

The website

The waitlist form keeps your name, email, and use case on our server so we can write to you about FieldSee; our backups hold a copy. To be removed, email [email protected]. Cloudflare delivers the site and protects it, and sees the network address of each visit.

Who else sees data

Amazon Web Services, which runs the AI model that identifies a first photo.
Search engines, which see the brand and model our server searches for.
Apple or Google, when your phone cannot turn speech into text on its own, and as the app stores.
Google, for ML Kit diagnostic and usage metrics from text recognition in the Android phone and headset apps. These metrics do not include the images, recognized text, or recognition results.
Cloudflare, for the website.
Meta, as the maker of the headset and the Meta Horizon Store, under Meta's terms. The headset app sends it none of your records.

We do not sell data, share it for advertising, or link it to you: there is no account to link it to.

Children

FieldSee is not directed to children under 13, and we do not knowingly collect their data.

Security

Everything the app sends to our server travels over HTTPS. Your records stay in the app's private storage on your phone.

Changes and contact

When this policy changes, we update this page and its date. Questions, or a request about your data: [email protected].