Security

Baseline commitments

• Encrypt files at rest in object storage.
• Do not train on customer data.
• Provide deletion: contract deletion removes source files and derived outputs.
• Log access to contracts and authentication events.

Access control

• Org-based access control: users can only access contracts in their org.
• All routes under /app require authentication.
• Server-side authorization checks on every contract fetch.

Auth security

• No password auth.
• Rate limit magic link requests by IP + email.
• Database sessions (revocable).
• Audit log sign-in and failed sign-in events.

Data minimisation

• Store only what is needed for extraction and reminders.
• Avoid storing full extracted plain text unless required; store evidence quotes + metadata.

Legal safety

• “Not legal advice” displayed in UI.
• Evidence-first UI: show clause quote next to summary.

Renewal Guard (UK) — Docs Index

These docs define the product, scope, data model, extraction schema, prompts, security constraints, and coding standards.

Codex rule: When implementing features, follow these docs in this order:

1. PRODUCT.md
2. REQUIREMENTS.md
3. AUTH.md
4. DATA_MODEL.md
5. EXTRACTION_SPEC.md
6. PROMPTS.md
7. SECURITY.md
8. CODING_STANDARDS.md
9. RUNBOOK.md
10. ROADMAP.md