How we protect your data.
The controls below are in place today. Anything still planned is marked as planned.
Last reviewed 5 August 2026
Encryption
04- AES-256-GCM
- Sensitive fields encrypted individually before they reach the database
- Managed key protection
- Encryption keys are protected and regularly rotated through a managed key service and cannot be exported by the application
- Encrypted at rest
- Database storage, snapshots and backups
- TLS 1.2+
- Enforced on every connection; older protocols refused
Access
03- Multi-factor sign-in
- Authenticator apps and hardware security keys
- Audit trail
- Who changed what, and when — exportable
- Restricted staff access
- Limited to support and fault investigation, and logged
AI
03- Approval required
- The assistant works inside the permissions you set; money movement and lodgements wait for a person
- Sensitive data protection
- Data is classified by sensitivity and limited to what is necessary before being submitted to a model service
- No training on your data
- Your records aren't used as training data, by us or our providers
Resilience
04- 35-day recovery
- Point-in-time restore to any minute in the window
- Multi-zone resilience
- Production data is protected through availability-zone redundancy
- Deletion protection
- Production database cannot be dropped by a single action
- Additive corrections
- Posted records aren't edited in place; fixes create a visible entry
Privacy
03- No card numbers stored
- Payment details handled by our PCI DSS certified payment provider
- No data sold
- Not to advertisers, data brokers, or partners
- Export and delete
- On request, subject to records we're required to retain
Compliance status
03- SOC 2
- Planned
- Our control design references SOC 2 and NIST. Aiviance does not currently hold a SOC 2 report.
- Australian Privacy Principles
- Applicable
- Personal information is managed with reference to the Privacy Act 1988 (Cth), the Australian Privacy Principles and applicable data-breach notification obligations.
- GDPR
- Rights supported
- Requests for access, correction, erasure and portability can be submitted to privacy@aiviance.ai where applicable.
We publish the current status of each framework. Certifications and reports are listed only after they have been formally completed, and this page is updated when that status changes.
Phishing and impersonation
04Services handling financial data may be targeted by phishing or impersonation attempts. The following principles always apply; any message that contradicts them should not be treated as an official Aiviance communication.
- We will never ask for your password, your one-time code, or your bank sign-in — not by email, not by text, not on a call.
- Our email only ever comes from an @aiviance.ai address. Read the domain, not the sender name.
- We will never ask you to move money, pay an invoice, or change payment details because an email told you to.
- Bank connections and payments happen inside Aiviance, after you have signed in yourself — never through a link that collects your bank details on the way.
If a message does not follow these principles, do not open its links. Access Aiviance by entering the address yourself or using a saved bookmark, then forward the suspicious message to security@aiviance.ai.
Reporting a vulnerability
If you discover a potential security issue affecting Aiviance, send the details to security@aiviance.ai. We receive, assess and respond to good-faith security reports through the process below.
What to include
- What you found, and the URL or endpoint it affects
- The steps to reproduce it, or a short proof of concept
- What someone could do with it, in your view
- How to reach you if we need more detail
What happens next
- We aim to acknowledge reports within five business days
- Following initial assessment, we provide an appropriate update on the status of the report
- With mutual agreement, we may recognise the researcher publicly
Safe harbour
Research carried out in good faith under this policy is authorised: we won't pursue legal action over it, and we won't ask anyone else to.
Staying inside the policy means testing only against your own account and your own data; never accessing, altering, or keeping another customer's records; not degrading the service for anyone else; and giving us a reasonable window to fix the issue before you publish. Denial-of-service testing, spam, physical attacks, and social engineering of our staff or suppliers are outside it.
Aiviance does not currently operate a paid vulnerability-reward programme. We still encourage researchers to submit security issues under this policy and will provide an appropriate update on their assessment and status.
Common questions
Aiviance production data is stored in Australia and protected through encryption and dedicated key-management controls.
Only authorised personnel may access relevant data when necessary to provide customer support or investigate faults. All access activity is recorded in audit logs.
No. Neither Aiviance nor its model service providers use your financial data to train models. Before a request is sent to a model service, the data is classified and limited to the information required for that task.
Not currently. Aiviance security controls are designed with reference to SOC 2 and NIST control frameworks. This status will only be updated after the relevant certification or assessment has been formally completed.
You can export your data and request account deletion. Some financial records may need to be retained to meet statutory obligations, so not all data can necessarily be deleted immediately after an account is closed.
Aiviance will never ask for your password, one-time code or online banking credentials through any channel. Official email is sent only from the @aiviance.ai domain; verify the sender domain and treat any request for this information as suspicious.
Found something we should fix?
Vulnerability reports and security reviews go straight to the team.