Local-First Architecture
Most privacy tools work by proxying your traffic through their servers. We took a harder path. SecurePresent runs 100% within the browser's local JavaScript runtime.
- No Data Exfiltration: Your screen content never leaves your device.
- No Content Logging: We do not have servers that ingest or store page text.
- Offline Capable: The masking engine works even if you disconnect from the internet.
Why we need "Read and Change Data"
Chrome displays a scary warning when you install our extension. Here is exactly why we need each permission.
"Read and change all your data on websites you visit"
The Reality: To blur text on a page (like $50,000), code must be able to "read" the webpage to find that number and "change" the CSS to apply a blur filter. Without this permission, the extension cannot interact with the page content to protect it.
"storage"
The Reality: We use local storage to save your user preferences (e.g., "Always mask emails") and your license key. This data lives on your hard drive.
Need a formal security review?
We understand enterprise procurement. Download our technical whitepaper which details our threat model, data flow, and SOC2 readiness controls.