Privacy policy

In one table

What i2c.net collects, at a glance

Everything else — browsing the board dataset, the address list, the tools — runs entirely in your browser and sends us nothing beyond the analytics above.

Analytics

Google Analytics, and how to switch it off

Every page loads Google Analytics 4. It records which pages get read, roughly where visitors are (derived from IP, at city level at best), what device and browser they use, and which site or search they arrived from. We look at it in aggregate to decide what to write next. We never try to identify an individual, and there's nothing in the interface that would let us.

Google is the data processor here and sets its own cookies (_ga and similar) to tell a returning visit from a new one. Their handling is governed by Google's privacy policy.

To opt out: block it. Any content blocker, Firefox's strict tracking protection, a DNS filter such as Pi-hole, or Google's own opt-out add-on all work. Nothing on this site breaks when analytics is blocked — every page, every tool and the download all function normally. There's no cookie wall and no nag.

Worth knowing: this site self-hosts its fonts rather than pulling them from Google Fonts, so with analytics blocked, reading a page makes no third-party requests at all.

Contact

The contact form

The contact form collects exactly what you type: name, email address, subject and message. There's also a hidden honeypot field that catches bots — if you're human you'll never see it.

The form posts straight from your browser to Web3Forms, a relay service, which emails the message to us. i2c.net's own server never receives it. That's a deliberate design: this is a static site with no database, so there's nowhere for a message to sit and no store to breach. Web3Forms' handling is covered by their privacy policy.

We keep the resulting email as long as the conversation is useful — a correction to the dataset might be kept as a record of why a value changed. Ask us to delete it and we will.

Affiliate links

Outbound buy links

i2c.net is reader-supported. Buy links are Amazon Associates affiliate links, marked rel="nofollow sponsored" in the HTML. If you buy something after clicking one, we may earn a commission at no extra cost to you.

We don't track your clicks ourselves, and we get no personal data back — Amazon reports commissions in aggregate, so we can see that a sale happened, never who made it. Once you're on Amazon you're on Amazon: their cookies, their privacy notice, their rules. As stated on our about page, a product appears here because it's a correct answer, not because of a payment.

The one that stores data

The i2c tool download and the sponsor offer

This is the only part of i2c.net that stores anything about you, so it gets the most detail. It applies only if you start the i2c tool download — reading the site never triggers any of it.

The tool is free, funded by a sponsor offer you complete once. To make that work:

• We create a session record on our server containing a random session ID, your IP address, whether the offer completed, which offer it was, and how many times the file has been downloaded. That's the whole record — there's no name, no email, and nothing about you beyond the IP.
• We send your IP address and browser user-agent to our offer provider (OGAds). Their API requires both — offers are country- and device-specific, and they can't tell which are available to you without them. We pass nothing else: no name, no email, no browsing history.
• Your browser stores the session ID in localStorage under the key i2c_locker_session. It's a random identifier, meaningless on its own, and it's what lets you close the tab and come back to your unlocked download.

Retention: 48 hours. Session records are deleted automatically once they expire — an hourly sweep removes them whether or not you ever returned. We don't archive them, and there's no long-term record of who downloaded what. To clear the session ID from your own browser, clear site data for i2c.net, or use the tool page in a private window.

The offer itself is served by the provider and governed by their terms; completing one is a transaction between you and them. If you'd rather not take part at all, the tool's source is plain readable code and you're welcome to ask us for it — we'd rather you had it than felt cornered.

Server side

Logs and hosting

The site runs on our own server (Caddy on a Linux VPS in the United States). We don't run general web access logging, so there's no routine record of which IP requested which page.

The locker service does write operational logs — that's the small program handling the download flow. It records completed sessions by their random ID, and it logs the IP address of anything that fails authentication, because that's a security event worth seeing. Those logs live on the server's system journal and rotate away on the usual schedule. They exist to keep the thing working and un-abused, not to profile anybody.

Your rights

GDPR, CCPA and what you can ask for

Wherever you are, you can ask us to show you what we hold, correct it, or delete it — and you can ask without giving a reason. Use the contact form; it reaches us directly.

In practice the answer is usually short, because there's usually nothing: we hold no accounts, no profiles and no purchase history. If you emailed us, we hold that email. If you started a tool download in the last 48 hours, a session record with your IP exists until it expires. That's the entire list.

The legal bases we rely on, in GDPR terms: legitimate interest for aggregate analytics and for keeping the download from being abused; consent when you choose to submit the contact form or start the unlock flow; and contractual necessity for the session record, since the download can't work without one. For third parties, requests are best made directly — Google and Amazon each have their own process, and we can't reach into their systems on your behalf.

If you're in California: we do not sell or share personal information as the CCPA defines it, and there's nothing to opt out of.

Children

Children's privacy

i2c.net is a technical reference about wiring sensors to microcontrollers. It isn't directed at children under 13, and we don't knowingly collect personal information from them.

There isn't much here to collect regardless — no accounts, no profiles, no comments, nothing a child could sign up to. The only place any personal data enters at all is the contact form (which asks for an email in order to reply) and the tool download (which records an IP for 48 hours). If you believe a child has sent us something through either, tell us via the contact form and we'll delete it.

Changes

Changes to this policy

If this policy changes we'll update the date at the top. Substantive changes — a new third party, a new kind of data — get a note here rather than a silent edit, because a privacy policy you can't diff isn't worth much.

Contact

How to reach us

Questions, corrections, or a deletion request all go through the contact form. Who we are and how the dataset works: about i2c.net.