Security & Data Protection
How Campvori is designed to protect accounts, academic information, documents and authorized integrations.
Effective September 24, 20261. Security approach
Campvori uses authenticated accounts, user-scoped access controls and private-data controls as part of its application architecture. Security is treated as an ongoing engineering responsibility rather than a policy-page promise.
2. Account protection
Use a unique password and protect your email and connected-school accounts. Campvori supports secure password-reset flows through its authentication provider. Never send passwords, one-time codes or secret API tokens to Campvori Support.
3. Academic documents and records
Academic documents are intended to remain associated with the authenticated user who uploaded them. Extracted academic information requires user review where Campvori’s confirmation workflow is used. Users should remove documents they no longer want stored.
4. School integrations
Campvori connects to school systems only through supported, authorized methods such as approved APIs, OAuth/LTI or documents the user chooses to upload. A student identifier by itself does not authorize access.
5. Secrets and credentials
Private service credentials and integration secrets must not be placed in public client-side code. Campvori’s production deployment should keep server secrets in protected environment or secret-management systems and restrict access to the minimum required.
6. Security limitations
No internet service can guarantee absolute security. Users should report suspected account compromise or a security issue promptly and should not publicly disclose sensitive student information when reporting a problem.
7. Report a security concern
Email supportcampvori@gmail.com with the subject “Security Report.” Include a clear description and steps to reproduce, but do not include passwords, access tokens, Social Security numbers or unnecessary private student records.
