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. Last Updated: June 2026.
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 |
|---|---|---|
| Original documents | Supabase Storage (AWS S3) | Yes (AES-256) |
| Document chunks | Supabase database (PostgreSQL) | Yes (AES-256) |
| Knowledge entities | Supabase database (PostgreSQL) | Yes (AES-256) |
| Gap findings | Supabase database (PostgreSQL) | Yes (AES-256) |
| Generated outputs | Supabase database (PostgreSQL) | Yes (AES-256) |
| Stripe payment data | Stripe (not stored by us) | Yes (per Stripe policy) |
All data in transit is protected with TLS 1.3.
Third-Party Processors
| Service | Purpose | Data Shared |
|---|---|---|
| Supabase | Database and file storage | All project data |
| Anthropic | AI entity extraction and analysis (primary) | Document text chunks |
| OpenAI | AI generation, repair, and fallback (secondary) | Knowledge Model context |
| Google Gemini (via Lovable AI Gateway) | AI fallback (tertiary, failover only) | Knowledge Model context |
| Stripe | Payment processing | Email, payment details |
| Mailgun | Transactional email | Email address, email content |
| Cloudflare | Application runtime and edge routing | Request metadata |
Anthropic, OpenAI, and Google are accessed under API terms that prohibit using customer data for model training. The full subprocessor list with purpose and region is at /trust/subprocessors.
Retention Schedule
| Data Category | Active Retention | Post-Deletion Purge (Active Systems) | Backup Retention | Post-Cancellation Grace | Log Retention |
|---|---|---|---|---|---|
| Workspace content (requirements, decisions, objectives, stakeholders, comments, activity) | Retained for the life of the workspace | Purged from active systems within 30 days of deletion request | Removed from backups within 90 days | 30 days read-only grace, then deletion | n/a |
| Account & profile data (email, name, auth identifier) | Retained while account is active | Purged from active systems within 30 days of account deletion | Removed from backups within 90 days | 30 days grace before account deletion | n/a |
| Workspace membership records | Retained while workspace exists | Purged within 30 days of workspace deletion or member removal | Removed from backups within 90 days | Follows workspace lifecycle | n/a |
| Uploaded documents (X-Ray source files) | Retained while project exists | Purged from object storage within 30 days of project deletion | Removed from backups within 90 days | Follows project lifecycle | n/a |
| AI analysis outputs (gap findings, scores, generated artifacts) | Retained while project exists | Purged within 30 days of project deletion | Removed from backups within 90 days | Follows project lifecycle | n/a |
| Billing & payment records (invoices, subscription state) | Retained for 7 years after issue (financial recordkeeping) | Not purged on account deletion — retained as required by law | Per Stripe policy | n/a | n/a |
| Stripe payment data (card details, payment methods) | Stored only by Stripe; not stored by RequirementsHub | Per Stripe customer deletion process | Per Stripe policy | Per Stripe policy | n/a |
| Access & security logs (authentication, admin actions, security events) | Retained for security monitoring and incident investigation | Not purged on account deletion — required for security audit trail | Included in standard backup cycle | n/a | 12 months |
| Email communications (transactional emails sent via Mailgun) | Retained by Mailgun per their retention policy | Per Mailgun policy on request | Per Mailgun policy | n/a | Per Mailgun policy |
| Invitation records (pending and accepted workspace invites) | Pending invitations retained until accepted, revoked, or expired (30 days) | Purged within 30 days of workspace deletion | Removed from backups within 90 days | Follows workspace lifecycle | n/a |
- "Active systems" means the production database and object storage that serve live application requests. Once data is purged from active systems it is no longer accessible through the application or APIs.
- Backup retention reflects the rolling window during which deleted data may remain in encrypted backups before being overwritten. Backups are not restored or accessed except during disaster recovery.
- To request deletion outside the self-service flow, email privacy@requirementshub.ai. We will confirm completion in writing.
Data Residency
Customer data at rest is hosted in Supabase on AWS us-east-1 (Northern Virginia). We do not currently offer tenant-level region selection. Enterprise customers with data residency requirements should contact sales@requirementshub.ai.
Questions
Last updated: June 2026