Docs → Client policies

Acceptable use — the plain-English version

What the Acceptable Use Policy means in practice. The authoritative text is the Acceptable Use Policy itself — this page is the readable tour.

Last updated: August 2026

At a glance

The short version

Nothing illegal — Do not use systems we manage for anything against the law — full stop.

Own accounts only — Every person gets their own credentials. Temps included — accounts take minutes to create and seconds to shut off.

Controls stay on — Do not switch off or work around security controls. If one is slowing you down, ask — friction is often fixable without touching protection.

Speak up early — Tell us when something looks wrong. Nobody has ever been in trouble for reporting too soon.

Why it matters

Protections are collective
Most controls only work if they stay on for everyone. One shared password quietly undoes work that protects the whole company.

Compliance rides on it
In regulated industries, one improvised exception can undo a compliance posture your contracts depend on.

Note: This summary does not replace the Acceptable Use Policy. Where they differ, the policy wins.

Common questions

Someone on my team needs an exception. What now?+

Ask us. Exceptions are sometimes fine — the point is that they are decided on purpose, not improvised at a desk.

Does this apply to personal devices?+

When they touch managed systems or company data, yes — the policy covers use, not ownership.

What happens if someone breaks the policy?+

We flag it to your leadership with context, not drama. The goal is fixing exposure, not catching people out.

Related docs

Security practices
The controls this policy keeps switched on.

Data handling
What we do — and never do — with client data.

Account access
How access, resets, and people changes work.

Unsure whether something crosses a line?
Ask before, not after — that question has never annoyed anyone.