Privacy Policy

1. Summary

Kellet is a self-imposed content blocker. This policy describes what data the service collects, why it is collected, how long it is kept, and how you can review or delete it.

Kellet does not sell personal data and does not run third-party advertising. The activity your agent records - what it blocked, what you browsed, what it captured - is never shared outside the service.

Separately from that, this website uses Google Analytics, and only if you accept the cookie banner. It collects visitor data about this website alone - which pages were visited, and the broad device and location details listed in section 4. It never receives your activity data, your rules, or anything an agent uploaded.

2. Data we collect

Account data - the email address you register with, a hashed password, and profile fields you choose to add.

Device metadata - the human-readable name you give each device, its enrollment status, and its last-seen timestamp.

Activity data - for each enrolled device, the browsing events, application usage, and blocked-content events the agent uploads, along with the timestamps they occurred. Browsing events include the domain, the full URL and the page title where the agent captured them.

Captured images - when on-screen detection is enabled and "capture a frame on a block" is left on, the flagged frame is uploaded and stored alongside the activity record it belongs to. Screenshots and camera frames are uploaded only when a capture is requested from the app.

Configuration data - the blocking rules, category preferences, and guardrail settings you configure.

3. Why we collect it

We use account and device data to authenticate you and route agent uploads to the right account.

We use activity data to show you your own history and to enforce the rules you have configured.

We use configuration data to serve the correct rule set to your enrolled agents.

4. Website analytics

This website uses Google Analytics to count visits and see which pages help people most. It is the only third-party tracker on the site, and it measures visitor behaviour on this website only. It is not connected to your account, and it is not connected to anything your enrolled devices do.

Nothing loads until you accept. If you decline the cookie banner, or simply ignore it, no request is ever made to Google and no analytics cookie is set - the tag is not placed in the page at all, rather than being loaded and told to stay quiet. If you accept and later change your mind, tracking stops.

Exactly what is collected, and nothing beyond it: the pages you visit on this website and their titles; the site that referred you here, if any; how long you spend on a page; whether you are a first-time or returning visitor; your approximate location, at country and city level, derived from your IP address, which is not itself retained; and your device type, browser, operating system, screen size, and language.

Page views are the only thing this site reports. There is no click tracking, no scroll tracking, no form-content capture, and no session recording. Your name, email address, and account identifier are never sent. A cookie stores a randomly generated visitor number so that repeat visits can be told apart from new ones; it does not identify you.

What Google never receives is anything the blocking agent produced. Your browsing history from enrolled devices, blocked-content events, application usage, captured frames, and your rules stay inside the service and are not sent to any analytics provider.

Advertising features and ad personalisation are switched off, so none of this is used to build an advertising profile or shared with ad networks. Google acts as a data processor here, and its own handling is governed by its policies. If you would rather not be counted at all, decline the banner or use your browser's Do Not Track or tracker-blocking settings.

5. Data we do not collect

Classification of what is on your screen happens locally on the device. Frames that are not flagged are not uploaded; see section 2 for the flagged and on-demand captures that are.

We do not use third-party advertising, and no analytics provider other than the one named in section 4.

We do not collect biometric identifiers, physical location beyond what is inferable from routine network metadata, or contents of files that were not flagged by the agent.

We never see or store your card number. Payments are handled by Stripe, and only the plan, status, and the last four digits of the card are returned to us.

6. Retention

Account data is kept for as long as your account is active. Once you close the account, it is deleted within 30 days.

Activity data retention depends on your plan tier. See the Pricing page for the current retention window per tier.

Backup snapshots may retain deleted data for up to 30 additional days before being expired.

7. Access and deletion

You can review and delete your activity data at any time from the app.

You can request full account deletion, which removes all associated data within 30 days (plus the backup window in section 6).

You can export your activity data for your own records on request.

8. Contact

Questions about this policy or a data request should be sent through the contact page.

This policy applies to the Kellet web app and the Kellet blocking agent. Third-party services those tools depend on, including Stripe for payments, are governed by their own policies.