Privacy Policy

Privacy at a glance

Our full Privacy Policy is published in English below. This is a summary of its main points. If anything is unclear, or you want to exercise any of your rights, write to us in Spanish, French, Portuguese or German at privacy@fieldsignal.com and we will reply in that language.

Who we are. Fieldsignal LLC, a company registered in Wyoming, United States, at 30 N Gould St, Ste N, Sheridan, WY 82801. We decide how your personal information is used. Our representative in the European Union, appointed under Article 27 of the GDPR, is Prighter Group, whose primary location is in Spain. You may contact them instead of us at app.prighter.com/portal/15913182475. Our representative in the United Kingdom, appointed under Article 27 of the UK GDPR, is Prighter Ltd, 20 Mortlake Mortlake High Street, London SW14 8JN. You may contact them instead of us at the same address: app.prighter.com/portal/15913182475.

What we use your information for. To create and run your account, to store and sync the field records you create, to take payment, to provide support, to keep the service secure, and — only if you ask for it — to generate reports. We do not use your field data or your location for advertising, and we do not sell or share your personal information.

The four things you should know before you read further.

We collect precise location. Your GPS position is attached to the notes, photos and tracks you create. If you switch on live location sharing, your teammates can see where you are while it is running. That switch is off until you turn it on, and you can turn it off at any time.
Reports are generated by a third-party AI. When you ask for a report, the field data you select is sent to Anthropic to write it. Your data is not used to train AI models. Every other part of FieldSignal works without this feature.
If you belong to a team, your account owner can see what you create. They can access, export and delete the field data in the team's projects, including data you created. Ask them what your team's settings are.
Your data is stored in the United States, and we operate the company from Mexico. If you are in Europe or Brazil, that means your information leaves your country. We use the European Commission's Standard Contractual Clauses and equivalent safeguards to protect it.

Your rights. You can ask us for a copy of your information, correct it, delete it, receive it in a portable format, restrict or object to how we use it, and withdraw any consent you have given. You can also complain to your national data protection authority. We answer within 30 days — 15 days in Brazil, 20 days in Mexico — and if we say no, you can appeal.

How long we keep it. While your account is open. When you close it, there is a 60-day grace period in which you can restore it, then we delete your data from our systems within a further 30 days.

Cookies. Our website sets no cookies except those it needs to work. We use no advertising cookies and no tracking pixels.

This Privacy Policy explains what personal information Fieldsignal LLC collects when you use the FieldSignal mobile application and the fieldsignal.com website, why we collect it, who we share it with, and the choices and rights you have. It applies worldwide.

Please read it together with our Terms of Service. If you are a Team customer, our Data Processing Addendum also applies.

1. Who we are

Fieldsignal LLC ("FieldSignal", "we", "us") is a Wyoming limited liability company. We are the controller of the personal information described in this policy, except where section 9 says otherwise.

Postal address
Fieldsignal LLC
30 N Gould St, Ste N
Sheridan, WY 82801
United States

Privacy contact: privacy@fieldsignal.com
Security contact: security@fieldsignal.com
General contact: info@fieldsignal.com

Representative in the European Union (GDPR Article 27)

We have appointed Prighter Group, together with its local partners, as our privacy representative in the European Union. Our representative's primary location is in Spain.

You can contact our representative instead of us, or as well as us, about anything relating to how we handle your personal information, and you can use them to exercise any of your rights under the GDPR:

app.prighter.com/portal/15913182475

That page is operated by our representative rather than by us. If you use it to make a request, your request and the details you put into it are handled by our representative on our behalf, under a written agreement, and then passed to us. You can always write to privacy@fieldsignal.com instead if you would rather deal with us directly.

Supervisory authorities may also address our representative directly on all issues relating to our processing.

Representative in the United Kingdom (UK GDPR Article 27)

We have appointed Prighter Ltd, 20 Mortlake Mortlake High Street, London SW14 8JN, United Kingdom, as our privacy representative in the United Kingdom.

app.prighter.com/portal/15913182475

The Information Commissioner's Office may also address our representative directly on all issues relating to our processing.

Person in charge of personal data processing (Brazil, LGPD Article 41 — encarregado)
Guillermo Robles — privacy@fieldsignal.com. Communications may be sent in Portuguese, and we will reply in Portuguese.

If you are in Switzerland and wish to raise a data protection matter with us, please write to privacy@fieldsignal.com.

A note on language. This policy is published in English. We offer our app in Spanish, French, Brazilian Portuguese and German, and we are working to publish this policy in those languages too. Until we do — if anything here is unclear to you, write to privacy@fieldsignal.com in Spanish, French, Portuguese or German, and we will answer you in that language. Where the law that applies to you requires this information to be given to you in your own language, that law applies.

2. Scope of this policy

This policy covers:

the FieldSignal app on iOS and Android, including data you and your team capture in the field;
the FieldSignal website at fieldsignal.com, including the product-updates signup form;
our support and billing operations.

It does not cover the practices of Apple, Google, or any other company whose own privacy policy applies to your dealings with them. When you buy an individual subscription through the App Store or Google Play, Apple or Google is the seller and handles your payment under its own privacy policy.

3. Information we collect

3.1 Information you give us

Category	Examples
Account information	Name, email address, password (stored only as a hash), display name, optional profile photo, language preference.
Team information	Team name, your role and permissions, which team you belong to, and the administrative relationship between an account owner and team members.
Field data	Notes you type or dictate; photographs you take; checklist and inspection responses; drawings and annotations; project, site and visit names; time entries; corrective actions; sign-offs.
Location data	Precise GPS coordinates attached to notes, photos and tracks; recorded track logs; your live location shared with your team members, if you switch it on, which carries your phone's battery level and whether it is charging, shown to your team alongside your position; and your location at the moment you send a Field Check-In. A Field Check-In always includes your location and cannot be sent without it — telling your team where you are is what it is for. If you do not want to share your position, send an ordinary message instead.
Files you import	Shapefiles, GeoPDFs and other GIS files, and any logo or branding you upload for your reports.
Support and correspondence	What you tell us when you contact support, report a bug, or reply to us by email.
Marketing signup	Your email address, if you sign up for product updates on our website.

A note on dictated notes. When you dictate a note, your device converts your speech to text. We ask for that conversion to happen on your device. On iOS, and on Android 13 and later, it normally does. On earlier versions of Android, and on any device or language with no on-device speech model, the conversion is performed instead by Apple's or Google's own speech service, which means your recorded audio is transmitted to them for that purpose. That is your operating system's speech feature rather than ours; we do not control it, and we do not currently detect when it happens. If this matters to you, type the note instead. Separately from the conversion: the audio file we save is kept by us — on our servers and, as section 8 explains, on your phone — and we never send it to any other company.

A note on photographs of people. Field photographs often capture people who are not FieldSignal users — colleagues, contractors, someone walking past a site. We do not run face recognition and we make no attempt to identify anyone in a photograph. Where you are working as part of a team, your team decides how those images are used and is responsible for telling the people it photographs. If you appear in a FieldSignal photograph and want it dealt with, write to privacy@fieldsignal.com with enough detail to identify roughly where and when it was taken, and we will work with the team that holds it to remove the image or obscure your face.

3.2 Information we collect automatically

Category	Examples
Device and technical data	Device model, operating system version, app version, language and region settings, crash and diagnostic reports, and general connectivity state.
Usage data	Sync events and error logs, and — inside a crash report — a short trail of the kinds of actions that led up to the error, used to operate the app and fix faults. We do not use analytics tools to track how you use the app.
Activity and audit records	For team accounts, a record of changes made to shared field data: who changed what, and when. This exists so that a team can account for its own records.
Weather data	Weather conditions for the location and time of a field record. Your coordinates are cut down to four decimal places — roughly 11 metres — before they are sent, and they go to the US National Weather Service (for locations in the United States) and to Open-Meteo. Nothing identifying you accompanies them: no name, no account, no device identifier. Requests to the National Weather Service are made from your phone, so it also sees your phone's IP address, as with any internet request. Requests to Open-Meteo are made by our servers, so Open-Meteo sees our servers' address, not your phone's. When you search for a place, the words you type are sent to Open-Meteo, through our servers, to find it; its place names come from GeoNames.
Map requests	When the app loads map tiles, our map provider receives the coordinates being displayed and your IP address. That much is inherent in how internet mapping works. When you select certain public base layers, the same is true of the United States government map services that publish them.
Map images in reports	Where a report includes a map image, our servers request that image from Microsoft Azure Maps, which receives the coordinates of the area shown, the outlines and markers to be drawn on it, and the text of any labels you placed on the map. That request is made by our servers, not by your device, so Azure Maps does not receive your device's IP address or location. Azure Maps is listed on our sub-processor page.
Website analytics	Aggregate page-view statistics collected by Plausible Analytics. Plausible does not use cookies, does not store anything on your device, and does not create a cross-site profile of you. See section 10.

A note on map provider analytics. Mapping software commonly collects the device's own location, a session identifier and your IP address for the map provider's own analytics — separately from the tile requests described above. We have turned that collection off in the app, on both iOS and Android. If we ever turn it back on, we will update this policy and say so before it takes effect.

3.3 Information from others

Source	What we receive
Apple / Google	Confirmation that a subscription was purchased, renewed, or cancelled, and an anonymised transaction identifier. We do not receive your payment card details.
Stripe	For Team plans: billing contact details, billing address, tax identifiers, and the last four digits and brand of the payment card. We do not receive or store full card numbers.
Your team's account owner	If you are invited to a team, the account owner supplies your email address in order to send the invitation.

3.4 Information we do not collect

We do not ask for and do not want: government identification numbers relating to you as an individual, payment card numbers, health information, or information about children. Please do not put information of this kind into field notes or photographs.

On biometrics, because the honest answer needs a sentence rather than a word. We do not collect biometric identifiers: we do not create, extract or store a voiceprint, a faceprint, or any other template used to recognise a person. We do store the audio of the voice notes you record, and your field photographs may show people's faces. We do not analyse either of them to identify anyone, and we never use them to build a biometric template.

The one exception is a business tax identifier — a VAT number or equivalent — which we may need in order to invoice a Team plan correctly. We use it only for billing and tax compliance.

4. Why we use your information, and our legal bases

Where the GDPR, UK GDPR or LGPD applies, we rely on the legal bases set out below.

Purpose	Legal basis (GDPR / UK GDPR)	Legal basis (LGPD)
Creating and administering your account; providing the app and its features; syncing your data; storing your field records	Performance of a contract — Art. 6(1)(b)	Execution of a contract — Art. 7, V
Attaching precise location to records you create, and generating tracks	Performance of a contract — Art. 6(1)(b)	Execution of a contract — Art. 7, V
Keeping activity and audit records for team accounts	Legitimate interests — Art. 6(1)(f) — the team's interest in being able to account for its own records	Legitimate interests — Art. 7, IX
Sharing your live location with your team	Consent — Art. 6(1)(a), given in the app and withdrawable at any time	Consent — Art. 7, I
Taking payment, managing subscriptions, invoicing, and tax compliance	Contract — Art. 6(1)(b); legal obligation — Art. 6(1)(c)	Contract — Art. 7, V; legal obligation — Art. 7, II
Generating AI PDF reports from data you have entered, at your request	Performance of a contract — Art. 6(1)(b)	Execution of a contract — Art. 7, V
Providing support and responding to you	Contract — Art. 6(1)(b); legitimate interests — Art. 6(1)(f)	Contract — Art. 7, V; legitimate interests — Art. 7, IX
Keeping the service secure, preventing abuse, diagnosing faults, and maintaining backups	Legitimate interests — Art. 6(1)(f) — our interest in a reliable and secure service	Legitimate interests — Art. 7, IX
Understanding aggregate website traffic (cookieless)	Legitimate interests — Art. 6(1)(f) — our interest in knowing whether our website works	Legitimate interests — Art. 7, IX
Sending product-update emails you asked for	Consent — Art. 6(1)(a), withdrawable at any time	Consent — Art. 7, I
Complying with law, and establishing or defending legal claims	Legal obligation — Art. 6(1)(c); legitimate interests — Art. 6(1)(f)	Legal obligation — Art. 7, II; regular exercise of rights — Art. 7, VI

Where we rely on legitimate interests, we have considered whether those interests are overridden by your interests and rights. You may object to that processing — see section 11.

A note on location and consent. Several US state privacy laws — including those of Virginia, Colorado, Connecticut and Texas — treat precise geolocation as sensitive data that may not be processed without your consent. FieldSignal never captures location until you grant location permission through your device, and live location sharing is off until you switch it on. Wherever the law that applies to you requires consent for location, that permission and that switch are the consent, and you can withdraw either at any time.

We do not use your field data, your photographs, or your location to build advertising profiles, and we do not make automated decisions about you that produce legal or similarly significant effects.

5. AI-generated reports

When a report includes an AI-written summary, FieldSignal sends part of the visit's data to Anthropic PBC, whose Claude models write the summary. The summary is returned to the app and placed in your PDF.

What is sent:

the project name, the project's location name, and the visit's title, date and duration;
the text of the visit's notes, including the text of any voice notes dictated, because a voice note becomes part of the written record it belongs to. On a shared team visit, this includes notes added by other members of the team. Authors' names are not sent;
the weather recorded with the visit;
totals only: how many notes, voice notes, photographs and drawings the visit has; for each checklist, how many items were answered, passed and failed; and the distance covered and the number of points in the route;
who the report is for and what it should focus on, if you filled these in.

What is never sent: the visit's photographs, voice recordings and individual checklist answers, and the coordinates of its records or its route.

Three things you should know:

Your data is not used to train AI models. Anthropic's commercial terms do not allow it to train its models on what we send. This is a contractual commitment we rely on. Anthropic's stated practice is to delete what we send within 30 days, unless it needs to keep it longer to enforce its usage policy or to comply with the law.
Notes are sent exactly as they were written. We cannot filter them. If you or a teammate typed a place, a person's name or anything else into a note, it goes with the note. The same applies to the project, location and visit names, and to what you type about who the report is for.
AI output can be wrong. Reports are a drafting aid. Review a report before you rely on it or send it to a client. See our Terms of Service for the applicable disclaimer.

If you do not want your data processed this way, do not use the AI summary. Field Observations reports never include one, and every other part of FieldSignal works without it.

6. Who we share information with

We do not sell your personal information. We share it only as described here.

Sub-processors. We use the service providers listed on our Sub-processors page to host, transmit, process and support the service. Each is bound by a written data processing agreement that restricts them to processing on our instructions and requires appropriate security. The sub-processors page names each provider, what it does, and where it processes data. We keep that page current.

Your team. If you belong to a team, other members of that team can see the data you contribute to shared projects, according to the permissions your account owner sets. Your account owner can access, export and delete the field data created in the team's projects, including data you created. If you switch on live location sharing, team members with the relevant permission can see your current location while it is active. If this matters to you, ask your account owner what your team's settings are before you capture anything personal.

Apple and Google. For individual subscriptions, Apple and Google act as the seller and process your purchase under their own terms and privacy policies. For push notifications, Apple and Google carry the message to your device.

When you email a report. A finished report is a document, and the coordinates of the photographs and records inside it are embedded in that document at full precision. If you email a report from FieldSignal it leaves as an attachment through our transactional email provider, named on the Sub-processors page — so that provider handles the report, and the location data inside it, in order to deliver it. If you would rather it did not, download the report and send it yourself.

Professional advisers, and business transfers. Our accountants and lawyers, under a duty of confidentiality. If FieldSignal is ever sold or merged, your information may transfer to the acquirer, who would remain bound by this policy or give you notice of a materially different one.

Law and safety. We may disclose information where we are legally required to, or where it is necessary to establish, exercise or defend legal claims, or to protect the rights and safety of any person. If we receive a government or law enforcement demand for your data, we will notify you unless we are legally prohibited from doing so.

We do not disclose your personal information to advertising networks, data brokers, or analytics companies that would use it for their own purposes.

7. International transfers

FieldSignal is operated from Mexico and our infrastructure is located primarily in the United States. If you are in the European Economic Area, the United Kingdom, Switzerland or Brazil, your personal information will be transferred outside your country.

Two providers carry most of it. Your account and field data are stored by Supabase, on Amazon Web Services, US West. Our website and the server-side functions behind it run on Vercel, whose primary processing facilities are in the United States and whose terms reserve the right to process data in other countries. The Sub-processors page records, for each provider, where it processes data and on what basis.

We rely on the following safeguards:

Standard Contractual Clauses. Our agreements with sub-processors that receive EEA, UK or Swiss personal data incorporate the European Commission's Standard Contractual Clauses (Decision 2021/914), with the UK International Data Transfer Addendum where the UK GDPR applies.
Brazil. Transfers out of Brazil are made on the basis of standard contractual clauses under LGPD Article 33, II(b), in the form approved by ANPD Resolution CD/ANPD No. 19/2024.
Supplementary measures. Data is encrypted in transit and, on our servers, at rest; access is restricted and logged, and we will challenge any overbroad government request we consider unlawful.

Access from Mexico. FieldSignal is operated from Mexico, and our own personnel there access personal information in order to run and support the Service. This is us handling your information ourselves — it is not a disclosure to another company, so the contractual clauses described above, which govern our sub-processors, are not the thing that governs it. What governs it is this policy, the security controls in section 14, and the fact that we remain the controller and remain subject to the law that protects you wherever we happen to work from. That access is limited to what operating and supporting the Service requires. We tell you because you are entitled to know where the people handling your data actually are, not only where the servers are.

You may request a copy of the relevant safeguards by writing to privacy@fieldsignal.com.

8. How long we keep information

What	How long
Account information	For as long as your account is open. When you close it, a 60-day grace period applies during which you can restore it. After the grace period, we delete your account information from our live systems within a further 30 days — so 90 days from closure at the outside. Asking us to erase your information is different from closing your account, and is not held for the grace period — see section 11.
Field data (notes, photos, checklists, locations, imports)	Same as account information: 60-day grace period, then deleted from live systems within a further 30 days.
Deleted documents	When you delete a document from a project, it is removed for everyone on the project at once. The file we store is erased within 30 days.
Voice recordings on your phone	When a dictated note is saved with its audio, the app keeps a copy of the recording on your phone as well as sending it to our servers. That copy stays for as long as the note is on your phone. There is no way in the app to delete a recording and keep its note: to remove a recording, delete the note. When you delete a note, the copy on your phone is not always removed at once — it can remain for a time, in particular if the note was deleted on another device, or the app was restarted before the deletion reached our servers. Signing out does not remove recordings already on your phone. Deleting the app removes them. If your phone backs up app data — for example to iCloud or Google — that backup may include these recordings.
Data on an account that reverts to the free tier	Nothing is deleted. Your data stays for as long as the account is open; only access to paid features stops.
Activity and audit records	The activity ledger keeps its entries — it is how a team accounts for its own field records, so its entries are not removed when a member leaves or closes their account, and each entry keeps a reference to the person who made it. An audit record that can be un-authored is not an audit record. The one thing we clear from an entry is the name of a deleted document's file, when that file is erased (see "Deleted documents" above); the entry, its author and its time remain. Everything else about that person is deleted as described below. The ledger itself goes when the team account closes.
Live location positions	Deleted when you stop sharing. In practice a position exists for minutes: the positions for a sharing session are erased the moment the session ends, whether you end it yourself or it times out. A backstop job removes anything those routes miss. Nothing is recorded at all when sharing is off.
The record that you shared	Separately from the positions themselves, we keep a record that a sharing session happened — who shared with whom, and when it started and ended. That record is not a location history and contains no positions. It is kept for as long as the team account is open, and is deleted with the team's data.
Team data after a member leaves	Field data the member created stays with the team; the member's account information is removed from the team.
Field Check-In records	A check-in is a message to your team, and it stays with the team that received it for as long as that team account is open — including the location it carried, because that was the content of the message. If you close your account, your name is removed from check-ins you sent but the check-ins themselves remain with your team.
Billing and tax records	Seven years, or longer where tax law requires. These survive deletion of your account — tax and accounting law requires us to keep them — reduced to what those laws actually need.
Support correspondence	Kept while we deal with your matter and for a reasonable period afterwards, so that we can pick up a follow-up from you, and then deleted. We do not keep it indefinitely.
Crash and diagnostic reports	Held by our error-reporting provider for 30 days, then deleted automatically.
Backups	Our database is backed up once a day and each backup is kept for 7 days. So information deleted from the live service stops existing in any backup within a week of that deletion. Your files — photographs, voice recordings and anything you imported — are not held in database backups at all. And we do not restore deleted data: if we ever have to rebuild the service from a backup, we re-run the deletion for every account that was deleted before that backup was taken.
Marketing signup	Until you unsubscribe, plus a suppression record so we do not email you again.

You can delete individual records at any time in the app, and you can delete your whole account from Settings.

9. When we are a processor, not a controller

For Team and Enterprise customers, the customer organisation is the controller of the field data its members create, and FieldSignal acts as a processor on that organisation's instructions. In that case, our Data Processing Addendum governs, and requests from individual team members about that data should be directed to the customer organisation. We remain the controller of account, billing and technical data in all cases.

10. Cookies and similar technologies

The FieldSignal website sets no cookies other than those strictly necessary for the site to function. We do not use advertising cookies, tracking pixels, or third-party analytics cookies, and there is therefore nothing for you to consent to or opt out of.

Our website analytics provider, Plausible Analytics, is cookieless by design: it stores nothing on your device, sets no identifier, and does not track you across websites. It reports aggregate figures only.

We also host our own fonts, images, scripts and stylesheets rather than loading them from third-party content delivery networks. This matters more than it sounds: a page that pulls a font or a script from someone else's server hands that server your IP address whether or not any cookie is involved. Ours does not.

The FieldSignal app does not use cookies. It stores data locally on your device so that it works offline. You can remove that data by deleting the app.

Do Not Track. Our website does not behave differently in response to a Do Not Track browser signal, for the simple reason that we do not track you across websites in the first place. There is nothing for the signal to switch off.

If we ever introduce non-essential cookies or advertising technologies, we will publish a cookie notice and a consent mechanism, obtain your consent before any such technology runs, and update this policy with a new version number before doing so.

11. Your rights

Subject to the law that applies to you, you have some or all of the following rights:

Access — a copy of the personal information we hold about you.
Correction — to have inaccurate information corrected.
Deletion — to have your information deleted.
Portability — to receive your information in a structured, machine-readable format, and to have it sent to another provider where technically feasible.
Restriction — to have our use of your information limited while a dispute is resolved.
Objection — to object to processing based on legitimate interests, including on grounds relating to your particular situation.
Withdrawal of consent — at any time, without affecting processing already carried out. Withdrawing consent to live location sharing, or unsubscribing from product updates, takes effect immediately.
Complaint — to lodge a complaint with your supervisory authority. In the EEA, that is the authority in your country of residence, work or the place of the alleged infringement; in the UK, the Information Commissioner's Office; in Brazil, the ANPD; in Mexico, the Secretaría Anticorrupción y Buen Gobierno.

Three things to know about deletion, because "delete" is not the whole story.

Asking us to erase your information is not the same as closing your account. Section 8 describes a 60-day grace period after you close your account, during which you can restore it. That period exists for your benefit — so that a mis-tap does not cost you your work — and it is not a waiting period we impose on your rights. If you ask us to erase your personal information, rather than simply closing your account, we act on that request straight away and do not hold it for the grace period, subject only to the exceptions described in section 8 and below. So tell us which you want. If you close your account in the app without saying anything, we treat that as a closure, and the grace period applies.

Your work does not vanish from your team. If you delete your account or leave a team, we delete your personal information — your profile, your contact details, your account itself. But the field records you created inside a team's projects stay with that team, with your name removed and replaced by a "Former Member" label. Your employer or client keeps the inspection you filed; it simply stops being attributed to you. We do it this way because the alternative is deleting a team's operational records without its knowledge. One related exception: your team's activity ledger keeps a reference to you as the author of the entries you made, for the reason given in section 8.

We will not delete your account while it would take other people's work with it. That happens if you own a team that still has other members, or a project in which someone else has added work or has a visit scheduled. The app lists each one and what to do about it: for a team, transfer ownership to another member in Teams; for a project, contact us and we will help you resolve it. Once nothing is in the way, you can delete your account. This does not limit your right to have your personal information erased: write to privacy@fieldsignal.com and we will act on it as described above.

Automated decision-making. We do not make decisions about you solely by automated means that produce legal or similarly significant effects.

How to exercise your rights

Write to privacy@fieldsignal.com. You may also delete your account, export your data, and change your location-sharing settings directly in the app.

We will acknowledge your request and respond within 30 days — or sooner where the law that applies to you requires it, which means 15 days in Brazil and 20 days in Mexico. Where a request is complex, we may extend that period as the applicable law allows and will tell you if we do. We do not charge for responding, unless a request is manifestly unfounded or excessive.

If we say no. If we refuse a request in whole or in part, we will tell you why. You may appeal that decision by replying to it, or by writing to privacy@fieldsignal.com with "Appeal" in the subject line. A different outcome is possible on appeal, and we will respond within 45 days. If we refuse again, we will tell you how to complain to your supervisory authority or state Attorney General.

We may need to verify your identity before acting on a request — usually by confirming you control the email address on the account. We will not ask you for more information than we need to do that.

Authorised agents. If someone makes a request on your behalf, we will ask for proof that you authorised them.

12. Notice to residents of California and other US states

This section supplements the rest of this policy for residents of California, and applies equivalently to residents of other US states with comprehensive privacy laws.

We do not sell or share your personal information

FieldSignal does not sell personal information, and does not share personal information for cross-context behavioural advertising, as those terms are defined in the California Consumer Privacy Act. We have not done so in the preceding 12 months. Because we neither sell nor share, we do not display a "Do Not Sell or Share My Personal Information" link, and we have nothing to opt you out of. We do not knowingly sell or share the personal information of anyone under 16.

Categories of personal information

We collect, and expect to collect over any 12-month period, the following categories, as defined by the CCPA. Each is collected from you, your device, your team's account owner, or our payment providers, for the business purposes described in section 4, and disclosed only to the recipients described in section 6.

CCPA category	Collected?	Examples
Identifiers	Yes	Name, email address, account identifier, IP address
Customer records (Cal. Civ. Code § 1798.80(e))	Yes	Name, billing address, business tax identifier, and the last four digits and brand of a payment card, for Team plans
Protected classification characteristics	No	—
Commercial information	Yes	Subscription plan, purchase and renewal records
Internet or network activity	Yes	App usage and diagnostic data, activity and audit records, aggregate website statistics
Geolocation data	Yes	Precise GPS coordinates, tracks, live location
Audio, electronic, visual information	Yes	Field photographs; voice notes — both the recording and the text it is converted to
Professional or employment information	Yes	Your role within your team
Sensitive personal information	Yes — precise geolocation only	See below
Biometric information	No	We store voice recordings and photographs, but extract no voiceprint, faceprint or other identifying template from them — see section 3.4
Education information	No	—
Inferences / profiles	No	We do not create profiles about you

Sensitive personal information

Precise geolocation is "sensitive personal information" under the CCPA. We use it only to provide the service you asked for — attaching a location to your records, drawing your tracks, and sharing your live location with your team when you switch that on. We do not use or disclose it to infer characteristics about you. Under Cal. Code Regs. tit. 11 § 7027(m), that use does not trigger the right to limit, and we therefore do not display a "Limit the Use of My Sensitive Personal Information" link.

Your California rights

You have the rights to know, access, correct, delete, and obtain a portable copy of your personal information, and the right not to be discriminated against for exercising them. We offer no financial incentives. Exercise your rights at privacy@fieldsignal.com or in the app. We honour Global Privacy Control and other opt-out preference signals; because we do not sell or share, such a signal requires no change to how we treat your data.

Retention

We do not retain personal information for longer than reasonably necessary for the purposes in section 4. Section 8 sets out our retention periods.

Shine the Light

California Civil Code § 1798.83 permits residents to request information about disclosures to third parties for their direct marketing purposes. We make no such disclosures.

13. Notice to users in Mexico (Aviso de Privacidad)

Fieldsignal LLC, at the address in section 1, is the responsable for the personal data described in this policy. The data we collect, the purposes for which we use it, and the third parties with whom we share it are set out in sections 3, 4 and 6.

Purposes requiring your express consent: sharing your live location with your team members. All other purposes described in section 4 are necessary to provide the service and do not require separate consent.

You may exercise your ARCO rights — acceso, rectificación, cancelación y oposición — and revoke your consent, by writing to privacy@fieldsignal.com. We will respond within the period required by law. You may also lodge a complaint with the Secretaría Anticorrupción y Buen Gobierno.

14. Security

We protect your information with encryption in transit (TLS) and, on our servers, at rest; row-level security that isolates each team's data at the database layer, access controls and logging for the small number of people who can reach production systems, and regular backups. The copy of your data kept in the app on your phone is not separately encrypted by FieldSignal; it relies on your phone's own lock and storage security.

No system is perfectly secure. If we become aware of a breach affecting your personal information, we will notify you and the relevant supervisory authorities as and when the law requires. Please report any suspected vulnerability to security@fieldsignal.com.

15. Children

FieldSignal is a professional tool for adults. Our Terms of Service require you to be at least 18. It is not directed to children, and we do not knowingly collect personal information from anyone under 18. If you believe a child has given us personal information, write to privacy@fieldsignal.com and we will delete it.

16. Changes to this policy

We will update this policy as the service changes. When we make a material change, we will increase the version number at the top of this page, update the effective date, and — where the law requires or the change is significant — notify you in the app or by email before it takes effect. Continued use after a change takes effect means you accept the updated policy. Previous versions are available on request.

17. How to contact us

Purpose	Address
Privacy questions and data subject requests	privacy@fieldsignal.com
Security reports	security@fieldsignal.com
Everything else	info@fieldsignal.com

Fieldsignal LLC · 30 N Gould St, Ste N, Sheridan, WY 82801, United States