Thank you for using the GlanceGuard Chrome extension. GlanceGuard exists to protect your privacy from shoulder surfing, so it is built on a simple principle: your data never leaves your device. This Privacy Policy explains exactly what the extension does with your camera, what is stored, and what is not.

No Account, No Cloud, No Network

GlanceGuard does not require an account, registration, or login. The extension contains zero networking code — it makes no fetch, XHR, or WebSocket requests of any kind. It cannot upload anything, because it has no code capable of doing so. We do not collect, store, or transmit any personal information.

How Your Camera Is Used

When the guard is armed, the extension processes your webcam feed entirely inside the extension itself, on your device:

• Frames are downscaled to a tiny 96×72 grayscale buffer used only to detect motion in the peripheral zones of the frame.
• Each frame is discarded immediately after being compared to the previous one. No frame is ever stored to disk, uploaded, displayed, or retained in any form.
• Where available, Chrome's built-in on-device face detection is used to count faces in the frame. Face data is likewise processed in memory and discarded instantly; no biometric information is stored.
• When you disarm the guard, the camera is released.

The one-time setup page shows you a live preview of your own camera so you can see the detection zones. That preview exists only on that page while it is open and is never recorded.

Information Stored Locally

The only data GlanceGuard stores — locally on your device, using Chrome's extension storage — is your settings:

• Whether the guard is armed
• Your chosen sensitivity level (Chill, Balanced, or Paranoid)
• Whether tabs should be muted while shielded
• Whether playing media should be paused while shielded

Nothing else is stored. This data never leaves your device and is removed when you uninstall the extension.

Permissions Explained

• Camera — used exclusively for on-device intruder detection, as described above.
• Tabs and scripting — used to apply and remove the frost overlay, mute tabs, and pause media on the pages you have open when the shield triggers.
• Storage — used to save your four settings locally.
• Offscreen — used to run the camera detection engine in a background document, which is how Chrome extensions access a camera without keeping a visible page open.

What We Do Not Collect

• We do not record, store, or transmit camera frames — ever
• We do not track your browsing activity or history
• We do not read the content of the websites you visit
• We do not sell or share any data with third parties
• We do not use analytics inside the extension
• We do not show ads

Verifiability

We believe a camera extension should prove its privacy claims rather than ask for trust. GlanceGuard ships with readable source and no external libraries at runtime — you (or anyone you trust) can inspect every line and confirm that no networking or storage of camera data exists.

Children's Privacy

GlanceGuard does not collect data from anyone, including children. The extension is suitable for general audiences.

Contact Information

If you have any questions or concerns regarding this Privacy Policy or the GlanceGuard extension, please contact us at:

Email: openjargon[at]gmail.com

Changes to This Privacy Policy

We may update this Privacy Policy from time to time. Any changes will be posted on this page with an updated effective date. Because the extension has no network capability, any future change to data handling would require a new extension version reviewed by the Chrome Web Store.

Thank you for trusting GlanceGuard. Guarding your privacy is the entire point.