Security overview

• Everything travels over an encrypted connection (HTTPS/TLS).
• Recordings and audio are encrypted at rest with AES-256.
• The database is encrypted at rest.

• No file is public. Each one is served through a signed link that expires.
• The database enforces access. A request reaches only the workspace you belong to.
• One person runs ScreenDub, and only that person can reach production. No support team, contractor, or outside party has standing access to your recordings.

• Your finished video is exported in your browser. We never receive the file.
• Your PDF guide is built in your browser the same way.
• Trimming, cropping, and blurring happen on your device.

• We use Google's paid AI tier. Its terms state that your files, prompts, and responses are not used to train or improve its products.
• The AI reads your recording from our storage and keeps no copy. Access to the file ends when the analysis finishes.
• Google keeps a short log of requests to catch abuse and meet legal obligations. It is not used for training.

• What you record belongs to the workspace you were in.
• The workspace owner controls membership and can remove anyone, effective immediately.
• The owner can see and delete anything teammates made in their workspace.

Stripe handles cards and is PCI-DSS compliant. We never see or store card details.

• You can delete a project or your whole account from settings at any time.
• Deleting your account permanently removes your profile, projects, recordings, and generated content. Backups hold files for up to 7 days, then they are gone.

Single sign-on (SSO/SAML) and a SOC 2 report are not available today. No system is perfectly secure, and we will not pretend otherwise. The lists above are what is actually in place.

Security reviews and questionnaires are welcome. Email hello@screendub.io or use the contact form.