Tenant isolation
Every tenant-owned record is designed to carry a tenant boundary. Database row-level security, application authorization, storage paths, AI retrieval, background jobs, and audit logs are planned to be tenant scoped.
Trust posture
Security and data residency are product requirements, not afterthoughts.
AdviserPro is intended for sensitive borrower and mortgage-advice information, including identity documents, bank statements, income evidence, liabilities, assets, property records, lender submissions, and advice notes.
Region-aware storage
Source documents and derived artefacts are planned to stay in approved storage regions. New Zealand storage is preferred where required, with Australia/Sydney considered for accepted MVP tenants where clearly disclosed and contracted.
Audit logging
Important events such as document upload, view, download, accept, reject, role changes, AI runs, source usage, application edits, and submission status changes are intended to be retained for review.
Controlled access
The platform model separates authentication from AdviserPro permissions. Roles, memberships, signed document access, revocable public links, and least-privilege storage integrations are core design principles.
Infrastructure direction
Lean MVP today, enterprise-ready path tomorrow.
The current product direction uses Vercel, Supabase Postgres/Auth/Storage, and OpenAI APIs for the MVP, with Supabase hosted in the Oceania/Sydney region. The architecture is being shaped so AdviserPro can support tenant-owned Microsoft 365 storage and AdviserPro-managed AWS S3 storage in New Zealand or Australia as customer assurance needs mature.
Encryption in transit and at rest
Row Level Security for tenant data
Signed expiring links for documents
No PII in analytics events or app logs
OpenAI treated as a processor, not a system of record