Security and data handling
- Your accounts
- Least-privilege access
- Access removed at the end
Your accounts, not ours
We build in your code repositories, your cloud account, and your AI provider account, under your own agreements with those providers. You pay AI and cloud usage directly. When the work ends, everything stays where it is, in your name.
Access we ask for
- Least-privilege access: only the systems and permissions a workflow needs, requested in writing
- Read-only access wherever reading is enough
- A test company or sandbox for development, before anything touches production
- Access removed within 5 business days of the end of an engagement or Operate plan
How AI providers handle your data
Our contracts state your data is not used to train AI models. We use AI providers through their business APIs and check the selected provider’s current data terms before each statement of work. You choose the provider and the region where your account runs.
What protects your core systems
- Automations write drafts first. Validation rules check the data before anything posts to your ERP, CRM, or other core systems.
- Low-confidence or failed items go to a review queue for a person.
- AI agents act only within rules you approve. Nothing goes to a customer or vendor without a person’s approval.
- Every automation falls back to your existing manual process if it fails.
- Promotion from test to production happens once, after acceptance testing.
Monitoring and support
Automations and software covered by Dooder Operate are monitored with automated alerts around the clock. People respond during business hours, Monday to Friday, 8am to 6pm Central. For a critical issue, we respond within 4 business hours and confirm your manual fallback the same day.
What we don’t claim
We don’t hold SOC 2 or other security certifications today. We describe the practices above in writing in every statement of work, and we answer your security questionnaire before work starts.
How common concerns are handled
| Concern | How it’s handled |
|---|---|
| Vendor lock-in | Code and accounts in your name, with a handover package |
| Data used to train models | Contract term, plus a provider terms check per SOW |
| Core system integrity | Drafts, validation rules, a review queue, test before production |
| Ongoing risk | Monitoring, written response times, access removal at the end |