In short
- PlungeAI runs on Cloudflare. Traffic is encrypted with TLS, and stored data is encrypted at rest.
- Each customer's data is tied to its own account. One customer cannot reach another's.
- API keys are kept only as hashes, and the keys of the accounts you connect are encrypted with AES-256-GCM.
- We do not train or fine-tune any AI model on your data.
- We tell you within 72 hours of learning of a personal data breach that affects you.
- PlungeAI has no SOC 2 or ISO 27001 certification yet.
This page sums up the security measures in our Data Processing Addendum (Annex 2). Where the two differ, the DPA wins.
Infrastructure and encryption
The websites, the products and their databases and files run on Cloudflare's network. Requests pass through Cloudflare's protections against network attacks, and forms are protected against automated traffic.
- In transit. Traffic to the services is encrypted with TLS. Plain HTTP requests are redirected to HTTPS.
- Between our services. Calls run over Cloudflare Service Bindings, or are authenticated with signed requests that carry replay protection.
- At rest. Databases and stored data are encrypted at rest by Cloudflare.
Access control
- Staff tools sit behind a sign-in, and each staff request is checked against the staff member's role before it runs.
- Access goes only to the people who need it for their role, and is removed when they no longer do.
- The most sensitive operations can require an extra authenticator code.
- Every change staff make in our operator tools is recorded in an audit log.
- Your resources are protected by server-side checks that decide who may read, run or change each one.
Keys and credentials
- API keys. We store only a SHA-256 hash. The full key is shown once, when you create it, and cannot be read back. We keep its first characters and last four so you can recognise it.
- Connected accounts. OAuth tokens and keys for the accounts you connect are encrypted with AES-256-GCM, under keys derived per user from a master key held outside our databases. Key versions are recorded, so keys can be rotated.
- Secrets in traces. When our systems find a secret, such as a password or a key, in an execution trace, they replace it with a marker before the trace is stored.
- Cards. Card and bank details are processed by Stripe. PlungeAI never stores a full card number.
Keeping customers apart
Every record is tied to the customer it belongs to, and your personal data is scoped to your account. The services are designed so that one customer cannot reach another customer's data. Agency and Consulting keep their data in their own databases and file storage, apart from the rest of the platform, and each client sees only its own data.
Your data and AI
We do not use your personal data, your content or the output to train or fine-tune any AI model, and we do not license it to anyone for training.
Your content stays until you delete it or the services end. Inside the services, records are kept live for these periods, then archived until your account closes:
| Record | Kept live |
|---|---|
| Execution traces | 7 days |
| Audit logs | 90 days |
| Run records | 180 days |
| Billing ledger | 400 days |
After your account closes you can export your content for 30 days, and we delete your personal data within 30 days after the services end. The Privacy Policy says what we keep for our own records, such as invoices.
Availability and backups
The services run on Cloudflare's distributed infrastructure. Our databases offer point-in-time recovery for a limited period, and backups expire on their normal cycle and are used only to recover the services. The current state of the services is on the status page.
Code and fixes
Production code is kept under version control and reviewed before it is deployed. We apply security fixes to our code and its dependencies according to how severe the risk is, and rate limits protect the services.
Subprocessors
The companies that process data for us are listed, with what each does, what it sees and where, on the Subprocessors page. We tell account owners by email at least 30 days before a new one starts processing your personal data.
Incidents
We keep a process to detect, contain, investigate and fix security incidents. If a personal data breach affects you, we email your account owners without undue delay, and no later than 72 hours after we learn of it, with what happened, what it means and what we are doing about it.
Report a vulnerability
If you think you have found a security problem in PlungeAI, write to trust@plungeai.com. Tell us what you found, where, and how to reproduce it.
While you look, please do not access or change other people's data, do not slow down or interrupt the services, and give us time to fix the problem before you tell anyone else. We do not run a paid bug bounty.
The same contact is in our security.txt.
Certifications
PlungeAI has no SOC 2 or ISO 27001 certification, and no audit has started. The Trust Center, coming soon, will hold our security documentation. Until then, write to trust@plungeai.com for a security review or a questionnaire.