Security.
Where ProductCraft runs, how your data is protected, and what we have not done yet. Every statement here describes how the platform runs today.
Hosting
Where your data is hosted
ProductCraft runs on DigitalOcean in Frankfurt. The APIs, the databases and the queues are all in that one region. Two services leave it, and both stay in Europe: email goes out through Amazon SES in Stockholm, and files are stored in Cloudflare R2 in Western Europe.
The one exception is Trawl. To read a web page and fill in your schema, Trawl sends the page text and your instructions to Google's Gemini API, which may process them outside the EU. No other product sends your data to an AI model.
| What | Provider | Where |
|---|---|---|
| Applications and APIs | DigitalOcean Kubernetes | Frankfurt, Germany (fra1) |
| Databases | DigitalOcean Managed PostgreSQL | Frankfurt, Germany (fra1) |
| Queues and caches | Run inside our cluster, on DigitalOcean storage | Frankfurt, Germany (fra1) |
| Files (uploads, avatars, received mail) | Cloudflare R2 | Western Europe |
| Outgoing email | Amazon SES | Stockholm, Sweden (eu-north-1) |
| Trawl page reading | Google Gemini API | Google decides; may be outside the EU |
The full list of companies that process data for us is on the subprocessors page.
Encryption
In transit and at rest
- In transit. Every public address, from the APIs to the console, is HTTPS only, and browsers are told never to use plain HTTP for productcraft.co (HSTS). Our services reach the database over TLS.
- At rest. DigitalOcean encrypts the managed databases and the storage volumes, and Cloudflare encrypts every file in R2.
- Secrets get a second layer. The most sensitive values you give us, such as push notification keys, sign-in provider secrets and your domains' email signing keys, are encrypted again by ProductCraft itself (AES-256-GCM) before they are stored, with keys kept outside the database.
Credentials
Secrets you give us are never shown again
When you upload an Apple or Firebase push key, a web push key, a sign-in provider secret or a CAPTCHA secret, no screen and no API response ever returns it. You see that one is stored, plus a fingerprint or its last four characters so you can tell which one it is. To change it, you replace it.
Workspace API keys work the same way in the other direction: we show a new key once, store only a hash of it, and cannot recover it. A lost key is rotated, not looked up.
Access
Who can do what
- Workspaces are the boundary. Your data belongs to a workspace, and only its members and its keys can reach it. A product that is switched off for a workspace refuses every request for it.
- Roles and policies. Owner, admin and member roles come built in, and you can add your own. API keys carry a policy that lists what they may do, and nobody can grant a key more than they hold.
- AI agents ask first. An agent connects through a browser approval that names the workspace and what it may do, and it never gets more than the person who approved it. See Build with AI.
Audit
Every change is on the record
- The workspace audit log in the console records changes to your workspace and who made them, including each call an AI agent made on someone's behalf, and the ones that were refused.
- Auth keeps an audit log per app that you can export, or send to your own log collector in signed batches.
- Flags keeps the full history of every flag change, with a diff and one-click restore.
Backups
Database backups
DigitalOcean backs up our PostgreSQL databases every day and keeps each backup for seven days, and can restore a database to any point within that window. The backups stay in DigitalOcean.
Our database runs on a single node. If it fails, DigitalOcean replaces it automatically, and we expect some downtime while it does.
Not yet
What we have not done yet
- No SOC 2 or ISO 27001 report. We plan to start a SOC 2 audit. Until we have a report, this page is our account of how the platform runs.
- No two-step sign-in for console accounts yet. Auth offers it to your own users; the ProductCraft console does not offer it to you yet.
- No uptime commitment. We do not offer an SLA yet. Current status is on the status page.
Contact
Report a vulnerability or an incident
Email security@productcraft.co. Tell us what you found and how to reproduce it. Please give us a chance to fix it before you publish it, and do not access other people's data while you test.