CreatorSense Privacy Policy.

1. Who we are and what this covers

CreatorSense makes Trace, a forensic watermarking service for paid creator content. In this policy "CreatorSense", "we" and "us" means CreatorSense, a business name of Matt Orchard (sole trader), ABN 65 815 285 275, Sydney NSW, Australia. You can reach us at info@creatorsenseai.com.

This policy covers:

• this website (www.creatorsenseai.com) and the free leak scan;
• the CreatorSense app at /app, including Trace, Vault links, wall drops, live early access, the public Trace API and webhooks;
• the affiliate program and Refer a creator;
• the CreatorSense MCP connector for Claude and other AI tools (Part C);
• the CreatorSense Chrome extensions (Part D).

It covers two groups of people: creators, agencies and their team members who use CreatorSense (Part A), and the fans and buyers whose details creators add to Trace (Part B).

We follow the Australian Privacy Act 1988 and the Australian Privacy Principles (APPs). If you are in the European Economic Area or the United Kingdom, section 14 also applies. If you live in California or another US state with a privacy law, section 15 also applies.

2. Our two roles

We handle personal information in two different capacities, and it matters which one applies.

• For your own account (your login, billing, support emails, referral payouts, how you use the site and app) we decide how the information is used. Under the GDPR we are the controller.
• For the fan details and content a creator puts into Trace, the creator (or the agency acting for the creator) decides which fans to add, what to send them and what to do with a result. We hold and process that information on the creator's behalf and only to provide Trace. Under the GDPR the creator is the controller and we are the processor. Our Data Processing Addendum sets out the terms.

If you are a fan and want to ask about your details, the creator is usually the right first contact. You can also email us and we will pass the request on and help the creator answer it (see section 12).

3. Part A: information we collect about creators, agencies and visitors

Account. Your name or display name, email address and password (stored only as a one-way hash). If you sign in with Google, the name, email and Google account id Google gives us. Two-factor and passkey settings. For agencies: team members' logins, their roles (owner, manager, chatter) and an audit log of team actions.

Billing. Your plan, invoices, billing country and address, and the card brand and last four digits that Stripe shows us. Stripe holds the full card details; we never see or store them.

Content. The originals you upload (video, images, audio), the marked copies Trace makes, leaked copies you submit for a check, the web addresses where you found them, your cases and your evidence packs. Your content may show you or other people. You must have the right to upload it (see the Acceptable Use Policy).

Integrations. If you turn on mark-on-unlock with OnlyFansAPI or Fanvue, we store the API key or access tokens you give us, encrypted, and receive the purchase and unlock events those services send. Those events include the buyer's handle or account id and the item they unlocked.

API. Your API keys (we store only a hash of each key), their scopes and request logs.

Device and usage. IP address, browser and device type, pages and features used, timestamps, and error reports.

Trace Vault activity (when you use Vault links). For each unlock link we may log: the buyer's IP address; coarse device and browser details (including a first-party device token, not a raw fingerprint dump); whether the unlock link was opened; viewing activity events such as viewed, closed, and a soft "tab hidden / possible screenshot" signal (this is not screenshot-proofing); and a simple risk score used to spot abuse. The creator who sent the link and the buyer who opened it can each see the activity that relates to that link in the product. CreatorSense admins may also review these logs when investigating abuse, security incidents or support requests.

Leak Radar (optional, creator opt-in). If a creator turns on Leak Radar for their opted-in content, we may run reverse-image (and similar visual) searches against that content to find copies posted elsewhere. Hits can include the page address, a saved copy of the page or a WARC capture where we can take one, and the time we found it. Creators choose what to submit; we do not opt anyone in by default.

Evidence packs. When a creator exports a case we assemble an evidence pack that can include hashes, delivery and match records, saved leak pages or WARC captures, and a third-party timestamp. When configured, timestamps use an RFC 3161 timestamp authority (including freetsa.org). The authority receives a hash of the record only, never the content, names or handles. Packs are for the creator to download and share; we do not file takedowns for them.

Admin security logging. Security-related admin actions (for example plan changes, bans, and access to sensitive Trace tools) are written to internal audit logs with the admin account, time and action. Those logs are kept for up to 90 days unless a longer hold is needed for an incident.

Messages. What you send us by email.

Affiliate program. Your affiliate code, click and sign-up counts, the accounts credited to you, commission records, and the PayPal or Wise email you give us for payouts. See the Affiliate Program Terms.

Refer a creator. Your invite code; if you signed up with someone's invite, who invited you; the accounts that signed up with your invite; and the month credits added to your Stripe balance. When someone opens your invite link, the sign-up page shows them your first name. See the Refer a creator terms.

Website. Your cookie choice; analytics data if you accept analytics cookies; the referral or invite code from a link you followed; and campaign tags (utm values and the referring website's host name, never full addresses). The last two are kept in your browser for 60 days and sent to us when you sign up. See the Cookie Policy.

Free leak scan. The creator name or handle you search (used to run the scan, not stored) and, if you ask us to email the result, your email address and whether you opted in to a weekly check.

Older tools. The MCP connector and Chrome extensions handle some extra data, described in Part C and Part D.

4. How we use it

We use the information above to:

• create and run your account, and let agency team members work together;
• mark, store and deliver your content, run leak traces, keep cases and produce evidence packs;
• bill you, apply the "Right account, or your money back" guarantee and pay referral commission;
• send service email: receipts, trial and renewal notices, usage alerts, security notices and replies to you;
• keep the service secure, stop fraud and abuse, and fix errors;
• understand which pages and features are used, so we can improve them;
• meet legal, tax and accounting duties, and respond to lawful requests.

We do not sell personal information. We do not share it for advertising, and we do not build advertising profiles. We do not use your content or your fans' details to train AI models.

We only send marketing email if you asked for it (for example the weekly leak scan), and every such email has an unsubscribe link.

5. Who we share it with

• Service providers who run parts of CreatorSense for us: hosting, storage, payments, email, error monitoring and analytics. They are listed, with what they do and where, on the Subprocessors page. They may only use the information to provide their service to us.
• Payout providers. When we pay referral commission, PayPal or Wise receives the email you gave us and the amount.
• Your own team. On an agency account, team members see what their role allows.
• People you choose to share with. Evidence packs and exports go where you send them. We do not send them to takedown providers or anyone else for you, with one exception: when you authorise it for a case, we email the platform you choose (such as OnlyFans, Fansly or LoyalFans) an account notice and your evidence brief. That notice includes your name, the username you give us, the account it reports, where the leaked copy was found and the brief's contents. You are copied in, and we keep a record of each send (case, platform, address, account, time and the brief's fingerprint).
• Integrations you connect. If you connect OnlyFansAPI or Fanvue, we call those services with your key to do what you asked.
• Legal reasons. If the law requires it, or to protect people from serious harm, we may disclose information to police, courts or regulators. Where we can, we tell you first.
• A change of ownership. If CreatorSense is sold or merged, information may pass to the new owner, who must keep to this policy or tell you before changing it.

6. Evidence timestamps and the public ledger

Some Trace records can be timestamped so that you can later show a record existed at a certain time.

• Timestamp authority. When configured, Trace sends a hash (a fingerprint) of an evidence record to an RFC 3161 timestamp authority (we use freetsa.org when that integration is on), which signs the time. The authority receives the hash only, never content, names or handles. The authority used is named inside each evidence pack.
• Arweave. When the Arweave feature is switched on, Trace writes a hash of an evidence record to Arweave, a public, permanent ledger. What is written is the hash, a short hash prefix, internal reference ids (a CreatorSense account id, a record id and the id of the file or link the record is about), the event type and a time. No content, fan handles, names, emails or IP addresses are written. Anyone can read Arweave, and nothing written there can be deleted, including by us.

7. Where information is stored and sent

CreatorSense is based in Australia, but our main hosting is in the United States. Our service providers process information in the United States and, for Cloudflare's network, in data centres around the world. Stripe may also process data in Ireland. The Subprocessors page lists locations.

Before sending personal information overseas we take reasonable steps, as APP 8 requires, so that it is handled in a way consistent with the APPs: we use providers with published security and privacy commitments and contract terms that limit their use of the data. For transfers out of the EEA and UK, see section 14.

8. Part B: information about fans and buyers

This part is for people whose details a creator or agency has added to Trace, usually because they bought or subscribed to that creator's paid content.

What Trace holds about you.

• the handle or username the creator entered, and optionally a nickname;
• the platform (for example the subscription site the creator sells on);
• any notes the creator added, and labels such as a tier or a "don't send" flag with the creator's reason;
• a mark number: a code Trace assigns to you for that creator;
• delivery records: which marked copy was made for you, when, and a delivery id;
• if the creator sent you a Vault link: the IP address, coarse device and browser details, unlock and viewing activity (viewed, closed, and a soft tab-hidden / possible-screenshot signal), and a risk score for that session, kept for 90 days; you and the creator can each see the activity for that link;
• if the creator uses mark-on-unlock: the purchase or unlock event the platform integration sent, with your handle or account id;
• if a copy of the creator's content is found online and checked: the result of that check and the case record.

Where it comes from. The creator (typed in, imported from a file, or sent by an integration the creator connected with their own key), and your device when you open a Vault link.

Why. So each buyer receives a copy carrying their own invisible mark, and so the creator can later check which delivered copy a leaked copy matches.

What a match means. A match shows which account a leaked copy was delivered to. It does not prove who shared it: an account can be shared, a device can be compromised, or someone else can copy a file. A result with no match is inconclusive. It is not evidence that anyone did or did not share a file. We tell creators this in the app and in every evidence pack.

What we do not do. We do not contact fans, publish fan details, sell them, or pool them across creators: each creator's fan list is kept separate. The mark inside a file carries a code, not your name.

Your choices. The creator controls these records. Ask the creator to see, correct or delete them. You can also email us at the address in section 18; we will pass your request to the creator and help them respond. If the creator has closed their account, we will deal with the request ourselves.

9. Part C: the CreatorSense MCP connector

This part covers the MCP server at https://www.creatorsenseai.com/mcp, which lets an AI tool you authorise (for example Claude) query your own CreatorSense account. It replaces the separate MCP privacy policy dated 9 August 2026; its commitments are unchanged.

What MCP can access. Data already in your CreatorSense account, depending on your MCP plan: on Free, your entitlement, connected platforms and sync health, profile summary, Creator DNA, revenue summaries (net of platform fees) and Trace case status; on Pro, also assembled briefings, tax set-aside estimates, audience demographics, content performance, YouTube and live social analytics, forecasts, workload and wellness signals, opportunities and schedule tools. No extra platform credentials are collected for MCP.

What MCP cannot access. Your platform passwords, OAuth tokens or other login secrets; private messages on connected platforms; payment card or bank details; audience members' personal data beyond aggregated segments; other users' accounts.

Read-only, with one exception. MCP tools do not post, delete or change anything on your social accounts. Trace tools can open a case for a leak address you submit and prepare a takedown notice for you to send yourself.

Authentication. Connecting uses OAuth against your CreatorSense account. Tokens travel over TLS. Revoke access in the AI tool's settings or your account controls at any time.

Minimisation. Tools return the data needed for the request and nothing beyond your entitled account.

What we log. For each MCP request: the time, a token or session identifier (not the secret), the tool name, the response status and time taken, and your plan. We do not log the prompt you typed into the AI tool or the full response, as a matter of default practice. These logs are kept for 90 days, then deleted.

The AI tool's own policy. The provider of the AI tool you connect (for example Anthropic for Claude) handles your conversation and the data it receives under its own privacy policy. Read it before connecting.

10. Part D: the CreatorSense Chrome extensions

Each extension has a single purpose, loads no remote code, and does not sell or transfer user data except to provide that purpose. None is used for advertising, credit or lending decisions.

CreatorSense Trace extension

Lets you sign in, add Trace account labels by typing them, upload a file you choose for marking, and save the marked file with the browser's downloads feature. It stores your CreatorSense session (sign-in token and basic account display fields) in the extension's local storage. It sends only the files you select and the labels you type, to the CreatorSense Trace API over HTTPS. It does not read or automate any website, store other sites' passwords, send messages, crawl in the background or read your browsing history. Its host access is limited to CreatorSense's own app and API addresses.

CreatorSense Data Sync

Reads your own analytics from supported creator dashboards you are signed in to (for example Beehiiv, Substack, Amazon Associates, LTK, Depop, Kajabi, Teachable, YouTube Studio, TikTok Studio, X Analytics and Meta Business Suite) and sends them to your CreatorSense account over HTTPS. Typical fields: your account or channel name and id, aggregate performance figures (followers, views, opens, clicks, sales) and aggregate earnings where the dashboard shows them to you. It does not collect direct messages, subscribers' email addresses, payment details or your platform passwords. It stores your sync session, the platforms you enabled and the last sync time in local browser storage. Disable a platform in the extension or disconnect it in the app to stop further collection.

Kit extensions (ClipPitch, AffiliateKit, UGC Starter Kit, Digital Product Quickstart, Tax Mini)

The kits keep your drafts, trackers and settings in your browser. Tax Mini's calculation runs in the extension. When you use an AI feature, the text you entered for it is sent to your CreatorSense account to generate the result; we do not use it for anything else. Paid kit plans are billed through your CreatorSense account by Stripe.

11. Cookies and similar technology

The site and app use cookies and browser storage to keep you signed in, protect forms, remember your cookie choice, credit a referral link you followed and, only if you accept, measure traffic with Google Analytics. If you have not answered the banner, Google Analytics receives cookieless signals with no identifier stored on your device. If you decline, it does not load at all. The full list, with lifetimes, is in the Cookie Policy.

12. Your rights and how to make a request

You can ask to see the personal information we hold about you, to correct it, to delete it, or to receive a copy in a common format. You can also ask us to stop using it for a particular purpose. Much of this you can do yourself in the app: edit your details in Settings, export or delete fans and cases in Trace, and delete your account in Settings.

To make a request, email info@creatorsenseai.com with the subject "Privacy request". Tell us what you want and which account or handle it concerns. We may ask you to confirm your identity before acting; we will not ask for more than we need. We reply within 30 days. Requests are free.

If we refuse a request, we will tell you why in writing (unless the law stops us) and how to complain. Where a request is about fan details held for a creator, we pass it to the creator and help them answer it (see section 2).

13. How long we keep information

We keep personal information only as long as we need it for the purposes in this policy or the law requires. When we no longer need it, we delete it or make it anonymous.

14. If you are in the EEA or the UK

The EU General Data Protection Regulation and the UK GDPR give you the rights to access, correct, delete, restrict, object to and port your personal data, and to withdraw consent at any time without affecting earlier processing. You also have the right not to be subject to decisions based solely on automated processing that significantly affect you; CreatorSense does not make such decisions. A Trace match is a technical comparison shown to the creator, not a decision about you.

Lawful bases for the processing we do as controller:

International transfers. Your data is processed in Australia and the United States and on Cloudflare's global network. Neither Australia nor (for most providers) the United States has an adequacy decision covering these transfers, so we rely on the European Commission's Standard Contractual Clauses and, for the UK, the International Data Transfer Addendum (or the UK IDTA), together with our providers' own transfer terms. Where a provider is certified under the EU-US Data Privacy Framework, that framework may also apply. You can ask us for a copy of the relevant safeguards.

Contact and complaints. Contact us at info@creatorsenseai.com. You can also complain to the data protection authority where you live or work (in the UK, the Information Commissioner's Office).

15. If you are in California or another US state

This section is our notice under the California Consumer Privacy Act as amended by the CPRA, and similar US state laws, to the extent they apply to us.

• Categories we collect: identifiers (name, email, handle, IP address, account ids); commercial information (plan and purchase history); internet activity (pages and features used); approximate location from IP; audio or visual content you upload; and account login details (sensitive personal information, used only to sign you in). Sources and purposes are in sections 3, 4 and 8.
• Selling and sharing: we do not sell personal information and do not "share" it for cross-context behavioural advertising. We have not done so in the past 12 months.
• Sensitive information: used only to provide the service, not to infer anything about you.
• Your rights: to know what we collect, use and disclose; to delete; to correct; and to opt out of sale or sharing (which we do not do). We will not treat you differently for using them.
• How to ask: email info@creatorsenseai.com. An authorised agent may ask for you with your written permission; we may still verify your identity with you.
• Retention: see section 13.

16. Children

CreatorSense is for adults only. You must be 18 or older to create an account or to use any CreatorSense service. Content showing anyone under 18 in a sexual context must never be uploaded, and we report it to the authorities. We do not knowingly collect information about children. If you think we hold a child's information, email us and we will delete it.

17. Complaints and changes

Complaints. If you think we have mishandled your personal information, email info@creatorsenseai.com first. We will acknowledge your complaint within 7 days 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) at www.oaic.gov.au or on 1300 363 992. EEA and UK residents can also use the authorities in section 14.

Data breaches. If a data breach is likely to cause serious harm, we will notify affected people and the OAIC as the Notifiable Data Breaches scheme requires, and other regulators where their law requires.

Changes. We will post any change on this page with a new date. If a change materially affects how we use your information, we will email account holders before it takes effect.

18. Contact

CreatorSense, a business name of Matt Orchard (sole trader), ABN 65 815 285 275, Sydney NSW, Australia
info@creatorsenseai.com

Version note: version 2.3 (8 November 2026) adds platform notices: with your authorisation for a case, we send an account notice and your evidence brief to the platform you choose. Version 2.2 (4 November 2026) added Trace Vault activity logging, Leak Radar (opt-in reverse-image search), evidence-pack timestamping via freetsa.org, and who can see Vault activity and admin security logs. Version 2.0 was the first CreatorSense-wide policy; it replaced the CreatorSense MCP Privacy Policy (effective 8 August 2026, last updated 9 August 2026), whose MCP content is now Part C.

Other legal documents: Terms of Service · Acceptable Use Policy · Refund Policy · Affiliate Program Terms · Data Processing Addendum · Subprocessors · Cookie Policy · Security · Copyright Policy.