Security & Data-Handling Overview

Authentication & account security

• Password hashing. Passwords are hashed with bcrypt (an industry-standard, deliberately slow algorithm). We never store plaintext passwords.
• Configurable password policy. Your admin sets minimum length, an uppercase requirement, a special-character requirement, and periodic password expiry.
• Brute-force protection. Accounts lock after repeated failed sign-ins (default 5 attempts, then a temporary lockout). Sign-in responses are constant-time, so they don't reveal whether an email exists.
• Session security. Sessions use cryptographically random tokens stored only as one-way hashes — the raw token is never saved. They expire after a configurable period (default 12 hours), carry a hard 90-day maximum, and are re-validated on every request.
• Multi-factor authentication (MFA). Authenticator-app TOTP with one-time backup codes. Always required for platform super-administrators; your organization can additionally require it for managers and/or all users.

Access control & tenant isolation

• Role-based access control (Doer, SME, PM, Org Admin, platform Admin) governs what each user can see and do.
• Per-organization data isolation. Beyond application-level checks, the database enforces PostgreSQL Row-Level Security on every tenant table as a second layer, so one organization's queries cannot return another's records.

Data protection

• Encryption at rest. All application data is stored in an encrypted Amazon Aurora PostgreSQL database.
• Encryption in transit. Connections use TLS/HTTPS, including application-to-database traffic.
• Secrets management. Database credentials, signing keys, and integration credentials are held in AWS Secrets Manager — never in source code.
• Network isolation. The database runs in a private network segment with no public internet access; connectivity is restricted to the application tier.

Auditing & monitoring

• Audit log of security-relevant events (sign-ins, MFA changes, administrative settings changes) with timestamp, actor, and source IP.
• Acceptance records — terms-of-use acceptance is recorded with evidence (user, timestamp, IP, browser).
• Email integrity — bounce and complaint handling with reputation monitoring.

What your organization controls

Data ownership, access & deletion

• You own your data. Your Org Admin controls your organization's data and can delete users, tasks, projects, templates, and playbooks directly — a capability that can be delegated to a PM or SME.
• Deletion on request. Full deletion of your organization's data is available on request.

Hosting, backups & availability

• Hosted on Amazon Web Services (AWS) in the United States (Aurora PostgreSQL, Lambda, API Gateway, CloudFront, S3) within a private virtual network.
• Backups & recovery. Automated database backups with point-in-time recovery; our practice is nightly backups with restore procedures tested quarterly.
• Availability. We operate on a best-effort basis at this stage and do not offer a formal uptime SLA during evaluation; a production SLA can be discussed for paid engagements.

Subprocessors

We use a small set of trusted providers to operate the service, under their own security and confidentiality commitments:

• Amazon Web Services (AWS) — cloud hosting and infrastructure.
• Amazon SES — transactional email.

Data handling & privacy

• The evaluation demo uses fictional sample data. Please do not enter real, personal, or confidential information into the demo.
• How we handle information on our website and demo is described in our Privacy Notice.

On our roadmap (not yet in place)

Contact

Security questions or a vendor assessment? Contact security@dotheplan.com.