Privacy and data handling

Setup-first privacy for one approved chase.

Admin Chief is designed around narrow proof runs. Buyers approve the source, scope, exclusions, and review path before sensitive inbox data is connected.

Scope firstApproved source boundaries

Use a named thread, label, folder, upload, export, or manual evidence pack. Broad inbox access is not the default proof-run path.

Minimal outputTrack the chase, not everything

The product focuses on expected items, received evidence, source excerpts, deadline risk, draft text, approval state, and audit metadata.

Review gateNo sensitive send by default

Follow-up drafts stop at human review. The first setup keeps outbound sending disabled unless a separate implementation is explicitly agreed.

Private surfacesProof-run routes are noindex

Dashboard, setup, review, OAuth, and API surfaces are treated as private operational areas, with no-store and noindex guardrails where applicable.

Current privacy boundary

Admin Chief handles admin follow-up and record chasing. It is not positioned as legal, financial, HR, insurance, tax, or professional advice, and it should not be described as an unsupervised autonomous sender.

Contact details from setup intake are used to respond to the setup request.
Source rules, scan windows, and exclusions are approved before any inbox connection.
Checkout links are used after fit and scope are clear, not as a blind purchase step.
Roadmap tool access, mature managed outcomes, and autonomous sending are not claimed as shipped.