amply

Privacy Policy

Last updated: 18 October 2026

This policy explains what personal information amply Pty Ltd ("amply", "we", "us") collects through the amply Advice Assistant web application (app.amplyadvice.com.au), how we use and protect it, and the choices you have. amply is a technology provider — we do not hold an Australian Financial Services Licence and do not provide financial advice ourselves.

Who this policy covers

amply is a tool used by financial advisers and their licensees. This policy covers information about advisers who use the platform and information advisers enter about their clients while using it. If you are a client whose adviser uses amply, your adviser (not amply) is responsible for how your personal information is collected and disclosed to us, and remains your primary point of contact for privacy questions.

What we collect

We collect the following categories of personal information:

We do not use third-party advertising or web analytics trackers in the application, and we do not collect information for advertising purposes.

How we use it

We use personal information to:

We do not sell personal information, and we do not share it with third parties for their own marketing purposes.

Where information is stored and processed

Client profiles, projections, and uploaded documents are stored in Google Cloud and Firebase infrastructure in Sydney, Australia (australia-southeast1). Application servers run in the same region. Some features send data to the providers listed below, and several of those process it outside Australia.

If you connect an assistant (such as Claude, ChatGPT, or Cursor) in Settings, client facts included in that assistant's tool results are sent to the assistant product you chose. Those results can include client and partner first names, ages, balance totals, missing profile fields, saved scenario names, and projection results. They do not include contact details. amply does not control that product's retention, training, or where it processes data; its own privacy terms apply. You can disconnect the assistant at any time under Settings, then Integrations, and its next request is refused.

Third parties we use (sub-processors)

ProviderPurposeRegion
Google Cloud / FirebaseDatabase, file storage, hosting, and application serversAustralia (Sydney)
Firebase AuthenticationAdviser sign-inGlobal (not pinned to Sydney)
Google Vertex AI (Gemini 2.5 Flash)Document summaries and the Gemini fact-find fallback, until 20 October 2026Australia (Sydney)
Google Vertex AI (later Gemini models)Summaries after 20 October 2026, and any Gemini 3 model an adviser selectsOutside Australia
Anthropic (Claude)Default models for AI chat and the advice agentOutside Australia
LangSmithError and performance tracing. Prompts, responses, and audio are not sent. Account and client identifiers, timings, and error details may be.United States
StripeSubscription billing and payment processingGlobal
DeepgramVoice-to-text transcription. Audio is not kept by amply and is opted out of model training.United States
Google Vertex AI LiveSpoken Talk sessionsUnited States
Google Calendar APICalendar sync, when you connect it in SettingsGlobal
Google Gmail APIReading or drafting email, when you connect it in SettingsGlobal
Google Document AIDocument text extraction (OCR)Australia (Sydney)
Connected assistant (Claude, ChatGPT, Cursor, or another MCP client)Projection and client-summary results, only after you connect that assistant and accept the on-screen consent. You can revoke the connection in Settings.Chosen by the adviser. Not controlled by amply.

Alpha period notice

amply is currently in a pre-release alpha phase. Data retention, backups, and availability are not guaranteed during this period. Advisers should avoid entering real client information they are not authorised to store with a third-party technology provider, and should prefer synthetic or anonymised test data where practical.

Security

Traffic between your browser and amply is encrypted with TLS, and browsers are instructed to connect only over HTTPS (HSTS). Data stored in Google Cloud is encrypted at rest with AES-256 by Google. Sensitive credentials, such as Google Calendar and Gmail refresh tokens, are encrypted again by the application before they are stored. Access to production data is restricted to authorised personnel. amply does not store payment card details — these are handled directly by Stripe.

Your rights

Under the Privacy Act 1988 (Cth) and the Australian Privacy Principles, you may request access to, correction of, or deletion of personal information we hold about you, and you may opt out of your data being used to improve the platform. To make a request, contact us at support@amplyadvice.com. We aim to respond within 30 days.

Cookies

We use only essential cookies and browser storage required for signing in and maintaining your session. We do not use cookies for advertising or cross-site tracking.

Children

amply is a professional tool for financial advisers and is not directed at children.

Changes to this policy

We may update this policy as the platform evolves. Material changes will be reflected by updating the date at the top of this page.

Governing law

This policy is governed by the laws of New South Wales, Australia.

Contact us

Questions about this policy or your personal information can be directed to support@amplyadvice.com.