Data Governance
Where your data lives, who can touch it, how long we keep it, and exactly which third parties are involved. Full transparency, because operations work only runs on trust.
/1.0How Your Data Flows
We are a data processor acting on your instructions. Your data moves through a defined path, and only as far as it needs to:
- We pull data from the systems you connect, run it through the workflows and AI agents we build for you, and write results back to your systems.
- Data sent to an AI model goes only to the providers listed below, under contracts that prohibit training on your data.
- We do not sell, rent, or share your data with anyone outside the sub-processors required to deliver the service.
/2.0Who Accesses Client Data
- Only the Fellowship team members assigned to your engagement, on a need-to-know basis.
- Access is granted with least privilege, logged, and revoked when an engagement ends or a team member rolls off.
- Automated systems access only the specific scopes their task requires.
- Sub-processors (below) access data only to perform their function, under their own contractual and compliance obligations.
/3.0Retention by Data Type
| Data Type | Retention | Notes |
|---|---|---|
| Operational data processed in workflows | Duration of engagement | Deleted or returned on offboarding |
| OAuth tokens & credentials | Until revoked / offboarding | Encrypted; revocable by you anytime |
| System & access logs | Up to 90 days | Secrets/payloads scrubbed; events only |
| Backups | Up to 35 days rolling | Encrypted; purged on schedule |
| Contracts & billing records | As required by law | Retained for tax / legal compliance |
| Lead form submissions | Until no longer needed | Deleted on request |
/4.0Deletion on Offboarding
When an engagement ends, you choose: we return your data in a portable format, delete it, or both. We revoke our access to your connected systems, rotate or destroy stored credentials, and remove operational data from our environment within 30 days of offboarding, except records we are legally required to retain (such as contracts and billing). On request, we provide written confirmation of deletion.
/5.0Sub-Processor List
These are the third parties that may process client data on our behalf. The specific set used in any engagement depends on which systems you connect and what we build. We will inform clients of material changes to this list.
| Sub-processor | Purpose | Data involved |
|---|---|---|
| Anthropic (Claude) | AI model inference | Content sent to AI agents |
| Amazon Web Services | Hosting, storage, compute, AI (Bedrock) | All hosted data |
| Cloudflare | CDN, DNS, network security | Traffic metadata in transit |
| Google Workspace | Email & document workflows (when connected) | Email / calendar / files in scope |
| OpenAI | Supplementary AI inference (when used) | Content sent to specific agents |
| Client-connected platforms | CRMs, accounting, voice, etc. you authorize | Only the scopes you grant |
Anthropic and OpenAI process API data under business terms that prohibit using your inputs or outputs to train their models. See our AI Usage & Ethics page for detail.
/6.0Data Processing Agreement
A DPA is available on request, including for GDPR- and CCPA-exposed clients. It sets out the processing terms, sub-processor commitments, and the security measures described on our Data Security page.
Governance questions? Email support@fellowshipautomation.com.