Version: 1.3
Effective date: 15 November 2026 (published 15 November 2026).
What changed in version 1.3: a new section 5.6C and new items in sections 6.1, 7, 8.1, 9.1, 9.2B, 9.2C, 11.3 and 13.8 about the business contact details we collect from businesses' own websites to contact them about Preen: what we collect (including, for an address that has a person's name, that person's name and role as the website gives them), why, where we got it from, that we send those emails through Google Workspace, how to opt out, and how long we keep the records. It also adds Sentry, a service provider in the United States, to the list in section 9 for crash and error reports from our website and app. The outreach wording applies from the day the first such email is sent, and the Sentry wording from the day Sentry starts receiving reports, whichever version of this policy otherwise applies. Nothing else changed.
What changed on 17 October 2026: a new item in section 6.1 about the details we receive from Apple when a Business buys a Preen plan in the Preen iPhone app. It applies from 17 October 2026, whichever version of this policy otherwise applies. Nothing else changed.
What changed when client profiles began (13 November 2026): a new item 4.8 and a new section 5.6B about the profile photo, preferred name, birthday, saved looks, preferences and allergy or health notes a Client can choose to add to their own Preen login, and when businesses they have booked with can see them. They apply from 13 November 2026, whichever version of this policy otherwise applies. Nothing else changed.
What changed when call requests began: a new section 5.6A and a new item 13.7 about the "Is Preen right for you?" form on preen.au, where a person can ask Preen for a call: what we collect, why, that we keep it for 12 months and then delete it, and that occasional news is sent only if the separate box is ticked, and that if it is, a record of the email address, name, business name and what the person agreed to stays on our news list until they unsubscribe. It applies from the day that form goes live on preen.au, whichever version of this policy otherwise applies. Nothing else changed.
What changed in version 1.2: a new section 4.7 (including how safety records are corrected), a corrected Vercel row in section 9.1, and new items in sections 5.2, 9.2A, 12.2 and 13, about client safety records a Business can choose to keep on the Platform: allergies, sensitivities, medical and staff alerts, dated patch-test records, and photos and files (such as before and after photos and signed consent forms). They explain who can see them, what photo details are removed when photos are uploaded, that these records are not used for marketing, AI or analytics and are left out of the Platform's self-serve exports, how copies are provided when someone is entitled to one, and how they are deleted. Nothing else changed. Version 1.2 takes effect on 26 October 2026.
What changed in version 1.1: new sections 5.7 and 13.5, and new items in sections 7, 8.1 and 10.1, about the Preen partner program: the information we collect from people who apply to be partners and from partners, why, what a partner is told about a business that signs up with their link or code, the partner code kept in your browser for up to 60 days, and how long we keep partner records. Version 1.1 also adds a paragraph to section 4.4, a new section 4.6 and a new item in section 5.2 about personal details a Business chooses to record about a Client (such as the names of a partner, children or pets, a birthday or life events), how the Platform suggests them from a Business's notes using fixed rules and not AI, and the Business's responsibilities for that information (personal details came in with version 1.1). Nothing else changed. Version 1.1 takes effect on 5 October 2026.
Version 1.0 took effect on 9 September 2026, the day preen.au began collecting names and email addresses through its waitlist. Earlier drafts were never shown to anyone.
This policy explains how Preen handles personal information about visitors, Clients, Business users and other people who interact with the Platform.
1. About this policy
1.1 Preen Software Pty Ltd (ACN 700 854 664) (ABN 76 700 854 664) is referred to in this policy as Preen, we, us or our.
1.2 Preen is an Australian-first beauty and wellness booking and payments platform. It helps salons, spas, barbers, lash and brow technicians and other service providers manage bookings, client relationships, checkout and communications. It also helps consumers discover Venues, make and manage Bookings, save favourites and payment methods, and pay Businesses.
1.3 We use the Privacy Act 1988 (Cth), including the 13 Australian Privacy Principles (APPs), as the framework for handling personal information. Other privacy or health-records laws may also apply to a Business because of the services it provides or where it operates.
1.4 This policy applies to personal information handled by Preen through our websites, applications, communications and related services. A Business is separately responsible for how it handles its own Clients' personal information and for giving any additional privacy notices required for its services.
2. Defined terms
2.1 In this policy:
- Booking means an appointment for services at a Venue made or managed through the Platform.
- Business means a business that uses the Platform to offer or manage services, including its authorised personnel.
- Client means an individual who visits, enquires about, books or receives services from a Business, whether or not the individual has a Preen account.
- Client Data means personal information about a Client that a Business or Client enters into, generates through or otherwise makes available to the Platform in connection with the Business's services. It includes booking details, client profiles, communications and appointment or service notes.
- Payment Processor means the third-party payment processor engaged to process card payments through the Platform. Stripe is the intended Payment Processor.
- Platform means the Preen websites, applications, booking marketplace, software and related services.
- Processor means an entity that processes personal information on the documented instructions of another entity. For Client Data controlled by a Business, Preen acts as the Business's Processor to the extent described in section 4.
- Sub-processor means a third party engaged by Preen to process personal information on Preen's behalf, including the Payment Processor.
- Venue means a Business's location or listing on the Platform.
2.2 Personal information, sensitive information and health information have the meanings given in the Privacy Act where it applies. In general, personal information is information or an opinion about an identified individual, or an individual who is reasonably identifiable. Health information is a type of sensitive information and receives additional protection.
3. Who is responsible for personal information
3.1 Information Preen handles for its own purposes
Preen is responsible for personal information we collect and use to operate our own relationship with you. This includes account administration, Client accounts, favourites, wallet and marketplace usage information, Business subscriptions, Platform security, product support, our own service communications and marketing undertaken by Preen. Preen is the APP entity for this information in its own right, separately from any role it has as a Business's Processor.
3.2 Client Data a Business controls
A Business is responsible for the Client Data it collects to provide its services, including client profiles, Booking records and appointment or service notes. For that Client Data:
- the Business decides why the information is collected and how it is used for its services;
- Preen stores and processes the information on the Business's behalf and instructions, subject to law and our agreement with the Business; and
- requests or complaints about a Business's service records may need to be handled by that Business, with assistance from Preen.
The words controller and Processor in this policy describe the parties' practical and contractual roles. They do not replace any obligations that either party has under the Privacy Act or other applicable law, and they do not by themselves determine which party is legally accountable for a particular act or practice.
3.3 Payment information
Card payments are processed by the Payment Processor. The Business is the merchant of record for charges it makes to its Clients, while Preen is the merchant for its own subscription charges to Businesses.
Raw card numbers and card security codes are collected and held by the Payment Processor and are not stored by Preen. Preen receives and uses tokenised payment references and limited payment, transaction and status information needed to enable the wallet, Bookings, charges, refunds, reconciliation, fraud prevention and support.
4. Client notes, sensitive information and health information
4.1 A Business may record service notes about a Client, such as skin or scalp conditions, allergies, sensitivities, patch-test results, contraindications, treatment history or other information relevant to safely providing a service. Depending on their content and the circumstances, those notes may be sensitive information or health information under the Privacy Act.
4.2 An organisation that provides a health service and holds health information may be covered by the Privacy Act even if it would otherwise qualify for the small-business exemption. Some beauty and wellness services may amount to a health service depending on what is done or claimed. A Business must assess its own services and comply with the Privacy Act and any applicable State or Territory health privacy laws.
4.3 The Business, not Preen, decides what service notes to collect and is responsible for:
- collecting only information reasonably necessary for its functions and, for sensitive information, obtaining the Client's consent unless a specific exception in the Privacy Act applies;
- explaining to the Client why the information is needed, how it will be used and who may receive it;
- avoiding speculative, irrelevant or excessive notes;
- limiting access to personnel who need the information to provide or manage the service;
- keeping the notes accurate, current and expressed respectfully; and
- responding to Client requests about the notes, with Preen's reasonable assistance.
4.4 Preen stores and processes these notes as Client Data on the Business's behalf, in order to provide, secure and support the Business's use of the Platform, and to comply with law. We do not use appointment or service notes for Preen's own marketing or to build advertising profiles, and we do not use them to train third-party or Preen models. Where we analyse Platform usage to maintain or improve the Platform generally, we use aggregated or de-identified information for that purpose rather than the content of appointment or service notes.
These limits also apply to personal details a Business records about a Client. The Platform uses fixed rules to suggest details from the Business's existing notes and does not use AI to generate these suggestions or send the notes to an AI service for that purpose. Notes and saved details are stored and processed using the hosting and storage providers described in section 9. A suggested name or life event is saved to the Client's personal details only when an authorised member of the Business's team chooses to add it. If a suggestion is dismissed, the Platform stores a dismissal record so it is not offered again. That record may include the suggested name or event.
4.5 A Client should avoid adding sensitive information to free-text fields unless the Business genuinely needs it. If a Client is unsure why a Business is requesting health-related information, the Client should ask the Business before providing it.
4.6 Personal details and life events may reveal sensitive information, including health information, sexual orientation or religious beliefs. The Business must collect only information reasonably necessary for its functions, obtain the consent of the individual concerned where required, and give required privacy notices. These responsibilities also apply to information about a Client's partner, children or other identifiable people. Staff confirmation of a suggestion does not replace any consent required from the individual.
4.7 Client safety records. A Business can choose to keep the following on a Client's record so that its team can provide services safely:
- allergies, sensitivities, medical alerts and staff alerts, each with an optional severity;
- dated patch-test records, including the product tested, who carried out the test, the result and any notes; and
- photos and files, such as before and after photos and signed consent forms, with an optional caption.
These records are likely to be health information or other sensitive information, and photos show the Client. The responsibilities in sections 4.2, 4.3 and 4.6 apply to them. In particular, unless an exception in the Privacy Act applies, the Business must obtain informed, voluntary, current and specific consent from a Client who has capacity to consent, or from an authorised representative where the Client lacks capacity. Before collecting, or as soon as practicable after, the Business must explain what it collects, why, who it may be disclosed to, any overseas handling, the consequences of not providing the information, and how the Client can access and correct it. A Business switching this feature on does not obtain any Client's consent.
As an additional Preen rule (not a statement of what the law requires), a Business must also have a parent's or guardian's permission before photographing a child, even where the child can consent for themselves.
Members of the Business's team can reach these records according to their role, and Preen's own systems that run the service process them. Authorised Preen personnel may access records where necessary to fulfil the Business's instructions, secure the service or meet legal obligations. We coordinate access and correction requests with the Business while meeting our own obligations.
Safety records are corrected, not rewritten. An owner or manager can mark an alert or a patch-test record as recorded in error, with a reason; it stays on the record and in the audit trail, and a patch test marked so no longer counts. A patch test that recorded a reaction keeps counting, however old it is, and is removed on its own only after it has been marked as recorded in error; removing all of a Client's safety records, or the Client, removes it too. A Client who disputes a record can have their own statement attached to it, and it is shown wherever the record is shown. If a Client asks us to correct a record, or to attach their statement, and the Business does not act in time, we can do it ourselves, and we tell the Business.
The Platform shows a Client's active alerts, and whether a service needs a patch test, when the Business's team opens that Client's bookings and checkout on supported web screens. Owners, managers and staff can see photos and files; reception staff cannot. Photos and files are kept in private storage that only the Platform can read. Authorised roles receive file links valid for two minutes; anyone who has a link can use it until it expires.
For JPEG, PNG and WebP photos, we remove standard EXIF, XMP and IPTC metadata (such as location and camera details) when they are uploaded. Some display information, such as a colour profile, remains, and this does not guarantee removal of every hidden detail. PDFs are stored exactly as uploaded, including their metadata and any names or details inside them.
Preen does not use client safety records for Preen's or the Business's marketing, does not send them to an AI service (including the AI receptionist), and does not include them in analytics or in information shared with Preen partners. Safety records are excluded from the Platform's routine self-service exports. Verified access and termination requests receive copies through our secure transfer process using the providers disclosed in section 9. Notifications never contain them (see 9.2A). We keep a record of who added, changed or removed a safety record and when, without the content of the record, to protect the record's integrity.
A Client booking online may see a general note that a service needs a patch test. The booking page does not look up, and does not reveal, whether any person has had a patch test or a reaction.
4.8 Health information a Client chooses to tell us. If you choose to tell us about an allergy, sensitivity or health condition, we keep it on your login as health information and share it only with businesses you have booked with, only while you have ticked the separate box to share it, and only where that business uses Preen's client safety records. You can remove it or untick the box at any time and businesses can no longer see it. If a business has added it to its own records, it is part of that business's records. It is deleted if you delete your account. Please don't rely on it for an emergency: check with your provider at the appointment.
5. Personal information we collect and hold
Depending on how you use the Platform, we may collect and hold the following kinds of information.
5.1 Account and identity information
- name, contact details, login credentials and authentication records;
- profile information and account preferences;
- Business name, role, Venue details and evidence that a user is authorised to act for a Business; and
- records of account creation, consent, acceptance of terms and account changes.
5.2 Booking and service information
- services selected, Venue, staff member, date, time, duration and Booking status;
- requests, confirmations, cancellations, rescheduling and no-show records;
- client profiles, preferences, favourites and appointment history;
- personal details a Business chooses to record so its team can remember them, such as the names of a Client's partner, children or pets, the Client's birthday, and upcoming or recent life events (for example a wedding, a holiday or a new baby);
- client safety records a Business chooses to keep, such as allergies, sensitivities, medical and staff alerts, patch-test records, and photos and files including before and after photos (see section 4.7); and
- appointment or service notes entered by a Business or Client, including information described in section 4.
5.3 Payment and commercial information
- tokenised payment-method references and payment status information provided by the Payment Processor;
- deposits, prepayments, cancellation or no-show fees, refunds, disputes and chargeback records;
- Business subscription plan, billing cycle, invoices, credits and payment history; and
- transaction, point-of-sale and reporting information generated through the Platform.
5.4 Communications
- booking confirmations, reminders, confirmation requests and other transactional messages;
- marketing preferences, consents and unsubscribe records;
- enquiries, support requests, complaints and our responses; and
- enquiry text submitted to the optional AI receptionist feature, where a Business enables that feature.
5.5 Technical and usage information
- device, browser, operating system, IP address, date and time information;
- authentication, security and audit logs;
- pages or features used, errors, performance and diagnostic information; and
- cookies, local storage and similar technology described in section 10.
5.6 Partner program information
- partner program applications: name, business or brand, the kind of audience, web or social links, email address, audience size, anything else the applicant tells us, and a record of the consent given on the form; and
- for approved partners: partner code, ABN, GST registration status, any ATO Statement by a supplier, bank account details for payments (kept in our accounting system), commission statements, tax invoices and payment records.
5.6A Call requests
When someone uses the "Is Preen right for you?" form on preen.au to ask us for a call, we collect:
- first name, business name, email address and Australian mobile number;
- suburb and state, if given;
- the days and times they prefer for a call, if given;
- anything else they choose to tell us in the notes box;
- their answers to the five questions (the kind of business, how many people take appointments, the booking system they use now, what they would most like to fix, and when they are thinking of changing); and
- how they found us: the campaign tags on the link they used, the website that sent them and the page they first landed on.
We use this to email them to confirm a time, to hold the call, and to plan the call around their answers. We keep it as Preen's own company records, separate from any Business's Client Data. We do not sell it. It is stored for us by our hosting and database providers, and our email provider sends the emails about it, all Sub-processors listed in section 9. We disclose it to others only as section 8 describes, for example where the law requires. We delete it 12 months after it arrives (section 13.7). We send occasional Preen news to the email address only if the person ticks the separate, optional news box on the form. If they do, we also keep their email address, name and business name, with a record of what they agreed to, on our news list until they unsubscribe, and they can unsubscribe at any time.
5.6B Client profile and preferences
You can choose to add a profile photo, a preferred name, a birthday, saved looks and a few preferences. If you turn sharing on, businesses you have booked with can see them, and only while it stays on. You can remove them or switch sharing off at any time, and they are deleted if you delete your account.
5.6C Business contact details we collect to contact businesses about Preen
We sometimes contact hair, beauty and wellness businesses to tell them about Preen. Where we do, we collect, from the business's own website, the contact details the business has published there. We do not buy lists and we do not collect details from social media, from directories we do not own the page of, or from private sources.
We collect and hold:
- the business name, its website and its trade (for example hair or beauty);
- the email address the business publishes on its website, which may be a general address (such as info@) or an address that includes a person's name;
- where the address is a person's, that person's name and role in the business as the website gives them, and a short note of why an email about Preen relates to that role;
- the web page it appears on, the date we checked it, the line it appears in and a saved picture of the page, so that we can show where we got it (the picture can show other details on the page, which we do not use);
- the booking system the business appears to use, as shown on its website; and
- what we have sent, and anything the person or business replies, including a request to stop.
We use this to send a small number of emails about Preen to the business, relevant to running a hair, beauty or wellness business, and to handle replies. We send them from Preen's own email addresses (such as sam@, jas@ and rhi@getpreen.au) through Google Workspace (section 9.2B). Each email says who we are, why the business is getting it, and how to stop it. We rely on the business having published the address on its own website, which the Spam Act 2003 (Cth) treats as inferred consent when the conditions in section 11.3 are met. We send at most three emails to a business, and none after a request to stop. We do not use these details for advertising audiences and we do not sell them.
We do not collect this information from the person it is about. The source is the business's own public website. The first email we send names the page the address came from, says that we send it from Google Workspace, and links to this section, so the person can see where we got their details and what we do with them. We tell people this as soon as practicable after we collect their details, which is in that first email. If you want to know where we got your details, or you want us to correct or delete them, email privacy@preen.au. Sections 14 and 16 explain how to ask for access or correction and how to make a complaint.
To stop the emails, reply "unsubscribe" or use the unsubscribe line at the bottom of the email. We stop within the same day. We then keep a minimal record of the address (and the date of the request) so that we never email it again, and we add it to our shared opt-out list (section 11.3). Section 13.8 explains how long we keep the rest of the outreach records.
5.7 Information we generally do not need
Unless a particular Business lawfully needs it for a service, the Platform is not intended to collect government identifiers, detailed medical records or other highly sensitive information. Do not enter such information into general support, profile or Booking fields.
6. How we collect personal information
6.1 We may collect personal information:
- directly from you when you create an account, make a Booking, save a favourite or payment method, contact us, use the Platform or communicate with a Business;
- from a Business when it creates or updates a Client profile, Booking, service note, charge or communication;
- automatically when you use the Platform, through logs, cookies and similar technology;
- from the Payment Processor when it reports on payment methods, transactions, refunds, disputes or fraud signals;
- from Apple, when a Business buys a Preen plan in the Preen iPhone app through Apple's App Store: the transaction details we need to provide that plan, such as the plan, its dates and transaction identifiers (we never receive card details);
- from a business's own website, the contact details that business has published there, as described in section 5.6C;
- from another person who makes a Booking for you or otherwise provides your information with authority; and
- from our service providers where necessary to operate, secure and support the Platform.
6.2 If you provide personal information about another person, you must have authority to do so and, where required, tell them about this policy and the relevant Business's privacy practices.
6.3 You may browse public parts of the Platform without creating an account. It may be impracticable to make or manage a Booking, save a payment method, receive service messages or use other account features anonymously or under a pseudonym because the Business and Preen need to identify and contact the relevant Client.
6.4 If we receive personal information we did not ask for, we will assess whether we could lawfully have collected it. If not, and where lawful and reasonable, we will destroy or de-identify it.
7. Why we collect, use and disclose personal information
We collect, use and disclose personal information where reasonably necessary to:
- create, authenticate, administer and secure accounts;
- display Venues and services and enable Clients to discover and save them;
- create, confirm, change and manage Bookings;
- enable Businesses to manage calendars, Client relationships, service delivery, checkout and reporting;
- process deposits, prepayments, cancellation or no-show fees, in-Venue payments, subscription fees, refunds and payment disputes;
- send transactional email and SMS messages, including confirmations, reminders and confirmation-request links;
- operate the optional AI receptionist for a Business that enables it;
- provide support, respond to complaints and resolve technical or payment issues;
- prevent, detect and investigate fraud, misuse, security incidents and breaches of our terms;
- maintain, troubleshoot and improve the reliability, accessibility and functionality of the Platform, using aggregated or de-identified information where the analysis would otherwise involve appointment or service notes or other sensitive Client Data;
- comply with law, court orders and lawful requests, and establish, exercise or defend legal claims;
- manage our corporate, accounting, audit and record-keeping obligations; and
- send marketing where we have the consent or other lawful basis required by the Privacy Act and the Spam Act 2003 (Cth);
- send a small number of emails to businesses whose contact details are published on their own websites, to tell them about Preen where the message relates to their business, and handle their replies and requests to stop (section 5.6C); and
- assess partner program applications and reply to applicants, run the partner program (recording which partner referred a Business, preparing commission statements and paying partners), and meet our tax obligations for partner payments, including GST, recipient-created tax invoices and withholding where a partner does not quote an ABN.
We may use or disclose information for another purpose where you have consented or the Privacy Act otherwise permits or requires it.
8. Who receives personal information
8.1 We may disclose or make personal information available to:
- the relevant Business and its authorised personnel in connection with an enquiry, Booking or service;
- a Client where the information relates to that Client's account, Booking or transaction;
- the Payment Processor to set up tokenised payment methods and process charges, refunds and disputes;
- the Sub-processors listed in section 9;
- Google, as our email provider for the outreach emails described in section 5.6C, which carries and stores the emails we send and the replies we receive (section 9.2B);
- a Preen partner whose link or code a Business used when it signed up, limited to the Business's name, that it signed up, and the subscription amounts it paid while the partner earns commission on it, so the partner can check their commission;
- the Australian Taxation Office, about payments to partners, where tax law requires it;
- professional advisers, auditors, insurers and prospective transaction parties where reasonably necessary and subject to appropriate confidentiality restrictions;
- regulators, courts, law-enforcement bodies and other persons where required or authorised by law; and
- another entity in connection with a proposed or completed merger, financing, reorganisation or sale of all or part of our business, subject to appropriate protections.
8.2 A Business receives information needed to manage its own Clients and Bookings. A Business must not use Client Data obtained through Preen for unrelated purposes or unlawful marketing.
8.3 We do not disclose Client appointment or service notes to other Businesses merely because the Client uses a cross-business Preen account or wallet. A Business can access only the Client Data made available to it through its relationship with that Client, subject to Platform permissions.
9. Sub-processors and overseas handling
9.1 The current and intended service stack for the Platform, and where each is known to handle personal information, is:
| Sub-processor | Purpose | Countries |
|---|---|---|
| Supabase | Database, authentication and storage | Australia (Sydney region) |
| Vercel | Application hosting and content delivery | Australia (Sydney) for the application's functions; United States (account and platform data); edge network worldwide |
| Stripe | Payment processing (the intended Payment Processor) | Australia and United States |
| Resend | Transactional email delivery | Japan (sending region) and United States (account data, logs and API records) |
| ClickSend | SMS delivery | Australia |
| OpenAI | Processing enquiry text for the optional AI receptionist | United States |
| Google Workspace (Google) | Sending Preen's own outreach emails to businesses from our own email addresses, and receiving the replies (section 5.6C) | United States and other countries where Google runs its services |
| Sentry (Functional Software, Inc.) | Error reporting. Tells us when the website or app crashes or breaks so we can fix it. Receives technical details of the error (the type of error, which part of the code failed, device and browser type, app version). We set it up to remove names, email addresses, phone numbers, IP addresses and booking details before it is sent, but we cannot guarantee that every report is free of personal information (section 9.2C). | United States |
9.2 These providers store or process personal information outside Australia, in the countries named above. The particular locations can depend on the provider, product configuration and routing at the time, and we will update this table when we learn of a change. We do not claim that Platform data remains only in Australia.
9.2A We do not send health information overseas in the content of emails or SMS messages. Service notes, including any allergy, sensitivity, patch-test or contraindication detail a Business records, are not included in the body of a notification. Notifications identify the appointment and link to the Platform, where the record is available to the Business behind authentication.
The same applies to client safety records described in section 4.7: alerts, patch-test results, photos and files are never included in an email or SMS. Photos and files are stored with Supabase in the Sydney region. When they are uploaded or removed they pass through Vercel's application functions in Sydney, reached through its edge network (see 9.1). Copies provided under section 4.7 are held for transfer with Supabase in the Sydney region.
9.2B Outreach emails (section 5.6C). We send these emails from Preen's own Google Workspace email addresses, using Google's email service. Google is a service provider based in the United States. It stores and processes the emails we send and the replies we receive in the United States and in other countries where it runs its services, so a business's email address, and anything in the emails and replies, can be handled outside Australia. We do not upload outreach lists to any other email sending service. The first email names the page the address came from, so Google handles that page address too. The date we checked, the saved picture of the page, the person's role and the notes we keep about why we contacted them stay in our own records and are not put in the emails. Google does not receive Client Data from any Business, and no Client Data is used for outreach. We take reasonable steps to make sure Google handles this information consistently with the Australian Privacy Principles, based on its published terms and privacy information. Privacy protections and remedies in the United States and other countries may differ from those in Australia.
9.2C Error reports. We use Sentry, a service provider in the United States, to find and fix errors in our website and app. When something breaks, technical details about the error, such as the type of error, which part of the code failed, your device or browser type and the app version, are sent to Sentry. We set it up so that it does not receive your name, email address, phone number, IP address or booking details, and we remove names, email addresses, phone numbers, IP addresses and similar details before a report is sent. We cannot guarantee that every error message is free of personal information, so we list Sentry here as an overseas recipient. We do not use Sentry for advertising. We take reasonable steps to make sure Sentry handles this information consistently with the Australian Privacy Principles, based on its published terms and privacy information. Sentry's staff and providers in other countries may be able to access reports. Privacy protections and remedies in the United States and those countries may differ from those in Australia.
9.3 Where APP 8 applies to an overseas disclosure, we will take reasonable steps in the circumstances to ensure the overseas recipient handles personal information consistently with the Australian Privacy Principles, unless an exception applies. Depending on the relationship and service, those steps may include due diligence, contractual privacy and security obligations, access restrictions and reviewing provider information. We do not represent that OpenAI or another Sub-processor will not use content submitted to it for its own purposes beyond providing the relevant feature to us; we will disclose honestly if a provider's data-use settings change in a way that materially affects this policy, and Businesses should avoid submitting unnecessary sensitive information through the AI receptionist feature.
9.4 Overseas recipients may be subject to foreign laws, including lawful government-access requirements. Privacy protections and remedies in another country may differ from those in Australia. Preen remains responsible for its own compliance with the Privacy Act, including any accountability that applies under section 16C.
9.5 For Client Data controlled by a Business, the Business also remains responsible for assessing and giving any notices required for its use of Preen and the resulting overseas handling. Further processing terms are set out in the Data Processing Terms incorporated into the Business Terms of Service.
10. Cookies and similar technology
10.1 We use cookies, local storage and similar technology where needed to:
- keep users signed in and remember choices;
- protect accounts and prevent misuse;
- maintain Booking and checkout sessions;
- remember, for up to 30 days, which link or campaign first brought you to our website (for example the `utm` parameters on a link), so that if you later ask us to contact you we know which of our own marketing worked;
- remember a Preen partner's code and when you first opened that partner's link, for up to 60 days, so that if your business signs up we can record which partner referred it (blocking or deleting this storage may stop the referral being recorded); and
- understand errors, performance and basic use of the Platform.
10.2 We may use limited product analytics or diagnostics to improve the Platform. We do not currently use behavioural advertising or cross-site advertising cookies. If those practices are introduced, we will update this policy and provide any required notice or choice before they apply.
10.3 You can use browser or device controls to block or delete cookies. Some essential Platform features may not work properly if essential storage is blocked.
11. Transactional messages, reminders and marketing
11.1 Preen and Businesses may use the Platform to send transactional messages about an enquiry, Booking, payment or service. These can include confirmations, reminders, changes, receipts and links asking a Client to confirm a Booking. A message stays transactional only while it is free of promotional content; adding marketing material to an otherwise factual message can make the whole message a commercial electronic message under the Spam Act 2003 (Cth).
11.2 Clients can opt out of optional reminders using available settings or by contacting the relevant Business or Preen. Some messages that are necessary to complete a requested transaction, communicate a material service change, protect an account or comply with law may still be sent.
11.3 Marketing is separate from transactional messaging. Preen will send electronic marketing only with consent or another lawful basis and in accordance with the Spam Act 2003 (Cth). Marketing messages will identify the sender and include a working unsubscribe facility. We will give effect to unsubscribe requests as soon as practicable and, in any event, within the time currently required by the Spam Act 2003 (Cth), which is 5 business days.
Outreach to businesses. When we contact a business about Preen, we do it in line with the Spam Act 2003 (Cth). We only use an email address that the business has conspicuously published on its own website, and where it is reasonable to think the business published it to receive messages like ours, and where nothing published with it says the business does not want unsolicited messages, and we only send messages that relate to running that business. Where the address includes a person's name, we also check that the website gives that person's role in the business and that the message relates to that role. Every one of these emails names Preen Software Pty Ltd, gives our contact details, and includes an unsubscribe line that is set out in the email and keeps working for at least 30 days, and the option to reply "unsubscribe". The first email also names the page we got the address from, says that we send it from Google Workspace, and links to section 5.6C of this policy. We treat any reply that means "stop", and any automatic reply that says the business does not accept marketing or sales emails, as a request to stop. We stop within the same day: we add the address to our shared opt-out list, which we check before we contact anyone in any way (email, Instagram messages, post and in person), and we do not contact them again. You can also ask us to stop at any time by emailing privacy@preen.au. We act on that request as soon as we see it, and within the time in section 11.3 at the latest.
11.4 A Business is responsible for ensuring that any marketing it sends or directs through the Platform is lawful, within the scope of the Client's consent and not based on sensitive information unless that use is specifically permitted. Preen's tools do not give a Business permission it does not otherwise have.
12. Storage and security
12.1 Platform information is stored using Supabase and hosted or delivered using Vercel, with the other Sub-processors in section 9 processing information for their stated functions.
12.2 We take reasonable technical and organisational steps appropriate to the nature of the information and risks. These include encryption in transit, access controls and row-level security, least-privilege service access, and review of database privileges. We also use authentication, logging, monitoring and operational processes appropriate to the Platform as it develops.
Client safety records are protected by row-level security that limits them to authorised members of the Business. Photos and files are held in private storage, can be written only by the Platform after it checks the uploader's authority and removes standard photo metadata, and can be opened only through links valid for two minutes issued to authorised members of the Business.
12.3 No internet or storage system is completely secure. We do not claim that Preen has a particular security certification or that all security incidents can be prevented. Raw card data is handled by the Payment Processor rather than stored by Preen, but that does not remove every security or privacy risk associated with payment transactions.
12.4 Users must protect their login details, use appropriate access settings, keep Business-user access current and tell us promptly if they suspect unauthorised access.
13. Retention and deletion
13.1 We retain personal information only for as long as reasonably needed for the purposes described in this policy, including to provide the Platform, keep appropriate transaction and audit records, resolve disputes, enforce agreements and comply with legal, tax, accounting and regulatory obligations.
13.2 Retention periods differ according to the type of information, the sensitivity of the information, the relationship with the Business or Client, legal requirements and whether a dispute or security issue is active. For example, we generally expect to retain Booking and transaction records for as long as needed for tax and dispute-resolution purposes, and marketing consent or unsubscribe records for as long as needed to honour those choices, in each case subject to the exceptions in this section.
13.3 A Business may control retention of its Client Data while its account is active. After termination, the Business has the export period and deletion arrangements stated in the Data Processing Terms. Deletion from active systems may be followed by a limited period in protected backups, which are isolated from ordinary use and expire or are overwritten under backup processes.
13.4 Where the Privacy Act requires it and no lawful reason for retention remains, we will take reasonable steps to destroy or de-identify personal information. De-identified and aggregated information that no longer identifies an individual may be retained and used for legitimate business purposes.
13.5 We delete partner program applications we decline, or do not act on, 12 months after our decision or after they arrive. We keep approved partners' commission statements, tax invoices, tax records and payment records for at least five years, as tax law requires.
13.6 A client safety record stays on the Platform until the Business removes it, or the Business's account ends and its data is deleted under the Data Processing Terms. The Business can remove each record on its own, and an owner or manager can remove all of a Client's safety records in one step from the Client's record. When a photo or file is removed, the stored file is deleted from active storage, normally within an hour. Switching the feature off hides records without deleting them. Currently, removing records in the Platform requires switching the feature back on. Businesses must review how long they keep these records and remove records they no longer lawfully need. Protected backups follow section 14.4 of the Data Processing Terms.
13.7 We delete a call request 12 months after it arrives. If the person ticked the news box, the news-list record (email address, name, business name and the consent they gave) is not deleted with the call request. It stays until they unsubscribe, and after that we keep the unsubscribe record for as long as needed to honour it, as described in 13.2.
13.8 For outreach to businesses (section 5.6C): we keep the lead record, the proof of where and when we found the address (including the saved picture of the page), the emails we sent and any replies until 12 months after the last email we sent or reply we received, and then delete them. When someone asks us to stop, we keep only the minimal record of the request and delete the rest of the outreach record within 12 months of that request. If we never contacted the business, we delete the record within 3 months of collecting it. The exception is the minimal record of a request to stop (the address and the date of the request), which we keep for as long as needed to make sure we never email that address again, as described in 13.2. The emails and replies in our Google Workspace mailboxes are deleted on the same schedule. Google may keep backup copies for a limited period after we delete them.
14. Access and correction
14.1 You may request access to personal information about you that Preen holds and ask us to correct information that is inaccurate, out of date, incomplete, irrelevant or misleading. You may also be able to view or update some information through your account.
14.2 Send a request to privacy@preen.au. You do not have to use a particular form, but enough detail to identify you and the information will help us respond. We may take reasonable steps to verify identity or authority before providing access or making a correction.
14.3 If the request concerns Client Data controlled by a Business, we may refer the request to that Business or assist it to respond. Contacting the Business directly may be the quickest route for appointment or service notes. Preen and the Business will each remain responsible for their own legal obligations.
14.4 We will respond within a reasonable period, generally within 30 days. We will not charge for making a request or for correction. If a lawful basis permits or requires us to refuse access or correction, we will give written reasons where required and explain available complaint options. If we do not make a requested correction, you may ask us to associate a statement with the information as provided by law.
15. Data breaches
15.1 We maintain processes to identify, contain, investigate and respond to suspected data breaches. We will work with affected Businesses and service providers as appropriate.
15.2 The Notifiable Data Breaches scheme under Part IIIC of the Privacy Act requires a covered entity that has reasonable grounds to suspect an eligible data breach to carry out a reasonable and expeditious assessment, generally completed within 30 days, and, if there are reasonable grounds to believe an eligible data breach has occurred and it has not been remedied, to notify affected individuals and the Australian Information Commissioner. An eligible data breach generally involves unauthorised access to or disclosure of personal information, or loss of information, that is likely to result in serious harm.
15.3 Where a breach involves Client Data controlled by a Business, the Business will generally lead decisions and notifications concerning its Client Data, and Preen will provide reasonable information and assistance. Where a breach involves personal information Preen holds for its own purposes under section 3.1, Preen will lead the assessment and any required notification for that information. This allocation does not prevent either party from meeting a legal obligation that applies directly to it.
16. Privacy complaints
16.1 If you believe Preen has mishandled your personal information, contact our Privacy Officer at:
- Email: privacy@preen.au
- Address: 28 Cordyline Drive, Reedy Creek QLD 4227
Please explain what happened, the information involved and the outcome you are seeking. We may ask for further information and may need to verify your identity.
16.2 We will acknowledge and investigate the complaint, consult relevant Businesses or providers where needed, and aim to give a substantive response within 30 days. If we need more time, we will tell you why and give an expected response date.
16.3 If the complaint concerns a Business's collection or use of Client Data, we may refer it to the Business and assist with the response. You may also complain directly to that Business.
16.4 If you are not satisfied with our response, you may contact the Office of the Australian Information Commissioner:
- Website: www.oaic.gov.au
- Telephone: 1300 363 992
The OAIC generally expects you to complain to the relevant organisation first and allow it a reasonable time to respond. Other State, Territory, health privacy or fair-trading bodies may also have jurisdiction depending on the issue.
17. Changes to this policy
17.1 We may update this policy when our practices, technology or legal obligations change. We will publish the updated version through the Platform and update its version and effective date.
17.2 If a change materially affects how we handle personal information, we will take reasonable steps to give additional notice and obtain consent where required by law. An updated policy applies prospectively and does not retrospectively authorise a use or disclosure that was unlawful when the information was collected.
18. Governing law
18.1 This policy is governed by the laws of Australia and Queensland, without limiting any right you have under the Privacy Act or another law that cannot be excluded.
19. Contact
Questions about this policy or Preen's privacy practices can be sent to:
- Privacy: privacy@preen.au
- General support: support@preen.au
- Entity: Preen Software Pty Ltd (ACN 700 854 664)
- ABN: ABN 76 700 854 664
- Address: 28 Cordyline Drive, Reedy Creek QLD 4227