Data handling

Framework version: 7 October 2026. Applies to FINMOND Intelligence.

Operator: FINMOND Global Limited. Contact: admin@finmond.co.uk.

Data flow

Account → private project brief → research plan → provider research and public source retrieval → source evidence and quality checks → typed analysis → versioned report artifacts → owner approval → private workspace publication → transactional notification → scheduled monitoring and evidenced alerts.

Access model

Server-side authentication and project ownership checks protect every workspace and report route. Ordinary users cannot access owner administration. Downloads require an authenticated session. Email links open the private application and never expose a public artifact directory. Account recovery and verification links are time limited and single use.

Storage and processors

The V1 architecture stores SQLite records and report artifacts on the configured persistent data volume. Passwords and session identifiers are stored as hashes. Provider secrets remain in deployment environment variables. Hosting disk encryption and encrypted backup storage are operator configuration obligations. OpenAI, Stripe and the configured SMTP provider receive the data needed for their functions. The operator must record the actual providers, region, contracts and transfer safeguards before onboarding commercial clients.

Retention, deletion and backups

Report versions and their hashes remain available for history and review. Maintenance can remove expired authentication records and clear old successful email bodies. Client exports, deletion requests and account closure require an authorized operator workflow. Backups contain private data and must be restricted, encrypted and tested for recovery. A deletion is not complete until it is also covered by the backup expiry policy.

Research evidence

Each material conclusion should retain its source relationship, retrieval timestamp, extracted evidence and appropriate quality score. Assumptions and model interpretation are labeled. The service does not invent missing evidence. Monitoring stores previous and current observations and does not send an alert for an unchanged baseline.

Incident handling

The operator must investigate suspected cross-client access, protect affected accounts, preserve relevant audit evidence, restore service safely and assess notification duties under applicable law. Contact the operator promptly with the account, project reference and observed issue; never include passwords or secret keys.