Sredible handles some of the most sensitive information a business produces: salaries, contractor invoices, technical R&D details and tax filings. This statement describes the controls in place today, accurately, and what we are still working on. It is not a certification.
Compliance status
- SOC 2 and ISO/IEC 27001: readiness in progress. We have mapped our controls to the SOC 2 Trust Services Criteria (Security, Availability, Confidentiality and Privacy) and to ISO/IEC 27001:2022 Annex A, written the supporting policies and are closing the gaps. Sredible is not yet SOC 2 attested or ISO 27001 certified; we will say so here when an independent auditor has issued a report or certificate.
- Privacy law: the platform is built to support PIPEDA, Quebec Law 25 and, where it applies, the GDPR. See our Privacy Policy.
- Our providers: our hosting, database and payment providers hold their own SOC 2 reports and ISO 27001 certifications, which we review as part of vendor management.
Data residency
- The application runs in Vercel's Montréal region, and the database, uploaded files and backups are stored in Canada (Supabase, Canada Central).
- A few providers process limited data outside Canada: email delivery, text messages, AI features and payments. The Privacy Policy lists each one, what it receives and where.
Encryption
- In transit: all traffic uses HTTPS (TLS 1.2 or higher), with HTTP Strict Transport Security so browsers never fall back to plain HTTP.
- At rest: the database, file storage and backups are encrypted at rest with AES-256 by our providers.
- Credentials: passwords are stored only as salted hashes. Tokens for the development tools a customer connects are encrypted again by the application (AES-256-GCM) and never sent back to the browser.
Sign-in and access control
- Two-step sign-in is required for every account: an authenticator app, a code by text or email, or a passkey (Face ID, Touch ID, Windows Hello or a security key). There is no "trust this device" option; the second step is asked at every sign-in. Backup codes cover a lost phone.
- Brute-force protection: sign-in, code, password reset and other sensitive endpoints are rate limited per IP address and per account, and limits are shared across all servers.
- Roles and page permissions: organizations assign roles (owner, admin, preparer, reviewer, viewer, billing). Owners and admins can limit each person to chosen claims and set individual pages to view only or hidden. Clients of a firm see only the pages the firm allows.
- Server-side checks: every page, action and file download checks the signed-in person's rights on the server. Files are never served from public links.
- Sessions: sessions expire after 14 days, and people can review and sign out their other devices.
- Staff access: access to production systems is limited to the people who operate them, protected by two-step sign-in, and logged by our providers.
Application security
- Strict browser security headers on every page: a Content Security Policy, protection against framing, no sniffing of file types, a strict referrer policy and a permissions policy that allows the camera only on the proctored exam.
- Changes go through version control and review, with type checks, linting and automated tests before release, and database changes go through versioned migrations.
- Dependencies are checked for known vulnerabilities.
- The database's public API is switched off and locked down after every migration, so the database is reachable only by the application.
- The calculation engine, form logic and AI prompts run only on our servers.
- Independent penetration testing is planned before our SOC 2 audit.
Logging and monitoring
- An audit trail records sign-ins, failed sign-ins, two-step sign-in and passkey changes, password changes, team invitations and permission changes, claim exports and deletions, data exports and account deletions, with the time, IP address and browser. Each person can see their own events in Settings, Privacy and data. Events are kept for 24 months.
- Each claim also keeps an activity history of changes to the file.
- Application and infrastructure logs are reviewed for errors and suspicious activity.
Backups and continuity
- The database is backed up daily by our provider, and backups are stored in Canada.
- Our business continuity plan sets recovery targets; regular restore tests are part of our SOC 2 readiness work.
Data lifecycle
- Owners can export any claim at any time, and every person can download a copy of their own data.
- Deleted claims are removed at once, or after 15 business days if the organization chose to keep deleted claims for recovery.
- People can delete their account themselves. Expired codes, old visitor chats and old audit events are purged automatically on a schedule. Our Privacy Policy lists every retention period.
Incident response
If we become aware of a security incident affecting your data, we will investigate and contain it, notify affected customers without undue delay, and report to the Office of the Privacy Commissioner of Canada, the Commission d'accès à l'information du Québec and, where the GDPR applies, the competent supervisory authority within the time the law requires (72 hours under the GDPR).
Report a vulnerability
Email security@sredible.com with the details. We acknowledge reports within one business day and will not take legal action against good-faith research that respects our Terms of Service: do not access other people's data, disrupt the service or disclose the issue before we have had a reasonable time to fix it.