Security and data protection
Your data moves through SyncBlaze constantly, so protecting it is part of the core design, not an add-on.
How we protect your data
- Encryption in transit
- Every connection, from SDKs, agents and S3 clients, uses TLS 1.3. Plain HTTP is refused.
- Encryption at rest
- All stored data is encrypted with AES-256. Keys are rotated and kept separate from the data.
- Client-side encryption
- Encrypt backups and document fields before they leave your systems, with keys we never see.
- Immutable storage
- Object lock protects backups and buckets from deletion until retention ends, even by account admins.
- Least-privilege access
- Scoped API keys, agent tokens per job, role-based team permissions and SSO on Business.
- Audit log
- Every sign-in, key change, restore and deletion is recorded and can be exported.
Data location and privacy
| Regions | EU (Frankfurt), EU (Amsterdam), US East, US West, Asia (Singapore) |
|---|---|
| Data residency | Data stays in the region you choose unless you enable replication |
| Data processing agreement | Available on all paid plans |
| Data export | All data exportable at any time through the API, CLI and S3 |
| Deletion | Deleted data is removed from primary storage immediately and from internal backups within 30 days |
Report a vulnerability
If you believe you have found a security issue, email security@syncblaze.cc. We reply within two business days and will not take legal action against good-faith research. Our security.txt has details.
Start on the free plan
No card needed. Upgrade when your project grows, or talk to us about a custom setup.