Privacy policy
Growth Engine
Who we are
Growth Engine is a brand of a sole trader in New South Wales, Australia, trading as DATAILABS. [FOUNDER: the owner's full legal name, the ABN, the business name registered with ASIC once the registration for Fairsoar is complete (FA-23), and the postal address to print here (the PO box of card PO1)]
This policy covers this website and the service we run for creators and businesses who hire us to publish safe-for-work promotion on their own social accounts. It does not cover those platforms: each has its own privacy policy. In this policy "we" means that sole trader. We are the controller of the personal data described here, except where a signed client contract says otherwise. [FOUNDER: whether, for a client's own personal data and for data about a creator's audience, we act as controller or as processor; the legal council left this for a lawyer and the client contract must say which]
Australian privacy law
We handle personal information in line with the Privacy Act 1988 and the Australian Privacy Principles: we collect only what we need, tell you why, keep it secure, let you see and correct it, and disclose it overseas only to the providers listed below, which we choose with care. [FOUNDER: confirm that the policy may say the Australian Privacy Principles are followed whether or not the Act binds the business; the research of 10 November 2026 found the Act probably does not apply to a small business below the annual turnover threshold, and a lawyer should confirm it] Email follow-up to a prospective client is sent only after they opt in, and every message carries an unsubscribe link (the Spam Act 2003). We send no text messages.
What we collect
From visitors to this website. The site has no account, no tracking and no form to fill in today. Our hosting provider and the network in front of the site handle each request, so they see your IP address, the time, the page requested and your browser type. We do not read these logs to identify anyone. [FOUNDER: how long the hosting provider and Cloudflare keep these request logs, and whether any log is available to us]
When you write to us. If you email contact@example.com, we hold your address, your message and our reply. A person reads every message. Today the homepage asks creators to send a profile link by email, and we read that profile to reply. When the homepage form is switched on, the form collects an email address and a profile link, and nothing else. [FOUNDER: how long emails sent to the contact address are kept in the founder's inbox, and which email provider holds it]
About prospective clients. If you ask to become a client, we hold your contact name and email, your answers to our intake questions, a score that helps the operator sort prospects, and the record of your opt-in to email if you gave one and of any withdrawal. The score is advice only: a person decides whether to take on a client, and no decision about you is made by software alone.
About clients. We hold your name, contact details, country and GST status, your signed contract and the consents you gave, each with its date, your confirmation that you are 18 or over and that you hold an existing account on the platform, the instructions you give us for your content, the media you supply, and the content we prepare and publish for you. We hold a record of every action taken on your account and who took it. We hold the sign-in connection to each social account you connect, sealed with a key stored outside the database. We hold invoices and the sales totals needed to work them out.
Sales figures. From a connected Fanvue account we read totals per link and per day. From a creator who uses OnlyFans we accept only the statements the creator hands us ourselves, and only the totals we need; we never collect anything from OnlyFans automatically. We keep no fan-level records: no fan names, handles, emails or subscription histories. A fan-level table would be built only after the platform allows it in writing and a privacy impact assessment is done, and this policy would change first.
What we never collect. We never ask for or store the password to a social account, the logins or chats of a client, or a client's bank or payment details. The sign-in to each social account is the platform's own, and you can end it in that platform's settings at any time.
Sensitive information. We do not ask for health, sexual orientation or similar information. Because our clients work in adult-capable fields, a client record could show something about adult-platform work. We hold such records only as the contract needs them. [FOUNDER: whether records that show a client's adult-platform work count as sensitive information under the Privacy Act or special category data under the GDPR; the decision record on data region leaves this for a lawyer before the first outside client]
Why we use it and the legal basis
- To answer your message and decide whether to work with you. Basis for people in the EU and the UK: our legitimate interest in running a business and answering enquiries (GDPR Article 6(1)(f)), or steps you ask us to take before a contract (Article 6(1)(b)).
- To provide the service to a client: to prepare, approve, publish and measure content, keep the consents and contract, and invoice. Basis: the contract (Article 6(1)(b)).
- To keep records the law requires, such as invoices. Basis: a legal obligation (Article 6(1)(c)).
- To send email follow-up to a prospective client. Basis: your consent, given by ticking a box, which you can withdraw at any time (Article 6(1)(a)).
- To protect the service, prevent misuse and keep it working. Basis: our legitimate interest (Article 6(1)(f)).
We do not do these things: sell personal data, use it for advertising by others, track anyone across platforms, or use platform data to train an AI model. We do not use a client's data for another client. We do not message anyone who has not written to us or opted in, and we send no unsolicited messages.
Adding information from other sources. We do not do this today. If we ever add third-party information to the record of a prospective client for our own sales, we will do it only under a written assessment of our legitimate interest, record the source for each prospect, name the source if you ask, and stop at once when you object. We never do it for a fan of a creator or for anyone whose data reached us through a platform.
Automated decisions. Software scores prospects and checks content against the rules and the client's instructions before it is published. None of this makes a decision with a legal or similarly significant effect on a person without a human taking part: a person moves a prospect to a client and a client approves content, or content is approved against the client's own written score bar.
Who receives it
We do not sell personal data. We use these providers to run the site and the service, and each receives only what its job needs. Prompts sent to an AI model carry no contact details and no personal data beyond what the task needs.
Running this website today
- Railway hosts the website, in Amsterdam. It holds the site's pages and the request logs described above.
- Cloudflare runs the domain name, sits in front of the website, redirects our other addresses to it and forwards email sent to contact@example.com to the owner's inbox. Cloudflare sees each request and each email it forwards.
Running the service for clients, as it is switched on
- Supabase holds the database in Frankfurt: client, prospect and consent records, the sales totals, invoices and the sign-in records of the client portal.
- Cloudflare R2, in its EU jurisdiction, holds signed contracts, evidence documents and media files.
- Backblaze B2 holds the nightly copy of the database and files at a second vendor. Every object is sealed with a key we hold before it leaves. [FOUNDER: the region of the Backblaze bucket for the nightly backup; no document names it]
- Amazon Web Services runs email sending (Amazon SES) and image checks (Amazon Rekognition) for content safety and the age check. [FOUNDER: the AWS regions used for SES and Rekognition]
- Documenso, which we host ourselves, collects contract signatures.
- Xero sends invoices, with the client's name, country, GST status and the amount. [FOUNDER: where Xero stores that data and the lawful basis for sending it there; no document states it]
- Google Cloud Vision checks whether an image shown as an invented person appears online.
- Black Forest Labs makes images, and an AI language model provider writes and checks captions. We send them the instructions for the content and no contact details. [FOUNDER: the language model provider and its region, which the model registry names when it is loaded, and whether a data processing agreement is in place]
- Sentry and Grafana Cloud receive error reports and performance data. Our code removes tokens, authorisation headers and webhook bodies before anything leaves, and contact details are never written to logs. [FOUNDER: the regions of Sentry and Grafana Cloud, and whether they are switched on when the service goes live]
- The social platforms you connect (Instagram, Threads, YouTube, Bluesky, X and Fanvue) receive the content we publish for you and the connection you gave us, and nothing else.
We also share details where the law requires it, and with a platform when it asks for a list of our clients with their contact details (for example to check an app listing).
Where it is held and sent
We store client data in the EU: the website and service run on Railway in Amsterdam and the database is on Supabase in Frankfurt. We are based in Australia, so when we open client data from Australia it is sent back from the EU to us. Australia has no EU or UK adequacy decision, and no ready-made standard contractual clauses cover an Australian controller receiving data from an EU host. [FOUNDER: the transfer mechanism to state for data sent from the EU and the UK to the business in Australia, and for each provider above outside the EU; a lawyer should settle this before the first outside client]
How long we keep it
We keep personal data only while it is needed for the purpose it was collected for.
- An enquiry from the homepage that did not become a prospective client is deleted after 12 months. A prospective client record that never became a client is deleted after 12 months. Both are deleted sooner if you ask.
- An email opt-in and its withdrawal are deleted when you ask, and when the prospective client record they belong to is deleted.
- When a client leaves, access to every connected account ends at once, the contact details on the client record are replaced with placeholders at once, and everything else is deleted within 30 days, except what the law requires us to keep and the one read-only sales-totals connection that stays only while the contract's share after exit runs, only if the client agreed to it in the contract. That connection reads sales totals and never publishes.
- Invoices and the sales records they are worked out from stay for the period the law requires and are deleted when it ends. They no longer name a person once the contact details have been replaced. [FOUNDER: how long invoices, contracts and the sales records behind them must be kept; the research on money records has not been done and there is no accountant (AB1)]
- The nightly copy at the second vendor holds what existed at the time. A deletion does not reach a copy already made; it falls out of the copies as they expire. [FOUNDER: how long nightly backup copies are kept before they are deleted]
- Records of actions taken on the service (an audit log) hold ids and the kind of action, never an email address, a link or a name.
Security
Connection tokens and other secrets are sealed with a key held outside the database and are never written to logs. Each client's data is separated from every other client's by the database itself. Backups are sealed before they leave. Every process that opens the database refuses to start if its database login can reach more than its job needs. If a breach of personal data is likely to cause serious harm, we will tell the people affected and the regulator, and tell a platform when its terms require it. [FOUNDER: the data breach procedure to state: who is told, in what time and by whom (the EU and UK rules set 72 hours for the regulator)]
Cookies
This website sets no cookies today. It has no advertising cookies, no analytics, no tracking pixels and nothing that follows you across other sites. The tracking links we create for clients redirect a visitor to the client's page; they set no cookie and store no IP address.
When we run a test of two or three versions of the homepage, we will set one cookie, named fs_design, so you see the same version each time you come back. It holds only the name of the version, belongs to this site alone, is not readable by scripts on the page and lasts 90 days. [FOUNDER: confirm the 90 days; no document sets it and the code chose it as a proposal] Visitors from the EU, the EEA and the UK, and visitors whose country we cannot tell, are asked first and the cookie is set only if they agree; if they do not, nothing is stored. The test also counts how many people saw each version, with no name or address, and counts an enquiry only when your cookie names the version you used.
When the client portal and console are switched on, signing in uses cookies that are strictly necessary to keep you signed in. They are set only for people who sign in.
Your rights
You can ask for a copy of the personal information we hold about you and ask us to correct it. If you are in the EU or the UK you can also ask us to delete it, restrict how we use it, move it to another provider, or stop using it where we rely on our legitimate interest, and you can withdraw a consent at any time, which does not affect what we did before. Write to contact@example.com from the address we hold. We may ask for a little proof that you are that person. You will not be charged. We will reply [FOUNDER: the period to promise for an answer; 30 days is the limit for an Australian access request and the EU and UK rules allow one month, and R-406 uses 30 days for a client's data]. Deletion requests are handled as the data deletion page describes.
Complaints
Tell us first at contact@example.com and we will try to put it right. If you are not satisfied, in Australia you can complain to the Office of the Australian Information Commissioner (oaic.gov.au). In the United Kingdom you can complain to the Information Commissioner's Office (ico.org.uk). In the EU you can complain to the data protection authority of the country where you live or work.
People in the EU and the UK
The GDPR and the UK GDPR apply to the service for creators in the EU and the UK, wherever our servers are. We have not yet named a representative in the EU or the UK, which the law requires once we offer the service there. [FOUNDER: the EU and UK representative's name and address once appointed (GDPR Article 27); the legal council advises the occasional-processing exemption is not available, and whether the marketing intentionally targets EU and UK creators is not yet confirmed]
Children
The service is for adults. A client must confirm they are 18 or over before they can be onboarded, and we do not knowingly collect personal data from anyone under 18.
Changes
We will update this policy when what we do changes, and the current version is always the one on this page.
Contact
Questions about this policy, requests about your information and complaints go to contact@example.com.