Acceptable Use & Device Policy¶
| Field | Value |
|---|---|
| Status | draft |
| Owner | DIR |
| Applies to | The operator and any future contributors; all endpoint devices used to access Partile source, cloud, vendor consoles, or any data; the development workstation(s) and any mobile test devices. |
| Review cadence | Annual, or on any change to who has access or what devices are in use. |
| Mapped controls | SEC-05 (secrets never logged/persisted), SEC-08 (TLS), supports access-control and cryptography policies. |
| Evidence | This policy; ../procedures/onboarding-offboarding-procedure.md; device inventory (Tier 2 — restricted). |
| Exception handling | Device exceptions (e.g. a temporary test device) are time-boxed and recorded by DIR. |
Purpose¶
Set the minimum bar for how devices and accounts are used so that an endpoint compromise does not become a data or source compromise. Scaled for a remote, no-office company: the endpoint is the perimeter.
Acceptable use¶
- Partile accounts, source, and data are used only for Partile work.
- No secrets in chat, tickets, commits, screenshots, or this data room.
Secrets live in environment/Secret Manager/operator secret stores
(
cryptography-and-secrets-policy.md). - No copying personal data or production data to local disk, personal cloud, or unmanaged tools. (Today there is no production data — this rule is set before it exists.)
- Generative-AI / agent tooling (e.g. the Atelier/Claude workflow) may process source and governance docs but must not be fed secrets, real user PII, or Tier-2 material; outputs are reviewed before merge.
Device baseline¶
Any device with access to Partile source, cloud, or data must have:
- Full-disk encryption enabled.
- A screen lock with a short auto-lock timeout and a strong passphrase/biometric.
- OS and browser kept current with security updates.
- A supported OS (no end-of-life systems).
- No shared local OS accounts for Partile work.
Mobile test devices used for iOS or Android dev builds carry no real user data (pre-beta) and are wiped/de-registered when no longer needed.
Networks¶
- All public access to backend and vendor consoles is over TLS; production DB and Redis access is private GCP data-plane traffic (SEC-08).
- Avoid untrusted public Wi-Fi for privileged operations; prefer trusted networks or a VPN/tunnel. The Cloudflare dev tunnel is for dev API exposure only.
Lost / compromised device¶
Treat as a security incident (incident-response-policy.md): revoke the device's
sessions and console access immediately, rotate any secrets that may have been
exposed, and record it in the incident log.
Exceptions¶
A short-lived deviation (e.g. a borrowed test device) is recorded by DIR with an expiry. Anything touching real user data (once it exists) gets no exceptions to encryption or access revocation.