PRIVACY POLICY

Last updated: 5 September 2026

This is a structured draft, not legal advice tailored to your situation. If you have specific concerns, email hello@webgecko.au.

Who we are

WorkPost is operated by WebGecko (ABN 32 300 992 377), a Queensland, Australia business. We help tradies, plumbers, electricians, builders and similar trades, turn job photos, videos and voice notes into social media posts, and run the everyday side of the job: clients, quotes, invoices and a simple job calendar. This policy explains what personal information we collect, how we hold it, who we share it with (including overseas), and how you can access, correct or delete it.

Personal information we collect

Account details: your name, email, business name, trade and timezone. Content you create: job photos and videos, voice recordings, the text transcribed from those recordings, and the captions our AI generates from your photos and voice notes. Connection details: if you link Instagram, Facebook, Threads, LinkedIn, TikTok or your Google Business Profile, the OAuth access token needed to post on your behalf. Business suite records, if you use them: your clients' names, phone numbers, emails and addresses, plus the jobs, quotes and invoices you create against them, including any message we send them on your instruction and any quote-signature record. Subscription and usage: your plan tier (Free or Pro) and how many AI actions you've used this period. We don't collect payment card details, whoever you pay handles that and only tells us your plan status: the app stores (Apple/Google, via RevenueCat) if you subscribe in the app, or Stripe if you subscribe on our website. Card payments on your invoices: if you switch these on, Stripe collects your identity and bank details directly to verify you and pay you out, we never see them, and only store your Stripe account reference and whether it's active. When your client pays an invoice by card, they enter their card details with Stripe, not with us; we're told the amount and that it succeeded so the payment can be recorded against the invoice.

How we collect and hold it

You give us most of this directly in the app, signing up, taking or uploading photos/video, recording voice notes, and typing in client and job details. We hold it in Supabase, our database and file storage provider, hosted in Sydney, Australia. Your login session is encrypted on your device (the access token is AES-encrypted and the encryption key lives in your phone's hardware keystore, not in plain storage) so a lost or compromised device doesn't expose it in plain text.

Why we collect it

To run the app: storing your content, transcribing voice notes, generating draft captions, publishing approved posts to the social accounts you connect, and powering the business suite (clients, quotes, invoices, job calendar). To identify you and manage your account and subscription. To personalise captions to your business and trade. To contact you about your account or respond to a support request. We don't sell your personal information and don't use it to serve you ads.

AI processing of your photos and voice notes

When you ask WorkPost to generate a caption, the relevant job photo(s) are sent to Anthropic (Claude), based in the United States, to write the draft caption. If you've recorded a voice note, it's sent first to Groq, also based in the United States, to convert it to text, that transcript is then sent to Anthropic too, so the caption matches what you actually said. These photos and transcripts can contain a customer's name, their address (visible in the shot, or mentioned on the recording) or their likeness, whatever's genuinely in the photo or the voice note; we don't ask you to remove it first. Both providers process this in the United States, and neither Anthropic nor Groq trains its models on the data you send them, it's used only to generate your caption or transcript, per their own commercial API terms. You always review and can edit the result before anything is posted, nothing generated by AI is published without your approval.

Overseas disclosure

Some of the providers we rely on to run the app are based in the United States, so your information (or parts of it) is disclosed there. Anthropic (US) receives job photos and transcribed voice-note text to generate draft captions, and doesn't train on it. Groq (US) receives your voice recordings to transcribe them to text, and doesn't train on it. Meta (Instagram, Facebook and Threads, US), LinkedIn (US), TikTok (ByteDance, with servers in the US and Singapore) and Google (US) receive the content you approve for posting, published via the OAuth connection you authorise. RevenueCat (US) receives your subscription status to manage billing entitlements. Stripe (US, with an Australian entity) receives your identity and bank details if you enable card payments on your invoices, and processes your clients' card payments, money from those payments goes directly to your own Stripe account, never through us. Twilio (US) receives the phone number and message text when you send a review-request or invoice-payment SMS. Resend (US) receives the email address and message text when we email an invoice instead, because a client has no phone number on file. Your database, file storage and account records are held with Supabase in Sydney, Australia. Supabase Inc. is a United States company and its personnel can access that infrastructure remotely for support and maintenance, so although your data is stored in Australia it is accessible to an overseas provider. We take reasonable steps to ensure these providers only receive what they need to do their job and are bound by their own data-handling terms. The Office of the Australian Information Commissioner does not maintain a list of countries with privacy laws it considers substantially similar to Australia's, so no APP 8.2 exception applies here, this disclosure is what APP 8.1's "reasonable steps" looks like for WorkPost.

Your business suite customers

If you store your customers' names, phone numbers, emails or addresses in the business suite (clients, jobs, quotes or invoices), that information belongs to your business relationship with them, not to us, it's visible only to your account. We hold it to run the features you use against it: sending the review-request and invoice-payment texts you trigger, generating quotes, and recording jobs. You're responsible for collecting and handling your customers' information appropriately, including telling them how you use it if your own obligations require that. It's deleted the same way as the rest of your account: when you delete your WorkPost account, your clients', quotes' and invoices' records are permanently deleted with it (see "Data retention and deletion" below).

Texting your customers on your instruction

WorkPost can send an SMS to a client on your books, a review request or an invoice payment link, but only when you press send. Nothing sends automatically or on a schedule. When you use this feature, you're telling us you already have a business relationship with that person (you did a job for them) and that you're allowed to text them about it. Every message carries your business name so the recipient knows who it's from, and every review-request message tells them how to opt out. If someone replies STOP to a review-request text, we add their number to a suppression list for your account and won't send them another one, checked automatically before every send. That opt-out record outlives your account if you delete it: we keep proof the STOP was honoured, stripped down to a hash of the number rather than the number itself, because an unsubscribe is meant to stay honoured, not disappear along with an unrelated account action. We keep a record of every message sent (who, when, which job, why we were allowed to contact them) so there's a paper trail if it's ever questioned. Invoice payment links are a different kind of message, you're following up on work you already did for that specific person, not asking them to do anything new, so they don't carry a STOP line, but they still carry your business name.

Asking your customers for a review

If you use the review-request feature, we text every customer whose job you mark complete the same message, asking them to leave a Google review, we never pick and choose based on how the job went, and we never will. That's Google's own rule (selectively asking only happy customers for reviews breaches their guidelines and risks your reviews being removed), and it's also required for genuine reviews under the Australian Consumer Law. Every message also offers a private way to tell you directly if something wasn't right, so a customer with a problem can reach you either way. We never offer a discount, rebate or any other incentive in exchange for a review, that's against Google's policy and against consumer law, and we've deliberately never built the option to.

Managing your Google Business Profile

If you connect your Google Business Profile, you're authorising us to post updates to it on your instruction, the same approve-then-publish flow as your other connected accounts. Google requires us to tell you within 48 hours of any automated change we make to your profile, and we do, you'll see it in the app. You can disconnect your profile at any time from Settings, which stops us posting to it.

Signing a quote electronically

When your client accepts and signs a quote through the link you send them, we capture what they drew as their signature, their typed name, the IP address and browser/device information their signature came from, the exact date and time, and a snapshot of the quote as it stood at that moment (the line items, prices and total they were agreeing to). This is what makes an electronic signature stand up if it's ever disputed, it's the same information the Electronic Transactions Act 1999 (Cth) and the Electronic Transactions (Queensland) Act 2001 require to treat an electronic signature as equivalent to a handwritten one. We keep this record for as long as the quote exists in your account.

Access and correction

You can view and edit your account details, content and business-suite records directly in the app at any time. If you can't find or fix something yourself, email us at hello@webgecko.au and we'll help, including providing a copy of the personal information we hold about you, or correcting it, within a reasonable time.

Data retention and deletion

We keep your account and content for as long as your account is active. You can delete your account at any time from Settings, this permanently deletes your account and the content, connections and business-suite records associated with it. The one exception: if a customer opted out of review-request texts (replied STOP), we keep proof that opt-out happened, a hash of their number, not the number itself, so it stays honoured, as the Spam Act requires. If you contact us to request deletion instead, we'll action it within a reasonable period, except where we're required to retain records by law.

Security

We restrict access to your data at the database level: every table is protected by row-level security policies so your data is only reachable by your own account, and plan/entitlement fields are enforced server-side rather than trusted from the app. Your session credentials are encrypted on your device rather than stored in plain text. No system is perfectly secure, and we don't claim otherwise, but we take reasonable, current precautions to protect your information and keep improving them.

Requests from police and government

Sometimes a law-enforcement body or government agency asks a business to hand over personal information. Here is exactly what we do. We only accept requests in writing, to hello@webgecko.au. Before we disclose anything we check that the request is a valid legal instrument, a warrant, subpoena or a notice under a law that actually applies to an Australian business, and that the authority making it has jurisdiction over us. An informal request with no legal instrument behind it is refused. If a request looks unlawful, overbroad or misdirected, we get legal advice and challenge it rather than complying quietly. When we do have to comply, we disclose only the specific records the instrument names, pulled as a targeted query, never a bulk export of your account because it is easier. We write down every request we receive and what we did about it: the date, the authority, the instrument, what was asked for, what we actually provided, and the reasoning. And we tell you your data was requested, unless the instrument legally prohibits us from telling you. No authority has standing or automated access to WorkPost: there is no agency login, no API key, no feed. As of the date of this policy we have never received such a request.

Complaints

If you're unhappy with how we've handled your personal information, email hello@webgecko.au with details and we'll investigate and respond. If you're not satisfied with our response, you can complain to the Office of the Australian Information Commissioner (OAIC) at oaic.gov.au.

Children

WorkPost is not intended for anyone under 16. We don't knowingly collect information from children. If you believe a child has provided us information, contact us and we'll remove it.

Changes to this policy

We may update this policy as the app evolves. We'll update the "last updated" date above, and where a change is material we'll let you know in the app before it takes effect. Continued use of the app after a change means you accept the updated policy.

Contact

Questions, access requests, correction or deletion requests, or complaints: email hello@webgecko.au.

Questions: hello@webgecko.au