Database • permissions • audit logs

Secure Production Database

The platform now includes a PostgreSQL schema blueprint and JSON fallback store. Production should use the database, encryption, backups, and server-enforced permissions before broad paid launch.

Core tables
  • users
  • matters
  • drafts
  • uploads
  • documents
  • versions
  • finished_items
Operations
  • payments
  • service_products
  • referral_accounts
  • referral_locks
  • referral_rewards
  • payout_requests
  • audit_logs
Review/finalization
  • attorney_profiles
  • conflict_checks
  • attorney_engagements
  • ai_voice_runs
  • finalization_handoffs
  • finalization_releases
Production rule: browser-local records are not enough for real users. Use production database records, encrypted storage, access logs, malware scanning, backups, password reset, and permission checks.