- Updated 2026-10-09
Privacy policy
What ClearDeck collects and what it never collects — for the Android app and for this website.
This policy covers two things: the ClearDeck Android app and this website. They are separate, so they are described separately.
It is written to be short and specific rather than long and reassuring. Where the answer is “we do not collect that”, it says so plainly.
Who we are
ClearDeck is published by Beijing Fenghong Technology Co., Ltd. (北京烽鸿科技有限责任公司). In this policy, “we” means that company.
Part 1 — The Android app
The one thing we never touch
The content of your network traffic never leaves your phone. ClearDeck filters connections on the device itself. There is no remote node, no relay server and no component that could forward your traffic anywhere, because none exists in the architecture. The sites you visit, the requests your apps make and the contents of your communications are never uploaded to us.
That statement is not a promise about our intentions; it describes how the product is built. You can verify it — the app’s filtering runs entirely locally, and the privacy and trust page documents each data path.
What the app collects, if you agree
On first launch the app shows a privacy notice and will not run until you decide. If you agree, the app collects:
| What | Why |
|---|---|
| Device information — model and system version | To understand which devices the app runs correctly on |
| App usage statistics — which features are opened | To learn which parts of the product are actually used |
| Crash and performance reports | To find and fix stability problems |
These are processed on our behalf by the Umeng SDK (友盟).
What the app never collects
- The content of your network traffic.
- The list of sites or hosts you visit.
- The contents of your access records.
- Anything from a deep-inspected connection beyond the local decision to block or allow it.
- Contacts, messages, photos, files, location, or any other personal data. The app does not request permissions for them.
Data the app keeps on your device only
Some data is stored locally and is never uploaded:
| Data | Where it lives | When it goes away |
|---|---|---|
| Access records (which app contacted which host, and the verdict) | Local database on your phone | Cleared when protection stops; exportable to CSV beforehand |
| Your settings and block/allow rules | Local storage on your phone | Removed when you uninstall |
| Rule lists and traffic statistics | Local database on your phone | Removed when you uninstall |
You can export the access records as a CSV file at any time from Tools → Export access log. That file is written to your own storage and is not sent to us.
Deep inspection and the certificate
Deep inspection is an optional feature that is off by default. It matches rules against the full request path rather than only the hostname, which requires installing a ClearDeck certificate so the phone will show the app its own connections.
- The certificate is generated on your device and never leaves it.
- Installing a user certificate means ClearDeck is technically able to see the decrypted content of the connections it intercepts. This is inherent to the technique, not a design choice.
- Content seen during inspection is used only to make a local block or allow decision. It is not uploaded.
- You can limit deep inspection to specific apps, restrict it to Wi-Fi, and cap how much of each connection is read (256 KB by default).
Removing the certificate from your phone turns the feature off and changes nothing else.
Your choices
- Declining the privacy notice means the app cannot run. The product is maintained with this feedback, so we do not offer a version with collection disabled. Uninstalling the app stops all collection immediately.
- You can withdraw consent by uninstalling the app.
Children
The app is not directed at children and we do not knowingly collect data from children.
Part 2 — This website
The website is a static site. It has no login, and almost nothing to collect.
The launch notification list
If you enter an email address in the launch-notification form, we store:
| Stored | Why |
|---|---|
| Your email address (lower-cased) | To tell you when ClearDeck is released |
The language you submitted from (en or zh) |
So the notification arrives in the right language |
| Which page the form was on | To understand which pages people actually find |
| The submission timestamp | Basic housekeeping |
That is the whole record. We use it for one message at launch. There is no newsletter, no marketing list, and we do not sell or share it with anyone.
The list is stored in a database where the public key used by the website can only insert rows and cannot read them back, so the address you submit cannot be read through the website by anyone else.
To have your address removed, contact us at the address at the end of this policy.
Analytics
This site uses Cloudflare Web Analytics, which is cookieless. It reports aggregate page views and referrers without setting cookies, without fingerprinting individual visitors and without tracking you across other websites. Because there are no cookies and no personal data, there is no cookie banner.
We do not use Google Analytics, advertising pixels, social-media trackers, or any other third-party script.
Hosting
The site is hosted on GitHub Pages. As with any web host, GitHub processes the technical data required to serve a page — such as your IP address — in its own capacity as the hosting provider. See GitHub’s privacy statement for that.
No cookies
This site sets no cookies of its own. Your language choice and your scanline-effect
preference are stored in your browser’s localStorage, which stays on your device
and is never transmitted to us.
Changes to this policy
If this policy changes, the “updated” date at the top changes with it. Material changes will be noted in the changelog.
Contact
Contact details are not final yet and will be published before the first public release. Until then, please use the project’s issue tracker.