What StackKit collects, why, and how to get rid of it.
Last updated 24 September 2026
You can read every part of StackKit without an account and without telling us who you are. We keep a record of page requests so we can see what is read and which crawlers fetch it, and if you create an account we keep your email address so we can sign you in and send the weekly email. We do not sell anything about you, and there is no advertising network on this site.
StackKit is operated from Bangladesh and is the data controller for the information described here. Questions, corrections and deletion requests go to [email protected].
Each page request is recorded at our CDN, before the page is served. That record contains:
An IP address is personal data, so we do not keep it indefinitely: IP and user-agent are erased from records older than 30 days, leaving the counts and the page history behind. We use this to understand what gets read, and to see which search and AI crawlers fetch the site.
Clicking through to a tool is counted: which tool, the page you clicked it from, and an approximate country and city from our CDN. No IP address, account or browser identifier is kept with it. It tells us which listings are useful. Some of those links are affiliate links (see the Terms); the tool's vendor may then set its own cookies on its own site to credit the referral, under its own privacy policy. We receive no personal data about you from them.
An account needs only an email address. There is no password — we email you a link, and following it signs you in. We store your address, a display name and a handle derived from it, the tools and posts you save, and any replies you write. Replies are public: your display name, handle and words are shown to everyone who opens that thread.
Creating an account subscribes you to the weekly email. Your address is stored for that purpose and nothing else. Every issue carries an unsubscribe link, and unsubscribing does not close your account.
We use Google Analytics 4 to see which pages get read and how people arrive. It runs on every page and reports your page views to Google, along with the usual things a web request carries: your IP address, which Google uses to place you in a country or city and then discards, your browser and device, and the page you were on before. We do not send Google your email address, your name, or anything you have saved. IP anonymisation is on by default in GA4, and we have not turned on advertising features or data sharing with Google's ad products.
None of that happens unless you accept it. The analytics tag is not loaded until you agree on the banner, so on a visit where you decline — or simply never answer — your browser does not contact Google at all and nothing above is sent. Accepting loads the tag and turns on a randomly generated ID that joins your visits together. The two cookies involved, and how to change your answer, are listed on the Cookies page. The advertising permissions Google's consent framework also asks about are refused outright and never offered to you, because the site runs no advertising.
The visit records described above, kept on our own infrastructure, still run alongside it, and remain the only measurement that sees crawlers and visitors without JavaScript.
If you would rather not be counted, Google publishes an opt-out browser add-on at tools.google.com/dlpage/gaoptout, and any tracker blocker will stop it too. Nothing on the site breaks when it is blocked.
We use these services to run the site. Each sees only what its job requires.
| Service | What it handles |
|---|---|
| Supabase | Database and sign-in: your email, saved items, replies |
| Cloudflare | Serving the site; the visit records described above |
| Resend | Delivering sign-in links and the weekly email |
| Cloudinary | Hosting video shown in the feed |
| Google Analytics | Which pages get read: page views, IP address, device |
| YouTube, Vimeo, Loom | Only when you press play on a video hosted there |
Some of these providers process data outside Bangladesh and outside your own country, including in the United States. Where the law requires it, those transfers rely on the providers' standard contractual clauses or equivalent safeguards.
Google Analytics is the only one of these you get a say over, and the only one that is not contacted unless you say yes. The rest are how the site is served at all.
We do not sell personal data, and we do not share it for advertising.
For readers in the UK and EU, the legal basis for each use is:
Account data is held in a database that only lets each member read and change their own saved items. Visit records, click records and the subscriber list cannot be read from the public site at all. Traffic is encrypted in transit, and there are no passwords to leak. No system is perfectly secure; if a breach affected your data, we would tell you and the relevant authority as the law requires.
You can ask for a copy of what we hold about you, ask us to correct it, ask us to delete it, or object to or restrict how we use it, and you can withdraw any consent at any time. Deleting your account removes your email address, saved items and replies. Write to [email protected] and we will act within 30 days. If you are in the UK or EU and are unhappy with our response, you may complain to your national data protection authority.
California residents: we do not sell or share personal information as the CCPA defines those terms, and we do not use sensitive personal information.
StackKit is meant for working professionals and is not directed at children under 13.
If this policy changes in a way that affects you, the date at the top will change and the change will be described here.