How Your Documents Are Protected
Research documents are often unpublished, confidential or both. This page explains plainly how Brevton handles them today: what we do, what we don't claim, and who to ask when you need more detail.
- In transit
- HTTPS (TLS)
- Stored in
- Amazon S3, on AWS
- Sign-in
- Amazon Cognito
- Who can see it
- Members you invite
- Ownership
- Stays with you
What We Do Today
Brevton is in early access, built by a small team. These are the practices it is built on, described plainly.
Encrypted in Transit
Traffic between your browser and Brevton, including document uploads, is encrypted with HTTPS (TLS).
Built on AWS
Documents are stored in Amazon S3 and sign-in is handled by Amazon Cognito.
See the architectureOnly the People You Invite
Documents you upload stay in your workspace and are visible only to the members you invite. Accounts are invite-only during early access.
You Keep Ownership
You keep ownership of everything you upload. Our Terms & Conditions say so explicitly.
Read the TermsDeletion on Request
Ask us to delete your account and the documents in it at any time by emailing contact@brevton.com.
Request deletionNo Borrowed Badges
We don't claim certifications or audits we haven't completed. Send us your security questionnaire and we'll answer it directly.
Send a questionnaireFull detail: the Terms & Conditions and Privacy Policy describe how we handle your documents and personal data.
On our roadmap: single sign-on (SSO), role-based permissions and audit logs for team workspaces. These are plans, not current features — see the roadmap.
Have a Security Question?
Email contact@brevton.com with your questions or your organization's security questionnaire. It goes straight to our founding team.