Privacy Policy

Last Updated: 11 October 2026

1. Who We Are

Wahlu is operated by WAHLU LABS PTY LTD (ACN 696 304 140, ABN 99 696 304 140). For privacy questions, requests, or complaints, contact hello@wahlu.com.

Our business is based in New South Wales, Australia.

2. Scope of This Policy

This policy explains how we collect, use, store, disclose, and delete personal information when you use wahlu.com, the Wahlu application, connected social integrations, support channels, billing flows, and related services.

It applies to personal information we collect from account holders, workspace members, website visitors, leads, and people who contact us.

3. Data We Collect

Depending on how you use Wahlu, we may collect the following categories of data.

Account and profile data: name, email address, profile image, login method, workspace and team details, and account preferences.
Billing and payment data: plan, billing status, transaction records, invoice metadata, country, tax details where required, and limited payment metadata from our payment processor, currently Stripe. We do not store full card numbers.
Connected platform data: OAuth tokens, refresh tokens where applicable, account IDs, page or profile metadata, permissions, token expiry dates, and integration status for services such as Meta (Instagram, Facebook Pages and Threads), TikTok, LinkedIn, YouTube, X, Bluesky, Pinterest, Tumblr and Google services, and the chat and server details for Telegram and Discord.
Content data: drafts, captions, prompts, images, videos, brand assets, media library items, scheduled posts, publishing history, and workflow settings.
Usage and device data: IP address, browser type, device information, pages viewed, events, timestamps, referrers, cookies, and diagnostic logs.
Support and communications: emails, feedback, support messages, product requests, and other information you choose to send us.

4. How We Use Data

We use personal information to:

create and manage your account, workspaces, and subscriptions;
provide scheduling, publishing, and AI-powered content features;
connect and maintain third-party platform integrations;
process billing, credit allocation, renewals, and support issues;
send transactional notices, service updates, and account messages;
monitor performance, fix bugs, prevent abuse, and improve the service;
comply with legal obligations and resolve disputes; and
protect Wahlu, our users, and third parties from fraud, misuse, and security threats.

5. Legal Bases

For users in jurisdictions that require a legal basis for processing, we generally rely on one or more of the following:

Contract: where we need the data to provide the service you asked for.
Legitimate interests: where we need the data to run, secure, analyse, and improve Wahlu in a way that is reasonable and proportionate.
Consent: where you choose to connect integrations, accept certain cookies, or otherwise authorise a specific use.
Legal obligations: where we need the data for tax, accounting, fraud prevention, law enforcement requests, or other legal duties.

In Australia, we also handle personal information in line with applicable privacy laws and reasonable expectations for a SaaS business.

6. Sharing and Disclosure

We may share personal information with:

Service providers and subprocessors that help us run Wahlu, such as hosting, analytics, email delivery, authentication, customer support, storage, and payment processing providers.
Meta, to measure our own advertising, as described in section 14.
Connected platforms when you ask us to publish, sync, or retrieve data through an integration.
Professional advisers such as lawyers, accountants, insurers, or auditors where reasonably necessary.
Authorities or regulators where required by law, court order, or to protect rights, safety, or the service.
A buyer, investor, or successor in a merger, acquisition, restructure, financing, or asset sale.

We do not sell personal data.

7. Third-Party Integrations

Wahlu lets you connect third-party services including Instagram, Facebook Pages, Threads, TikTok, LinkedIn, YouTube, X, Bluesky, Pinterest, Telegram, Discord, Tumblr and Google services where supported. When you connect an integration:

we receive the tokens, account identifiers, scopes, and related metadata needed to operate that integration;
we use that access only to provide the features you requested, such as scheduling, publishing, refreshing tokens, or reading limited business metadata where relevant; and
your use of those platforms remains subject to their own terms, privacy policies, and platform rules.

Meta platforms (Instagram, Facebook and Threads):

Account details: we store the connected account's ID, username or Page name, profile picture and the permissions you granted, to show which account is connected and to publish to it.
Publishing: we send the posts, replies and thread parts you write or schedule in Wahlu to the account you chose, and keep the published post's ID and link so you can see it in your history. On Threads, Wahlu only publishes replies to your own posts (the extra parts of a thread and an optional follow-up reply); it doesn't read, hide or reply to other people's replies.
Insights: when you open Insights, we read the account's follower count, reach and views over the last 28 days, and the views, likes, comments, shares, saves, reactions, replies, reposts and quotes of posts you published from Wahlu. We show these numbers to you and don't store them.
Removing access: you can disconnect an account in Wahlu, or remove Wahlu in your Instagram, Facebook or Threads settings, at any time. We then delete its stored access token. See Data Deletion for how to ask us to delete the rest.

We use data from Meta platforms only to provide the features you use in Wahlu. We don't sell it, use it for advertising, or use it to train AI models.

What we access: when you connect a Pinterest business account, we read its profile: username, business name, profile picture, account type and follower count. When you make a Pin, we read your boards and board sections so you can choose one. On Insights, we read your 10 latest Pins (title, picture, board and link) and the analytics for your account and those Pins over the last 30 days: impressions, saves, Pin clicks, outbound clicks, engagement rate, save rate and video views.
Permissions and why: user_accounts:read for your profile and account analytics; boards:read to list your boards and show which board a Pin is on; pins:read to list your latest Pins and their analytics; pins:write and boards:write to create the Pin you made on the board you chose, because Pinterest requires both to create a Pin. Wahlu doesn't create, edit or delete boards, and doesn't edit or delete Pins.
Publishing: Wahlu creates only the Pins you make and choose to post or schedule. It never posts to Pinterest on its own: repeating queues and Autopilot can't post to Pinterest.
What we store: your access and refresh tokens, encrypted; the account's ID, username, business name, profile picture, account type and the permissions you granted; for each Pin you make in Wahlu, the board you chose (its ID and name), the title, description, link, alt text and media, and the published Pin's ID and link. From Insights we store numbers only: your follower count and account analytics, and the analytics of your 10 latest Pins. Pin titles, pictures and board lists are read from Pinterest each time and never stored.
How long: tokens and profile details while the account is connected. Stored Insights numbers cover only your 10 latest Pins; numbers for a Pin that drops out of that list are deleted at the next refresh. Wahlu reads new numbers only when you first open Insights for an account or press Refresh, at most once every 15 minutes per account and once every 5 minutes per post. Everything is deleted when you disconnect the account or delete the brand, workspace or your Wahlu account.

X (formerly Twitter)

What we access: your X profile (user ID, username, name, profile picture and follower count), and the posts you write in Wahlu, which we publish. On Insights (paid plans), we read your 10 latest original posts, from Wahlu or anywhere else, with their text, links, pictures and numbers: impressions, likes, replies, reposts, quotes, bookmarks, link clicks, profile clicks and video views.
Permissions and why: tweet.write to publish your posts; media.write to upload the images and videos you attach; tweet.read to read your posts and their numbers for Insights; users.read for your profile and follower count; and offline.access so Wahlu stays connected without you signing in again.
What we store: your access and refresh tokens, encrypted; your profile details and the permissions you granted; the ID and link of each post published through Wahlu. From Insights we store your follower count and, for your 10 latest posts and any post published through Wahlu in the last 30 days, the post's text, date, link, links in it, the addresses of its pictures and its numbers. Pictures load from X in your browser; we keep no copy.
How long: tokens and profile details while the account is connected. Older stored posts are removed whenever Insights is refreshed or Wahlu publishes a post. Wahlu reads new numbers only when you first open Insights for an account or press Refresh, at most once every 15 minutes per account and once every 5 minutes per post. Everything is deleted when you disconnect the account or delete the brand, workspace or your Wahlu account.

Bluesky

What we access: you approve Wahlu on your own Bluesky server, so we never see your password. We read your account's ID (DID), handle, display name, profile picture and server address, and publish the posts you write in Wahlu. For a link card, Wahlu reads the linked page's title, description and picture. On Insights (paid plans), we read public data from Bluesky's public API: your follower count and your 10 latest posts with their text, links, pictures, likes, reposts, replies, quotes and bookmarks. Bluesky has no impressions or clicks, so we show none.
Permissions and why: atproto and transition:generic. This is the permission set Bluesky servers offer today for posting. It covers more than posting, but Wahlu uses it only to publish your posts, upload the images and videos you attach and check Bluesky's video upload limits.
What we store: your access and refresh tokens and a security key made for this connection, encrypted; your profile details and the permissions you granted; the ID and link of each post published through Wahlu. From Insights we store the same as for X: your follower count and, for your 10 latest posts and any post published through Wahlu in the last 30 days, the text, date, link, links, picture addresses and numbers. Pictures load from Bluesky in your browser; we keep no copy.
How long: as for X. Older stored posts are removed whenever Insights is refreshed or Wahlu publishes a post. Wahlu reads new numbers only when you first open Insights for an account or press Refresh, at most once every 15 minutes per account and once every 5 minutes per post. Everything is deleted when you disconnect the account or delete the brand, workspace or your Wahlu account.

For Pinterest, X and Bluesky:

Who sees it: the people in your Wahlu workspace. We don't share this data with anyone else. It goes only to the platform's own API when Wahlu acts for you, and it is held by the hosting providers described under Sharing and Disclosure. We don't sell it, use it for advertising, combine it with other people's accounts or use it to train AI models.
Disconnecting: in Wahlu, open your brand's settings, go to Accounts and select Disconnect. For X and Bluesky we first revoke Wahlu's access at the platform. For all three we then delete the stored tokens, profile details and stored Insights straight away. Pinterest doesn't let apps revoke a person's access, so also remove Wahlu in Pinterest. See Data Deletion for the steps on each platform.
Deleting everything: you can delete your Wahlu account yourself. We disconnect your accounts and delete your data as the Data Deletion page explains. For any other request about this data, email hello@wahlu.com.
Platform rules: Wahlu uses this data in line with the Pinterest Developer Guidelines, the X Developer Agreement and Policy and the Bluesky Developer Guidelines. Your use of each platform is also covered by its own terms and privacy policy.

How it works: Wahlu posts to your channel or group as its own bot, @wahlu_bot. You add the bot as an administrator that can post messages. There is no sign-in and no password, and the bot's token is Wahlu's own, not yours.
What we access: when you start the bot to connect, Telegram tells us your Telegram user ID. We ask Telegram about the chat you choose: its ID, type, title and @username, and whether you and the bot are administrators there. We publish the posts you write in Wahlu. We don't read or store the messages in your chats.
What we store: the chat's ID, type, title and @username, the bot's permissions there, and the Telegram user ID of the person who connected it; for each post published through Wahlu, the message ID and link. A connect request holds your Telegram user ID for up to 15 minutes, then it is deleted.
How long: while the chat is connected. When you disconnect it in Wahlu, we delete these details and the bot leaves the chat, unless another Wahlu connection still uses it. You can also remove @wahlu_bot from the chat in Telegram at any time.

Discord

How it works: you add Wahlu's bot to a Discord server you manage, and choose the channel it posts in. The bot posts with Wahlu's own token. The sign-in token Discord gives us for you is used once to read your user ID, then revoked; we never store it.
Permissions and why: bot to add the bot, with View Channels, Send Messages, Embed Links and Attach Files so it can post your messages, link previews and files; identify to read your Discord user ID and check that you can manage the server.
What we store: the server's ID, name, icon and invite link if it has a custom one; the chosen channel's ID, name and type; the bot's permissions; the Discord user ID of the person who added it; for each post published through Wahlu, the message ID and link. We don't read or store the messages in your server.
How long: while the server is connected. When you disconnect it in Wahlu, we delete these details and the bot leaves the server, unless another Wahlu connection still uses it. You can also remove the bot in Discord under Server Settings, Integrations.

Tumblr

What we access: you sign in on Tumblr and allow Wahlu. We read the blogs you can post to (each blog's ID, name, title, address and avatar) so you can choose one, and publish the posts you make in Wahlu to it. We don't read your other posts, your dashboard or your messages.
Permissions and why: write to publish your posts and upload the images and videos you attach; offline_access so Wahlu stays connected without you signing in again.
Publishing: Wahlu posts to Tumblr only when you post or schedule a post yourself. Looping queues and Autopilot never post to Tumblr.
What we store: your access and refresh tokens, encrypted; the blog's ID, name, title, address and avatar, and the permissions you granted; for each post you make in Wahlu, its title, text, link, tags, alt text and media, and the published post's ID and link.
How long: while the blog is connected. When you disconnect it in Wahlu, or delete the brand, workspace or your Wahlu account, we delete the tokens and blog details. Tumblr doesn't let apps give up their access, so also remove Wahlu in your Tumblr settings under Apps.

For Telegram, Discord and Tumblr:

Who sees it: the people in your Wahlu workspace. It goes only to Telegram, Discord or Tumblr when Wahlu posts for you. We don't sell it, use it for advertising or use it to train AI models.
Deleting a brand, workspace or account: we delete these details, but Wahlu's Telegram or Discord bot stays in your chat or server until you remove it there. See Data Deletion.
Platform rules: Wahlu follows the Telegram Bot Platform terms, the Discord Developer Policy and the Tumblr Application Developer and API License Agreement. Your use of each platform is also covered by its own terms and privacy policy.

LinkedIn company pages

What we access: when you connect a LinkedIn company page, we read the pages you are an administrator of, with each page's ID, name, public URL name and logo, so you can choose one. We don't store your own LinkedIn member ID or profile.
Permissions and why: w_organization_social to publish the posts, images and videos you make as the page; rw_organization_admin to list the pages you administer and read their name and logo; r_organization_social to read the page's own posts, so Wahlu can check whether a post went out when LinkedIn's reply was unclear. Wahlu doesn't change page details, manage roles, or edit or delete posts.
What we store: your access token, encrypted; the page's ID, name, public URL name and a copy of its logo; for each post you make in Wahlu, its text and media, and the published post's ID.
How long and removing access: the token and page details while the page is connected; LinkedIn tokens expire after 60 days. LinkedIn doesn't let apps revoke access, so when you disconnect the page in Wahlu we delete them, and you can also remove Wahlu in your LinkedIn settings. See Data Deletion. Wahlu uses this data in line with the LinkedIn API Terms of Use.

Google Business Profile

What we access: when you connect Google Business Profile, we read the list of business accounts and locations you manage, with each location's name, so you can choose one. We don't read your reviews, address, opening hours or insights.
Permission and why: business.manage, the permission Google requires for Business Profile, to list your locations and publish the posts you choose to the location you picked. Wahlu doesn't change your business details, reply to reviews or delete posts.
Publishing: Wahlu publishes only the updates, events and offers you make and choose to post or schedule, one at a time. Repeating queues and Autopilot can't post to Google Business Profile.
What we store: your access and refresh tokens, encrypted; the location's name and its Google account and location IDs; for each post you make in Wahlu, its text, post type, button and link, event title and dates, offer code, link and terms, and media, plus the published post's ID and link.
How long and removing access: tokens and location details while the location is connected. When you disconnect it in Wahlu, we revoke Wahlu's access at Google first, then delete them. You can also remove Wahlu from your Google Account. See Data Deletion. Section 8 explains how we follow Google's Limited Use rules.

8. Google API Services User Data and Limited Use

Wahlu uses Google API Services for supported Google features. Our use of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

We only use Google user data to provide or improve user-facing features you actively use inside Wahlu.
We do not sell Google user data.
We do not use Google user data for advertising, retargeting, or data-broker style profiling.
We do not use Google user data to train general-purpose or cross-customer AI or machine learning models.
We do not let humans read Google user data except where necessary for support you asked for, security work, legal compliance, or other limited situations permitted by Google's policies and applicable law.
We do not transfer Google user data to third parties except where needed to provide the user-facing feature you requested, for security purposes, to comply with law, or as part of a permitted business transfer.

9. Instagram Comment and Message Automations

Wahlu Automations lets a business that has connected its own Instagram professional account reply automatically to comments with chosen words, direct messages, story replies and story mentions shared by Instagram. This section covers the extra Instagram data the feature handles, both for the business using Wahlu and for people who comment on or message that business.

What we receive and store.

From the connected business: its Instagram account IDs, username, the permissions it granted, and an access token, which we encrypt.
Comments: for the connected account only, through Meta's webhooks, comments on the business's own posts and reels, including the comment text, the comment and post IDs, and the commenter's Instagram-scoped ID.
Messages: direct messages, story replies, story mentions and button taps sent to the connected account, including the message text or button data and the sender's Instagram-scoped ID. For recent automation conversations, we also keep encrypted copies of replies sent by Wahlu and outgoing replies reported by Instagram.
Automation records: for each person an automation responds to, the step it reached, when they last replied, whether each reply and message was delivered and, if the business adds a follow check, whether that person follows the business's account.
Emails shared in a DM: if the business turns on the step that asks for an email, the email address the person replies with, their Instagram-scoped ID and username, which automation asked, when they replied and the wording of the request they answered.
Reply choices: whether a person stopped or restarted automated DMs, the time they chose, and when a default reply can next be sent.
AI replies: the customer-facing facts, reference links and tone the business saves. We keep encrypted questions and generated answers, request IDs and credit status.
The automations themselves: the keywords, chosen posts, reply and message text, and links the business writes.

Apart from the username stored with an email someone chose to share, we don't store commenters' or senders' usernames, names or profile pictures, and we don't receive comments or messages for Instagram accounts that aren't connected to Wahlu.

How we use it. Only to run the business's automation: to check whether a comment or message matches the business's keywords, post its public reply, send its private reply and follow-up messages within the time Instagram allows, avoid sending the same message twice, and show the business its automation's activity. An unmatched DM can receive the business’s default reply, at most once per person every 24 hours. We do not store story photos or videos. We don't use this data for advertising, sell it, build profiles from it or use it to train AI models.

AI processing. When the business enables AI replies or runs a test, we send its saved knowledge, tone and that question to Google Gemini to draft an answer. We do not send the whole conversation history or private brand notes. A saved link is sent as text; Wahlu does not fetch its page. Answers begin with an AI disclosure. When a person is needed, automatic replies pause. AI can make mistakes.

Who decides. The business chooses what its automation says and does. For people who comment on or message the business, Wahlu handles this data on the business's behalf.

Emails collected for a business. When an automation asks for an email, the request says how the business will use it (by default, to send what was asked for and occasional updates). Nobody has to share an email: people can reply “skip” or ignore the request. We check that the reply looks like an email address, store it for that business only, and show it to the business in Wahlu, where it can search, export and delete the emails it has collected. The business decides how it uses them and is responsible for doing so lawfully, including honouring unsubscribe requests. We don't email these addresses ourselves, share them with other businesses, sell them or use them for advertising.

How long we keep it.

Comment and message content is encrypted before we store it.
Webhook events as received from Meta are deleted automatically 14 days after they arrive.
Automation run records, which hold the encrypted comment or message that started or continued a conversation, the person's Instagram-scoped ID and delivery status, are deleted automatically 30 days after the run starts.
Saved conversation messages are deleted 30 days after each message. The contacts list is built from retained runs and does not create a separate permanent contact profile.
Encrypted AI questions and answers are deleted after 30 days. Daily AI budget records expire after 32 days. Saved brand knowledge and tone stay until replaced or the brand or workspace is deleted. Credit records are handled separately from message history.
Automations are kept until the business deletes them, deletes its brand or workspace, or asks us to delete its Instagram data.
Stop and restart choices, human reply pauses and default-reply cooldowns are kept until the business’s brand, workspace or Instagram automation data is deleted. They do not expire with run history.
Collected emails are kept until the business deletes them, deletes its brand or workspace, or asks us to delete its Instagram data. They don't expire on their own.
When a business disconnects Instagram in Wahlu, or removes Wahlu in Instagram, we delete its stored access token, so its automations can no longer send anything.

Deleting this data. A business can remove Wahlu from its Instagram account and ask for its data to be deleted, or email hello@wahlu.com. We then delete the Instagram connection, that account's automations, their run records and saved messages, the emails collected through them, its AI question, answer and daily budget records, and its webhook events. If you commented on or messaged a business that uses Wahlu, you can ask that business, or email us with your Instagram username and the business's account, and we'll delete the records we can match to you, including an email you shared. Whatever you choose, run records are deleted automatically 30 days after the run starts; a shared email stays until the business deletes it or you ask us to. See Data Deletion for step-by-step instructions.

10. Data Retention

We keep data for as long as reasonably necessary for the purposes described above.

Account and workspace data: while your account is active, and usually up to 24 months after closure if needed for legitimate business records, dispute handling, fraud prevention, or reactivation requests.
Billing, payment, and tax records: usually 7 years where we need them for accounting, tax, and compliance.
Connected platform tokens and credentials: while the integration is active and for a limited period afterwards to support disconnects, troubleshooting, security, and lawful record-keeping.
Content, scheduled posts, and media: while your account remains active, and then for a limited cleanup period after cancellation or deletion unless legal retention is required.
Security and diagnostic logs: usually 30 to 180 days, unless a longer period is reasonably required for abuse prevention or investigation.
Backups: rolling backups may persist for a limited period after deletion before they are overwritten.
Stored X, Bluesky and Pinterest insights: only for recent posts, and deleted when you disconnect the account, as section 7 explains.
After you delete your account: we keep your answers to the short exit survey and anonymous usage facts: your plan, the number of days since you signed up, counts of brands, connected platforms by type and posts scheduled and published, which features you used, and whether you started a trial. These are stored without your name, email, handle, content or any account identifier, so they can't be linked back to you. We also keep a record that the deletion happened, and security records showing that access was revoked, until they expire.

After cancellation, your subscription stops renewing, but your account and stored data are not automatically deleted. If you want deletion, you need to request it separately.

11. Security Measures

We use reasonable technical and organisational measures designed to protect personal information. These may include access controls, secret management, encrypted transport, logging, monitoring, and credential protection.

Where Wahlu stores OAuth credentials for connected platforms, we store those credentials in encrypted form before writing them to persistent storage. No internet service can be completely secure, so we cannot guarantee absolute security.

12. International Transfers

Wahlu and its service providers may process data in Australia and other countries where our infrastructure, vendors, or subprocessors operate. By using the service, you understand that your information may be transferred to and processed outside your home jurisdiction, subject to reasonable safeguards and contractual controls where appropriate.

13. Your Rights and Deletion Requests

Depending on where you live, you may have rights to access, correct, delete, restrict, object to, or export certain personal information.

To make a request, email hello@wahlu.com.

We may need to verify your identity before completing the request.
We aim to respond within 30 days, although complex requests may take longer where the law allows.
For account deletion requests, we generally aim to disable account access promptly and complete operational deletion within 30 days, subject to backups, fraud prevention, legal retention, and billing records that we need to keep.
If you simply cancel your subscription, we may retain your account until you separately request deletion.

14. Cookies and Analytics

Wahlu uses cookies and similar technologies to keep you signed in, remember preferences, measure traffic, understand usage patterns, and improve the service. Some cookies are necessary for core functionality, while others support analytics or product performance.

On wahlu.com we use the Meta Pixel to measure our advertising. When you sign up, start a trial, subscribe, buy a plan or join our newsletter, our servers also tell Meta about it (Meta's Conversions API), so we can see which ads work. We send a hashed (scrambled) copy of your email address and Wahlu account ID, Meta's own cookie IDs, your IP address and browser type, and, for payments, the amount. We never send your name, what you create in Wahlu or data from your connected social accounts.

You can control cookies through your browser settings, but disabling some cookies may affect how the site works.

15. Children's Privacy

Wahlu is not directed to children under 18, and we do not knowingly collect personal information from children. If you believe a child has provided us with personal information, contact us and we will investigate and take appropriate action.

16. Changes to This Policy

We may update this Privacy Policy from time to time. If we make a material change, we may update the date above, post a notice in the product or on the site, or contact users where appropriate.

17. Contact and Complaints

For privacy questions, complaints, or requests, contact hello@wahlu.com.

If you are in Australia and think we have not handled your privacy complaint properly, you can also contact the Office of the Australian Information Commissioner or another relevant regulator in your jurisdiction.