Question 1

Who holds the encryption keys?

Accepted Answer

You do. Files are encrypted client-side and keys stay in your KMS (BYOK). What reaches SecureData is ciphertext — your data cannot be read without your keys.

Question 2

Is data dispersal mandatory?

Accepted Answer

No — dispersal is optional and enabled per vault. Keep everything in one region for simplicity, or shard sensitive vaults K-of-N across independent sites.

Question 3

Does the forensic watermark survive re-encoding or screen recording?

Accepted Answer

Yes. The invisible per-download payload is designed to survive re-encoding, cropping, filters and screen capture, and every match returns a confidence score.

Question 4

Which sign-in methods are supported?

Accepted Answer

Email + password, SMS and WhatsApp one-time codes, TOTP apps, FIDO2 passkeys and SSO (SAML/OIDC) — combined into multi-factor, action-tiered policies where downloading requires stricter proof than uploading.

Question 5

How do real-time alerts reach the team?

Accepted Answer

WhatsApp, email, SMS and webhooks into Slack or your SOC — and admins can reply with commands like Freeze or Revoke that execute immediately.