Privacy Policy
Effective Date: 2026-03-24
We wrote this for developers. No dark patterns, no "by using this service you waive all rights" language. Just what we collect, why, and what you can do about it.
1. What We Collect
Account Data
- Email address — required to create an account, used for login, billing receipts, and support.
- Password hash — we store an Argon2id hash of your password. We never store or transmit your plaintext password.
Billing Data
- Payment details (card number, expiry, CVV) are handled entirely by Stripe. We store only Stripe customer IDs and subscription IDs, not raw card data.
Usage Data
- API request logs — endpoint called, HTTP status, response time, timestamp. We do not log request/response bodies by default.
- Compute unit consumption — tracked per-tenant for billing and quota enforcement.
- Database storage — tracked per-tenant in bytes.
Infrastructure Data
- IP addresses — logged at the load balancer level for security (rate limiting, abuse detection). Retained for 30 days.
- HTTP headers — standard web server logging (User-Agent, Referer). No fingerprinting.
Cookies
- Session cookie (
polydb_session) — HttpOnly, Secure, SameSite=Strict. Used to keep you logged into the dashboard. Expires on session end or logout. - No tracking cookies — we do not use analytics cookies, advertising pixels, or third-party tracking scripts.
2. What We Do Not Collect
- The contents of your database (we can see it exists; we don't read it)
- Keystrokes or screen recordings
- Location data beyond IP-based region (us-east-1)
- Social graph or behavioral profiles
3. How We Use Your Data
| Data | Purpose |
|---|---|
| Account access, billing receipts, service announcements, support | |
| Password hash | Authentication |
| Usage metrics | Billing calculation, quota enforcement, capacity planning |
| IP addresses | Security, rate limiting, abuse detection |
| Logs | Debugging, incident response, performance monitoring |
We do not sell your data. We do not share your data with advertisers. We do not train AI models on your data.
4. Subprocessors
We use the following third-party services to operate PolyDB Cloud. Each subprocessor has agreed to handle data in compliance with applicable privacy laws.
| Subprocessor | Purpose | Data Shared | Location |
|---|---|---|---|
| AWS | Infrastructure (Fargate, ALB, SES, Secrets Manager) | All service traffic, email delivery | us-east-1 |
| Neon | PostgreSQL hosting (tenant databases) | Your database content | us-east-1 |
| Stripe | Payment processing, subscription management | Email, billing details | United States |
If we add new subprocessors, we'll update this list and notify you by email before the subprocessor begins processing your data.
5. Data Location
All data is stored and processed in AWS us-east-1 (Northern Virginia). We do not currently offer data residency in other regions. If this matters to you for compliance reasons, contact us.
6. Data Retention
| Data Type | Retention |
|---|---|
| Account data | Until account deletion + 30 days |
| Database content | Until account deletion + 30 days |
| Access logs | 30 days |
| Billing records | 7 years (legal requirement) |
| Support emails | 2 years |
When you delete your account, we initiate deletion within 7 days and complete it within 30 days. Billing records are retained for legal compliance.
7. Your Rights (GDPR and Beyond)
If you're in the EU/EEA, UK, or California, you have specific rights over your data. We honor these for everyone, not just residents of regulated jurisdictions.
| Right | What it means | Endpoint |
|---|---|---|
| Access | Get a copy of all data we hold about you | GET /api/gdpr/export |
| Rectification | Correct inaccurate account data | PATCH /api/auth/profile |
| Erasure | Delete your account and all associated data | DELETE /api/gdpr/account |
| Portability | Export your database content in a portable format | GET /api/gdpr/export |
| Restriction | Pause processing while a dispute is resolved | Email support@polydb.dev |
| Object | Opt out of non-essential processing | Email support@polydb.dev |
To exercise any right, you can use the API endpoints above (authenticated) or email support@polydb.dev. We'll respond within 30 days. For GDPR requests, we'll respond within 72 hours for urgent erasure requests.
8. Security
- All traffic is encrypted in transit via TLS 1.2+.
- Passwords are hashed with Argon2id (memory-hard, resistant to GPU cracking).
- API keys are stored as hashes; the raw key is shown only once at creation.
- Tenant database schemas are isolated; cross-tenant data access is not possible through the API.
- We perform periodic security reviews. We have no bug bounty program yet, but responsible disclosure is welcome at security@polydb.dev.
9. Children's Privacy
PolyDB Cloud is not directed at children under 13. We do not knowingly collect data from children. If you believe a child has created an account, email support@polydb.dev and we'll delete it.
10. Changes to This Policy
When we make material changes to this policy:
- We'll email you at your account address at least 14 days before the change takes effect.
- The current version is always at
https://beta.polydb.dev/privacy. - We keep prior versions on request — email us if you need a specific historical version.
11. Contact
Privacy questions: support@polydb.dev Security disclosures: security@polydb.dev GDPR requests: support@polydb.dev (subject: "GDPR Request")
We're a small team. We read everything and respond within 2 business days.