Trust & Security

How your content is held

dns

What it runs on

  • The whole platform on Cloudflare — compute, database, object storage, network
  • One provider end to end, on paid enterprise plans, not free tiers stitched together
  • Files encrypted in transit and at rest

The whole stack is Cloudflare, and Cloudflare publishes its own certifications: Cloudflare's trust hub

shield_lock

Can anyone else see my content?

  • Each workspace is an isolated Cloudflare Durable Object with its own SQLite database, not shared rows in a shared table
  • Files in private Cloudflare R2, reached only through the workspace that owns them
  • Organization scoping checked on every read and write
  • Uploads keyed per organization; generated files behind unguessable keys and a login
  • Members reach only their own organization
  • Operator sign-in behind Cloudflare Access on a single-identity policy. Platform admin rights are granted only by explicit assignment — never by signing up, by being a workspace admin, or by paying
smart_toy

Is my content used to train AI models?

  • No
  • Text, voice and music, and most image and video, through one gateway
  • Before every text request the platform confirms the gateway reports zero retention, logging off, caching off — and refuses to send if not. That check is never more than 60 seconds old
  • Routes pinned to a dated review of each provider's no-training terms; changing the review forces every route to re-qualify
  • FLUX image and video requests go directly to Black Forest Labs, under its commercial API terms
  • Provider trust centers: Anthropic · OpenAI
key

Who can sign in?

  • A six-digit code by email. No password exists to leak or reuse
  • Codes last 10 minutes and lock after 5 wrong attempts
  • Sign-in protected by Cloudflare Turnstile and rate limits
  • Sessions held in HTTP-only cookies
  • The server resolves your workspace on every request; the browser cannot choose one
  • Removing a member ends their sessions immediately
report

What if something goes wrong?

  • A written incident procedure: containment, evidence preservation, notification, recovery, post-incident review
  • Confirmed incidents affecting your data notified within 72 hours
  • Workspace databases keep 30 days of point-in-time recovery
  • Account and sign-in events to a hash-chained audit log, so altered entries are detectable
  • Sign-in codes, cookies and tokens never written to logs
  • Execution logs redacted for secrets; platform operational logs retained by Cloudflare for up to 7 days
logout

What if I leave?

  • Admins export everything at any time: one ZIP, every asset, the Brand Kit, the leads
  • Closing a workspace ends access immediately
  • Content, files and memberships permanently deleted 30 days later
  • Outputs are yours to use, publish, edit and keep

Full detail, updated 21 September 2026: Security Overview. Security questions, vulnerability reports and Data Processing Agreement requests: security@designtech.ai. What we store and why is in the Privacy Policy.