Encryption · RLS isolation · Stripe PCI Level 1
Security at Brynlock
Brynlock encrypts all data in transit with TLS 1.2 or higher and at rest with AES-256 via Supabase managed Postgres on AWS. Every facility's data is isolated at the database layer with PostgreSQL Row-Level Security. Payments run through Stripe (PCI DSS Level 1), so Brynlock servers never store raw card numbers. Confirmed incidents are reported to affected operators within 72 hours.
Security contact: hello@brynlock.com
Last updated
Controls map
The table describes control areas and provider responsibilities. It is not an independent audit report or certification.
| Area | Control | Control area |
|---|---|---|
| Data in transit | TLS 1.2+ on all endpoints (TLS 1.3 preferred); HTTP redirects to HTTPS | Security |
| Data at rest | AES-256 via Supabase managed Postgres on AWS | Security · Confidentiality |
| Tenant isolation | PostgreSQL Row-Level Security on every public table | Security · Confidentiality |
| Authentication | Supabase Auth with secure cookies; service-role keys server-only | Security |
| Payment processing | Stripe PCI DSS Level 1; card data never touches Brynlock | Security · Confidentiality |
| Backups | Provider backup configuration; request retention and restore-test evidence | Availability |
| Logging & audit | audit_log table; tracked changes per record | Security · Processing Integrity |
| Vulnerability scanning | Continuous dependency scanning; manual code review on PRs | Security |
| Incident response | 48h acknowledgement · 72h customer notification on confirmed incidents | Security · Availability |
How Brynlock protects your data
Encryption
Encryption is the baseline. All data in transit is protected with TLS 1.2 or higher (TLS 1.3 for current browsers). Data at rest is encrypted with AES-256 via Supabase managed Postgres. Encryption keys are managed by Supabase and rotated on a regular schedule. See Supabase Platform Security for the underlying infrastructure controls.
Database row-level security
RLS covers every query made with a signed-in user's session. Every public table has PostgreSQL Row-Level Security policies that filter results by the authenticated user's facility_id before any row is returned. Service-role keys are restricted to server-side code paths (imports, scheduled jobs, health checks); they bypass RLS, so each of those paths scopes its queries to a facility in application code. Row-level isolation does not limit data portability. See the no vendor lock-in commitment for the export guarantee.
Payment security via Stripe
Card data never touches Brynlock servers. Payment processing runs through Stripe Elements, which sends card data directly from the tenant's browser to Stripe's PCI DSS Level 1 environment. Brynlock receives only the resulting payment_intent_id. See Stripe Security for processor controls.
Infrastructure and backups
Database records use Supabase and application hosting uses Vercel. Processing regions, subprocessors and backup retention depend on the configured services. Request current configuration and dated restore-test evidence before relying on residency or recovery requirements; we do not promise US-only processing or a fixed retention window here.
Incident response
48 hours to acknowledge, 72 hours to notify. Report incidents to hello@brynlock.com. All reports are acknowledged within 48 hours. For confirmed incidents affecting customer data, Brynlock notifies affected operators within 72 hours, consistent with state breach notification laws.
Responsible disclosure
Coordinated disclosure with researcher credit. Send vulnerability reports to hello@brynlock.com with steps to reproduce. Brynlock follows a 90-day coordinated disclosure timeline, credits researchers by name on request, and does not pursue legal action against good-faith research.
Common questions
How does Brynlock encrypt customer data?
All data in transit is encrypted with TLS 1.2 or higher, with TLS 1.3 negotiated by current browsers. Data at rest is encrypted with AES-256 via Supabase managed Postgres on AWS, with keys managed by Supabase and rotated on a regular schedule.
How is one facility's data isolated from another?
Every public table has PostgreSQL Row-Level Security (RLS). Queries made with a signed-in user's session are filtered against that user's facility_id by the database before rows are returned. Server-side jobs that use the service-role key (imports, scheduled jobs, health checks) bypass RLS, so those code paths scope every query to a facility in application code.
Is Brynlock SOC 2 certified?
This page does not provide a SOC 2 report or claim an independent examination has been completed. Contact us for current audit evidence before relying on SOC 2 assurance. A provider report does not establish that Brynlock itself has been examined.
Where is customer data stored?
Brynlock uses Supabase for database records and Vercel for application hosting. Other services process data as listed in our Privacy Policy. Contact us to confirm current regions and subprocessors for your requirements; this page does not promise US-only processing or storage.
How are backups handled?
Database recovery depends on the configured Supabase backup plan. Contact us for the current retention window and dated restore-test evidence before relying on a recovery commitment. Keep exports for your own operational continuity; an export is not a substitute for a tested database restore.
Does Brynlock ever store card numbers?
No. All payment processing flows through Stripe, a PCI DSS Level 1 certified processor. Card data passes directly from the tenant's browser to Stripe via Stripe Elements. Brynlock servers never receive, store, or log raw card numbers, CVVs, or full PANs.
What is the breach notification timeline?
For confirmed incidents affecting customer data, Brynlock notifies affected operators within 72 hours of confirmation, consistent with state data breach notification laws. Reports of suspected incidents are acknowledged within 48 hours of receipt at hello@brynlock.com.
How does Brynlock handle responsible disclosure?
Security researchers can report vulnerabilities to hello@brynlock.com. Brynlock follows a coordinated disclosure process, requests 90 days to patch before public disclosure, and credits researchers by name on request. Brynlock does not pursue legal action against good-faith researchers.
Security questions or audit requests?
Email hello@brynlock.com. Contact us for current security documentation. This page does not establish a completed or in-progress independent SOC 2 examination.