Privacy policy

Last updated 13 August 2026 · Peekless v0.2.0

Peekless collects nothing. There is no server, no account, no analytics and no third party. Every feature, including all camera processing, runs entirely on your own device. Nothing about you or your messages is transmitted anywhere, because there is nowhere for it to go.

Who this applies to

This policy covers the Peekless browser extension and this website. It is published by the makers of Peekless, who can be reached at info@ai2flows.com.

What Peekless can access

Peekless runs only on https://web.whatsapp.com/*. It has no ability to read, observe or act on any other tab, website, or your browsing history. Adding another chat platform in future would require a new permission that Chrome shows you before it takes effect.

On WhatsApp Web it reads the page's structure — which elements are message bubbles, chat previews, photos, names — in order to decide what to blur. It does not read, copy, log, store or transmit the contents of your messages, and it has no code that could.

What is stored, and where

Data	Where it lives	Leaves your device?
Your settings — what to blur, blur strength, idle timeout, theme	`chrome.storage.sync`	Only via Chrome's own sync, if you have it enabled. Never to us.
Your face template, if you enrol one	`chrome.storage.local` on that machine	No. Deliberately never synced.
Your settings PIN, if you set one	`chrome.storage.local`, as a salted hash	No. The PIN itself is never stored at all.

Settings sync is performed by Google Chrome between browsers you are signed into. That is Chrome's feature, not ours — we operate no server and never receive that data. Your face template is deliberately excluded from it.

No message content, contact names, photos, or usage statistics are stored.

Camera

The camera feature — Presence Guard — is optional and off by default. Peekless does not request camera access at install time, and the base product is fully functional without a camera or camera permission.

If, and only if, you explicitly enable it:

A disclosure screen explains exactly what happens before anything is requested.
The camera is active only while a WhatsApp Web tab is both focused and visible. Losing focus, switching tabs, or turning the feature off releases it immediately — your operating system's camera indicator going out is your proof.
Peekless samples a single still frame roughly every 1.8 seconds. It does not open a continuous recording.
Each frame is analysed in memory, on your device, by face models bundled inside the extension, and is then discarded. Frames are never written to disk, never stored, and never uploaded.
The only values derived from a frame are how many faces are visible and — if you have enrolled a face — a similarity score against your stored template.

Chrome's permission prompt is attributed to Peekless, not to WhatsApp, because the camera runs on the extension's own origin. Camera frames never enter the WhatsApp page at all. You can revoke access at any time from chrome://settings/content/camera, or by turning Presence Guard off.

Face recognition, if you enrol

Enrolling a face is a separate, optional step. When you do, Peekless computes an embedding — a fixed-length list of numbers derived from a face crop — and averages several of them into one template.

No photograph, video frame or crop is written to disk at any point. An embedding cannot be converted back into an image.
The template is stored in chrome.storage.local, which stays on that machine. It is deliberately kept out of synced storage so it is never transmitted anywhere, including to Google.
It is used for exactly one purpose: deciding whether the face in front of the camera resembles the enrolled one, in order to blur or not blur your screen.
You can delete it at any time from the Peekless setup page. Deletion is immediate.

This is not biometric authentication and is not offered as a security measure. It controls a blur, nothing more, and a photograph held up to the camera would defeat it. There is no liveness detection.

Network activity

Peekless makes no network requests. The face detection and recognition models and their runtime are bundled inside the extension package, so nothing is downloaded while it runs and the extension works entirely offline.

The only related network activity that exists is Chrome's own extension update check, performed by the browser against the Chrome Web Store — not by Peekless.

This website is static. It sets no cookies and runs no analytics.

Third parties

None. Peekless contains no advertising SDKs, no analytics SDKs, no crash reporters and no third-party network calls. Your data is not sold, rented, shared or transferred to anyone, because it never leaves your device in the first place.

The bundled face models (YuNet and SFace, from the OpenCV Zoo) are open-source software that runs entirely on your device. Using them involves no communication with anyone.

Permissions, and why each exists

Permission	Why it is needed
`storage`	To remember your settings and, if you enrol one, your face template.
`offscreen`	To run the camera and face models in a document owned by the extension rather than inside the WhatsApp page, so camera frames never touch that page.
`https://web.whatsapp.com/*`	To apply blur on WhatsApp Web. This is the only site Peekless can access.
Camera	Not in the manifest. Requested at runtime, on a dedicated Peekless page, only if you turn on Presence Guard.

Deleting your data

Face template: "Delete my face data" on the Peekless setup page.
Settings PIN: "Remove PIN" in the popup.
Everything: removing the extension from chrome://extensions erases all of its stored data.

Children

Peekless is not directed at children and collects no data from anyone, including children.

Changes to this policy

If this policy changes, the updated version will be published here with a revised "last updated" date, and will ship alongside the extension.

Contact

Questions about privacy, or about anything above: info@ai2flows.com.