Checkory Beta Legal
рд╕реБрд░рдХреНрд╖рд╛
рд╕реБрд░рдХреНрд╖рд╛ тАФ Checkory Beta public legal and trust documentation.
- Last updated
- 2026-06-17
- Version
- 1.0-beta-draft
- Legal review status
- translated-draft-needs-legal-review
Checkory is a beta AI-assisted legal document review tool.
This page is for transparency and product governance. It is not legal advice.
рдпрд╣ рдЕрдиреБрд╡рд╛рдж рдХреЗрд╡рд▓ рд╕реБрд╡рд┐рдзрд╛ рдХреЗ рд▓рд┐рдП рджрд┐рдпрд╛ рдЧрдпрд╛ рд╣реИред рдпрджрд┐ рдЗрд╕ рдЕрдиреБрд╡рд╛рдж рдФрд░ рдЕрдВрдЧреНрд░реЗрдЬрд╝реА рд╕рдВрд╕реНрдХрд░рдг рдореЗрдВ рдХреЛрдИ рдЕрд╕рдВрдЧрддрд┐ рд╣реЛ, рддреЛ рд▓рд╛рдЧреВ рдХрд╛рдиреВрди рджреНрд╡рд╛рд░рд╛ рдЕрдиреБрдордд рдЕрдзрд┐рдХрддрдо рд╕реАрдорд╛ рддрдХ рдЕрдВрдЧреНрд░реЗрдЬрд╝реА рд╕рдВрд╕реНрдХрд░рдг рдкреНрд░рднрд╛рд╡реА рд╣реЛрдЧрд╛ред
Security overview
This page describes current security practices at a high level and does not make unsupported encryption promises.
- The current upload flow may send files to Checkory over HTTPS for server-side processing and storage protection.
- Browser-only encryption should not be marketed as live until it is implemented and verified.
Current controls
Connections should use HTTPS/TLS. The app uses account sessions, OAuth/passkeys where configured, CSRF protections, CSP/security headers and admin access controls.
- Exact production encryption and retention controls require backend/product confirmation.
Monitoring and incidents
Security and operational logs may be used for abuse prevention, reliability and incident response.
- Report security concerns to [email protected].
Security limitations
No system is completely secure.
- Do not upload unnecessary sensitive personal data or confidential third-party data unless you are authorised.
Related legal pages
Contact
Contact: [email protected]
[email protected]