Privacy Policy

Last updated: September 20, 2026

Summary

Clarity is designed so your messages stay on your device. We do not operate accounts, servers that receive your pasted text, or analytics that track what you analyze.

What we do not collect

For Clarity:

• Messages you paste or type into the analyzer (we do not receive them on any server)
• Analysis results or scores sent to Clarity
• Personal identifiers or account information (there are no accounts)
• Usage analytics or behavioral tracking

How analysis works

When you analyze a message, processing happens entirely in your browser using local JavaScript. Nothing is uploaded to Clarity or any third-party service for analysis.

The Summary and How analysis works sections describe Clarity, the private message analyzer.

Media Lens preview

Media Lens is an unreleased, separate preview for public articles, advertisements, speeches, and campaign material. It is not deployed on this site. Its default fixture mode uses local example material and makes no network calls. Do not enter private messages or material you are not authorized to review. Any future live mode that sends prepared public text to an external service will require separate informed consent, an updated privacy notice, and additional security review before enablement. Clarity’s private analyzer remains governed by the on-device behavior described above.

Future Media Lens live URL (not available)

Live URL analysis is not available on this site today. It is disabled by default, not deployed, and not production-ready.

If live URL is later enabled after security, privacy, and owner review, it would apply only to Media Lens. Clarity message analysis would stay on your device, as described above.

The worker would run on a computer you or an operator control, usually the same machine and only as a local process. This site does not host that worker. A hosted or multi-tenant worker is not the current design and would need a separate privacy, tenant, and abuse review before anyone could claim that arrangement.

A consented live URL analysis would involve two separate network events:

• The worker would request the public page at the URL you submitted. The destination site and its content network would see the worker's network address, usually your computer.
• Prepared public span text from that page could be sent to TypeSafe's Jev typed classifier. TypeSafe would not fetch the URL. Newsjack provenance files, if used, would remain local.

Live pasted-text analysis would stay disabled. Private messages belong in Clarity and must not be submitted to Media Lens as a URL or as live paste.

Before any such request, you would have to confirm that the material is public and that you are allowed to review it. The worker would reject a live URL without that confirmation. That consent would cover contacting the origin and sending prepared public spans to TypeSafe.

By default the worker would not keep full article text, would not write Media Lens history, and would not create an account. Retention would be none unless you export a result yourself. Shutting down the worker and deleting any files you exported would remove local copies. This policy does not claim that TypeSafe retains nothing, deletes on request, or offers zero data retention. Prepared public spans would be processed under TypeSafe's own policy.

Do not submit private messages, passwords, medical or financial records, information about children, or any URL you are not authorized to fetch. Do not use a URL to reach internal, loopback, or other non-public systems. Paywalled pages would be left unanalyzed rather than bypassed.

This notice does not enable live URL or change any defaults.

Media Lens does not claim that TypeSafe AI will not retain, delete, train on, or otherwise use submitted inputs. Those practices are governed by TypeSafe’s applicable policy or written agreement. Media Lens makes no ZDR, deletion, or no-training claim unless a written agreement is attached to the release packet.

If live URL mode is ever enabled, the only production provider in scope is the pinned TypeSafe Jev integration. classifier.dev remains disabled, evaluation-only, and is not a fallback, second model, cascade, or production dependency.

Live pasted-text analysis stays disabled. classifier.dev remains off / KEEP_EVALUATION_ONLY.

Media Lens public claims (flags off)

While live flags remain off, Media Lens is unreleased, not available, a fixture/local preview, and not production-ready. It is not deployed on the public Clarity site. Live URL is not available. It is disabled by default. Live pasted-text is prohibited. There is no accuracy or named-person scoring product.

Media Lens does not claim that it:

• is production-ready before enablement approval
• is currently available while flags remain off
• detects manipulation with guaranteed accuracy
• fact-checks claims
• identifies manipulative people, outlets, or political actors
• provides anonymous or zero-retention processing
• guarantees no training or third-party processing
• is a diagnosis, safety assessment, or definitive credibility judgment

This policy also does not claim TypeSafe ZDR or that article text is deleted from TypeSafe without a written agreement attached to the release packet. It does not claim that classifier.dev is part of the live path. Incident copy must not say that Media Lens detected an attack on a named outlet or person.

Local storage on your device

Clarity may store two kinds of data locally in your browser:

• App cache (service worker): public app files so the tool can work offline after your first visit. This cache does not contain your messages.
• Optional analysis history: if you turn on “Save recent analyses on this device,” Clarity stores up to eight recent analyses (full message text, screening result, and timestamp) in localStorage under clarity-history-v2 on this device only. History is off by default. Legacy data from earlier releases without explicit opt-in is removed when you load the current version.

You can delete individual saved analyses or use “Delete all history” to remove all stored message text and results. Disabling the save toggle stops new writes; delete controls remove what is already stored.

Browser local storage may persist until you clear site data in your browser settings.

Fonts and hosting

Fonts are self-hosted from the same origin as the app. No third-party font or script requests are made when you use Clarity.

Your hosting provider

If you access Clarity through a website host (for example GitHub Pages), that host may collect standard web server logs (IP address, user agent, request time) as part of normal HTTP delivery. Clarity itself does not receive those logs.

Children

Clarity is not directed at children under 13. We do not knowingly collect information from children.

Changes

We may update this policy as the product evolves. Material changes will be reflected in the “Last updated” date above.

Contact

For privacy questions, email feedback@manipulationscore.com with Privacy in the subject line, or see Contact and Corrections for full instructions. Do not include private message content in your report.