Data handling

Your customers never chose our software. You did.

The homeowner whose address, phone number and gate code sit in your account made a decision about you — not about a software company they have never heard of. That is the whole reason this page exists.

Every field-service tool holds the same uncomfortable pile: names, service addresses, phone numbers, what's wrong with the property, when nobody's home. Your customers handed that to you. It ended up in software because that is how you run the work now.

So the question worth answering isn't whether we take security seriously — everyone says that. It's narrower and more checkable: when your customers' details are in OrbitOps Pro, where else do they go? Mostly, nowhere. Here is the specific version of that.

One

Your books get totals, not your client list

Connecting your accounting is the moment where customer data most often leaves one system for another. In OrbitOps Pro, the QuickBooks Online integration posts a single summary journal entry for the month. Five lines, against the accounts you chose. This is the whole shape of it:

Summary journal entry — June 2026
Billings — June 2026DR 18,420.00
Revenue — June 2026CR 17,180.00
Sales tax payable — June 2026CR 1,240.00
Collections — June 2026DR 15,905.00
Collections applied — June 2026CR 15,905.00

A real entry, with the figures changed. The descriptions are exactly this literal — a month name and an account role.

What goes across

  • Four figures: revenue, sales tax, receivables, cash
  • The account ids you mapped them to
  • The period the entry covers

What doesn't

  • Customer names or contact details
  • Service addresses
  • Invoices and their line items
  • Anything identifying a single job or property

You trigger each post yourself; nothing is scheduled and nothing runs behind you. The only thing OrbitOps Pro reads back from your books is the chart of accounts, so you can pick where the figures land. Disconnecting deletes the stored connection outright.

Put plainly: your accountant gets a month's numbers. Your customers stay in your account, where they were.

OrbitOps Pro is an independent integration with QuickBooks Online. Included in Executive and Premier.

Two

Our own support console can't show us who your customers are

We run a platform admin console — the screen we use to see that a company is healthy, that visits are getting reviewed, that nothing is stuck. It shows counts, statuses and timestamps.

It does not show your customers' names, contact details, service addresses, map coordinates or service notes, and it does not show financial figures. Not because those are hidden in the page, but because those columns are never selected from the database. The information doesn't arrive at the console and get suppressed; it never leaves the server.

There is a single gate in the code through which any future "reveal this" feature would have to pass. Today that gate refuses every time it is called — revealing end-customer details isn't a permission that is switched off for us, it is a thing that isn't built. If it is ever built, it will be a deliberate decision with a consent step and an audit trail, not a checkbox someone finds.

Questions

The questions operators actually ask

Does connecting QuickBooks Online send my customer list to my accounting platform?

No. The integration posts one summary journal entry per month: debits and credits against the accounts you map, with descriptions like "Revenue — June 2026". No customer records, no invoices and no line items are sent. The only thing OrbitOps Pro reads back is your chart of accounts, so you can choose which accounts the figures post to.

Can OrbitOps Pro staff see my customers' names and addresses?

Not through our admin console. It is built so that end-customer names, contact details, addresses, coordinates and service notes are never selected from the database at all, along with every financial figure — so they never reach the console in the first place, rather than being fetched and hidden. Revealing them is not a setting that is switched off; it is not implemented.

Is my company's data separated from other companies'?

Yes. Every read and write is scoped to your organization on the server, and the database refuses direct connections from the public API keys outright — there are no policies granting that access, so it is denied rather than filtered. Route-level checks in the browser are treated as convenience, never as the boundary.

Do you sell or share my customers' information?

No. We do not sell personal information, we do not share it with third parties for their own marketing, and we do not use it for advertising. The providers that do process data on our behalf in order to run the service are listed in our privacy policy.

Whose data is it?

Your customers' information belongs to your business, and you decide what goes into OrbitOps Pro. We process it on your behalf to provide the service. If one of your customers asks what is held about them, that request goes to you, because you are the business that serves them.

Run your field business, not your software.

Create your account and get set up in your trade. Scheduling, invoicing and card payments are included in every plan.

Got a question this page didn't answer? Ask us directly — it'll be one of the two of us replying.

Email support@orbitopspro.com to chat with us.