Minimum useful information
Support should be set up around the information needed for the agreed task, rather than broad access to everything.
Privacy summary
Helpful support only works when people stay in control.
This draft privacy summary explains the guardrails Cliff & Co is designed around: customer-controlled connections, limited access, clear approvals, client-owned accounts, and careful handling of family, school, business, financial, customer, and account information.
Guardrails
Privacy is handled through practical workflow design, not vague promises.
Customer-controlled connections
During guided setup, customers choose which devices, accounts, calendars, files, or work tools they approve for the agreed support.
Approval points
Purchases, payments, account changes, outgoing messages, customer-impacting actions, and sensitive decisions should require human approval.
Separate workflows
Personal, family, study, and business workflows should stay distinct, especially where client data, school information, or financial details are involved.
Client-owned accounts
Clients should keep ownership of their email, calendar, software, AI/API, and third-party app accounts.
No data selling
Cliff & Co should not sell client data. Setup information should be used for agreed support, setup, handover, and maintenance only.
Offboarding
When support ends, access should be removed and setup notes or configuration should be handed over, archived, or deleted according to the agreed process.
Documented handover
Setup, access, support boundaries, changes, and offboarding should be documented so the system remains understandable and reversible.
Draft-stage note
This page is a draft summary and should be reviewed before relying on it as a full legal privacy policy.