Admin Tea Privacy Policy

Admin Tea Pty Ltd (ACN 701 160 456, ABN 93 701 160 456) · South Australia · Version 12, 2 November 2026

The short version

Admin Tea is a workplace tool. We hold staff, payroll, rostering and NDIS participant information for the businesses that use Admin Tea. Those businesses decide what goes in, who in their organisation can see it, and are responsible for telling you about it and getting any consent the law requires.
Our core database and file storage are in Australia. Sign-in, maps, notifications, security checks, external content and connected services can involve overseas processing. Australian storage does not mean every data flow stays in Australia. Section 11 explains the differences.
Rosters, timesheets, clock-in locations and messages in Admin Tea are workplace records. People your organisation authorises can read them. Section 17 explains what is and is not private.
We do not sell or trade personal information, show advertising, build profiles, or use personal information to train artificial intelligence.
Closing a login does not erase employment or care records. Payroll, NDIS, client care, invoice and expense records are kept for 7 years after the account closes. A child's care records are kept until they turn 25 if that is later. Different rules apply to raw tax file numbers (section 14).
You can ask to see or correct your information, or complain, at any time: yasir@admintea.com. We respond within 30 days, or tell you within that time if we need longer and why.

This summary is a guide only. If it differs from the full policy below, the full policy applies.

1. About this policy

This policy explains how Admin Tea Pty Ltd ("Admin Tea", "we", "us") handles personal information. It applies to our website at admintea.com and to the Admin Tea platform, which includes rostering, time and attendance, onboarding, training, payroll, Single Touch Payroll, messaging, NDIS invoicing and claiming, referrals and case management tools.

It applies to you if you are:

a person who visits our website or contacts us, including about working with us or partnering with us;
an owner, manager or contact person of a business that holds an Admin Tea account;
a staff member, contractor or other person a business invites to use Admin Tea;
an NDIS participant, client, nominee, emergency contact, referee or other person whose information a business records in Admin Tea.

We handle personal information in line with the Privacy Act 1988 (Cth), the Australian Privacy Principles (APPs), the Privacy (Tax File Number) Rule 2015 and the Notifiable Data Breaches scheme. We apply the Privacy Act and the APPs to all personal information we hold, whether or not an exemption in that Act could apply to us or to the information. Where we act for a Customer, we also follow the Customer's instructions, as section 3 explains.

What this policy is. This policy explains our personal information practices. Our Terms of Service and Data Processing Agreement separately govern the service supplied to Customers. This policy is not a separate service contract or a guarantee of uninterrupted or risk-free security. Neither those contracts nor this policy exclude our privacy obligations, authorise unlawful handling, or limit rights or remedies that cannot lawfully be excluded. A Customer's contract does not bind its staff, participants or other individuals to a waiver of their privacy rights.

Notice and consent. Reading this policy, acknowledging it at registration, or using Admin Tea does not by itself give consent to every handling activity described here. Where consent is required, it must be informed, voluntary, current and specific, and given by someone with capacity or lawful authority. You can contact us or the Customer to withdraw consent for future handling that depends on it. We will explain any effect on the service and any lawful reason information must still be retained. This policy supplements collection notices relevant to individual forms and features.

What this policy does not cover. It does not cover:

how a Customer handles information, including how it decides who in its organisation can see what, and what it does with information it downloads, prints, screenshots, exports or sends from Admin Tea. That is governed by the Customer's own privacy policy and obligations;
other organisations' independent handling, including linked websites, embedded content and Customer-selected integrations. Their own policies also apply. Our obligations still apply to information we collect or disclose through those services;
information solely about a company that does not identify a person. Business contact details, sole trader information and ABNs can be personal information where an individual is reasonably identifiable.

Australian service. Admin Tea is offered to organisations in Australia. Australian privacy law is the basis of this policy. Other laws may also apply depending on the circumstances; this policy does not displace them or restrict where you may exercise statutory rights. Information about our own applicants, employees and contractors is also handled under applicable law and relevant personnel notices; we do not assume the employee records exemption covers applicants or contractors.

Information from our providers. Where this policy describes what a provider we use does with information, or where it holds it, we rely on that provider's published documentation and our contract with it at the date of this policy. We check these descriptions when we review this policy and when a provider tells us of a change. If a provider changes its practices without telling us, we will update this policy as soon as we become aware.

Reading this policy. Examples help explain our practices. Where we say we "may" handle information, the activity depends on the feature or circumstances and must have a lawful basis; its inclusion here is not itself permission.

2. Words we use

Personal information is information or an opinion about an identified person, or a person who is reasonably identifiable, whether or not it is true and whether or not it is recorded in writing.
Sensitive information is a type of personal information the Privacy Act gives extra protection, such as health information, disability information, criminal record information and biometric information.
Customer is a business that holds an Admin Tea account, such as a care provider, NDIS provider, support coordination practice or other employer.
Authorised User is a person a Customer invites or allows to use its account, such as its managers, payroll officers, staff and contractors.
Customer Data is information a Customer or its Authorised Users put into, or collect through, Admin Tea. Most personal information in Admin Tea is Customer Data.
Hold means to have possession or control of a record. We hold Customer Data on a Customer's behalf.
Workplace record is a record a Customer keeps to run its business, such as a roster, timesheet, clock-in record, pay record, training record or work message.
Provider is a company whose service we use to run Admin Tea, such as our hosting or email provider.
You means the person reading this policy, whichever of the groups in section 1 you belong to.

3. Our role and the Customer's role

Admin Tea is used by Customers to run their workforce, payroll and client services. Most personal information in Admin Tea is Customer Data, entered by or collected for a Customer about its staff, contractors, clients and NDIS participants.

For Customer Data, we provide hosting and processing on the Customer's lawful instructions. The Customer chooses the records, purposes, features and authorised users, subject to our retention schedule and legal duties. It must have authority to provide the information and give required notices and obtain required consents, including for sensitive information and workplace location checks. Describing us as a service provider or processor does not remove obligations that apply directly to us under Australian law.
For our own purposes, such as running Customer accounts, securing the platform, billing, improving the service and responding to enquiries, we decide how information is handled and we are responsible for it.

Our responsibility. We do not routinely verify every uploaded record or consent. We rely on Customers' instructions and contractual commitments, but remain responsible for our own handling. If we become aware of potentially unlawful collection, access or instructions, we assess the concern and take appropriate steps, which may include restricting access, seeking clarification, preserving evidence or arranging lawful correction or deletion. Support, security and legal access is limited as described in sections 8 and 13.

Misuse by an Authorised User. Customers and users must comply with the law and our Acceptable Use Policy. We may restrict or suspend access to address misuse and notify the Customer where appropriate. Responsibility depends on the circumstances, including our own actions and safeguards. Tell us if you believe misuse has happened (section 18).

If you are a staff member, participant or client of a Customer, please also read that organisation's privacy policy. Requests about Customer Data are usually best made to the Customer first, because it controls the record and can act on your request directly. You can always contact us instead, and we will help or pass your request on (section 16).

Employee records exemption. A private sector employer may have a limited exemption for handling employee records directly related to a current or former employment relationship. It does not generally extend to an external service provider handling those records for the employer. We apply the APPs to the personal information we hold, including Customer employee records.

Health records laws. State and territory laws, including health records laws in Victoria, NSW and the ACT, may apply to Customers and to our own activities depending on the information and circumstances. We comply with obligations that apply to us and assist Customers with theirs. A Customer's responsibility does not exclude ours.

4. Information we collect

What we collect depends on who you are and which features a Customer uses. We limit collection to what is reasonably necessary for our functions and activities. Sources include you, Customers, connected services and relevant public registers as described in section 7. We do not buy personal profiles from data brokers.

If you are	We may collect
A Customer's owner, manager or contact person	Name, role, email address, phone number, business name, ABN, business address, account settings, billing contact details and payment references, records of your agreement to our terms and policies, and records of the notices we send you. We check ABNs against the public Australian Business Register. We do not collect or store card numbers. Invoices are paid by bank transfer, and we see the payer name and reference on our bank statement.
A staff member, contractor or other Authorised User	Identity and contact: name, email address, phone number, postal address, date of birth, emergency contacts. Account and sign-in: email address, the mobile number you use for two-step sign-in (section 4.6), hashed password, multi-factor authentication settings, passkey public keys, records of your agreement to our policies, and records of sign-ins and security changes, including resets of two-step sign-in. Employment: job title, employment type, start and end dates, qualifications, certificates and their expiry dates, training records and progress, availability, work preferences, and documents uploaded during onboarding. Depending on what the Customer requires, uploaded documents can include identity and right-to-work documents, first aid and other certificates, and police check or NDIS worker screening results (section 5). Rostering and attendance: shifts, timesheets, clock-in and clock-out times, travel kilometres, receipt photos, leave, shift swaps and shift offers. Location: with device permission, a reading when the shift clock page loads or reloads, and an available reading saved with clock-in, whether or not the Customer makes the check mandatory (section 4.1). Payroll, tax and super: pay rates, award classifications, pay history, payslips, bank account details, tax file number and declaration answers, and superannuation fund and member details. Messages: the content, sender and time of messages sent through Admin Tea's messenger (section 4.2).
An NDIS participant, client or their nominee	Name, contact details, date of birth, NDIS number, plan and budget information, plan manager or support coordinator details, service agreements, quotes, invoices, claims, case notes, goals, referrals, risk and support needs, and consent records. Some of this is sensitive information (section 5).
A website visitor or someone who contacts us	What you tell us when you contact us, your contact details, and technical information about your visit (below). Our website has no analytics or advertising trackers.
Everyone who uses the platform	Technical information: IP address, browser and device type, and the date and time of actions, recorded for security and audit purposes.

4.1 Location

The shift clock page requests a single device location reading when it loads or reloads. Your browser asks permission unless you have already granted or refused it. This request can occur before you clock in and even where your employer has not made location checks mandatory. If a reading is available, the page sends coordinates to Google Maps to display the map and look up an address. When you clock in, the available coordinates, accuracy and address are saved with your timesheet and can be seen by authorised Customer users. Repeated clock-ins therefore create dated location records. The feature does not continuously track movement or request background location while the page is closed.

You can refuse or withdraw location access in your browser or device settings at any time. If your employer requires location checks, you may then be unable to clock in through the app and will need to ask your employer to record your time. Your employer is responsible for telling you before it turns location checks on, as workplace surveillance laws may require.

4.2 Messages

Admin Tea's messenger is for work communication between staff and the Customer. Messages are workplace records with the following visibility; privacy obligations still apply:

messages about a shift can be read by the staff assigned to it and by people the Customer permits to manage rosters;
direct messages between a staff member and the Customer can be read by that staff member and by people the Customer permits to manage messaging;
users cannot edit or delete a message once sent. Messages are kept while the Customer's account is open (section 14).

Please do not use the messenger for personal matters, or to send tax file numbers, bank details or health information that has a proper place elsewhere in Admin Tea. If you do, that information becomes part of the message record and is visible to the people above.

4.3 Information about other people

Before providing information about someone else, such as an emergency contact, referee, participant or nominee, make sure you have lawful authority and provide the notices and obtain the consent required in the circumstances. Someone not objecting is not necessarily consent. Customers must make relevant collection information and this policy available to affected people, including those without a login. We also take reasonable steps required of us to notify people or ensure they are aware of our collection, including through Customers.

4.4 Photos, documents and free-text fields

Some features let you upload files or type free text, such as onboarding documents, certificates, receipt photos, case notes and message content. We store what you upload or type as you provide it. We do not check its contents, and it may contain more personal or sensitive information than the feature needs. Upload only what the Customer has asked for, and crop or redact photos and documents so they show only what is needed. A photo is taken or uploaded only when you choose to; Admin Tea does not access your camera, photo library, contacts or files without your action.

4.5 What we do not collect

We do not collect, and the platform is not designed to collect:

biometric information such as fingerprints, face scans or voice prints (section 5 explains passkeys);
continuous background location or tracking of your route; the shift clock page readings and saved records are explained in section 4.1;
audio or video recordings, screenshots, keystrokes, or what you do on your device outside Admin Tea;
your browsing on other websites, or information from social media, data brokers or advertising networks;
your device's contacts, calendar, photo library or files, other than a file you choose to upload;
card numbers or online payment credentials;
advertising profiles about your habits or interests. The service does generate operational results such as pay calculations, eligibility flags and security risk signals, which can be personal information; see section 9.

These are limits on what our features request. If a user includes additional information in an upload, message or free-text field, we still hold and process it as Customer Data. Unrequested information is assessed under section 7; uploading it does not remove its privacy protection.

Two-step sign-in is mandatory for every account and cannot be switched off. After you register and verify your email address, you must add a mobile number and confirm it by entering a 6-digit code we send to it by text message. Sign-in codes can then be texted to that number. You can also add an authenticator app, which we recommend, or a passkey, but your account must always keep at least one mobile number. To change your number, you add the new one before removing the old one.

Why we collect it. We use this mobile number only to confirm it is yours, send you sign-in codes and protect your account. We do not use it for marketing or for any other purpose. Google, which sends the codes, states that phone numbers used for sign-in are stored by Google to improve spam and abuse prevention across its services. On screen, Admin Tea shows only its last digits.

Who handles it. The number is held by Google Cloud Identity Platform (Firebase Authentication), our authentication provider, as part of your account's sign-in record. Text messages are sent through Google's service and delivered by mobile carriers, which receive the number and the message. An invisible Google reCAPTCHA check runs when a code is texted, to block automated abuse. Section 11 describes where these providers process information.

How long we keep it. The number is kept while it is a sign-in method on your account. It is removed from your sign-in record when you remove it, when two-step sign-in is reset, or when your login is deleted, subject to the authentication provider's deletion cycle (section 14).

If you lose access. If you can no longer use any of your sign-in methods, two-step sign-in can be reset. For a staff account, the Customer's owner can reset it after confirming the request with you directly, but only if the owner's own account has two sign-in methods set up. If you are a Customer's owner, or you are linked to more than one Customer, our support staff reset it after verifying your identity. A reset removes all your two-step methods and passkeys, signs you out on every device, is recorded in the audit log, and we email you. You must add a mobile number again at your next sign-in. We also email you a security alert whenever a sign-in method is added to or removed from your account.

5. Sensitive information

Some Customer Data is sensitive information. It includes health and disability information about NDIS participants in case notes, plans, risk assessments and service records. It may include health information about staff, such as medical certificates or vaccination records, and criminal record information, such as NDIS worker screening or police check results, that a Customer asks staff to upload.

We collect sensitive information only where reasonably necessary and with valid consent, unless an applicable legal exception permits collection. For Customer Data, the Customer arranges required consent and notices, subject to our own obligations. We use it to deliver the relevant service and for other handling permitted by law, including necessary security or legal matters. We do not use it for marketing, product research or AI training. An address, location or invoice can reveal health or disability information in context; maps, exports and connected services must therefore be used carefully (section 11).

We do not collect biometric information. Passkey sign-in uses your device's fingerprint or face unlock, but that check happens on your device. Only a public key reaches us, and it cannot be used to identify your fingerprint or face.

Location information can expose private activities and is handled with appropriate care. Device permission allows the technical reading; it does not replace a Customer's workplace surveillance notice, a lawful collection purpose or any other required consent. Section 4.1 explains when readings occur.

6. Government identifiers

Admin Tea holds some government identifiers: tax file numbers, NDIS participant numbers, ABNs and, where a Customer records them, worker screening numbers and numbers from identity documents a Customer asks staff to upload. We use each of them only for the purpose the law provides, such as reporting to the Australian Taxation Office or preparing the claim file a Customer uploads to the National Disability Insurance Agency. We do not use a government identifier as our own identifier for anyone. Each person and account in Admin Tea has an internal identifier that we generate. Section 12 has more on tax file numbers.

7. How we collect it

We collect personal information:

directly from you, when you register, complete onboarding, use the platform, or contact us;
from a Customer, such as your employer or care provider, which enters or imports information about you;
from another Customer, where you or a Customer has chosen to share information through Admin Tea, for example an NDIS referral from a support coordinator to a provider, or a shift a Customer offers to a connected agency;
from government systems a Customer uses through Admin Tea, such as the Australian Taxation Office and the National Disability Insurance Agency;
from public registers, such as the Australian Business Register, to check business details;
automatically, from your device, when you use the platform (technical information, and location as described in section 4.1).

If you do not give us information. You can choose not to give information. If you do, a Customer may be unable to roster, pay or onboard you, or to provide services to you, and some features will not work. The law requires some records, such as tax and payroll records, to identify people.

Anonymity. You can deal with us anonymously or under a pseudonym for general enquiries. That is not practical for payroll, tax, super or NDIS services, because the law requires those records to identify people, or for support requests about an account, because we must confirm who we are dealing with.

Accuracy. We take reasonable steps to keep the personal information we use accurate, up to date and complete. For Customer Data, those steps are giving you and the Customer the tools to see and update records, and correcting records when you or the Customer ask us to (section 16). We rely on you and the Customer for the accuracy of what is entered, and we do not independently verify it. Pay, tax and super results depend on what is entered. If a record about you is wrong, tell the Customer or us as soon as you notice, so it can be corrected before it is relied on.

Unsolicited information. Where APP 4 applies, we determine within a reasonable period whether we could lawfully have collected unsolicited personal information. If not, and it is not a Commonwealth record, we destroy or de-identify it as soon as practicable where lawful and reasonable. Otherwise, we protect it under the applicable APPs. Information made public by someone else is not automatically exempt from these obligations.

8. Why we use it

We use personal information to:

provide the Admin Tea platform to Customers and their users, including rostering, time records, onboarding, training, messaging, payroll, invoicing, claiming and case management;
calculate pay and send the Single Touch Payroll reports a Customer approves and declares to the Australian Taxation Office;
create and secure accounts, verify sign-ins, prevent fraud and misuse, investigate security incidents and keep audit records;
send service messages, such as invitations, rosters, shift alerts, security alerts (for example when a sign-in method is added, removed or reset), password resets, account notices and legally required notices;
bill Customers and manage our relationship with them;
provide support when a Customer asks for it (section 13);
meet legal obligations, including tax, workplace and record-keeping laws, and respond to lawful requests (section 20);
establish, exercise or defend legal claims, handle complaints and disputes, and deal with regulators and insurers;
improve Admin Tea using de-identified usage information.

Each use or disclosure needs a lawful basis. We use and disclose personal information for its primary purpose, a related secondary purpose you would reasonably expect (directly related for sensitive information), with valid consent, or under another applicable legal permission. The purposes listed here do not create an unrestricted right to use information.

De-identified information. "De-identified" means information from which no one can reasonably be identified. When we improve the service, we use counts and patterns, such as how many Customers use a feature or how long a page takes to load. This never includes tax file numbers, bank or super details, case notes or other sensitive information. We do not attempt to re-identify de-identified information, and we do not disclose it in a form that identifies a Customer or a person.

What we do not do. We do not sell personal information, and we do not trade it, meaning we do not give it to anyone in exchange for money or anything else of value. We do not use personal information to show advertising, and we do not share it with advertisers or data brokers. We do not combine it with information from other sources to build a profile of you. We do not use personal information to train artificial intelligence models, and we do not currently use generative artificial intelligence in the platform. If we add a feature that uses artificial intelligence, we will update this policy first, Customers will be able to choose whether to use it, and Customer Data will not be used to train models.

Marketing. We send only service messages at present. If we ever send marketing messages, we will do so only with consent and with a working unsubscribe option in every message, as the Spam Act 2003 (Cth) requires, and you can opt out at any time by using that option or emailing us. We do not use Customer Data about staff, participants or clients for marketing, and we do not use the mobile number on your sign-in record for marketing. Service messages, such as security alerts and roster changes, are not marketing and continue while you hold an account, because the service cannot work without them.

Feedback and testimonials. If you send us feedback, we may use it to improve the service. We will not publish your name, your organisation's name or your words as a testimonial without asking you first.

9. Automated decisions

Admin Tea uses automated rules for the activities below. Some can affect pay, access to work or access to an account. The table explains the information used and the role of the program. Additional APP privacy policy requirements for significant automated decisions commence on 10 December 2026; we will review these disclosures against the requirements and guidance as they take effect.

Kind of decision	Kinds of personal information used	Role of the program
Pay calculation: pay, penalties, allowances, leave accrual and balances, tax withholding and super	Award classification, pay rate, rostered and worked hours, leave records, tax declaration answers, super details	The program does something substantially and directly related to the decision: it calculates a result. A Customer's payroll officer reviews and approves each pay run before it is paid or reported. The Customer makes the decision.
Clock-in location check (if the Customer turns it on)	Device location at clock-in, work site location	The program decides alone. A clock-in outside the permitted area is not accepted. The Customer can record your time another way.
Expired mandatory documents (if the Customer turns it on)	Document type and expiry date, staff status	The program decides alone. The staff member is made inactive and not offered shifts until the document is renewed. The Customer can override this.
Sign-in protection	IP address, browser and device information, recent sign-in attempts	The program decides alone. Suspected automated abuse is blocked and repeated failed attempts are temporarily limited. Access returns automatically after a short time, or sooner if you contact us.

Customers remain responsible for employment and care decisions and for reviewing calculations and source records. If an automated outcome appears wrong, contact the Customer or us to request human review, explain the problem and seek correction of the underlying information. We investigate platform issues and assist with review; a request does not guarantee reversal of a lawful outcome or a decision controlled by the Customer. We will update these disclosures when relevant features change.

10. Who we share it with

We disclose personal information only as follows:

The Customer you work for or receive services from, and the people that Customer authorises in Admin Tea. What each of those people can see is set by the Customer.
Other Customers, when a Customer or you choose to share information through Admin Tea, such as a referral, an agency shift or a connected provider. The receiving Customer then holds that information under its own privacy policy.
Government agencies, when a Customer uses Admin Tea to lodge, such as the Australian Taxation Office (Single Touch Payroll and tax file number declarations). These lodgements are made in the Customer's name and on its instruction. Admin Tea does not send NDIS claims to the National Disability Insurance Agency. A Customer downloads its claim file from Admin Tea and uploads it to the NDIS portal itself.
Our providers, who host, secure and deliver parts of the service under written terms that limit them to that purpose (section 11).
Professional advisers and insurers, such as lawyers, accountants, auditors and insurers, under a duty of confidentiality, and only what they need.
Where the law requires or authorises it, including a court order, a lawful request from a regulator or law enforcement body, or to lessen a serious threat to someone's life, health or safety (section 20).
To establish, exercise or defend a legal claim, including a complaint, dispute or proceeding involving you, a Customer or us, and only what is reasonably necessary for that.
A buyer or successor in a merger, sale, restructure or insolvency, only where disclosure is lawful, necessary and protected by appropriate confidentiality and privacy safeguards. Due diligence uses de-identified or aggregated information wherever practicable; a confidentiality agreement alone is not authority to disclose identifiable records. We will tell affected Customers before a transfer where lawful and practicable and honour applicable contractual rights. A transfer does not authorise unrelated new uses.

We do not disclose personal information to anyone else, or for any other purpose, except as this policy describes or the law requires.

11. Where it is held and overseas disclosure

Core storage and email. Our core Firestore database, uploaded files and regional application processing are configured for Google Cloud's Sydney region (australia-southeast1). Database backups are held in Australia. This is a statement about core storage and processing, not a guarantee that all service metadata, support access, internet routing or connected services remain in Australia. The services below have separate arrangements.

Automated email. Automated invitations, security alerts and roster updates use SMTP2GO's Australian API endpoint. SMTP2GO receives recipient details and message content. Delivery also involves the recipient's email provider and may involve overseas processing; an Australian sending endpoint does not establish end-to-end Australian residency.

Customer-support email. We use yasir@admintea.com, a Titan Email mailbox purchased through GoDaddy, for correspondence between Admin Tea and its Customers. Titan handles the contact details, support messages and any attachments sent through that mailbox, together with delivery and security metadata. We do not use this mailbox to store the platform's payroll, TFN or participant records. Please include only information needed for your enquiry and avoid sending TFNs, passwords, bank details or detailed health records.

Server logs. Our servers write operational logs to a Google Cloud Logging bucket in the Sydney region, kept for 400 days. These logs can include internal identifiers, email addresses, IP addresses and error details. We design them not to contain tax file numbers, bank or super details, pay amounts, case notes or message content, and we review them for that. Before 15 September 2026 these logs went to Google's default bucket, which is not limited to one region. Those earlier entries expire 30 days after they were written, so none remain after 15 October 2026.

Administrative audit log. Our Google Cloud project also has a locked administrative audit log with 400-day retention, configured globally. It records operator or service identities, resources and administrative actions. Resource names and metadata may contain identifiers; we do not intentionally place business record content in this log. It is separate from the regional application logs.

Services that can handle information outside Australia. The table identifies the main information flows and known locations. Global services may process technical information through changing networks, and their published locations are not necessarily limited to the countries named here. We identify countries where practicable, review provider arrangements and can provide further available information on request. Providers may handle some technical information for their own security and service purposes under their policies. A Customer-selected integration is distinguished from a provider we engage.

Provider and purpose	Information	Countries
Google Cloud Identity Platform: sign-in, including sending SMS codes	Email address, phone number, authentication credentials and settings, IP address, browser information and security metadata	United States, and the mobile carriers that deliver SMS codes
Google reCAPTCHA: blocking automated sign-in abuse, including when a sign-in code is texted, and scoring each page load and server call through Firebase App Check to block automated abuse	IP address, browser and device information	United States
Google Maps: showing addresses and clock-in locations on maps, and working out travel distance between staff and clients for open shifts	Addresses, precise coordinates, IP address and device information, including a location displayed before clock-in. For travel distance, the saved coordinates of a staff member's address, which can be their home, and of a client's address. Addresses can relate to participants or service sites	United States
Firebase Cloud Messaging and your browser's push service (Google, Apple or Mozilla): urgent shift notifications	Device token, notification payload (such as shift role, time, location and address) and delivery metadata. A notification may be visible on a device's lock screen	United States and global delivery infrastructure; see Firebase processing locations
SMTP2GO: sending our automated emails (invitations, security alerts and roster updates)	Recipient email address and the content of each email, which can include a person's name and work details; delivery metadata	Australia for sending and stored data, on the provider's statement for accounts using its Australian endpoint; the provider is a New Zealand company and has not stated whether its staff access the data from New Zealand; the recipient's own email provider may be overseas
Google Cloud administrative audit log: record of changes to our cloud project	Operator or system identity, resource names and action metadata, which may include identifiers	United States and Google's global network
Google Fonts, Google Hosted Libraries, Firebase Hosting, jsDelivr, cdnjs (Cloudflare), unpkg, the jQuery CDN, and the Bootstrap CDN (StackPath): delivering web pages, fonts and page components	IP address and browser information	United States and the providers' global networks
YouTube and Vimeo: playing training videos a Customer adds	IP address, browser information and viewing activity on the video	United States
Have I Been Pwned / Pwned Passwords, delivered through Cloudflare: checking proposed passwords against known breaches	First five characters of a password hash, plus network information such as IP address. This check does not send your password, full hash or account email	Global Cloudflare network, including the United States; the operator is Australian. See its privacy policy
Customer-selected embedded files and training content, including Google Drive and Microsoft OneDrive	IP address, browser information, content requests and any information you provide to that service. Its existing login cookies may identify you to it	Depends on the Customer's provider and account configuration; Google and Microsoft operate internationally, including in the United States
Titan Email, supplied through GoDaddy: our customer-support mailbox	Contact details, support messages, attachments, and delivery and security metadata	United States (Amazon Web Services hosting, Proofpoint screening, GoDaddy mail servers)

Our sign-in, maps, page delivery and password-checking integrations are not designed to receive raw TFNs, bank or super details, case notes or NDIS plans. Nevertheless, exports, email, Customer-selected content and user-entered fields can transmit personal or sensitive information. For example, a mapped service address or an exported invoice may identify a participant and the care they receive. Customers must have lawful authority for these disclosures and minimise what they send. Disabling an integration stops future transfers through it, but does not recall information already received by that service.

Support mailbox locations. The following arrangements concern support correspondence, not the platform records held in our core storage. Titan Solution Ltd SEZC, registered in the Cayman Islands, provides the mailbox. Titan's sub-processor list names Amazon Web Services, Inc. (United States) as the provider that hosts mailbox contents, and Proofpoint, Inc. (United States) for email security screening. GoDaddy (United States) supplies the mailbox and its mail servers receive incoming messages for our domain. Titan's optional spelling check and writing assistant send the text being checked to WebSpellChecker (Estonia) and OpenAI (United States) when used. We therefore treat support correspondence as held in the United States. Titan deletes mailbox data within 60 business days after the service ends. See Titan's privacy policy and GoDaddy's privacy notice.

Our responsibility. Where we disclose personal information to an overseas provider, we take reasonable steps to ensure it handles the information consistently with the Australian Privacy Principles, including by written contract, and we remain accountable under the Privacy Act for its handling. We do not rely on your consent to avoid that accountability. We will update this table, and give Customers the notice the Data Processing Agreement requires, before a new overseas provider starts handling personal information. If we must replace a provider urgently for security or continuity, we will update this table as soon as practicable afterwards.

Overseas law. Overseas processing can expose information to foreign legal access and different privacy protections. Australian storage alone does not eliminate foreign legal obligations affecting an international provider. We assess those arrangements and respond to lawful requests as described in section 20; this does not waive our Australian obligations.

12. Tax file numbers

We collect tax file numbers only through the employee's tax file number declaration. We use and store them as the Privacy (Tax File Number) Rule 2015 requires:

only for tax, payroll and superannuation purposes authorised by law;
with access limited to people the Customer has specifically authorised;
masked on screen unless an authorised person chooses to reveal one, with each read recorded in an audit log;
stored only in Australia and not sent to the providers in section 11;
securely destroyed once tax law no longer requires them. A payer must keep a TFN declaration until the second 1 July after it stops having effect (Income Tax Assessment Act 1936, s202CD), usually when the person stops working for the Customer or the Customer's account closes. We destroy the raw TFN automatically from that date, unless a legal hold applies. We keep whether a TFN was provided, which holds no TFN.

Providing a TFN is voluntary. If you do not provide one, higher withholding may apply, subject to lawful exemptions and any applicable period for supplying a TFN. We do not use a TFN to verify your identity for a privacy request. Do not put it in messages or general uploads. A payroll record's retention period does not automatically justify keeping its raw TFN for the same period: the specific TFN Rule and authorised purpose govern. If you suspect misuse, contact us promptly (section 18).

13. Security

We take reasonable steps, through technical and organisational measures, to protect personal information from misuse, interference, loss, and unauthorised access, modification or disclosure. What is reasonable depends on the sensitivity of the information, the risks, and the technology and threats at the time, and we review our measures as those change. At the date of this policy, our measures include:

encryption in storage and in transit;
mandatory two-step sign-in that cannot be switched off, with a confirmed mobile number on every account for text-message codes and an optional authenticator app or passkey, and a minimum 12-character password policy. Proposed passwords are checked against known breaches when that checking service is available; its information flow is in section 11;
two-step sign-in can be reset only by a Customer's owner for its own staff, after confirming with the person directly, or by our support staff after verifying identity (section 4.6). Each reset removes all sign-in methods and passkeys, ends every session, is recorded in the audit log and is emailed to the person. Security alert emails are also sent when a sign-in method is added or removed;
screens lock after 15 minutes without activity, and sessions end within 24 hours;
access controls enforced on our servers, so each Customer's information is separated and staff see only what their Customer permits;
audit logs of sign-ins, security changes (including resets of two-step sign-in), payroll actions and reads of tax, bank and super details;
credentials and keys held in a managed secret store, not in source code;
backups held in Australia, and a documented procedure for detecting, containing, assessing and notifying data breaches;
our personnel are bound by confidentiality and trained in handling personal information;
Admin Tea support staff can view a Customer's information only after that Customer grants time-limited access (at most four hours per grant), and each grant is recorded. Without a grant, we access it only where needed to keep the platform running securely, to respond to a security incident, or to comply with the law, and we record that access.

We may change specific measures as technology and threats change, without reducing the overall level of protection. This list describes our practices; it is not a promise that any particular measure will always be in place in the same form. Customers can ask us for a summary of our security controls under the Data Processing Agreement.

Security is shared. The Customer is responsible for deciding who in its organisation can access information, and for removing access promptly when someone leaves. You help protect your account by keeping your password, devices and sign-in codes to yourself, keeping your device and browser up to date, signing out on shared devices, and telling us straight away if you suspect misuse. We will never ask you for your password or a verification code, by email, phone or message. Treat any such request as a scam. Information you or a Customer take out of Admin Tea, for example by exporting, printing or taking a screenshot, is outside our security measures once it leaves the platform.

No system connected to the internet is completely secure. Security also depends on devices, networks and connected systems. These limitations do not exclude our duty to take reasonable protective steps or respond to incidents. Please report suspected weaknesses to yasir@admintea.com and avoid accessing other people's information or disrupting the service. This request does not prevent lawful reporting to a regulator or other protected disclosure.

14. How long we keep it

Information	How long	Why
Pay runs, payslips, Single Touch Payroll records, tax file number declarations, payment records, leave records and employee payroll records	7 years after the Customer's account closes, or after the record was last changed if that is later. Raw TFNs are destroyed sooner, from the second 1 July after the person stops working for the Customer (section 12)	Supporting Customer record-keeping, including the Fair Work 7-year requirement. Tax, super and particular records can have different legal periods and starting points; 7 years is not a universal statutory rule
Timesheets (hours worked)	7 years after the Customer's account closes, or after the record was last changed if that is later	Fair Work record-keeping for hours worked
Invoices, receipts, and income and expense records	7 years after the Customer's account closes, or after the record was last changed if that is later	Tax and GST record-keeping law (5 years), and the 7 years a company must keep its financial records
NDIS claims and payments, cancellations, incident and risk records, and worker screening and qualification records	7 years after the Customer's account closes, or after the record was last changed if that is later	NDIS Practice Standards and NDIS rules on incidents, worker screening and payments
Client and participant records, including care and progress notes, shift documents, service agreements, quotes, case notes, referrals and consent records	7 years after the Customer's account closes, or after the record was last changed if that is later. If the information was collected while the client was under 18, until they turn 25 if that is later. We ask whether the client was under 18 when support started, and their date of birth if so, to apply this rule	State health records laws (NSW, Victoria and the ACT) and the NDIS Practice Standards. We apply the longest period that fits the record
Other Customer Data, including rosters without worked hours, availability, onboarding, training, messages and notifications	While needed for the service or another lawful purpose. After account closure, the Customer has 60 days to request a copy, followed by deletion or de-identification within a further 90 days, subject to lawful retention and backup expiry	Providing the service; giving the Customer a fair chance to take its records
Security and sign-in audit records	13 months	Investigating misuse and security incidents
Server logs	400 days	Diagnosing faults and security incidents; evidence for Australian Taxation Office security requirements
Administrative audit log of our cloud project	400 days, set by Google and cannot be shortened	Showing who changed our systems and when
Backups	Point-in-time recovery for 7 days; daily backups for 30 days	Recovering from data loss. Deleted records can remain in restricted backups until expiry; any recovery must re-apply relevant deletions
Customer account, billing and contact records, and records of agreement to our terms and policies	7 years after the account closes	Tax and corporate record-keeping law; resolving disputes
Enquiries, support requests, access requests and complaints	For as long as reasonably necessary to resolve the matter and meet a documented legal or evidentiary need; generally no more than 7 years after closure unless a legal hold or longer requirement applies	Handling the matter and documenting its resolution; unnecessary sensitive attachments should be removed earlier
Authentication provider records, including the mobile number used for sign-in	Until account deletion is requested (a mobile number is removed sooner if you remove it or two-step sign-in is reset), followed by the provider's deletion cycle; Firebase documents up to 180 days for associated authentication data to leave live and backup systems	Account operation and provider recovery cycles, separate from our database backups. See Firebase retention information

A retention period is not permission to keep unnecessary information. We take reasonable steps to destroy or de-identify information no longer needed for a permitted purpose, unless a legal retention exception applies. Relevant records may be preserved for an actual or reasonably anticipated dispute, investigation or legal requirement; a legal hold must be limited to what is necessary and reviewed when its basis changes. Records the law requires are kept locked after a Customer's account closes. The Customer's users lose access the day it closes. Its staff can still read their own payslips, read-only, until 31 October after the end of the financial year of closure, so they can lodge their tax return. Otherwise the records are accessed only to answer the Customer, the person concerned or a lawful request, and are destroyed when their own period ends. Customers remain responsible for any longer requirement that applies to them, such as aged care rules, and should tell us before closing an account. Client records are deactivated, not deleted, while their period runs. Restricted backups expire on their normal cycle, and deletions must be re-applied following recovery.

Deleting your login. You can delete your Admin Tea login at any time from Settings. Deleting your login removes your ability to sign in straight away, so if you want a copy of your records, download it first from Settings > Export Data. It does not delete records the law requires your employer or us to keep, or records the Customer holds about you as its staff member or client, because those records belong to the Customer's business. When a Customer closes its account, we tell it which records are kept and until when, and it can ask us for a copy.

Deletion requests. The APPs do not provide an unconditional right to erase every record on request. You can nevertheless ask us or the Customer to delete information. We assess necessity, applicable retention duties and any other rights that apply, explain the outcome and take the steps required by law. Keeping an account open or describing information as a business record does not justify indefinite retention.

When you leave a Customer. If you stop working for or receiving services from a Customer, your records stay in that Customer's account under this table. If you work for more than one Customer through Admin Tea, each Customer sees only its own records about you.

15. Browser storage and cookies

Admin Tea stores information in your browser to keep you signed in, remember settings, deliver permitted push notifications and lock idle screens. Admin Tea does not use advertising or cross-site tracking cookies or third-party analytics on the platform or website. Browser privacy signals do not necessarily control third-party content; use browser and provider controls as well. Blocking necessary storage may prevent sign-in or other features.

Some features load content from the providers in section 11. When they load, those providers receive your IP address and browser information and may set or read their own cookies or browser storage under their own privacy policies. This includes Google reCAPTCHA, Google Maps and Google Fonts, and, on our website, the font, icon and script libraries it loads. Training videos play in YouTube's privacy-enhanced mode and Vimeo's "do not track" mode, which limit the cookies those services set, although YouTube may still store some information in your browser once you play a video. We do not control those providers' cookies and cannot switch them off for you; your browser settings can.

16. Access, correction and your choices

You can ask for access to the personal information we hold about you, and ask us to correct it if it is inaccurate, out of date, incomplete, irrelevant or misleading. Email yasir@admintea.com or write to the Privacy Officer (section 23). Much of your information is also visible to you in Admin Tea, such as your profile, timesheets, payslips and training records, and you can update some of it yourself.

Identity. We use proportionate checks to verify you or your representative before releasing information. We ask only for what is reasonably necessary and offer an alternative where an ordinary method is inaccessible. Please do not email a TFN or identity document unless we have arranged an appropriate method. We promptly explain any information needed to progress a request; verification does not automatically restart or suspend applicable response obligations.
Someone acting for you. A lawyer, union, family member, guardian, nominee or other representative can make a request for you if they give us your written authority, or evidence of their legal authority to act for you. We will confirm that authority before we respond.
Time. We respond within a reasonable period and aim to complete requests within 30 calendar days of receipt, subject to any shorter legal requirement. If more time is reasonably needed, we explain the reason and expected completion date within that period. An extension is not automatic because a Customer or provider is involved.
Cost. Making a request is free. Correction and associating a statement of disagreement are free. We ordinarily provide access without charge. If a permitted access charge is necessary, it will be reasonable and not excessive, with an estimate explained in advance; it will not be used to discourage a request.
Customer Data. We usually coordinate with the Customer that holds the record and tell you how your request is being handled. We remain responsible for our own response obligations and do not require you to obtain the Customer's permission to exercise rights against us. Tell us if sharing your request with the Customer could expose you to harm, so we can consider a safe and lawful approach.
Format. We will give you access in the way you ask for where reasonable, for example as a copy of a document or an export, or by explaining what a record says. If you are a staff member, you can also download a copy of your own records yourself from Settings > Export Data. A business owner can export their business's data the same way.
Access limits. We refuse access only on an applicable legal ground. Under APP 12 these can include an unreasonable impact on another person's privacy, a genuinely frivolous or vexatious request, or information relating to proceedings between you and us that would not be accessible through discovery. Commercial sensitivity alone is not a general exception: the relevant ground concerns evaluative information generated in connection with a commercially sensitive decision-making process. We consider partial access, redaction or an agreed intermediary where appropriate, and provide written reasons and complaint options where required.
Correction. Access refusal grounds are not blanket grounds to refuse correction. We take reasonable steps to correct information that is inaccurate, out of date, incomplete, irrelevant or misleading for its purpose. Some official or audit records require a linked amendment rather than overwriting the original. If correction is refused, we provide written reasons to the extent required by law and complaint options. On request, we take reasonable steps to associate your statement of disagreement with the information.
Notifying others. On request, we take reasonable steps to notify other APP entities to which we disclosed corrected information, unless impracticable or unlawful, and meet any additional applicable notification duties.
Deceased people. If a person has died, we will deal with their legal personal representative, or with the Customer that holds their record, on proof of authority.

Your other choices. You can withdraw location access (section 4.1), turn off push notifications in your browser, change your sign-in methods in Settings (your account must keep at least one mobile number), and delete your login (section 14). Withdrawing location or notification permissions may stop some features working, and your employer may need to record your time another way.

How to make a request. Email is convenient, but you can also call the number in section 23 or contact us through another available channel. You do not need a special form, legal wording or a reason for seeking access. We direct requests received by our staff to the Privacy Officer. Contact us for help if you need an accessible way to make or receive a request.

17. Privacy at work: what to expect

Because Admin Tea is a workplace tool, some information you enter is, by design, visible to your employer or care provider. Knowing this helps you decide what to put in. In Admin Tea:

Visible to authorised Customer users according to their access: your profile and onboarding details, rosters, timesheets, clock-in times and any saved location, travel and receipt records, training progress, documents and work messages. Pay, tax, bank and super details require the relevant permissions.
Recorded for security: when and from what device and IP address you sign in, security changes you make, and resets of your two-step sign-in, including who made them. These records are available to us and, on request about their own account, to the Customer.
Not visible to the Customer: your password, your multi-factor codes and passkeys, and your activity in other Customers' accounts if you work for more than one Customer.
Not collected at all: the things listed in section 4.5.

Workplace information can remain private and confidential even when authorised colleagues can access it. Using Admin Tea does not waive a reasonable expectation of privacy or permit unrestricted monitoring, disclosure or secondary use. Customers must limit access and use to lawful purposes and meet relevant workplace surveillance requirements. If you suspect misuse, contact the Customer, us or the relevant regulator (section 21).

18. Data breaches

We take prompt steps to contain and investigate suspected breaches. Where there are reasonable grounds to suspect an eligible data breach, we carry out a reasonable and expeditious assessment and take all reasonable steps to complete it within 30 calendar days. That assessment period is not a waiting period for notification. If we have reasonable grounds to believe an eligible data breach has occurred, we notify the OAIC and affected or at-risk individuals as soon as practicable in accordance with the Notifiable Data Breaches scheme, subject to applicable exceptions and effective remedial action.

Our Data Processing Agreement separately requires notice to affected Customers without undue delay and within 72 hours of awareness of unauthorised access to, disclosure of, or loss of their information held by us or our providers. That contractual deadline is not a general 72-hour Australian regulator deadline. We coordinate notifications with Customers where appropriate without abandoning our own duties, and meet any applicable ATO or other reporting obligations. Notices explain the information involved and recommended protective steps.

A notification does not by itself determine fault or liability. An incident involving a Customer, provider or compromised device may also involve information we hold; we assess the facts and our obligations rather than excluding it solely because it originated outside our systems.

If you think your account or information has been misused, or you have received a suspicious message that claims to be from Admin Tea, contact us straight away at yasir@admintea.com.

19. Young people and people who need support

Admin Tea is designed for organisational use, but Customer records may concern children and some workers may be under 18. We do not assume that describing the service as a workplace tool exempts it from protections for children. Relevant requirements, including any applicable children's privacy code, must be assessed as they take effect.

Capacity to consent is assessed in context. Age or disability alone does not establish that a person cannot decide for themselves. Customers must support accessible explanations and obtain consent from the person or a lawfully authorised representative where required. A parent, family member, carer or NDIS nominee does not automatically have authority for every decision or disclosure. We verify the scope of authority and consider the person's wishes, capacity, safety and applicable law before providing access.

20. Government, court and law enforcement requests

If a government agency, court or other third party asks us for personal information, we check that the request is lawful and disclose only what the law requires. Where the information is Customer Data, we refer the request to the Customer where we can, and we tell the Customer before disclosing unless the law prohibits us from doing so. We do not give any government agency direct or standing access to Admin Tea. Lodgements a Customer makes to the Australian Taxation Office through Admin Tea are the Customer's own lodgements, not disclosures we make in response to a request.

A request from a private party, such as a lawyer in a dispute, an insurer or an employer that is not the Customer, is not a lawful requirement unless it comes with a subpoena, court order or other legal compulsion. We do not release personal information to private parties on request alone. If we receive legal process about you, we will tell you where the law allows and we have a way to reach you.

21. Complaints

If you are concerned about how we have handled your personal information, contact our Privacy Officer at yasir@admintea.com with details of your concern and how you would like it resolved. We will:

acknowledge your complaint within 7 days;
investigate it, which may include asking you for more information and speaking with the Customer if it concerns Customer Data;
give you a written response within 30 days, explaining what we found, what we will do, and how to take it further if you are not satisfied. If we need longer, we will tell you why and when to expect our answer.

Complaints are free. You can complain about an APP or applicable registered privacy code, and use a representative or request accessibility assistance. We assess anonymous concerns to the extent the available information allows. For repeated matters with no new information, we may refer to our earlier response. We may set reasonable communication arrangements to protect staff from threats or abuse while still considering the underlying privacy issue. An inconvenient complaint, a request for compensation or an intention to seek legal advice is not by itself improper. Our response does not by itself determine legal liability, and no release or waiver is required to exercise a statutory privacy right.

Where a complaint involves a Customer, we coordinate where appropriate and still investigate our own handling. Please tell us if referral could expose you to harm. Employment, pay or care service issues may also be raised with the Customer, Fair Work Ombudsman or NDIS Quality and Safeguards Commission; overlapping issues do not remove our responsibility for the privacy complaint.

If you are not satisfied with our response, or we have not responded within 30 days, you can complain to the Office of the Australian Information Commissioner at www.oaic.gov.au or on 1300 363 992. The OAIC generally expects you to raise a complaint with us first. Nothing in this policy stops you from contacting a regulator at any time.

22. Changes to this policy and to the law

We review this policy at least annually and when practices change, and publish a new date and version. For material changes to handling, we give Customers and account holders at least 30 days' notice by email or in the app, except where law or urgent security needs require earlier action, when notice follows as soon as practicable. We also take reasonable steps to inform affected people without accounts, including through Customers. Material corrections to an inaccurate disclosure are explained promptly; calling a change a correction does not make it immaterial. Continued use alone is not consent to a new purpose requiring consent. Existing contractual notice and objection rights remain applicable.

Changes to the law. We review applicable legislation and regulatory guidance, including the automated decision transparency requirements commencing on 10 December 2026. Proposals are not treated as enacted law. A revised policy cannot retrospectively authorise unlawful handling, supply missing consent or remove a person's accrued rights.

Earlier versions are available on request.

Version	Date	What changed
12	2 November 2026	Added SMTP2GO, our automated email provider, to the table of services that can handle information outside Australia, with what it receives and where it says it stores it. Removed the Quill content delivery network from the provider table, which is no longer used.
11	1 November 2026	Stated that the saved coordinates of staff and client addresses go to Google Maps to work out travel distance for open shifts, and that reCAPTCHA scoring through Firebase App Check runs on page loads and server calls (section 11).
10	31 October 2026	Corrected the server log retention to 400 days, the locked setting (sections 11 and 14). Named the shift location and address in push notifications (section 11). Stated Google's use of sign-in phone numbers (section 4.6). Aligned the version number at the top of this policy.
9	28 September 2026	Corrected NDIS claiming. Admin Tea does not send claims to the National Disability Insurance Agency: a Customer downloads its claim file and uploads it to the NDIS portal itself (sections 6, 10 and 20).
8	28 September 2026	Removed Xero. Admin Tea no longer connects to accounting software, so no information is sent to or received from it (sections 2, 7, 10 and 11).
7	25 September 2026	Explained the mandatory mobile number for two-step sign-in: why it is collected, who holds and delivers it, that it is not used for marketing, how long it is kept, how resets work, that resets are audited, and security alert emails (section 4.6). Stated where our support mailbox is hosted, and listed it in the provider table (section 11).
6	25 September 2026	Set out retention periods for timesheets, invoices and expense records, NDIS records and client care records, including the age-25 rule for records collected about children; explained that required records stay locked after an account closes, that staff keep read-only payslips until 31 October after the financial year of closure, and that client records are deactivated rather than deleted; set when raw TFNs are destroyed (s202CD).
5	25 September 2026	Clarified consent and our own responsibilities; corrected location timing and workplace privacy wording; added password-checking and embedded-content disclosures; distinguished core Australian storage from other processing; clarified TFN retention, access, correction, complaints, breach response, representative authority and legal reforms. Descriptions below record earlier changes and do not override the current policy.
4	24 September 2026	Added the Bootstrap, Quill and Google Hosted Libraries content delivery networks to the provider table, which were in use but not listed. Added that we do not trade, profile or infer information, that we rely on Customers for notices and consents, that identity and right-to-work documents may be uploaded, that emails are not end-to-end encrypted, how backup restores handle deletions, how prospective buyers see information, how to report a security weakness, and what a breach of Admin Tea is not. Added our position on the proposed Privacy Act reforms, the Children's Online Privacy Code and the proposed treatment of location as sensitive information. Clarified how we rely on provider documentation, what "may" means, that identity checks pause the 30-day clock, and that corrections are not material changes.
3	24 September 2026	Added what we do not collect, uploads and free-text fields, misuse by an Authorised User, accuracy, requests made by representatives, deceased people, private-party requests, a section on privacy at work, and the Privacy Act's automated decision wording. Clarified that the policy is not a contract or warranty, that Australia is the only jurisdiction we design for, that breach notices and complaint responses are not admissions, and that no general right to erasure exists. Added unpkg to the page delivery providers.
2	24 September 2026	Added definitions, government identifiers, information about other people, server logs and their location, backup periods, a fuller retention table, lawful request handling, complaint steps and a version history. Clarified the employee records exemption, state health records laws, marketing, artificial intelligence and access request costs.
1	24 September 2026	First published version.

23. Contact us

Privacy Officer
Admin Tea Pty Ltd
Email: yasir@admintea.com
Phone: 0452 488 675
Post: write to us by email first and we will give you a postal address for documents that must be sent by post.

Service of court documents is governed by applicable law and court rules. Our registered office can be checked on the Australian Securities and Investments Commission register. This policy does not exclude any legally valid method of service.

You can ask for a copy of this policy in another format, such as large print or plain text, at no cost.