Privacy Policy

1. Who we are

OmniOps ("OmniOps," "we," "us," or "our") provides software for field-service and home-service businesses—including scheduling, CRM, quotes, invoices, payments, communications, and related tools (the "Service").

This policy applies to visitors of our websites (including getomniops.com), users of the OmniOps web application, users of the OmniOps mobile applications, and, where applicable, end customers who interact with features such as payment links or a customer portal operated for a contractor account.

Contact for privacy requests: hello@getomniops.com. General support: hello@getomniops.com.

2. Information we collect

2.1 Information you provide

• Account data: name, email, phone, password, company name, role
• Business data: business address, branding, settings, team members
• Customer & job data you enter: customer names, contact info, addresses, job notes, schedules, quotes, invoices, photos, files, and messages
• Payment & billing data: subscription billing details and payment method information processed by Apple or Stripe, and purchase records validated through RevenueCat (we do not store full card numbers on our servers)
• Communications: emails, in-app messages, and support requests you send us
• Optional device permissions: camera, photos, microphone, contacts, and location when you enable those features in the mobile app

2.2 Information collected automatically

• Device and browser type, OS, app version, IP address
• Usage data (pages/screens viewed, features used, approximate timestamps)
• Diagnostic data such as crash reports and performance metrics via Sentry, including device/installation identifiers. When you are signed in, these reports include your OmniOps account ID and are linked to your account for troubleshooting and reliability analysis. They are not used to track you for advertising.
• Cookies and similar technologies — see our Cookie Policy
• Location data when you grant permission (for maps, job locations, routing, or dispatch features)

2.3 Information from third parties

• Apple and RevenueCat (App Store purchase and subscription records)
• Stripe (payment status, fraud signals, Connect account status)
• Email/SMS providers when delivering messages you send through the Service
• Map and places providers when you use address search or maps
• Optional integrations you connect (e.g. accounting or advertising tools)

3. How we use information

We use information to:

• Provide, operate, secure, and improve the Service
• Create and manage accounts, workspaces (orgs), and team permissions
• Process Apple or Stripe subscriptions, validate App Store access through RevenueCat, and enable customer payments via Stripe
• Send transactional messages (receipts, invites, job updates, password resets)
• Provide support and respond to requests
• Monitor reliability, prevent abuse/fraud, and enforce our Terms
• Comply with law and respond to lawful requests
• Send product updates or marketing only where permitted (you can opt out of marketing)
• Power AI features you choose to use — see section 5, which sets out exactly what is sent, to whom, and what it is used for

4. How we share information

We do not sell your personal information. We share data only as needed:

• Service providers (subprocessors): hosting, database, email (e.g. Resend), SMS (e.g. Twilio), payments and subscription validation (Apple, Stripe, RevenueCat), maps, error monitoring (Sentry), and AI providers when you use AI features (see section 5). See our Subprocessor List.
• Your customers / public links: when you send invoices, quotes, portals, or payment links, the content you choose to share is delivered to those recipients
• Team members: users you invite into your organization can access org data according to their roles
• Legal & safety: if required by law, or to protect rights, safety, and security
• Business transfers: in connection with a merger, acquisition, or asset sale, with notice where required

5. AI features

Some parts of OmniOps are powered by AI models operated by third parties: the Omni assistant, the AI receptionist, voice input, and the features that draft a message, read a receipt photo, or suggest add-ons on a quote.

5.1 We ask before we send

The mobile app asks for your permission before it sends anything to an AI provider, and names what will be sent and who will receive it at the moment it asks. Nothing is sent until you allow it. You can withdraw that permission at any time in the app under Settings → Omni; the rest of OmniOps continues to work without it.

5.2 Who receives it

OpenAI, L.L.C. and Anthropic PBC, both in the United States. Voice input is transcribed by OpenAI.

The optional Jev routing pilot asks for separate permission before sending your current question and earlier requests needed for follow-ups to TypeSafe AI to choose tools. These can include names and other details you type. Tool results, photos and audio are not sent to TypeSafe by this pilot. Select Normal in Jev pilot to stop using TypeSafe; the choice also resets when the app restarts.

5.3 What is sent, and how it is collected

Only what the feature needs in order to answer: the question or instruction you type or speak, and the records it refers to, read from your organization's own data in the Service. In practice that is:

• Customer names, phone numbers, email addresses, service addresses and free-text notes
• The jobs, quotes, invoices and messages attached to those customers
• Photos you ask a feature to read, such as a receipt or a job site
• Recorded audio, when you use voice input

This data is not anonymized. Records are sent as they are stored. We do not de-identify, tokenize or redact them first.

5.4 What it is used for

Producing the response you asked for — an answer, a draft, a transcript, a suggestion — and nothing else. We do not use it to build advertising profiles, and we do not sell personal information.

5.5 Protection

Each AI provider acts as our subprocessor and processes this data only on our instructions, under written terms requiring confidentiality and security protections equivalent to those described in this policy. Each is listed — with the categories of data it receives, its location, and its compliance certifications — on our Subprocessor List.

6. Payments

iOS in-app subscriptions are processed by Apple, with RevenueCat validating purchase records and subscription access using your workspace identifier. Web subscriptions and customer card payments are processed by Stripe. Card data is handled by the payment provider under its privacy policy. We receive purchase and subscription status, billing identifiers, and, for Stripe payments where applicable, card brand and last four digits. User and account identifiers remain linked to these records for billing and app functionality.

7. Mobile app permissions

Depending on features you use, the mobile app may request:

• Location — job maps, routing, dispatch context
• Camera / photos — job photos, attachments, profile/branding
• Microphone — voice features if enabled
• Contacts — optional import of customer contacts
• Notifications — job and message alerts

You can deny or revoke permissions in device settings; some features may not work without them.

8. Data retention

• Account and business data: while your account is active and as needed to provide the Service
• After closure: we may retain limited data for a short period for recovery, then delete or anonymize, subject to legal holds
• Financial/tax records: retained as required by law (often several years)
• Backups and logs: retained for a limited operational period

To delete your account, open Settings → You → Delete account in the OmniOps app. You can also request deletion by emailing hello@getomniops.com.

9. Your rights

Depending on where you live (including GDPR and CCPA/CPRA regions), you may have rights to access, correct, delete, export, or restrict certain processing of personal information, and to opt out of certain uses. Contact hello@getomniops.com. We may need to verify your request.

If you are an end customer of a contractor using OmniOps, that contractor is typically the controller of your customer record. You may also contact them directly; we can assist where appropriate.

10. Security

We use administrative, technical, and organizational measures designed to protect information (including encryption in transit, access controls, and monitoring). No method of transmission or storage is 100% secure.

11. Children

The Service is directed to businesses and adults. We do not knowingly collect personal information from children under 13 (or under 16 where applicable). If you believe a child provided data, contact us and we will take appropriate steps.

12. International transfers

We may process data in the United States and other countries where we or our providers operate. Where required, we use appropriate safeguards for cross-border transfers.

13. Changes

We may update this policy from time to time. We will post the updated version with a new "Last updated" date and, for material changes, provide additional notice when appropriate.

14. Contact