Helpful support only works when people stay in control.

This policy explains the privacy guardrails Cliff & Co is designed around: customer-controlled connections, approved desktop helper 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.

Minimum useful information

Support is set up around the information needed for the agreed task. Where broader device access is approved, work remains scoped to normal assistant support and agreed workflows.

Customer-controlled connections

During guided setup, customers choose which devices, accounts, calendars, files, or work tools they approve for the agreed support.

Desktop helper access

When a customer installs and pairs the desktop helper, that approval means Cliff & Co may access and work across the computer for normal assistant tasks, including files, apps, screen context, and automation where the helper and operating system allow it. Customers can remove the helper or ask for access to be changed or revoked.

Approval points

Purchases, payments, account changes, outgoing messages, customer-impacting actions, and sensitive decisions require human approval unless a separate written arrangement says otherwise.

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 keep ownership of their email, calendar, software, AI/API, and third-party app accounts.

Managed AI usage

When Cliff & Co manages AI usage, usage limits, approval status, and billing preferences should be recorded without placing technical keys or billing details in public setup packets.

No data selling

Cliff & Co does not sell client data. Setup information is used for agreed support, setup, handover, maintenance, security, and service administration.

Offboarding

When support ends, access is removed and setup notes or configuration are 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.

Questions and requests

Clients can ask about access, correction, deletion, offboarding, or support boundaries by contacting Cliff & Co at [email protected].