Field OS Privacy Policy

Information we collect

• Company identity, industry, address, website, billing contact, requested user count, and administrator contact details.
• Account, profile, role, team, device preferences, authentication, billing status, and security-event information.
• Operational records entered by authorized users, including property, homeowner/contact, appointment, notes, disposition, outcome, communication, attachment, and location information.
• Technical, usage, performance, diagnostic, security, and statistical information generated when the Service operates.
• Payment-method display details and Stripe identifiers. Card numbers and security codes are entered directly into Stripe and are not stored in the Field OS database.

Customer Data and processing roles

Customer Data is information submitted to Field OS by or for a customer company. The customer keeps its rights in Customer Data and determines the business purposes for which its authorized users collect and use that information. Field OS generally acts as Customer’s service provider or processor when it handles Customer Data to provide the Service under Customer’s instructions.

Field OS independently determines how to process account, billing, security, support, legal-compliance, and Service Data for its legitimate operational purposes. Field OS does not treat Customer Data as its property merely because the data is stored or processed through the Service.

How information is used

We use information to provision and secure company workspaces, provide field-sales workflows, process subscriptions, deliver access and recovery emails, support users, prevent abuse, comply with law, and improve reliability.

We may use Service Data and aggregated or de-identified data that does not reasonably identify a customer or individual for lawful analytics, security, reliability, benchmarking, research, product development, service improvement, and business planning. We do not attempt to re-identify that data or use it to contact a customer’s prospects for Field OS marketing.

Company administrators control which authorized users operate in their company workspace. Access is also restricted by role and hierarchy.

Authorization, consent, and legal bases

A customer company authorizes and instructs Field OS to process Customer Data as described in the Terms of Service and this Policy. Depending on the information, purpose, and jurisdiction, Field OS processes personal information based on contract, legitimate interests, legal obligations, or consent where applicable law requires it.

Using the Service does not waive privacy rights that cannot legally be waived. When law requires a separate, specific consent or choice for a processing activity, Field OS or the customer responsible for that activity must obtain it rather than relying only on general acceptance of the Terms.

Service providers

Field OS uses service providers such as Supabase for authentication, database, and file storage; Vercel for application hosting; Stripe for payment processing; Mapbox for maps; and configured email, calendar, communications, and CRM providers. Each provider processes only the information required for its service and remains subject to its applicable contract and legal obligations.

Retention and security

Field OS uses encrypted connections, server-side authorization, company-scoped records, audit histories, restricted file access, monitored background queues, and independent backups. Personal profile information is retained while an account is active and is deleted or de-identified after a verified account-deletion request, subject to limited legal, security, billing, and fraud-prevention obligations.

Company-owned property, appointment, disposition, attachment, billing, export, and audit records can be retained in de-identified form so deleting one user does not erase another user’s or the company’s legitimate records.

Choices and account deletion

Users can correct their profile in User Settings and initiate permanent account deletion in User Settings → Help & Support or at the public Account Deletion page. Deletion removes the authentication login, profile contact data, recovery address, avatar, personal template media, and calendar connection. A Company Admin must transfer administration before leaving active company users without a billing administrator; when no active users remain, Field OS reconciles the company subscription before deleting personal account data.

For privacy requests that cannot be completed after sign-in, contact support from the login or verified recovery email. Field OS will honor applicable access, correction, deletion, restriction, objection, and other privacy rights subject to identity verification and lawful exceptions.

Questions

Contact Field OS at info@fieldos.pro.