Security at GradeCircle
Client data and engagement confidentiality are foundational — not an afterthought. Here is how we protect your information at every layer.
Security pillars
Six areas where we apply consistent, documented controls.
Encryption at rest & in transit
All data is encrypted in transit using TLS 1.2+ and at rest using AES-256. Database credentials and secrets are never stored in source code.
Authentication & MFA
Portal and admin access uses Supabase Auth. Multi-factor authentication (TOTP) is available. Sessions expire on inactivity and cannot be extended client-side.
Infrastructure security
Applications are deployed on Vercel's edge network with automatic DDoS mitigation, WAF rules, and isolated compute. Database is hosted on Supabase with row-level security enforced at the database layer.
Access control
Role-based access control (RBAC) is enforced at every API endpoint and database query. Principle of least privilege is applied across all services.
NDA & data handling
All client engagements begin with a mutual NDA. Client data is never used to train models or shared across engagements. Data is retained only for the period required to fulfil the engagement.
Engineering security practices
- Secrets managed via environment variables — never committed to version control
- HTTP security headers: X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy
- Rate limiting on public form and API endpoints
- Sanitised error responses — no stack traces or internal paths in production
- Automated database backups with point-in-time recovery
- Third-party integrations use scoped API keys with minimal permissions
Client data handling
GradeCircle processes client data solely for the purpose of delivering the agreed engagement. We operate under a mutual NDA that is signed before any discovery work begins. Client data is:
- Never used to train AI models or shared across client accounts
- Stored in an encrypted database with row-level security isolating each client organisation
- Deleted or returned at the conclusion of the engagement on request
- Processed in accordance with applicable data protection regulations
Sub-processors & third-party services
We use the following sub-processors to deliver the platform. Certifications are shown where we have recorded them.
| Provider | Purpose | Certifications |
|---|---|---|
| Vercel | Hosting & edge delivery | SOC 2 Type II |
| Supabase | Database & authentication | SOC 2 Type II, GDPR |
| Stripe | Payment processing | PCI DSS Level 1 |
| Resend | Transactional email | SOC 2 Type II |
| Anthropic | AI inference, including documents and inputs clients submit in the portal for analysis | SOC 2 Type II |
| Voyage AI | Text embeddings | SOC 2 Type II |
| Sentry | Error monitoring | — |
| Inngest | Background job processing | — |
| Cal.com | Meeting scheduling | — |
| Notion | Internal content and client reporting data | — |
| Slack | Internal notifications | — |
Vulnerability disclosure
We welcome responsible disclosure of security vulnerabilities. If you discover a potential security issue, please contact us before publishing publicly. We commit to:
- Acknowledging your report within 2 business days
- Providing a timeline for investigation and remediation
- Notifying you when the issue has been resolved
- Crediting researchers who disclose responsibly (if desired)
Submit a vulnerability report through our secure inquiry form — all reports are reviewed by our team.
Report vulnerabilityHave a security question?
Our team reviews all inquiries. Use our form to report vulnerabilities, ask compliance questions, or discuss data handling.
Last reviewed: November 2026