Docs → Client policies

How we handle client data

What data we touch as your IT provider, the discipline around it, and what happens to it if we part ways. The legal terms live in the privacy policy.

Last updated: August 2026

At a glance

The discipline

What we touch, and why
Managing your systems means our tools and people can see business data — inherent to the work, not a choice. The choice is discipline: access limited to the task at hand.

What we never do
No selling client data. No mining it for unrelated purposes. No browsing out of curiosity — access leaves a trail, and the trail gets reviewed.

Vendors & subprocessors
Third-party tools that process your data get the same scrutiny we apply to anything we run ourselves. Ask for specifics about your environment — real answers beat generic lists.

If we part ways
Your data is yours. Offboarding hands back credentials, documentation, and data in usable form, and removes our access completely. No hostage-taking.

Note: this page is the plain-English tour. The authoritative terms are the privacy policy and your service agreement — where they differ, they win.

Common questions

Who at BetaBoxTS can see our data?+

The people working on your environment, to the extent the work requires — not the whole company by default.

Where do the legal commitments live?+

In the privacy policy and your service agreement. This page explains practice; those documents bind it.

Can we get a copy of everything you hold for us?+

Yes — documentation, configurations, and data come back in usable form on request, not just at offboarding.

Related docs

Security practices
The controls that keep the discipline honest.

Backup & restore
Where your data’s safety net lives.

Acceptable use
The plain-English rules on the client side.

Questions about a specific tool in your stack?
Ask — you get a real answer about your environment, not a generic list.