Browser extension
Local processing
Security

Local processing & privacy

Understand the boundary between sensitive text, local detection, and service metadata.

On this page On this page

Detection happens on your device

SecureIntent’s core product message is local detection: supported text is evaluated on the device rather than submitted to a remote AI service for inspection. Sensitive values can be replaced before you share the resulting text.

Your promptContext + a secret
SecureIntentDetect & anonymize locally
A safer pasteContext + a placeholder

Text and metadata are different

DataProduct boundary
Raw sensitive textProcessed locally for detection; not sent as the detection payload.
Anonymous fingerprints & metadataMay be transmitted for product functionality.
Account & billing informationSeparate from clipboard detection; depends on the connected service.

“Local detection” does not mean that the entire application makes no network requests. Review the installed product and its applicable privacy policy before adopting it for sensitive work.

How this website works

This website uses fonts and assets to display the product documentation. The interactive demo only transforms fixed sample strings. It never reads your clipboard or sends a detection request.

The theme preference is stored in your browser. Docs feedback is session-only. Copy buttons write only the visible example or page content to your clipboard when you request it.

Account and billing pages connect to Clerk, Paddle and the SecureIntent API. Business enquiries submit your email and plan interest. Read the privacy policy for details.

Review before you rely on it

Security decisions should be based on the installed release, its configuration, and your own requirements. Read the source-review guide for the distinction between the website demonstration and the actual products.

Search documentation