Privacy Policy - MC Lens

Last updated: June 17, 2026

Applies to: MC Lens v1.3.0 and later.

MC Lens is a Chrome extension that enhances the Salesforce Marketing Cloud (SFMC) user interface with productivity and AI-assisted features. This policy describes what data the extension accesses, how it is stored, who it is shared with, and your rights.

MC Lens has two tiers with different privacy characteristics. Please read both sections.

1. Free tier - local only

The following features run entirely inside your browser and do not send any data to MC Lens servers or any third party:

Command Palette, Subscriber Lookup, Cross-BU Subscriber Search, Error Log, Send Performance, Automation Health Monitor, Engagement Hub, Admin Dashboard, DE Inspector, Dependency Mapper, Query Studio overlay (tabs, formatter, Data Views, Query Library), Email Health, Email Previews.

What's accessed

• Session tokens captured from your authenticated SFMC session and stored in chrome.storage.local (auto-expires ~55 minutes).
• SFMC metadata - names, keys, and IDs of Data Extensions, Journeys, Automations, Lists, Emails, Query Activities, Data Filters, Content Builder assets.
• Subscriber data - keys, email addresses, list memberships, event history - only when you perform a lookup.
• Send metrics, automation status, engagement events, error data, DE schemas - only for the BUs you have access to in SFMC.
• SQL query text you author in Query Studio.

Where it's stored

All free-tier data is stored only in chrome.storage.local on your machine. It is never transmitted to MC Lens servers or any third party.

Data	Retention
Bearer token	55 minutes
Cached SFMC metadata	5-60 minutes
Local bookmarks	Until you remove them
Automation health snapshot	Until next poll
Toolbar / feature settings	Until you change them
Query Studio tabs and recent queries	Until you clear them

2. Pro tier - server-backed (opt-in)

When you connect SFMC by entering your own Installed Package credentials (Client ID, Client Secret, Auth URL) in the extension popup, the following AI-powered features become available:

AI Studio - Subject Scorer, AI Email Editor; AI Chat Dashboard; Query Studio AI panel (Explain & Optimize, Ask AI); cloud-synced Saved Queries.

Pro features rely on MC Lens's backend infrastructure and share data with the sub-processors listed below.

Sub-processors

Sub-processor	Purpose	Data shared
Vercel, Inc.	Hosts MC Lens API	All Pro-feature API traffic
Supabase, Inc.	Database & authentication	User identity, organization, encrypted SFMC tokens, conversation history, audit log, scoring history, saved queries
OpenRouter, Inc.	LLM routing	Conversation messages, system prompts, and tool results - routed to the model providers below
OpenAI, L.L.C.	LLM (AI Chat, Query Studio AI) - routed via OpenRouter	Your prompts, system prompts, conversation history, and tool results (SFMC metadata only)
Anthropic, PBC	LLM (Subject Scorer, AI Email Editor) - routed via OpenRouter	Email subject, preheader, and HTML content, plus your instruction

OpenAI and Anthropic receive data only through OpenRouter (MC Lens has no direct integration with either); they are OpenRouter's model providers. Connecting an Installed Package constitutes your consent to these sub-processors processing your data for the purposes above.

Data sent to AI providers

When you use an AI feature, the request is sent to OpenRouter, which routes it to the model that powers that feature - OpenAI (AI Chat, Query Studio AI) or Anthropic Claude (Subject Scorer, AI Email Editor):

• Subject Scorer - the subject line, the preheader, and the email's HTML body (used as context).
• AI Email Editor - the email's HTML body and your natural-language instruction.
• AI Chat / QS AI - your prompt, the system prompt, conversation history, and the results of any tools the model calls. Tool results contain SFMC entity metadata only - for example automation names, data-extension schemas, send metrics, and bounce category counts. Row-level subscriber data is never sent to AI: subscriber lookups are not available to the AI chat at all, and no individual subscriber record reaches the model.
• Query Studio Explain & Optimize - the SQL you submit for analysis.

Content sent to OpenRouter and its model providers (OpenAI, Anthropic) is subject to their privacy policies (openrouter.ai/privacy, openai.com/policies/privacy-policy, and anthropic.com/legal/privacy).

Data stored server-side

Stored in Supabase. Row-level security ensures your data is unreachable to any other user or organization, even via API.

Data	Retention	Notes
User identity	Until you disconnect	Derived from your SFMC tokenContext
Organization & business unit info	Until you disconnect	Scopes features per BU
SFMC refresh token	Until you disconnect	AES-256-GCM encrypted at rest
Installed Package client_secret (BYO)	Until you disconnect	AES-256-GCM encrypted at rest
Conversation history & tool invocations	Up to 90 days	Lets you resume past chats
Audit log	Up to 365 days	Every tool execution; for support and security
Subject-line scores	Until you remove them	History across emails
Cloud-synced saved queries	Until you remove them	Your Query Studio ★ saves
Cloud-synced bookmarks	Until you remove them	Bookmarks you sync to the cloud

3. Permissions

Permission	Why
storage	Cache SFMC data locally and store user preferences
activeTab	Inject toolbar and UI into the active SFMC tab
notifications	Desktop alerts when automations enter error state (opt-in)
alarms	Background polling and service worker keepalive
tabs	Detect SFMC navigation and route messages between tabs
webNavigation	Detect when the SFMC OAuth sign-in redirect completes, to finish connecting your account
Host access to *.exacttarget.com, *.marketingcloudapis.com	SOAP/REST API calls to your SFMC tenant
Host access to *.marketingcloudapps.com	Capture Data Extension context inside Contact Builder iframes
Host access to querystudio.herokuapp.com	Inject Query Studio enhancements into SFMC's hosted Query Studio iframe
Host access to mc-lens.vercel.app	API calls to the MC Lens Pro backend

4. Privacy protections

• Email masking - subscriber email addresses are masked in the Error Log (e.g., j****@example.com).
• Shadow DOM isolation - all injected UI is encapsulated in closed Shadow DOM to prevent data leakage to the host page.
• Row-level security - every Supabase query is filtered by your user_id and org_id.
• Encrypted secrets - SFMC refresh tokens and the BYO Installed Package client_secret are encrypted at rest with AES-256-GCM using keys held outside the database.
• No analytics or telemetry - MC Lens does not include analytics SDKs, page-view tracking, or behavioral telemetry.

5. Your rights

• Disconnect at any time - use the "Disconnect" button in the popup Settings tab. Disconnecting revokes server-side credentials and stops API access.
• Delete account & data - email thrishulpola999@gmail.com with the subject "MC Lens account deletion." All server-side data tied to your user will be purged.
• Clear local cache - use the "Clear Cache" button in the extension popup at any time.
• Remove the extension - uninstalling removes all browser-stored data. Server-side data is unaffected and requires the deletion request above.

6. Changes to this policy

Material changes will be reflected in the "Last updated" date.

7. Contact

For questions :

Thrishul Pola
Email: thrishulpola999@gmail.com

MC Lens is not affiliated with or endorsed by Salesforce, Inc.