Privacy Policy
Last updated: October 30, 2026
This policy describes what Infield collects, what happens to your voice notes and photos, who else processes your data, and how to get it out or delete it. Questions go to hello@tryinfield.com.
Two kinds of data
Account data is information about the person using Infield — name, email, phone number, role, and which company (“tenant”) they belong to. We decide how this is handled.
Customer content is everything created inside the product: companies, contacts, notes, voice transcripts, photos, deals, appointments, and comments. This belongs to the business that subscribes to Infield. We process it on their instructions and do not use it for our own purposes.
What we collect
Content you create. Notes typed, spoken, or photographed, the records they attach to, and comments and @-mentions on notes — in the mobile app or on the website.
Location. With your permission, the app (or your browser, on the website’s map) reads your device location to centre the map, to rank nearby search results, and to use as the starting point of a route. This is requested only while the map is open — Infield does not track location in the background, and your location is not stored. Addresses you save against a company are stored as coordinates so they can be shown as pins. When you ask for directions, the address is handed to Apple Maps or Google Maps, which you then use under their own terms.
Microphone. Only while you are recording a voice note, in the app or in your browser on the website. See below for what happens to the recording.
Photos and camera. Only images you deliberately take or pick to attach to a note, or scan as a business card or document. Photo-library access lets you choose existing photos; Infield does not scan or upload the rest of your library. A photo attached to a note, in the app or on the website, is stored with your company’s data, visible only to people in your company, and deleted when the note is deleted. Scanned business cards and documents are sent to our AI provider to read the text, and only the text is kept.
Device token. If you enable notifications, a push token for your device so we can deliver them — for example when a teammate @-mentions you or replies to your comment.
Website analytics. This website records aggregate visit and performance data, and uses Meta’s advertising pixel to measure our ads (see Advertising measurement). The mobile app contains no advertising or third-party tracking SDKs. Both the app and the website include a crash reporter, Sentry, which sends us error details when something breaks, without your name, email address, or IP address.
Creating an account. When you sign up we collect your name, work email, company name, how many people will use Infield, and, if you choose to give it, a phone number. We use it to create your workspace, to bill you, and to contact you about your account. Your password is handled by our authentication provider and never reaches us in a form we can read.
Payment details. Card details are collected and stored by Stripe, our payment processor, on their own systems. They never touch Infield’s servers and we cannot see them. We keep only what we need to run your subscription: a Stripe customer reference, your plan, seat count, and billing status.
What happens to a voice note
When you save a voice note, in the app or on the website, the recording is sent to a transcription provider (Groq, or OpenAI if Groq is unavailable), converted to text, and then discarded. Infield does not keep the audio file on its servers — only the transcript and the structured fields derived from it. Temporary copies created during processing are deleted as soon as the request finishes.
A recording made offline stays on your device. If you capture a voice note with no connection, the recording is held in the app’s private storage on your phone — it is the only copy of what you said — and the app retries the transcription on every sync. Once the transcript comes back, the recording is deleted from the device. It is also deleted when you remove the recording or the note, and every recording a device is holding is erased when you sign out. Audio is never uploaded to Infield for storage; it is sent only for transcription, at the moment it can be.
The transcript is then sent to an AI provider (OpenAI) that writes up the note — a summary, key details, to-dos, and upcoming meetings — and suggests people, companies, and follow-ups it recognises. Nothing it suggests is added until you accept it. Photos attached to a note are sent to the same provider to read any text in them, and it also writes the running summary shown on a company’s page from that company’s notes.
We do not train AI models on your data, and we do not build customer-specific models. Infield calls these providers through their business APIs, which do not use submitted content for model training.
Subprocessors
These are the companies that process data on our behalf. We will update this list before adding a new one.
| Provider | What it sees | Why |
|---|---|---|
| Supabase | Account details and the companies, contacts, notes, and voice transcripts you create in Infield | Database, authentication, and file storage (United States) |
| Fly.io | Voice recordings, note text, and note photos, while they are being processed | Running the Infield API that calls the transcription and AI providers (United States) |
| Groq | Voice recordings, at the moment you save a voice note | Speech-to-text transcription |
| OpenAI | Note text, photos attached to notes, scanned business cards and documents, and voice recordings when Groq is unavailable | Reading text out of photos and business cards, turning a transcript into structured fields, and transcription as a backup to Groq |
| Mapbox | Map coordinates for the area you are viewing, and the addresses and kinds of places you search for | Rendering the map, suggesting addresses as you type, and searching for nearby businesses |
| Expo | A push notification token tied to your device | Delivering push notifications |
| Vercel | Website visits, and sign-up details briefly in server logs | Website hosting and aggregate traffic analytics |
| Upstash | Your IP address or account ID, for at most 24 hours | Counting requests to sign up, open invitation links, and use connected AI apps, so they cannot be flooded |
| Resend | Name and email address | Delivering account and service email — sign-up confirmations, invitations, password resets, email-change confirmations, team and billing notices, and warnings before data is deleted |
| Sentry | Error and crash details from the website and the mobile app, with names, email addresses, and IP addresses left out | Alerting us when part of the website or app breaks, so we can fix it |
| Stripe | Name, email address, billing address, and payment card details | Processing subscription payments. Card details are held by Stripe and never reach Infield |
Apps you connect
Claude and ChatGPT. A company admin can allow Claude, ChatGPT, or both, under Settings. Each is off until an admin turns it on. Once it is on, a member can connect their own Claude or ChatGPT account to Infield. That assistant can then read the Infield data the member can see — companies, contacts, notes, appointments, and products — and add notes. It cannot edit or delete anything. What the assistant receives is handled by Anthropic or OpenAI under your agreement with them, not by Infield. An admin can switch an app off at any time, which cuts off its access for everyone in the company.
Google Calendar and Outlook. Where offered, you can connect your own Google or Microsoft calendar so the appointments you create in Infield appear there. Infield only adds, updates, and removes those appointments: their title, time, and description, the company’s name and address, and the contact’s name, phone number, and email. It does not read your other events. We keep the calendar account’s email address and an encrypted access token, which you can revoke by disconnecting in the app or in your Google or Microsoft account. Infield’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements: that information is used only to keep your calendar in step with Infield, is not used for advertising, is not sold, and is not used to train AI models.
Advertising measurement
Our website uses the Meta Pixel, from Meta Platforms, to measure how well our ads work. It records page visits and steps in sign-up, such as starting checkout, and Meta may link them to a Facebook or Instagram account you are signed in to. When a free trial starts and when a subscription is first paid, our servers also tell Meta, along with your email address, name, and phone number (each hashed before it is sent), your billing city, state, ZIP code, and country, and your IP address and browser details, so Meta can match the event to the ad that brought you. Meta uses this under its own terms and privacy policy. The mobile app does not use the Meta Pixel. You can block the pixel with your browser’s tracking protection or a content blocker, and manage how Meta uses it for ads in your Facebook or Instagram ad settings.
Who can see your data
Every record belongs to a tenant, and the database enforces that boundary on every read and write. Everyone on a team sees only their own company’s data, including connected apps acting for them. Data does not cross between tenants.
Infield staff do not browse customer content as a matter of course. Support access to a tenant’s data requires an explicit, time-limited support session, and every such access is written to an audit log.
Where it lives
Data is stored in the United States, encrypted in transit and at rest. If you are outside the US, using Infield means your data is transferred there.
Getting your data out, and deleting it
A company admin can export the company’s data at any time from the admin portal, under Settings — companies, contacts, deals, notes, comments, appointments, products, and team profiles, as a zip of CSV files. Uploaded product images and note photos are not included.
You can request deletion of your account from within the app, under your profile. Because accounts are provisioned by your employer, the request goes to your company’s administrator to action — it removes your credentials, profile, comments, @-mentions, push tokens, and personal goals. If you can no longer sign in, email us instead and we will coordinate it. The full list of what is removed and what your employer keeps is on Delete your account. Content you created on behalf of your employer is retained by that employer as their business record.
We keep data for as long as the subscription is active. When it ends, we email the company’s admins with the date their data will be deleted — 90 days later — and again a week before. If the subscription is not reactivated, we then delete or anonymise the customer content, unless we are required to keep it longer.
Your rights
Depending on where you live, you may have the right to access, correct, export, or delete your personal data, and to object to certain processing. Email hello@tryinfield.com and we will respond within 30 days. To remove your account and personal data specifically, see Delete your account. We do not sell personal information. The website and sign-up data described under Advertising measurement is shared with Meta to measure our ads, which some US state laws treat as “sharing” for cross-context behavioural advertising. To opt out of that, email us. Customer content — your companies, contacts, notes, and recordings — is never used for advertising.
Children
Infield is a workplace tool and is not directed to anyone under 16. We do not knowingly collect data from children.
Changes
If this policy changes in a way that materially affects how we handle your data, we will update the date above and tell account administrators before it takes effect.
Contact
Infield — hello@tryinfield.com