Privacy Policy
1. About this policy
This policy explains how the AppliFlo companies named in our Terms (“AppliFlo”, “we”) handle personal information. It covers our websites, web app, Chrome extension, API and MCP server, and signing pages (the “Service”). We follow the Australian Privacy Principles in the Privacy Act 1988 (Cth). This policy is also written to meet the EU and UK General Data Protection Regulation (GDPR) and US state privacy laws, such as the California Consumer Privacy Act (CCPA), where they apply to us.
Our two roles
- We decide how to use it (controller): information about our customers’ users, website visitors, and people who contact us or apply for jobs. This policy governs that information.
- We process it for a customer (processor or service provider): documents, form values, client and CRM records, and Recipient details that a customer puts into AppliFlo (“Customer Data”). The customer (for example, your migration agent, accountant or employer) controls that data. Its own privacy policy explains how it uses it. We handle it only on the customer’s instructions and under our Data Processing Addendum. If you are a client or Recipient of one of our customers, please contact that customer first. We will help it respond to you.
2. Information we collect
| Category | Examples | Source |
|---|---|---|
| Account and workspace | Name, email address, workspace name, role, country, organisation details you enter (such as ABN or MARN) | You |
| Customer Data | Uploaded documents and templates, filled field values, clients and contacts, CRM records, Recipient names and emails, signatures, messages you write to Recipients | Our customer and its users; Recipients; integrations the customer connects |
| “Fill as me” details | Personal details you save to fill your own forms, such as your address or passport number | You |
| Signing evidence | Signing events, timestamps, IP address, browser details, email verification and access-code results, document fingerprints | Automatically, when a document is viewed or signed |
| Chrome extension | Form field labels and values on pages where you choose to use the extension (see Extension Privacy) | You, through the extension |
| Billing | Plan, invoices, billing contact and address. Card details are handled by our payment provider, and we do not store full card numbers. | You; our payment provider |
| Support and communications | Emails, chat messages, feedback, survey answers | You |
| Technical and security | IP address, device and browser type, sign-in times, pages requested, error logs, rate-limit and abuse signals | Automatically |
| Cookies | Essential cookies only (see our Cookie Policy) | Automatically |
We do not ask for sensitive information about you, such as health or religious beliefs, for our own purposes. However, our customers’ documents may contain sensitive information and government identifiers, such as passport numbers, visa details, health declarations, Australian tax file numbers (TFNs) or US Social Security numbers. We treat these as Customer Data and protect them as described below.
You can browse our website without telling us who you are. To use the app, you need to give us an email address.
3. How we use information
| Purpose | GDPR legal basis (if it applies) |
|---|---|
| Provide the Service: sign-in, detecting and filling fields, routing and sealing documents, sending emails to Recipients | Contract |
| Keep the Service secure: preventing fraud, phishing and abuse, enforcing limits, investigating incidents | Legitimate interests; legal obligation |
| Keep signing evidence and audit trails so documents can be verified later | Contract; legitimate interests |
| Bill you and keep financial records | Contract; legal obligation |
| Support you and tell you about changes to the Service, your account, or these policies | Contract; legitimate interests |
| Improve the Service using aggregated or de-identified usage information | Legitimate interests |
| Send product news (you can unsubscribe at any time) | Consent or legitimate interests |
| Comply with law and respond to lawful requests | Legal obligation |
We use Customer Data only to provide the Service to the customer that controls it, as set out in our Data Processing Addendum.
4. AI processing
Some features use artificial intelligence: reading a PDF to find its fields, suggesting who should fill each field, filling forms, and drafting text in Docs. To do this, parts of a document (its text, layout and, for scanned pages, images) are sent to the AI providers listed on our Sub-processors page. Workspace owners can turn AI features off. When they are off, documents are not sent to AI providers.
- No training. We do not use Customer Data to train AI models. Our agreements with our AI providers prohibit them from training their models on the data we send.
- Workspace memory. AppliFlo remembers how your workspace mapped fields, such as “this box is the client’s family name”. It uses that memory only within your workspace. We exclude field values marked as government identifiers, such as TFNs, from this memory.
- No solely automated decisions. AppliFlo does not make decisions about individuals that have legal or similarly significant effects. AI suggestions are always reviewed and confirmed by a person before a document is sent or signed.
5. Who we share information with
- Sub-processors that host and operate the Service for us, such as cloud hosting, AI, email delivery and payments. They are bound by contracts to protect the information and use it only for us. See the current list.
- The customer that controls the data, and the people it chooses to share documents with, such as Recipients.
- Integrations you connect, such as your CRM, when you instruct us to exchange data with them.
- Related companies in the Globaly group that help us provide the Service, under the same protections.
- Professional advisers, such as lawyers, accountants and auditors, under duties of confidentiality.
- Authorities, when the law requires it or to protect people from harm. We push back on requests that are not legally valid. Where the law allows, we tell the affected customer.
- A buyer or successor, if our business is sold or restructured. This policy will continue to protect the information.
We do not sell personal information and do not “share” it for cross-context behavioural advertising, as the CCPA defines those terms. We have not done so in the past 12 months.
6. Security
We protect information with technical and organisational measures appropriate to the risk. These include encryption in transit (TLS) and at rest, workspace isolation, signing keys held in a hardware security module, one-time sign-in codes, least-privilege access for our staff and systems, and audit logging. Saved “Fill as me” details have an extra layer of application-level encryption. No system is perfectly secure. The security annex in our DPA describes our measures. Report security issues through our Responsible Disclosure page.
Data breaches. If a data breach is likely to cause serious harm, we will notify the Office of the Australian Information Commissioner (OAIC) and affected individuals under the Notifiable Data Breaches scheme. We will also notify affected customers without undue delay, and meet other breach-notification laws that apply. Where we act for a customer, we notify the customer within 72 hours of confirming the breach.
7. Tax file numbers and government identifiers
Some official forms ask for a tax file number. When a customer’s form collects a TFN, we handle it as a TFN recipient under the Privacy (Tax File Number) Rule 2015. We store and transmit it only to complete and keep that form for the customer. We do not use it to identify people, match records or for any other purpose. We restrict access to it and exclude it from workspace memory. It is deleted when the customer deletes the document, or under our retention rules. We apply the same care to passport numbers, visa grant numbers and US Social Security numbers.
8. Where information is stored and sent
Your data is stored in Australia (Google Cloud, Sydney region). Reading scanned pages (Microsoft Azure Document Intelligence) also happens in Australia. To provide the Service, some information is also processed outside Australia:
| Country | What and why |
|---|---|
| United States | AI processing of document text (Anthropic; Google Vertex AI); email delivery (Resend); billing (Globalymint, by our related company Globaly Inc.) and payments (Stripe); edge network and security (Cloudflare) |
| Japan | Email sending infrastructure (Resend) |
| Other countries | Cloudflare may route traffic through its nearest data centre to protect the Service |
Before sending information overseas, we take reasonable steps to make sure the recipient protects it consistently with the Australian Privacy Principles. We do this through contracts, security reviews and providers’ certifications. For information from the EU, UK or Switzerland, we use the European Commission’s Standard Contractual Clauses and the UK Addendum (see our DPA).
9. How long we keep information
We keep information only as long as we need it for the purposes above, or as the law requires. Customers control how long their documents are kept, and deleted documents stay in Trash for 30 days before permanent deletion. Our Data Retention & Deletion page has the details.
10. Your choices and rights
Depending on where you live, you may have the right to:
- access the personal information we hold about you;
- correct it if it is inaccurate;
- delete it;
- export it;
- object to or restrict some uses of it;
- withdraw consent where we rely on consent; and
- opt out of marketing.
Australian law gives you the right to access and correct your information. Residents of California and other US states with privacy laws have the rights to know, delete and correct, and the right not to be discriminated against for using them. EU and UK residents have the GDPR rights listed above.
To make a request, email privacy@appliflo.com. We will verify your identity, usually by email, and respond within 30 days. An authorised agent may make a request for you with written permission. We do not charge for requests unless they are clearly excessive. If we refuse a request, we will explain why.
If your information is Customer Data (for example, a form your agent asked you to fill), we will pass your request to the customer that controls it and help it respond.
11. Complaints
If you have a privacy concern, contact us first at privacy@appliflo.com. We will acknowledge it within 7 days and aim to resolve it within 30 days. If you are not satisfied, you can complain to:
- the Office of the Australian Information Commissioner (oaic.gov.au, 1300 363 992);
- if you are in the EU or UK, your local data protection authority; or
- if you are in the US, your state Attorney General.
12. Children
The Service is for business use by adults. It is not directed to children under 18, and we do not knowingly collect children’s information for our own purposes. A customer’s documents may include information about children, such as dependants on a visa application. We handle that as Customer Data on the customer’s instructions. If you believe a child has given us information directly, contact us and we will delete it.
13. Marketing
We send service emails you cannot opt out of while you have an account, such as sign-in codes, security notices and policy changes. We send product news only to account holders and people who ask for it. Every marketing email has an unsubscribe link. We do not use advertising trackers or sell lists.
14. Changes to this policy
We will post any changes here with a new version number and date. If a change is material, we will tell account holders by email or in the app at least 30 days before it takes effect, unless the change is needed sooner by law.
15. Contact us
Privacy questions and requests: privacy@appliflo.com
Post: Privacy Officer, Globaly Pty Ltd (ABN 66 637 148 951), Sydney NSW, Australia
US customers: Globaly Inc., 251 Little Falls Drive, Wilmington, New Castle County, Delaware 19808, US
If you are in the EU or UK and we are required to appoint a representative, we will list its details here.
