Data Handling
Where Your Data Lives
RequirementsHub builds a Knowledge Model from your documents — a structured map of stakeholders, objectives, systems, constraints, and requirements. This page explains how that data is stored, encrypted, and deleted, and which third parties process it.
What Is the Knowledge Model?
When you upload a document, we extract entities — named stakeholders, objectives, systems, constraints, requirements, and the relationships between them. This structured model is what powers gap detection, traceability, and maturity scoring. The original document is preserved alongside it.
Data Storage & Encryption
| Data Type | Where Stored | Encrypted | Deleted When |
|---|---|---|---|
| Original documents | Supabase Storage | Yes (AES-256) | Project deleted |
| Document chunks | Supabase database | Yes | Project deleted |
| Knowledge entities | Supabase database | Yes | Project deleted |
| Gap findings | Supabase database | Yes | Project deleted |
| Generated outputs | Supabase database | Yes | Project deleted |
| Stripe payment data | Stripe (not stored by us) | Yes | Per Stripe policy |
All data in transit is protected with TLS 1.3. Deletion of a project propagates through storage and database within 24 hours.
Third-Party Processors
| Service | Purpose | Data Shared |
|---|---|---|
| Supabase | Database and file storage | All project data |
| Anthropic | AI entity extraction and analysis | Document text chunks |
| OpenAI | AI generation first pass | Knowledge Model context |
| Stripe | Payment processing | Email, payment details |
Anthropic and OpenAI are accessed under enterprise API terms that prohibit using customer data for model training. No other AI providers receive your data.
Data Residency
Primary infrastructure is hosted in the United States and the European Union, depending on your account region. Contact us if your engagement requires a specific data residency commitment.
Questions
Last updated: June 2026