Chats delete themselves
By default, chats hard-delete 7 days after creation. The database enforces the deletion; there is no archive tier or soft-delete flag. You can pick a longer window.
TTL-based hard deletion at the database level
The defaults
No training on your conversations
Your conversations never train AI models. Our agreement with our model provider prohibits it, and so does our policy.
Contractual no-training commitment with the model provider
No selling, no ads
We do not sell or rent your data. We run no advertising. Subscriptions pay for the product.
Written into our privacy policy
Encryption, access, and deletion
Encryption in transit and at rest
TLS covers all traffic between your device and our servers. Stored data carries AES-256-GCM envelope encryption.
Each user's data is encrypted under their own key. One compromised key cannot unlock other users' data.
Key management
The master key never leaves FIPS-validated hardware security modules in plaintext. Least-privilege rules restrict who and what can use each key, and every cryptographic operation is logged.
Messages decrypt only while the AI processes them, then re-encrypt before storage.
Deletion
Delete any chat instantly, or let the default 7-day timer do it. Deleting your account removes your records.
We are extending verified deletion across every downstream system as part of our SOC 2 program.
What we encrypt
Email addresses, every chat message (yours and the assistant's), one-time passcodes, authentication tokens, and Knowledgebooks.
Passwords are protected with strong encryption and are never stored in plaintext.
Access control
- One-time-passcode sign-up; authentication checked on every request.
- Data is scoped to your account, and queries enforce that boundary.
- Biometric unlock happens in your device's Secure Enclave. We never receive biometric data.
- Internal systems follow least-privilege access.
Secure development
- Automated, containerized builds with dependencies pinned to exact versions.
- Requests our systems make on your behalf are validated and restricted before they run.
- Our analytics are content-free by design, with an automated check that fails the build if message content ever reaches the analytics pipeline.
Infrastructure
Ask Safely runs on AWS, which holds independent SOC, PCI DSS, and HIPAA attestations. AI responses come from Claude models through AWS Bedrock, under an agreement that bars the use of your conversations for model training.
Internal services communicate over controlled, authenticated network boundaries. We centrally log cryptographic and administrative activity, including every AI model invocation, so we can audit our own systems.
Compliance
Privacy regulations
Our data practices follow GDPR and CCPA/CPRA principles: data minimization, user control, and the right to deletion. The marketing site uses cookie-free analytics.
Vendor requirements
We review the security of every provider that processes user data for us, and each one signs terms limiting how it may use that data. We review each vendor annually.
Third parties
A short list of providers runs the service, including AWS for infrastructure and Anthropic's Claude through AWS Bedrock for AI. Web searches go to Brave Search without account identifiers. Each provider receives only what it needs. The full list is in our Privacy Policy.
Report a security concern
Found a vulnerability, or have a question about our practices? Write to support@asksafely.ai. We read every report and respond quickly.
- Maintained by
- SafeLife Inc — Security & Compliance
- Last updated
- October 1, 2026
- Related
- Privacy Policy