Cassian

Privacy Policy

Last updated: 15 November 2026

1. About this policy

Cassian (“Cassian”, “we”, “us”) is an Australian business based in Sydney, New South Wales. We provide software for online stores and advertisers: ClickWall (click-fraud detection and blocking), RivalView (competitor price monitoring and pricing), FeedCore (Google Shopping feed monitoring and optimisation), TrueTag (server-side tracking), custom reporting dashboards, and Cassian AI.

This policy explains what personal information we collect, how we collect, use, store and disclose it, and how you can access or correct it or make a complaint. It applies to our website (cassian.com.au), our customer dashboard (dashboard.cassian.com.au), our free tools (such as the leak scan, calculator and savings report), our emails, and the tracking snippet our customers install on their own websites.

We handle personal information in line with the Privacy Act 1988 (Cth) and the Australian Privacy Principles (APPs), including the changes made by the Privacy and Other Legislation Amendment Act 2024 (Cth). We aim to meet that standard whether or not a particular exemption would apply to us.

Two roles.For information about our customers and the people who use our website and dashboard, we decide how the information is used. For information about visitors to a customer’s website, collected through our tracking snippet, we act as that customer’s service provider: the customer decides to install it and is responsible for telling its own visitors about it, and we use the information only to provide the service and as set out in this policy. If you are a visitor to one of our customers’ websites, you can still contact us (section 13) and we will help or pass your request to the customer.

2. Information we collect

From you, our customers and prospects

  • Identity and contact: name, email address, phone number, business name and role that you give us.
  • Account and billing: login details (passwords are never stored in readable form), subscription and invoice records, and your plan. Card payments are processed by Stripe; we do not see or store card numbers.
  • Communications: messages you send us through forms, email or support, and records of calls and meetings with us.
  • Technical: IP address, browser type and version, device type, pages viewed and activity in our dashboard and website, collected through logs and cookies (section 12).
  • Information from connected accounts that you authorise (sections 5 and 6), and product costs you give us or that we read from your store (such as Neto or BigCommerce cost price). We use cost information only to show your margin and profit after ad spend and to stop automatic price updates going below cost.

About visitors to our customers’ websites (ClickWall and TrueTag)

When a customer installs our tracking snippet, we receive each visitor’s IP address, browser user agent, referrer and landing page, ad click identifiers (such as Google’s gclid, wbraid and gbraid, or Meta’s fbclid), and coarse device signals such as screen size, time zone, language, touch support, the graphics card and system the browser reports, and whether the browser reports being run by automation software. From these the snippet makes a device fingerprint: a short code that lets the same device be recognised when it clicks the customer’s ads again, even after cookies are cleared. Only the code leaves the browser. We also record how long a visitor stayed on the landing page and a summary of how the page was used (counts of scrolls, taps, clicks and key presses, how far down the page they scrolled, and the shape and rhythm of mouse movement and typing), never what they typed.

We do not collect visitors’ names or email addresses through the tracking snippet. If a customer turns on Form Shield, we also check how a form was completed (timing and interaction counts) to tell people from bots, and we scan the message text and email address for spam signals (such as spam links and throwaway inboxes) at the moment it is sent. We do not store what visitors type into a customer’s forms.

IP addresses, device fingerprints and similar online identifiers can be personal information when they can reasonably be linked to a person, so we treat them as personal information.

From people who use our free tools

When anyone enters a website address into our leak scan, we read pages that website shows every visitor (its homepage, a few product pages, its public product list where the platform publishes one, and its public Google Tag Manager container). We keep the result with the website address and, if you give it, your email address, so we can follow up about the findings. We do not log in to, or collect personal information from, the website being scanned. Information you enter in the calculator is used to show your estimate. If you ask for a savings report, we use the details you give to prepare and send it.

Sensitive information

We do not knowingly collect sensitive information (such as health, racial or ethnic origin, political or religious beliefs, or biometric information) and ask you not to send it to us. Our device signals are technical and are not biometric information.

3. How we collect it

Directly from you (forms, email, calls, your dashboard); automatically through our website, dashboard and tracking snippet; from connected platforms you authorise us to access (Google, Meta, your store platform); and from publicly available sources, such as public pages on a website you ask us to scan, competitor product pages (for prices) and business directories or public business websites (to find businesses our products may help).

4. Why we use it

  • To detect and score fraudulent or automated clicks and form submissions, and to exclude fraudulent sources from your connected ad accounts.
  • To monitor competitor prices, feed health and tracking, and to produce the reports, briefings and dashboards you see.
  • To set up, run, secure, support and improve our services, including detecting abuse and fraud against us and our customers.
  • To send account, billing and security messages, and to respond to you.
  • To contact businesses about our products where the law allows (section 11), and to understand how our website and tools are used, for example from server logs.
  • To meet our legal obligations, resolve disputes and enforce our terms.

We use personal information for the purpose we collected it, for related purposes you would reasonably expect, with your consent, or where the law requires or authorises it.

5. Data we receive from Google (Google Ads and Google Merchant Center)

If you choose to connect a Google account, you sign in to Google yourself and approve specific permissions. We only request the permissions below, and only use them for the purposes below.

Google Ads(permission: https://www.googleapis.com/auth/adwords) — used by ClickWall and our Google Ads reporting.

  • What we access: your Google Ads customer ID and account name, the list of your campaigns and their status, campaign performance figures (such as impressions, clicks, cost and conversions), and Shopping results per product (clicks, cost, conversions and conversion value for each product your ads showed).
  • What we change: we add IP addresses we have identified as fraudulent to your Google Ads account’s IP exclusion list, so those addresses stop seeing and clicking your ads. Google limits that list to 500 addresses, so when it is full we remove the oldest address we added. We do not create or edit ads, budgets, bids, keywords or audiences, and we do not remove exclusions you set yourself.
  • Why: to show you how much fraudulent traffic was stopped and to protect your ad spend.

Google Merchant Center(permission: https://www.googleapis.com/auth/content) — used by FeedCore and RivalView.

  • What we access: your Merchant Center account ID and name, your product listings (titles, prices, availability, identifiers and product links) and the approval status and issues Google reports for each product.
  • What we change: only what you turn on, always through separate supplemental data sources we create in your account, never your main product feed. If you turn on automatic price updates in RivalView, we write the new price for a product through a source named “Cassian RivalView prices” (price only). If you turn on FeedCore Optimise, we write the improvements you switch on (such as product titles, descriptions, brand, identifiers, product category and type, custom labels, condition, and whether a product is kept out of Shopping ads) through a source named “Cassian FeedCore”. We do not delete products or change your store. Turn either off in the dashboard, or remove the supplemental source in Merchant Center, and Google goes back to your own data.
  • Why: to show you which products are disapproved or have problems and how to fix them, to compare your listed prices with competitors, and, if you enable them, to keep your Shopping prices in line with your website and improve how your products appear on Google Shopping.

Limited Use. Cassian’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In particular:

  • We use Google user data only to provide and improve the user-facing features described above, visible in your dashboard.
  • We do not sell Google user data and do not use it for advertising, retargeting or interest-based ads.
  • We do not allow people at Cassian to read your Google data, except where needed for security, to comply with law, or with your consent for support, and then only the minimum needed.
  • We do not use Google user data to develop, improve or train generalised artificial intelligence or machine-learning models.
  • We do not transfer Google user data to others except as described in section 7.

6. Data we receive from Meta (Facebook and Instagram advertising)

If you choose to connect Meta for ClickWall, you sign in to Meta yourself and approve specific permissions. We use them only to protect your Meta advertising from repeat fake clicks.

  • What we access: your ad account ID and name, your Meta pixel ID, and the list of your ad sets with their status and audience exclusions. We do not receive your Facebook or Instagram profile, friends or private messages, or the personal profiles of people who see your ads.
  • What we change: we create a custom audience in your ad account, built from a custom event (ClickWallBlocked) that our snippet sends through your own pixel when ClickWall stops a visit, and we add that audience as an exclusion on your ad sets so Meta stops showing your ads to those visitors. We do not create ads, change budgets, bids or creative, or remove exclusions you set yourself.
  • Why: to keep fake and repeat clicks from using up your Meta ad spend.

We use Meta platform data only as described in this policy and in line with the Meta Platform Terms and Business Tools Terms. We do not sell or license it, do not use it to build profiles of individuals or to make eligibility decisions about them, and do not share it except with the service providers in section 7 or where the law requires. You can disconnect Meta in your dashboard at any time, and you can ask us to delete the Meta data we hold at dashboard.cassian.com.au/data-deletion or by emailing privacy@cassian.com.au.

7. Who we share information with

We do not sell personal information. We share it only with service providers that process it for us under their own security and confidentiality commitments, with the platforms you connect, and with authorities where the law requires:

  • Hosting and infrastructure: Vercel, Render, Cloudflare and Supabase (application hosting, databases and bot protection).
  • Email: Resend (account, report and enquiry emails). Payments: Stripe.
  • Google and Meta, when we call their advertising and commerce APIs on your behalf as described above.
  • AI-written summaries: to write the plain-language briefings in your dashboard, we send summary figures from your own account (which can include figures derived from Google data, such as counts and totals) to an AI model provider (currently Anthropic) acting as our processor. Under its commercial terms the provider does not use that data to train its models, and we do not either.
  • ClickWall AI detection, where a customer turns it on: for each ad click, we send that visit’s details (device and browser signals, network provider and approximate location, how the page was used, and the same device’s other recent ad clicks) to the same AI provider to judge whether a real person made the click. For contact-form submissions our checks find suspicious, we also send the message, the name given and the email’s domain (not the full address) so the AI can tell a real enquiry from spam; the message is not stored. Full IP addresses and ad click identifiers are not sent, and the provider does not use this data to train its models.
  • Professional advisers (such as lawyers, accountants and insurers) and, if our business is sold or restructured, the buyer or successor, who must keep the information protected and use it for the same purposes.
  • Courts, regulators and law enforcement, where required or authorised by law.

We never show one customer’s data to another customer. To spot click farms and ad-fraud bots, ClickWall checks whether the same device fingerprint has clicked other ClickWall customers’ ads; only a count is used, and no customer can see which other businesses were involved.

8. Automated decisions

Some of our services use computer programs, including AI, to make or support decisions that can affect individuals, mainly people who visit or submit forms on a customer’s website.

  • Kinds of personal information used: IP address, device and browser signals, device fingerprint code, ad click identifiers, how the page was used, approximate location, network provider, and, for forms, the content and timing of a submission.
  • Decisions made by the program: scoring a click or form submission as likely genuine or fraudulent, adding the source to a customer’s ad-platform exclusion list, and stopping or flagging a spam form submission.
  • Decisions made with human involvement: customers can review flagged clicks in their dashboard, remove a source from an exclusion, and set their own rules. Our staff can review a decision on request.
  • Other uses of AI: AI also writes the briefings and answers questions in the customer dashboard. These are about a customer’s business figures and do not make decisions about individuals.

The main effect of these decisions is that a visit may stop seeing or clicking a customer’s ads, or a spam message may not be delivered. If you think a decision about you was wrong, contact us (section 13) or the website owner and we will look into it.

9. Overseas disclosure

We use providers whose systems may be located, or whose staff may access information from, countries outside Australia, mainly the United States and Singapore, and possibly other countries where those providers operate. This includes our hosting, email, payment and AI providers and, when you connect them, Google and Meta. Our primary database is hosted in Sydney. Before we disclose personal information overseas we take reasonable steps to make sure the recipient handles it in a way that is consistent with the APPs, usually through contracts and by choosing providers with strong security commitments.

10. Storage, security and retention

Connection credentials, including Google and Meta access tokens, are encrypted before they are stored, and access to customer data is restricted by role. We use reasonable technical and organisational measures to protect information from misuse, interference, loss and unauthorised access, but no system is completely secure.

Raw click-level data (IP addresses and device signals) is deleted automatically after 90 days. Summary figures and reports are kept while your account is active. Google and Meta access tokens are deleted when you disconnect them in the dashboard. Data we have already synced for your account (such as campaign performance figures) is deleted when you close your account, or sooner if you ask us to, unless we must keep it to meet legal, tax or accounting obligations (for example, invoices and payment records, which we keep for the period tax and corporate law require, generally 5 to 7 years) or to resolve a dispute. When we no longer need personal information we delete or de-identify it.

Data breaches. If we have reason to believe an eligible data breach has happened, we will assess it quickly and, where the notifiable data breaches scheme under the Privacy Act requires, notify affected individuals and the Office of the Australian Information Commissioner (OAIC). If a breach affects information we hold for a customer, we will tell that customer as soon as practicable.

11. Marketing and business contacts

We send marketing messages only where the law allows, in line with the Spam Act 2003(Cth): with your consent, or where consent can reasonably be inferred, including where a business email address is publicly published and our products are relevant to the recipient’s role. Every marketing message says who we are and includes a working unsubscribe option, and we act on unsubscribe requests within 5 business days. You can also unsubscribe by emailing privacy@cassian.com.au. We will still send essential account, billing and security messages.

12. Cookies and similar technologies

Our website and dashboard use essential cookies for sign-in and security, and Cloudflare Turnstile to tell people from bots on our forms and login. Our tracking snippet on a customer’s website sets a short-lived session identifier, a random visitor identifier kept in that website’s own browser storage (so repeated ad clicks from the same browser can be recognised; it is never shared across websites and contains nothing personal) and, if Form Shield is on, a signed token showing a form was checked. When ClickWall blocks a paid ad click, the snippet also sets a first-party marker (_cw_iv) on that website for 30 days. It holds no personal information and lets the website’s own tags leave that visit out of conversion reporting to ad platforms. The device fingerprint described in section 2 is worked out each visit and nothing is stored for it. You can block or clear cookies in your browser settings, but some features may then not work.

13. Your rights, questions and complaints

  • Access and correction. You can ask us for the personal information we hold about you and ask us to correct it. We aim to respond within 30 days. We may need to confirm your identity first, and in limited cases the law allows us to refuse or limit access; if we do, we will tell you why in writing.
  • Deletion. You can ask us to delete personal information we no longer need, or the Google or Meta data we hold for your account, by emailing privacy@cassian.com.au or using dashboard.cassian.com.au/data-deletion.
  • Disconnect platforms. You can disconnect Google or Meta at any time in your dashboard, and remove Cassian’s access at myaccount.google.com/permissions or in your Meta business settings.
  • Complaints. Tell us at privacy@cassian.com.au and we will acknowledge it promptly and aim to resolve it within 30 days. If you are not satisfied, you can complain to the Office of the Australian Information Commissioner (oaic.gov.au, 1300 363 992).

14. Children

Our services are for businesses and are not directed at people under 18. We do not knowingly collect personal information from children. If you think we have, contact us and we will delete it.

15. Other websites

Our website links to other websites, including Google, Meta and tools we recommend. We are not responsible for their privacy practices, so read their policies.

16. Changes to this policy

We may update this policy as our services or the law change. The date at the top shows when it was last updated. We will tell customers about significant changes, and we will get your consent first if we want to use Google or Meta data in a new way.

17. Contact us

Cassian, Sydney, New South Wales, Australia. Privacy questions, requests and complaints: privacy@cassian.com.au. General enquiries: sales@cassian.com.au.