OnboardMe

Terms & policies

  • Privacy Policy
  • Terms of Service
  • Data Processing Agreement
  • Electronic records & signature disclosure
  • Google user data

Trust & security

  • Information security & business continuity
  • Subprocessors
  • Data storage & backups
Contact usLog in

© 2026 OnboardMe Pty Ltd

Privacy Policy

Last updated October 2026

Summary

This Privacy Policy explains how OnboardMe collects, uses, stores and discloses personal information, and what rights and controls you have over that information. We handle personal information as described in this Policy and applicable privacy law. If you do not agree with this Privacy Policy, you should not use our website or Services.

As a professional services platform, we recognise the sensitive nature of the information we process, including Unique Taxpayer References (UTRs) and similar tax identifiers, bank account details, identity documentation, and confidential business information. Protecting this data is a legal obligation and a core part of our mission.

Your use of the Service is also governed by our Terms of Service. Where we process personal information on behalf of your organisation (for example your clients' information), our Data Processing Agreement applies and forms part of our agreement with that organisation.

General

The operator of the OnboardMe platform is OnboardMe Pty Ltd (Australian company), trading as OnboardMe. OnboardMe provides a cloud platform for professional service firms to support client onboarding, engagements, payments and billing, and identity verification / AML screening (where enabled), among other workflows.

For personal information we collect in our own business capacity (for example account administration for your firm's subscription, our billing of your firm, security, and product improvement), OnboardMe Pty Ltd is generally the organisation responsible for how that information is used.

When your firm uses OnboardMe for its clients, your firm is responsible for that client data as the "controller" or equivalent under local law. We provide the platform only, and act as a "processor" or service provider for that processing, following your firm's instructions and our Data Processing Agreement. This Policy still describes how the platform works and our security practices; your firm's privacy notice may also apply to you.

Definitions

In this Privacy Policy:

  • OnboardMe, we, us or our means OnboardMe Pty Ltd (ACN 680 379 640) and, where the context requires, the personnel who operate the Service.
  • You means the individual reading this Policy, including a practice user or a client of a practice using the Service.
  • Customer means the organisation that subscribes to the Service.
  • Applicable privacy law means the UK GDPR and the Data Protection Act 2018.
  • ICO means the Information Commissioner’s Office.
  • Website means the OnboardMe websites and applications from which the Services are provided for this deployment, including uk.onboardme.app, and our marketing website at www.onboardme.app.
  • Personal information means information about an identified or reasonably identifiable individual, including "personal data" under UK GDPR and equivalent terms under applicable privacy law.
  • Client Data means personal information relating to the Customer's clients that is processed in the Service on the Customer's behalf. It forms part of what the Terms of Service call "Your Data".
  • Services means the OnboardMe platform for this deployment, including related websites and APIs.
  • Sensitive information — Special category data has the meaning in UK GDPR Article 9. Biometric data used for unique identification is special category data. Identity documents, UTRs, and bank details are personal data and may be confidential, but they are not automatically special category data. Where identity verification involves special category data, the Customer (as controller) is responsible for having an Article 9 condition; OnboardMe processes that data only as processor to provide the enabled feature.

Data Processing Agreement

When your firm uses OnboardMe for its clients, we act as a processor (or the equivalent under local law) as described above. The written terms for that processing — including what we are instructed to do, subprocessors, international transfers, security measures, breach notification, assistance with individual rights, and deletion at the end of the subscription — are set out in our Data Processing Agreement.

That DPA is incorporated into the Terms of Service for this deployment. It applies automatically to client data your organisation puts into the Service. If your organisation needs a countersigned copy for procurement, contact us using the details at the end of this Policy. A separately signed DPA prevails over the standard DPA to the extent they conflict.

The DPA does not apply to information we handle as an independent organisation (for example your firm's subscription billing and staff login accounts). End clients of your firm are not parties to the DPA; they should contact your firm about their information, and we will assist your firm as described in the DPA.

High-risk and restricted information

In addition to ordinary personal information (such as name, email, and phone), OnboardMe may process information that is legally restricted, commercially confidential, or both:

  • Sensitive / special category / special personal information as defined in applicable privacy law — in particular biometric data used for identity verification where that feature is enabled
  • Government identifiers: Unique Taxpayer References (UTRs) and similar tax identifiers
  • Bank account and payment details
  • Identity verification documents (for example passports and driving licences) and AML / PEP / sanctions screening records
  • Confidential business content such as engagement letters, contracts, and professional service records (typically not sensitive / special category / special personal information, but confidential)

Special category data has the meaning in UK GDPR Article 9. Biometric data used for unique identification is special category data. Identity documents, UTRs, and bank details are personal data and may be confidential, but they are not automatically special category data. Where identity verification involves special category data, the Customer (as controller) is responsible for having an Article 9 condition; OnboardMe processes that data only as processor to provide the enabled feature.

These categories are subject to tighter access control and encryption as described in this Policy and our Information security & business continuity policy.

Types of personal information we collect

Depending on how you use the Service, we may process:

  • Identity and contact: name, email, phone, postal address, job title, employer, practice or entity identifiers.
  • Electronic signatures: signature images, typed or drawn signatures, and related audit metadata when you sign documents in the Service.
  • Account and technical: login identifiers, session and device data, IP address, audit logs, integration identifiers (where you connect third-party systems).
  • Service content: information you or your organisation enters into forms, proposals, engagements, ethical letters, identity verification and AML screening flows, and related workflows.
  • Identity and AML verification: where those features are enabled, identity documents, facial / biometric capture used for matching, verification outcomes, and screening results returned by our verification provider.
  • Financial: billing details, subscription records, and transaction-related data processed by our payment partners where you pay us.
  • Usage and diagnostics: feature usage, performance metrics, error reports, and aggregated analytics.

How we collect personal information

We collect personal information only if it is reasonably necessary for our functions and activities, including providing the Services. We may collect personal information when:

  • you access, use, or otherwise interact with our website or Services;
  • a Customer (or a person acting for a Customer) submits Client Data so we can provide the Services at their request;
  • you communicate with our staff during support, billing, or onboarding;
  • we receive it from a third-party system the Customer has connected (for example a practice management or accounting integration); or
  • you otherwise deal with us in the course of our business.

Where we collect Sensitive information, we do so only where it is reasonably necessary for the Services (for example identity verification the Customer has enabled) and where collection is permitted or authorised by law, including with consent where required.

Where a Customer submits Client Data, that Customer is responsible for giving those individuals an appropriate collection notice (and any consent the law requires) before or at the time of collection. This Policy describes how we handle that information as a service provider. We do not independently notify every individual whose details a Customer enters, unless the law requires us to.

Why we collect, hold, use and disclose personal information

We process personal data for the purposes described in this Policy. Typical lawful bases under UK GDPR include: performance of a contract with you or your organisation; compliance with a legal obligation; legitimate interests (such as securing the Service, improving reliability, and preventing abuse), balanced against your rights; and consent where we rely on it for specific processing (for example, certain cookies or marketing where applicable).

Purposes and lawful bases (UK GDPR)

The table below summarises typical processing. Specific lawful bases may depend on our relationship with you or your organisation.

PurposeTypical lawful basis
Operating the Service (accounts, authentication, core features)Contract; legitimate interests (service delivery and security)
Billing, subscriptions, and financial recordsContract; legal obligation
Security, fraud prevention, abuse detection, loggingLegitimate interests; legal obligation
Identity verification and AML / PEP / sanctions screening (via ComplyCube where enabled)Processed as processor on the Customer’s instructions. The Customer is responsible for its Article 6 basis and, where special category data is involved (for example biometric data used for unique identification), its Article 9 condition.
Product analytics and diagnostics (aggregated or pseudonymous where possible)Legitimate interests; consent where required for non-essential cookies
Service messages and (where applicable) product updates to practice usersContract (service messages); legitimate interests or consent where PECR requires it (marketing)
Legal and regulatory compliance (including tax and AML-related obligations where applicable)Legal obligation; legitimate interests

Third parties requesting the Services

Professional firms use OnboardMe to onboard and engage their own clients. If a Customer (your accountant, lawyer, or other adviser) puts your information into the Service, that Customer decides what to collect and how to use it for their professional work. That Customer is responsible for its own privacy notice and for any consent the law requires. We do not control that Customer's privacy practices. We still take the security steps described in this Policy for information we hold.

Connecting an optional integration (for example Xero, FYI, GreatSoft, or Google Workspace) is the Customer's choice. That does not mean we endorse the third party's privacy practices. You should read the Customer's privacy notice and the third party's terms. Requests about Client Data should usually go to the Customer first; we assist as described in our Data Processing Agreement.

Direct marketing

We send service and transactional messages to practice users as needed to operate the Service. We may also send product and related updates to practice users at their work contact details. Where PECR or UK GDPR requires consent for electronic marketing, we will only send those marketing messages with consent. You can opt out of marketing at any time via unsubscribe or by emailing [email protected]. We do not use Client Data for OnboardMe marketing, and we do not disclose personal data to third parties for their own direct marketing without consent.

How we store and protect personal information

Production data for this deployment is stored in the AWS London region, consistent with UK data protection and sovereignty laws. Backups, recovery objectives, and security controls are described in our Information security & business continuity policy.

We take reasonable steps to:

  • take reasonable steps so that personal information we collect is accurate, up-to-date, complete and relevant, having regard to the purpose of collection
  • take reasonable steps so that personal information we use or disclose is accurate, up-to-date, complete, relevant and not misleading, having regard to that use or disclosure
  • take reasonable steps to protect personal information from misuse, interference and loss, and from unauthorised access, modification or disclosure
  • destroy or de-identify personal information we no longer need for the purposes for which it was collected, except where we must or may retain it (for example legal, tax, or dispute records, or encrypted backups until they expire)
  • Encryption: Customer data is encrypted in transit using TLS 1.2+. Data at rest on this AWS deployment is encrypted (including via AWS KMS / AES-256 for volumes and object storage), as described in our Information security & business continuity policy. Tax identifiers and other high-risk fields are subject to additional access restriction.
  • Access controls: Role-based access control (RBAC) and authentication policies limit OnboardMe staff access. Multi-factor authentication (MFA) is mandatory for OnboardMe staff accounts and privileged production access. Subprocessors are bound by confidentiality and security obligations appropriate to their role.
  • Monitoring: Access and security events are logged and monitored. Alerts may be sent to our security team at [email protected].
  • Backups: Encrypted backups are maintained within the United Kingdom (London region).
  • Retention: We retain personal information only as long as needed for the purposes above, including to perform our contract, meet legal, tax, and regulatory record-keeping duties, resolve disputes, and enforce agreements. When it is no longer required, we delete, de-identify, or anonymise it using secure methods. Typical periods are set out below.
  • Client Data: until the Customer deletes it in the Service, or within 90 days after the Customer's subscription ends (see the Data Processing Agreement).
  • Encrypted database backups: up to 365 days, after which deleted data no longer exists in any backup. Backups are not restored into production except for disaster recovery.
  • Practice user accounts: while the account is active, and then for as long as needed to close out the Customer relationship.
  • Subscription, invoice, and payment records: for as long as tax and company law requires (generally five to seven years, depending on the country).
  • Audit and security logs: 12 months.
  • Website enquiries and mailing-list data: until the enquiry and any resulting relationship ends, or until you unsubscribe.

Transmission of information over the internet is not completely secure. We cannot guarantee the security of information in transit. Once we receive it, we take the steps described in this Policy and our Information security & business continuity policy. Those steps do not reduce our security obligations under applicable privacy law.

This Policy does not cover the privacy practices of third parties (including Customers and optional integrations). We are not responsible for those practices.

Who we disclose personal information to

We do not sell your personal information. We share it only as needed to run the Service, comply with law, or with your direction, including with:

  • Infrastructure and security: cloud hosting, backup, logging, and monitoring providers for this deployment (see the Material subprocessors table below; primary hosting is AWS London region).
  • Identity verification and AML: when your organisation uses identity verification or anti-money laundering (AML) screening features, we share relevant personal information with ComplyCube, a United Kingdom-based identity and AML verification provider (see their Security & Compliance Center for further detail). This may include identity and contact details, identity documents, live facial images or biometric data used for verification, and AML / PEP / sanctions screening inputs and results. ComplyCube processes and stores that data in the United Kingdom. These features are enabled and directed by your organisation; ComplyCube acts as our subprocessor for that processing.
  • Analytics and diagnostics: PostHog, Sentry, and (on AWS deployments) CloudWatch, as described under Using our website and cookies.
  • AI-assisted features: OpenAI (United States), which receives the content a user submits to an AI-assisted feature (for example text used to draft an eForm template) and returns a draft. We do not use that content to train AI models.
  • Advertising measurement: Meta, when you sign up for a trial, as described under Our website.
  • Communications: email and SMS delivery providers (Resend and Mailgun for email, and TallBob for SMS) used to send transactional or service-related messages.
  • Payments: Stripe processes payment and billing-related personal data as needed to collect our fees for this deployment. Where a Customer uses the Service to collect payments from its own clients, we collect those payments on the Customer’s behalf through the same payment providers, which receive the payer’s name, contact and payment details. Payment providers may also process that information as independent organisations for their own fraud-prevention, card-scheme and legal obligations.
  • Optional integrations: practice management, accounting, document, or email systems that you or your organisation choose to connect (for example Xero, FYI, GreatSoft, Google Workspace, or Microsoft 365 for sign-in and sending email from the firm's own mailbox). What is shared depends on the integration and your configuration. These are generally engaged at your organisation's direction rather than as OnboardMe's default subprocessors.
  • AI assistants your organisation connects: if your organisation connects an AI assistant (for example Claude, ChatGPT, or Microsoft Copilot) to OnboardMe through our MCP server, that assistant can read and act on Client Data the connected user can access. The assistant is chosen and authorised by your organisation, processes data under its provider's terms (often in the United States), and is not an OnboardMe subprocessor.
  • Professional advisers: lawyers, accountants, or insurers where required and subject to confidentiality.
  • Authorities: regulators, courts, or law enforcement when we are legally required or permitted to respond.
  • Corporate transactions: a prospective or actual purchaser, investor, or successor, on confidential terms, if we negotiate or complete a sale, merger, or restructure of our business.

Subprocessors

The table below lists material third-party subprocessors we use to operate this deployment of the Service. Where a name is linked, it opens that provider's privacy or security policy. Optional integrations you connect yourself are not listed here.

SubprocessorPurposeLocation
Amazon Web Services (AWS)Cloud hosting, backups, logging, and monitoringUnited Kingdom (London region)
ComplyCubeIdentity verification and AML / PEP / sanctions screening (where enabled)United Kingdom
StripePayment processingAs operated by Stripe for United Kingdom payments
ResendTransactional and service email deliveryUnited States (and other locations as operated by Resend)
MailgunTransactional and service email deliveryUnited States and other locations as operated by Mailgun
TallBobSMS messagingAustralia (as operated by TallBob)
OpenAIAI-assisted features, such as drafting an eForm template from content a user supplies (not used to train AI models)United States
UptimeRobotExternal uptime and availability monitoringAs operated by UptimeRobot
PostHogProduct analytics and diagnosticsEuropean Economic Area (PostHog EU Cloud)
SentryApplication error monitoring and diagnosticsEuropean Union (error ingestion in Germany)

We may update this list from time to time. Material changes are communicated in line with your agreement with us (for example, via product notices or email to organisation administrators), including the subprocessor notice process in our Data Processing Agreement.

Using our website and cookies

We use cookies and similar technologies to operate the platform, maintain secure sessions, remember preferences, measure performance, and improve the product.

Types of tracking

  • Essential cookies: Required for login, secure sessions, and core App features.
  • Analytics cookies / technologies: Help us understand how features are used so we can improve reliability and design.
  • Functional cookies: Remember preferences such as theme or language.
  • Security cookies: Support detection of unusual behaviour and protection against abuse.

Third-party analytics and diagnostics

We use PostHog (EU Cloud) for product analytics, Sentry (error ingestion in Germany) for diagnostics, and AWS CloudWatch for operational metrics on this deployment. Error reports may include identifiers such as IP address, user or account IDs, and request context needed to diagnose faults. These tools are used for security, reliability, and product improvement — not to sell personal data.

Your choices

Essential cookies are required for the Service to function securely. For non-essential cookies (for example, some analytics), we aim to align with applicable requirements (including PECR) and your organisation’s choices; you can also use browser controls where appropriate.

Our website (www.onboardme.app)

This section covers visitors to our marketing website at www.onboardme.app, whether or not your organisation uses OnboardMe. Once you sign in to or start a trial on a regional app (for example anz.onboardme.app), the rest of this Policy applies to how we handle your information there.

What we collect on the website

  • Contact form: your name, email address, and optionally your phone number and business name, your message, and whether you would like marketing emails. We use this to reply to you. The message is emailed to our team through Resend and kept only as long as we need it to deal with your enquiry and any relationship that follows.
  • Mailing list: if you join our mailing list, or tick the marketing box on the contact form, we use your name and email address to send product updates and related news. You can unsubscribe at any time using the link in each email or by emailing [email protected].
  • Technical information: your IP address, browser and device details, and the pages you request, which our hosting provider processes to deliver the website and keep it secure. When you submit a form, Cloudflare Turnstile checks that the request comes from a person rather than a bot.

Analytics and cookies on the website

The first time you visit, we ask whether you accept analytics cookies.

  • If you accept: PostHog sets a first-party cookie (named ph_ followed by our project key) containing a random identifier, so we can recognise your browser on later visits. We record the pages you view, what you click, how far you scroll (heatmaps), page performance, and session recordings of how you use the site. Text you type into form fields is masked and is not recorded. The cookie can be read across onboardme.app sites. We also load the Meta Pixel, which sets cookies (_fbp, and _fbc when you arrive from a Facebook or Instagram ad) so we can measure how our ads perform.
  • If you decline, or before you choose: we set no analytics cookies and use no local storage. PostHog counts your visit anonymously using a privacy-preserving value calculated on its servers, which cannot identify you and is not used to recognise you on a later day. No session recordings are made.
  • Location: PostHog uses your IP address to estimate your approximate location (country and city).
  • Your choice is remembered in a cookie (named __ph_opt_in_out_ followed by our project key) so we don't ask on every visit. You can change it at any time using Cookie settings at the bottom of every page on the website.

Our intro video is loaded from YouTube's privacy-enhanced mode (youtube-nocookie.com) only when you press play; until then, only its preview image is loaded from YouTube's servers. Booking a demo takes you to Microsoft Bookings, where Microsoft's privacy statement applies.

Advertising measurement when you sign up

When you start a trial, we record which ad or campaign brought you to us (for example the campaign name in the link you followed) and store it with your new account. We also tell Meta that a sign-up happened, so we can measure which of our Facebook and Instagram ads lead to sign-ups. This includes your email address, first and last name and country (each converted to a one-way hash before it is sent), a random identifier for your account, your IP address and browser details, and any Meta cookie or ad click identifier. Meta uses this to match the sign-up to a Meta account and report the result to us; it does not receive your password or any information about your business or clients. On our United Kingdom deployment, we only tell Meta about a sign-up if you accepted analytics and advertising cookies on our website. Elsewhere we rely on our legitimate interests; to object, email [email protected].

Why we use this information

We use website information to answer enquiries, send updates you have asked for, protect our forms from spam, understand how people use the website so we can improve it, and measure our advertising. Where UK GDPR or similar laws apply, we rely on your consent for analytics and advertising cookies, session recordings and marketing emails, and for telling Meta about sign-ups on our United Kingdom deployment, and on our legitimate interests for anonymous visit counting, security, spam protection, and replying to your enquiries.

Providers we use for the website

ProviderPurposeLocation
PostHogWebsite analytics, heatmaps and session recordings (a separate project from the app)European Economic Area (PostHog EU Cloud)
MetaMeasuring our Facebook and Instagram ads (Meta Pixel, and sign-up events sent from our servers)United States and other locations as operated by Meta
ResendDelivering contact form messages to our teamUnited States (and other locations as operated by Resend)
MailerLiteMailing list sign-ups and product update emailsEuropean Union
Cloudflare (Turnstile)Spam and bot protection on website formsGlobal network operated by Cloudflare
YouTube (Google)Playing our intro video, only after you press play (privacy-enhanced mode)As operated by Google
Microsoft BookingsBooking a demo with our teamAs operated by Microsoft

Monitoring and logging

We use monitoring and logging for security, compliance, reliability, and product improvement.

  • User activity: pages visited, time spent, and feature usage, to improve user experience and product design.
  • System logs: session metadata, IP addresses, authentication events, and error logs, to maintain stability and detect threats.
  • Performance metrics: API response times, latency, and availability statistics.
  • Diagnostic data: collected when errors occur to improve stability. Error reports can include the signed-in user's identifiers, IP address, and request details.
  • Session replay: for a small sample of practice-user sessions, Sentry records a replay of the screen to help us diagnose errors, with all text and inputs masked and media blocked by default. Replays are never recorded on client-facing pages (such as onboarding, proposal, payment, or signing pages). Where we switch on PostHog session recording for performance analysis, form inputs are masked.

Infrastructure logs for this deployment are stored in the United Kingdom (London region), subject to the same security standards as other service data. Diagnostic and analytics data sent to Sentry, PostHog, or UptimeRobot is processed in those providers’ locations listed in the subprocessors table. Where practicable, we aggregate or pseudonymise analytics.

Automated decision-making

We do not carry out solely automated decision-making, including profiling, that produces legal or similarly significant effects concerning you as a decision of OnboardMe. Identity verification and AML screening features may return automated results from our verification provider (ComplyCube); your organisation remains responsible for how those results are used in its compliance decisions.

Data breach response

We follow incident response procedures aligned with UK GDPR personal data breach notification duties, including notifying the Information Commissioner’s Office (ICO) where required and notifying affected individuals when there is a high risk to rights and freedoms.

  • Breaches are detected through monitoring and alerting, investigated, and contained.
  • Where notification to the ICO or to individuals is required under UK GDPR, we act without undue delay and, where feasible, within 72 hours of becoming aware for the ICO where applicable.
  • Notifications describe the nature of the breach, likely consequences, and measures taken or proposed.
  • We review and test our incident response processes on an ongoing basis.

Compliance with UK law

We are committed to handling personal data in accordance with the UK GDPR and the Data Protection Act 2018, together with applicable sector rules (for example, financial record-keeping) where they apply.

We review our data handling practices regularly to reflect changes in law, technology, and industry practice.

How you can access or correct personal information

Where UK GDPR applies, you may have rights of access, rectification, erasure, restriction of processing, objection to processing (including in relation to direct marketing), data portability, and to withdraw consent where processing is based on consent. These rights are not absolute and may be limited by law or legitimate grounds. If your request is about Client Data we process as processor for a Customer, contact that Customer first. We may need the Customer’s instruction before we can act, unless the law requires us to deal with you directly.

To exercise your rights, email [email protected] with the subject line "Privacy request" and enough detail for us to verify your identity and locate the relevant information. If your organisation subscribes to OnboardMe, we may need to coordinate with your organisation's administrator where data is held on their behalf, as described in our Data Processing Agreement.

We will only release personal information to you where we are satisfied that it relates to you. We may ask you to verify your identity before we do so.

If we refuse a request for access or correction, we will give our reasons in writing where the law requires it (and otherwise where reasonable) and tell you how to complain.

We aim to respond within one month of receiving a valid request, or sooner if required. We may extend by up to two further months for complex or numerous requests, in which case we will tell you. There is no fee for a legitimate request unless the law allows a reasonable charge for manifestly unfounded or excessive requests.

Making a complaint

Complaints about this Privacy Policy or our collection, use or disclosure of personal information should first be directed to us at [email protected]. We will investigate and attempt to resolve your complaint.

You have the right to lodge a complaint with the Information Commissioner’s Office (ICO). We welcome the chance to address your concerns first. Please contact us using the details below.

ICO: make a complaint (opens in new tab)

Overseas disclosure

Primary infrastructure and stored customer data for this deployment are located in the United Kingdom (AWS London). OnboardMe Pty Ltd is based in Australia. Our authorised personnel access this deployment remotely from Australia for support, security, and operations, on a least-privilege basis; the data stays stored in the primary hosting location. When your organisation enables identity verification or AML screening features, relevant personal information (such as identity documents, live facial or biometric capture used for verification, and screening data) is shared with ComplyCube, a United Kingdom-based identity and AML verification provider, and is processed and stored in the United Kingdom. Payment processing is handled by Stripe. Transfers to PostHog and Sentry in the EEA may rely on UK adequacy regulations where they apply. Transactional email and SMS (Resend and Mailgun, which may process in the United States, and TallBob in Australia), AI-assisted features (OpenAI in the United States), product analytics (PostHog EU Cloud), and error monitoring (Sentry in the EU) necessarily involve processing outside the primary hosting region. Optional integrations you connect, including AI assistants your organisation connects through our MCP server, may involve further disclosure at your or your organisation’s direction. Where UK GDPR requires a transfer tool for a restricted transfer (including to OnboardMe in Australia, to TallBob in Australia, and to providers in the United States), we use one (for example the UK International Data Transfer Agreement, the UK Addendum to the EU SCCs, or the UK Extension to the EU-US Data Privacy Framework where the recipient is certified), unless a permitted exception applies.

Where a restricted transfer of personal data outside the UK is required to provide the Services, including remote access by our personnel in Australia, we use a valid UK transfer mechanism where the law requires one (for example adequacy regulations, the UK International Data Transfer Agreement, or the UK Addendum to the EU SCCs, which are incorporated into our Data Processing Agreement for Customer data), unless a permitted exception applies.

Transfer mechanisms, Customer instructions, and subprocessor locations for processing we do on your organisation's behalf are set out in the Data Processing Agreement.

Children's privacy

The Service is not directed at children, and we do not knowingly collect personal data directly from anyone under 18. Client Data that a Customer enters may include personal data about minors (for example trust beneficiaries or dependants). That data is the Customer’s responsibility as controller and is handled under our Data Processing Agreement; we delete it on the Customer’s instruction.

Changes to this Privacy Policy

We may update this Policy to reflect legal, regulatory, or operational changes. The updated version will be published on this page with a revised effective date. Where changes are material and we have your contact details, we may also notify you by email or through the App.

Further information

For privacy questions or requests, email [email protected] (our privacy contact). We do not currently appoint a statutory data protection officer under UK GDPR. Security reports may be sent to [email protected].

  • Email: [email protected]
  • Security: [email protected]

OnboardMe Pty Ltd (ACN 680 379 640). Postal or registered office details can be provided on request to the same email address.

Further information about privacy rights and how to complain to a regulator is available from:

  • ICO (United Kingdom) — ico.org.uk (opens in new tab)