Privacy policy
Your details.
A clear purpose.
This privacy policy covers the personal information Starworks HQ (“Starworks”, “we”) collects through this website, our ads and lead forms on LinkedIn, Facebook and Instagram, and meeting bookings. It says what we collect, why, who else handles it, and how to see, correct or delete it.
Visiting the site
We count page views ourselves, so we know which pages get read and which links bring people here. Those counts are not shared with an analytics company, and our own counting sets no cookies. The exceptions are LinkedIn and Meta, described below.
For each page you open we record the page, how long it was open, how far down it was read, the site or campaign link you came from, your device type, browser, operating system and country, and a short code your browser makes up for the visit. Your browser forgets that code when you close the tab; the records it is attached to keep it, which is how we can tell that one visit read four pages rather than four people reading one.
Your connection address and browser details are mixed with a secret and the date, then turned into a one-way code. Neither the address nor the browser details are stored, the code cannot be turned back into either, and because the date goes into it, the same person gets a different code tomorrow. We keep these records for as long as they are useful for understanding how the site is used.
We advertise on LinkedIn, and our pages load LinkedIn’s Insight Tag so we can tell whether those ads work. For each page you open, the tag sends LinkedIn the page address, including any campaign label in it, the page that linked you here, your connection address, browser and device details, and the time. When you send an application or book a call, the tag also tells LinkedIn that one happened, and whether the application was from an agency, but none of what you typed. If you have a LinkedIn account, LinkedIn can connect the visit to it. LinkedIn sets its own cookies to do this, some of them on this site’s address. It reports visits and applications back to us only in aggregate, such as by company size, industry or job function, and never tells us who you are. It also lets us show our ads again to people who have visited. LinkedIn’s cookie policy explains its processing. You can turn off ads based on other websites in your LinkedIn ad settings or, without an account, its guest controls, or block the cookies in your browser. The admin area of this site never loads the tag.
We also advertise on Facebook and Instagram, and our pages load Meta’s pixel so we can tell whether those ads work. For each page you open, the pixel sends Meta the page address, the page that linked you here, your connection address, browser and device details, and the time. When you send an application or book a call, it also tells Meta that one happened, and whether the application was from an agency, but none of what you typed: we have switched off the pixel’s automatic reading of pages and forms. If you have a Facebook or Instagram account, Meta can connect the visit to it. Meta sets its own cookies to do this, reports results back to us in aggregate, and lets us show our ads again to people who have visited. Meta’s privacy policy and cookie policy explain its processing. You can limit ads based on your activity on other websites in your Facebook or Instagram ad preferences, or block the cookies in your browser. The admin area of this site never loads the pixel.
Our hosting provider, Vercel, processes technical request information to serve and protect the site. It uses the country associated with your connection to send Australian visitors to the Australian homepage. This does not use your device’s precise location.
Lead forms on LinkedIn, Facebook and Instagram
Some of our ads open a form inside LinkedIn, Facebook or Instagram. When you send one, the platform passes us what is on it: usually your name, email address, phone number, business or company name and job title, which the platform may fill in from your profile, and your answers to our questions, such as what your business does, which city you work in, whether you own or manage it, or how many clients your agency looks after. It also tells us which ad the form came from.
An automation service copies each form into our own records, the same private database that holds applications, and sends us a private Telegram message so we can reply the same day. Neither keeps it for any other purpose.
We use these details to send what the form offered, such as a report or a check of what ChatGPT says for your category and city, and to follow up by text, phone or email about working with us. We send our occasional research emails only if you tick that box on the form, and you can unsubscribe from them at any time. The details are kept in our own records and email, and handled by the service providers that store and deliver them for us. We do not sell them. LinkedIn’s privacy policy explains how LinkedIn itself handles its forms, and Meta’s privacy policy explains how Meta handles forms on Facebook and Instagram.
Applications and partnership enquiries
When you apply, we collect the business, contact and project details you enter, including your name, email, phone, country, areas served and any notes. We save the application in a private database hosted by Supabase, and send its details to a private Telegram chat so we can reply quickly. The website sends it nowhere else. If you reached us from a link carrying a short label, such as the name of an email or a post, we save that label with your application so we know where enquiries come from. We also save the visit code described above, so we can see which pages were useful before someone applied. Your browser holds both for the visit only and neither says anything about you.
Sending the application is your agreement to be contacted by email or phone about this enquiry, as the form says under its Send button. If you press Send and the form asks you to fix a field first, we keep what you have entered so far, provided it includes an email address or phone number, so that a slip on the form does not lose your enquiry.
The form also saves what you type as you go, before you press Send, as it says at the top of the form, so that a closed tab or a dropped connection does not lose your enquiry. If you leave without sending, what you typed stays in the same private database and is seen only by us. Leaving without sending is not an agreement to be contacted, and it does not put you on any list.
We use these details to assess your enquiry and respond by email or phone, as you agree by sending the form. Submitting an application does not publish your details in a directory or subscribe you to marketing. Our service providers process the information needed to provide these services; applications are not publicly accessible.
Booking a meeting
Our scheduling service is Cal.com. Its scheduler loads with our booking page, so opening that page, or following the direct booking link, shares technical request information with Cal.com, including a short label for the link that brought you to us, such as the article you were reading. The details you enter there are used to arrange your meeting, add it to our connected calendar and send booking messages. Cal.com’s privacy policy explains its processing and cookies.
Access, corrections, deletion and complaints
We retain enquiries and lead form details while assessing and following up on them, and where needed to manage an ongoing business relationship. To ask what we hold about you, or to correct or delete it, email hq@starworkshq.com from the address you gave us. We may need to keep records required for an ongoing agreement or legal obligations.
Privacy questions and complaints go to the same address, and we reply within 30 days. If you are not satisfied with our answer, you can contact the Office of the Australian Information Commissioner.
Updated 24 October 2026.