Security
UseNorth handles personal and professional information — names, roles, work email addresses, and the diagnostic responses that participants give in conditions they are meant to experience as honest and safe. The security model reflects that responsibility.
What is collected and why
| Data | Where stored | Why collected |
|---|---|---|
| Name, role, email, organisation | north_leads, north_responses | Credential issuance and session tracking |
| Scenario responses | north_responses (jsonb) | Scoring and team map generation |
| Reflection text | north_responses | Qualitative diagnostic input for the Brief |
| Archetype and scores | north_leads | Credential and Strategist Brief input |
| Session codes | north_sessions | Team session coordination |
| Cloud platform and constraints | execution_* tables | NORTH Build credential and team output |
No third-party analytics platform receives individual participant data.
Key management
The Supabase publishable key is designed for browser exposure. It is committed to .env.example as a placeholder format. The actual production key is set in Vercel environment variables and .env.local (gitignored).
GOOGLE_AI_API_KEY is used exclusively in server-side API routes (e.g. /api/strategist-brief). It is not exposed to the client, not included in any client-side bundle, and not logged.
RESEND_API_KEY lives in Supabase Edge Function secrets — set via the Supabase dashboard, never in source code, never as a fallback value.
Database security
Participant data is served only through authenticated API endpoints; we run continuous external security review of those endpoints. Last completed: August 2026.
Direct database access (Supabase secret key, database password) is restricted to infrastructure operations and never touches client-side code.
Participant data handling
A participant's dimension scores are used to calculate their archetype and drive the adaptive Reckoning. In team outputs they appear only as aggregate pattern on the Coalition Map, which shows pattern, not score.
It shows pattern, not score. Individual responses cannot be reverse-engineered from the map.
The document is generated for the consulting partner and marked confidential. The input data (Coalition Map, Tension Map) is stored but the generated Brief text is ephemeral.
The qualitative reflection responses are stored to enable the Strategist Brief. They do not appear in team session outputs.
Responsible disclosure
If you discover a security vulnerability in UseNorth, please report it privately before disclosing it publicly.
Include a description of the vulnerability, steps to reproduce, the potential impact, and any suggested remediation. We acknowledge receipt within 48 hours and respond with an assessment within 5 business days.
Please do not open a public GitHub issue for security vulnerabilities.
Compliance
This document is reviewed and updated with each significant change to data handling, infrastructure, or third-party integrations. Last reviewed: 1 August 2026.