Skip to content
CreatorSense
Trace MCP Connect Prompts Extensions Pricing
Add to Claude

CreatorSense MCP Privacy Policy

Effective: 8 August 2026 · Last updated: 9 August 2026

1. Scope

This policy covers data accessed through the CreatorSense MCP server at https://www.creatorsenseai.com/mcp. CreatorSense (“we,” “our,” “us”) provides an MCP connector so authorised AI tools (for example Claude) can query your creator account data according to your subscription tier.

This policy is specific to CreatorSense MCP. It does not cover Orolith Agency MCP or the full Orolith talent desk product.

2. What MCP can access

The MCP Server provides AI tools with access to data already held in your authorised creator account. No extra platform credentials are collected solely for MCP. Available fields depend on your plan:

  • Free: entitlement, connected platforms / sync health, profile summary, Creator DNA, and revenue summaries (net of platform fees).
  • Pro ($10/mo): Free tools plus assembled briefings, tax set-aside estimates, audience demographics, content performance, YouTube / live social analytics, forecasts, workload / wellness signals, opportunities, and schedule tools.

Data is read from your CreatorSense account and platform connections you authorised. MCP tools are read-only — they do not post, delete, or modify your social accounts.

MCP cannot access:

  • Your platform credentials, OAuth tokens, or login secrets for third-party platforms;
  • Private messages / DMs on connected platforms;
  • Payment card or bank account details;
  • Audience members’ personal data beyond aggregated segments;
  • Other users’ accounts.

3. Authentication

Connecting an AI tool uses OAuth (or equivalent) against your CreatorSense-linked account. The AI client presents an access token with requests. You can revoke the integration from the AI client’s settings and/or your account controls at any time.

Tokens are transmitted over TLS. We retain token identifiers (not raw secrets) in access logs for security auditing for up to 90 days.

4. Minimisation

Tools return data needed for the requested operation. We do not grant AI tools broader access than your entitled account surface.

5. What we log

For each MCP request we may log:

  • Timestamp
  • Token / session identifier (not the secret value)
  • Tool name invoked
  • Response status and latency
  • Subscription tier at request time

We do not log the full natural-language prompt you typed into the AI tool, nor the full response payload, as a matter of default practice.

Request logs are retained for 90 days, then deleted.

6. This website, cookies and analytics

Sections 1 to 5 cover the MCP connector. This section covers the pages you are reading right now, which is a separate matter.

We use cookies to analyse traffic, so we can see which pages people read and which ones are not worth keeping. The tool we use for that is Google Analytics. It does not load, and no analytics cookie is set, unless you choose Accept on the banner. If you decline, nothing is loaded, we remember that choice locally, and you are not asked again. If you never answer, nothing loads either.

When you have allowed it, Google Analytics records:

  • Pages viewed, and the referring site if there was one;
  • Approximate location from a truncated IP address (we enable IP anonymisation);
  • Browser and device type;
  • Four specific actions: copying the MCP endpoint, clicking through to a Chrome Web Store listing, clicking a connect button, and leaving for the app.

We do not send your name, email or any account identifier to Google Analytics, and we do not use it to build an advertising profile of you. Google's handling of that data is governed by their own policies.

To change your mind later, clear this site's data in your browser and the banner will appear again on your next visit.

7. Third-party AI tools

When you connect Claude or another MCP client, that provider’s privacy policy governs how they handle your conversation and any data they receive. Review their policies before connecting, including training, retention, and subprocessors. We are not responsible for third-party AI provider practices.

8. Security

MCP traffic is protected by TLS, authenticated sessions, rate limiting, and abuse detection. Report suspected compromise to info@creatorsenseai.com.

9. Your controls

  • Revoke the AI integration in the client;
  • Disconnect or close your CreatorSense-linked account (subject to applicable retention);
  • Contact us to exercise access, correction, or deletion rights where applicable.

10. Children

CreatorSense MCP is not intended for users under 18.

11. Changes

We may update this policy. Material changes will be posted here with a new effective date. Continued use after that date constitutes acceptance.

12. Contact

info@creatorsenseai.com
CreatorSense · Sydney NSW, Australia

Related: MCP Terms · Connect guide

© CreatorSense · Sydney NSW, Australia
ABN 65 815 285 275
Log in Trace MCP Connect Extensions Pricing Terms Privacy info@creatorsenseai.com

Built with security and privacy practices aligned to ISO 27001, ISO 27035, and GDPR / the Australian Privacy Act. Payments via Stripe. See our Privacy Policy and Terms.

Instagram TikTok