Security

How DeepSight handles mortgage documents

Learn how files are transmitted, temporarily stored, processed and deleted, including when overseas service providers are involved.

Draft — pending legal review. This text has not been finalised and may change before launch.

Version 0.5 · effective October 20, 2026

At a glance

How uploaded documents are handled

  • Account data is hosted in Australia (Sydney).
  • Document content and prompts are processed by service providers in the United States, including the AI model provider.
  • Uploaded files are held in temporary storage only while being processed, then deleted. A daily clean-up removes anything left behind.
  • Document text is not retained in DeepSight's account database. Review sessions and reports are stored in your browser.
  • API data is not used to train general-purpose AI models by default.
  • Selected service providers hold security certifications or independent audit reports for their own defined scope. These do not certify the DeepSight platform itself.

Data flow

One review, step by step

From the moment you attach a file to the moment the report is on your screen.

  1. 01

    You attach the files

    Your browser uploads them over HTTPS to private, account-scoped temporary storage. There is no public link to them.

  2. 02

    The server reads, then deletes

    When the review runs, our server reads the files into memory and deletes them from temporary storage before doing anything else — usually within seconds.

  3. 03

    The model generates the output

    The relevant document content and prompts go to the AI service provider with response storage switched off. That does not necessarily switch off the provider's short-term safety or abuse-monitoring retention, described below.

  4. 04

    The report comes back to you

    The report streams to your browser. Under the current design, review sessions and reports are stored in the browser profile used, not on our servers.

Retention

Where data is held, and for how long

Four places, each with its own rules.

01

Account database

Australia · Neon Postgres, Sydney

  • Your account details: until 30 days after the account is closed. Passwords are stored only as argon2 hashes; for Google sign-in, your Google account ID.
  • Credit balances, orders and a usage ledger (check, model, token counts, credits): 7 years.
  • Sign-in history, the activity log of reviews run with the attached file names, and an error log of failed requests: 12 months.
  • Not held here: the documents, the text read from them, your questions, the answers or the reports.

02

Temporary file storage

Private Vercel Blob store

  • Files are held only while being processed and are deleted as soon as the server has read them — usually within seconds.
  • A daily clean-up deletes any upload more than an hour old that was never read, such as an abandoned upload, so a stray file is kept for about a day at most.

03

AI processing

United States · OpenAI

  • Relevant document content and prompts are sent to generate the review output, with response storage switched off.
  • API data is not used to train OpenAI's models by default.
  • OpenAI may keep API content for up to 30 days for safety and abuse monitoring, then deletes it, unless it is legally required to keep it longer.

04

Your browser and operational metadata

Your device · our hosting provider

  • Review sessions and reports stay in the browser profile you use until you delete them or clear browser data. Other users of the same profile may be able to view them, so export the records you need and avoid shared or unmanaged devices.
  • Session history keeps the names of attached files, not the files.
  • Our hosting provider, Vercel, records request metadata such as IP address and browser type.

The Privacy Policy sets out the full retention schedule. Third-party handling is subject to each provider's disclosed processing and retention terms; this page does not claim that every service provider keeps nothing.

Safeguards

How the platform is protected

Encrypted in transit

HTTPS only, with TLS 1.2 or later and HTTP Strict Transport Security. The database connection is encrypted too.

Encrypted at rest

The database and the temporary file storage are encrypted at rest by their providers.

Account-scoped access

Uploads use account-scoped access controls and private storage, designed to restrict access between accounts. These measures are not a guarantee that unauthorised access is impossible.

Admin changes are recorded

Access to the admin console is limited to administrators, and every manual credit change records who made it and why.

Not used for training

We use AI providers whose API terms exclude customer content from model training by default, and we switch response storage off.

Incident response

We assess suspected personal-data incidents and notify affected individuals and the OAIC when notification is required under the Notifiable Data Breaches scheme and other applicable law.

Security contact

Security or vendor due-diligence enquiries, and suspected vulnerabilities: security@deeps-sight.com. When reporting a vulnerability, please avoid accessing information you are not authorised to view or disrupting the service. We welcome responsible vulnerability reporting.