Skip to content
← Back to Home

Privacy Policy

Last updated: 9 November 2026

This policy explains how SoloOp handles information in its mobile app, website, operator dashboard, client and accountant portals, and related services.

SoloOp's US service is operated by THE DU VERGIER FAMILY LLC.

For accounts in the United States, and for SoloOp Paid and US Bank Feeds, the company responsible for your information is THE DU VERGIER FAMILY LLC, a Delaware limited liability company. You can reach us at support@solo-op.com.

Information we handle

  • Accounts and business records: names, email addresses, phone numbers, business details, clients, jobs, schedules, quotes, invoices, expenses, notes and communications you enter or send.
  • Addresses and location: business and service addresses, route information, and device location when you enable a feature that needs it. The optional Auto Timer can use background location after you grant permission; you can turn it off in the app or revoke permission in device settings.
  • Contacts and images: contact details you choose to import, plus job, invoice, receipt, logo and import images you choose to add. SoloOp does not need your entire address book to use the core app.
  • Payments and banking: invoice and payment records, payout details you provide, and, where you connect a US bank feed, the institution name, masked account information, balances and transaction records needed for matching. Stripe processes card and bank connections; SoloOp also stores the business banking fields and connected-feed data needed to provide the features you use. SoloOp does not store your online banking password.
  • Usage and diagnostics: app events, device and app details, error reports and crash diagnostics used to operate, protect and improve the service.

Website visitors and forms

  • Page visits: when you view pages on solo-op.com, SoloOp records the page path, the referring page if your browser supplies one, your country as reported in the request headers, your browser's user-agent text, whether the visit looks automated, and the time. Clicks on the app download buttons are recorded the same way. This record does not include your name, email address or IP address. Dashboard, client portal, accountant portal, referral partner, invoice, receipt and unsubscribe pages are not recorded. We use these records for things like a daily traffic summary.
  • Contact form: the name, email address and message you type are emailed to a SoloOp support inbox through Resend so we can reply.
  • Referral partner applications: the name, email address and country you enter, plus a company name and message if you add them.
  • Referral partner dashboard: partners can see the business name, join date, account status, attributed earnings and last payment date for operators who signed up with their referral code.
  • Third-party resources: pages may load resources such as fonts, images or video from third-party or content-delivery servers. As with any web request, those servers can see your IP address and browser details.

With your permission, SoloOp measures your website journey using a random session identifier: campaign source, public pages visited, engagement, button and download clicks, signup steps and technical failure categories. We do not include names, email addresses, passwords or form contents in these events. Detailed first-party events are retained for 90 days. Signup confirmation can be linked when you return in the same browser; another browser or device may not be linked.

When you allow analytics, we also use Microsoft Clarity to understand interactions with public marketing pages through heatmaps and session recordings. Clarity is not loaded on signup, login, account, dashboard, invoice, payment or other private routes. It uses cookies and masked interaction data; advertising storage consent is denied. Microsoft processes this data under its Privacy Statement. Public-page recordings exclude form contents. We do not send customer records to Clarity.

You can decline analytics and still use SoloOp. Change your choice using “Analytics choices” in the website footer. We honour Global Privacy Control and Do Not Track signals. Browser settings and declined consent create gaps in journey reports; a download click is not proof of installation. Our existing basic page counter operates separately without a persistent visitor identifier.

Bank Feeds

United States

Bank Feeds is read-only. You connect your bank through Stripe Financial Connections, using Stripe's connection screen rather than a SoloOp form. SoloOp asks for permission to read balances and transactions only, and Bank Feeds cannot move money. SoloOp does not store your online banking password. You can disconnect a bank feed in the app.

What we keep, and for how long: while a bank feed is connected, SoloOp keeps the balances and transactions it receives so it can match them to your invoices. When you disconnect an account, when your SoloOp Paid plan ends, or when you delete your SoloOp account, SoloOp disconnects the account at Stripe and deletes its copy of the transactions and balances. A short record of the institution name, the last four digits of the account and the disconnect date is kept so your history can show that the account was disconnected. Bank Feeds data is stored in the United States project described under Where data is hosted below.

Australia

When you connect your business bank account to Australian Bank Feeds, your bank data is shared through our open-banking provider with Du Vergier Pty Ltd (ABN 36 703 412 837), trading as SoloOp, as the recipient. SoloOp uses it to match the payments your clients send by bank transfer to your invoices. The connection is read-only, so SoloOp cannot move money. You can stop sharing at any time by disconnecting your bank in the app.

Sending client emails from your Gmail

If you choose to connect your Gmail account in Settings → Payments → Send client emails from your Gmail, the emails SoloOp sends to your clients go out from your own Gmail address: invoices and quotes with the PDF attached, reminders, receipts, booking confirmations and other messages about their jobs and payments. This is optional; without it, SoloOp sends them from its own address. SoloOp's own emails to you, such as sign-in and billing, still come from SoloOp.

  • What SoloOp receives from Google: the Gmail address you connect, and a token that only allows sending email (Google's gmail.send permission). SoloOp cannot read, search, change or delete your email, and does not access your contacts or calendar.
  • How it is used: only to send your business's emails to your clients from SoloOp, as described above, including the reminders and receipts you have SoloOp send automatically. Nothing else is sent from your account.
  • How it is stored: the token is encrypted before it is stored, in your account's region (see Where data is hosted below). It is never sent to your phone or browser.
  • What we never do with it: SoloOp does not use information from your Google account for advertising, does not sell it, does not use it to train AI or machine-learning models, and does not transfer it to anyone except as needed to send the email you asked to send. People at SoloOp do not read it, except with your permission for support, for security, or where the law requires.
  • Disconnecting: tap Disconnect in the same setting and SoloOp deletes the stored token straight away. You can also remove SoloOp's access at any time from your Google Account at myaccount.google.com/permissions.

SoloOp's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

How we protect your Google data

SoloOp uses encryption and access controls to protect the confidentiality of the information it receives from Google:

  • Only the permission it needs: SoloOp asks only for Google's gmail.send permission, plus your email address so it can show which account is connected. It cannot read, search or delete your email.
  • Encrypted in transit: all data moving between your device, SoloOp's servers and Google travels over encrypted connections (HTTPS/TLS).
  • Encrypted at rest: SoloOp's database is encrypted at rest (AES-256) by its hosting provider. On top of that, the Google refresh token that lets SoloOp send on your behalf is separately encrypted with AES-256-GCM before it is stored, using a key held only in SoloOp's server-side secrets. The encrypted token is bound to your business, so it cannot be used for any other account.
  • Locked-down access: the table that holds the token cannot be read by the app or the website at all, only by SoloOp's server functions. No other SoloOp user, including your own staff, can see it.
  • Only what is needed: short-lived Google access tokens are used in memory for a single send and are never stored or logged. SoloOp keeps only the connected email address, the encrypted token and the IDs of the messages it sent; it does not keep copies of your mailbox.
  • You stay in control: you can disconnect at any time in SoloOp (Settings → Payments, or on the website), and disconnecting deletes the stored token immediately. You can also remove SoloOp's access at myaccount.google.com/permissions.
  • If something goes wrong: if we ever learned of unauthorised access to Google user data, we would stop using the affected tokens, notify affected users and Google, and take steps to fix the cause.

Text messages (SMS)

No mobile information will be shared with third parties or affiliates for marketing or promotional purposes. Text messaging originator opt-in data and consent will not be shared with any third parties.

The SMS program terms are at https://solo-op.com/sms.

How we use it

We use this information to run your account, schedule and route work, prepare and send documents, process payments, match bank activity when you enable Bank Feeds, provide support, detect errors and abuse, and send service messages. Product update emails can be unsubscribed from separately; invoices and account messages still need to reach you.

When you choose an AI feature, such as reading a receipt or client list or asking the help assistant, the content needed for that request may be sent to the AI provider used by that feature. Review imported or suggested results before saving them.

Connecting your own AI app

If you connect an AI app such as Claude or ChatGPT, you sign in to SoloOp and choose whether to grant the permissions shown on the consent screen. The connected app can request your business records within those permissions, including client details, jobs, schedules, invoices, notes, mileage and timer records. Information returned to that app is processed under that provider’s terms and privacy settings, and may be processed outside your SoloOp account’s hosting region.

Where you grant write permission, the app can add or edit clients and jobs, including recurring schedules. The connection does not permit payment actions, changing financial records or sending client or crew notifications. SoloOp enforces the permitted actions and account access on its servers. Your AI app’s separate connections to email or other services are managed by that app; connecting SoloOp does not give SoloOp access to those services.

SoloOp keeps connection records and change receipts so you can review activity and disconnect an app in Settings → AI integration. Disconnecting stops further access through that connection. It does not undo changes already saved or remove information already returned to the AI app; manage that information with the AI provider. SoloOp does not share your SoloOp password with the connected app.

Providers and sharing

We use Supabase for regional database and authentication services; Stripe for payments, connected accounts and US Financial Connections; Resend for email; Google (the Gmail API) to send emails to your clients from your own Gmail, only if you connect it; Google Maps Platform for address and route features; Cloudflare for routing; Expo for app delivery; and Sentry for crash reporting. AI features may use Anthropic or xAI. These providers receive only information needed for the service they provide and may process it outside your database hosting region.

When you use web address search, the address text you type, your business country and any saved location used to focus the search are sent to Google Maps Platform. Suggestions are temporary; a selected address and its confirmed routing point are saved only when you save the client or depot. Google's handling of that information is described in the Google Privacy Policy. You can enter an address manually instead.

Information you choose to send to a client, crew member, or accountant is shared with that recipient through the relevant SoloOp feature. We may also disclose information where required by law or to protect the service and its users. We do not sell customer lists to advertisers.

Where data is hosted

SoloOp uses separate Supabase projects for Australia and New Zealand, the United States and Canada, and the United Kingdom and Europe. Your account is assigned to a project during signup; the US marketing page does not move an Australian operator's records into the US project. Some support and external services may process data in other countries.

Storage, security and retention

The website uses local storage and essential session technologies to keep you signed in. The website's page-visit records are described under Website visitors and forms above. Access controls, encrypted transport and regional database permissions protect data, though no system can guarantee absolute security.

We keep account data while you use SoloOp. The in-app deletion flow removes the SoloOp account and linked business records when it completes. Payment providers, email providers and records subject to legal obligations may have separate retention duties. If you need details about a particular record, contact us.

Your choices and requests

You can review and update much of your information in the app and export available records from the dashboard. You can disconnect a US bank feed in the app, control device permissions in system settings, and delete your account through Settings → Delete account. See the account deletion page for steps and an alternative contact path.

To request access, correction or deletion, or ask a privacy question, email support@solo-op.com. Depending on where you live, additional privacy rights may apply. We may need to verify your identity before acting on a request.

Your US privacy rights

Depending on where you live in the United States (for example California, Colorado, Connecticut, Texas or Virginia, among other states with privacy laws), you may have the right to know what personal information we hold about you, to access and correct it, to delete it, to receive a copy of it, and to opt out of the sale or sharing of personal information and of targeted advertising. SoloOp does not sell personal information, does not share it for cross-context behavioral advertising, and the website has no advertising pixels.

To make a request, email support@solo-op.com. We may need to verify your identity first, and we will respond within the time your state's law requires. You will not be treated differently for making a request. If we decline a request, reply to ask us to reconsider, and you may also contact your state attorney general.

SoloOp is a business tool and is not directed at children under 18.

Changes

We may update this policy as the service changes. We will update the date above and give additional notice when a material change needs it.