Effective date: 22 August 2026
Contact: support@inseine.co.uk


In'Seine does not collect, transmit, store on our servers, sell, or share any
user data — including any data about the child whose browsing it filters. There
is no account, no server operated by us, and no analytics.

This matters especially here. Many parental filters work by monitoring: they
record where a child goes and report it to a parent, which means that record
exists somewhere and can be lost, breached, or subpoenaed. In'Seine does not
monitor. It blocks sites; it does not keep a record of them. No such record is
created, on our servers or on your computer.


All of the following is stored locally, in the browser's own extension
storage (chrome.storage.local). None of it is transmitted anywhere.

| What | Why | Where it goes |
|---|---|---|
| A hashed version of the parent's PIN | To unlock the settings | Your computer only |
| Which filter categories are switched on | To decide what to block | Your computer only |
| Site addresses the parent adds to the allow list or block list | To allow or block them | Your computer only |
| Downloaded public blocklists for the chosen categories | To decide what to block | Your computer only |
| A count of consecutive failed PIN attempts, and any lockout time | To slow down guessing | Your computer only |
| A randomly generated Install ID | To match a paid unlock code to this installation | Your computer only, unless you buy the paid version — see below |
| Browser Break hours, any extra minutes granted, and the last time seen | To block the browser between the hours you chose, and to notice a changed clock | Your computer only |

The PIN is stored as a PBKDF2-SHA256 hash with a random salt, not as the digits
themselves.


In'Seine does not record, store, or transmit:

• The child's browsing history
• Which sites were visited, or which were blocked
• What was searched for
• Times of use, session lengths, or frequency
• Any personally identifiable information about any person, adult or child
• Authentication or payment information
• Location
• Screenshots or page content
• Any analytics, telemetry, crash reports, or usage statistics

There is no reporting feature, no parent dashboard fed by activity data, and no
history of blocked pages. These features do not exist in the code.


In'Seine is installed and configured by a parent or guardian on a computer used
by a child. It collects no data from that child, or from anyone else. No
personal information is gathered, stored remotely, or shared, so there is
nothing to disclose, sell, or delete on request.

The extension does not require a child to have an account, does not identify who
is using the browser, and does not distinguish between users.


In'Seine contacts one place: GitHub, where the public blocklists are hosted
(raw.githubusercontent.com/blocklistproject/Lists). It does so for two
reasons.

Downloading the lists. Once every 24 hours it fetches the public blocklist
files for the categories the parent has switched on.

Checking the clock — only if Browser Break is switched on. Browser Break
blocks the browser between hours you set, so it has to know the real time;
otherwise changing the computer's clock would defeat it. In'Seine reads the
timestamp that every web server puts on its replies, from the same GitHub
address, at most once every 30 minutes and only while a schedule is active. If
Browser Break is off, this never happens. No time server or other third party
is contacted.

These requests:

• Download the same files that every other user with those categories downloads
• Contain no information about you, your child, your settings, or any browsing
• Download files; they upload nothing

GitHub will see that a request was made from your IP address, as it would if you
opened that file in a browser. Their handling of that is governed by GitHub's
own privacy policy.

There are no other network requests from the extension, and no other party is
contacted. No analytics, no error reporting, no third-party scripts, no web
fonts, and no time server.


The paid version is bought through the In'Seine website, not through the
extension.

Payment is handled by Lemon Squeezy, who act as the merchant of record. They
collect what any shop needs to take a payment and issue a receipt, under their
own privacy policy. We never see your card details.

To issue your unlock code, the website checks your order number with Lemon
Squeezy and then signs the Install ID shown in your extension's settings.
The Install ID is a random string generated on your own computer when the
extension is first run. It is not derived from anything about you, your child,
your browsing, or your hardware, and it tells us nothing beyond distinguishing
one installation from another.

If a device limit applies to your order, the website records only which Install
IDs have been unlocked against that order number. No browsing data, settings, or
personal information is stored alongside it.

The extension itself never contacts the website. You paste the unlock code into
it, and it is verified offline against a public key built into the extension.


Only the two named above — GitHub, for the public blocklists, and Lemon Squeezy,
if you buy the paid version. No data is sold, licensed, shared, or disclosed to
anyone beyond that.


All data is held in the browser's local extension storage for as long as the
extension is installed.

To delete everything: remove In'Seine from the browser (chrome://extensions in
Chrome, about:addons in Firefox). This immediately and permanently deletes the
stored PIN hash, all settings, all downloaded lists, and the Install ID. Nothing
is held anywhere else, so there is nothing further to request.

If you have bought the paid version, records of your order are held by Lemon
Squeezy under their own retention policy, and you can contact them or us about
those.

Note that In'Seine can optionally be paired with a separate browser policy
setting, installed by the parent using an included script. That policy is stored
by the operating system, not by the extension, and is removed with the included
unlock script. It contains no personal data — only browser settings and a hashed
removal PIN.


| Permission | Why |
|---|---|
| storage, unlimitedStorage | To save settings and downloaded blocklists locally. The lists can exceed the default storage quota. |
| webNavigation | To see the address of a page before it loads, so a blocked address can be intercepted. This is how the extension performs its only function. |
| tabs | To redirect a tab to the block screen when a blocked address is detected. |
| alarms | To schedule the daily blocklist update. |
| host_permissions: <all_urls> | A web filter must be able to check every address navigated to, because any address could be one on a blocked list. Filtering against a list of sites is not possible without seeing the address of the site being visited. In'Seine reads only the address. It does not read page content, and it does not transmit addresses anywhere. |


If this policy changes, the effective date above will be updated and the change
noted in this repository.


support@inseine.co.uk