Privacy

This site, at keylineicons.com, and nothing else. The set is also published on GitHub, npm, Figma Community and paper.design, and those are other people's platforms: what they collect when you visit them is governed by their policies, not by this one.

There is no account to make, and nothing on this site asks you for a name, an email address, or anything else about you. Specifically:

• No sign-in, no user accounts, no profiles.
• No advertising, no ad network, no tracking pixels, and nothing that follows you to another site.
• No session recording and no heat maps.
• No third-party embeds: no iframes, no hosted video, no comment widget, no chat bubble, no scripts loaded from anyone else's domain.
• No forms. Nothing here collects an email address, so there is no list to be on and nothing to unsubscribe from.

Nothing is sold or handed to anyone for their own purposes. What is measured, and who processes it, is the next section.

Two things, both through Vercel (opens in a new tab), which hosts this site and processes the measurements on our behalf. Neither sets a cookie.

• Page views. Which pages are opened, and which site or search sent you. Counted without a cookie and without an identifier that survives the day, so a return visit next week is a new visit as far as the numbers are concerned.
• Loading speed. How long pages take to render and respond, which is what tells us a page of 585 drawings has become slow on a phone.

On top of those, a handful of things you do with the set are counted: copying an icon's snippet or its name, downloading an SVG, copying an install command, and a search that found nothing.

The empty search sends what you typed. It is the one event that carries anything you entered, and it is the reason the list exists: a search for a drawing the set does not have is a request for it from someone who will never file one, and it is the only signal in the product that says what to draw next. What is searched here is a public list of icon names.

Every one of those events describes the set, never you: an icon name, a style, a filter you picked, a file format, a package manager, a query typed into the icon search. No identifiers, no addresses, and nothing typed anywhere else on the site. The complete list is the Events type (opens in a new tab) in the repository, which is a shorter and more honest answer than this paragraph: an event that is not in it cannot be sent.

The icon browser lets you change how the set is drawn, and remembers it. That is the entire purpose of the only cookie this site sets for itself. Nothing in the section above sets one.

• Name: keyline-icons-browser, first-party, SameSite=Lax.
• Contents: size, stroke, color, showNames, columns. Nothing else, and no identifier of any kind. It does not say who you are, because the site does not know.
• Written only when you change one of those settings, never on arrival and never in the background.
• Lifetime: one year. It is a preference, not a session, and it is read by the server so the page is drawn your way in the first paint rather than corrected afterwards.

There is no consent banner because there is nothing to consent to: the cookie is set by an action you take, carries no identifier, and is never sent anywhere but back to this site. Reset in the icon browser puts the defaults back, and clearing site data in your browser removes it outright.

Your light or dark preference is kept the same way, in your browser's own local storage under theme. It never reaches the server.

Every page is served from this origin, and so is everything on it, including the two measurement scripts: they are served from a path on this site rather than from someone else's domain. Two more cases are worth naming, since both are usually third-party requests elsewhere:

• Fonts. Geist is downloaded when the site is built and served from here. No request goes to Google Fonts, so nothing there sees your visit.
• Contributor avatars. The pictures beside a drawing's credits come from GitHub, but this site fetches them and re-serves them. Your browser talks to us; github.com does not see you.

The site is hosted on Vercel, which keeps ordinary server logs as every web host does: the IP address a request came from, the time, the URL, the browser's user agent string. They exist so the site can be delivered and defended against abuse. They are not used to build a profile of you and are not sold.

The site makes one outbound call of its own, and it makes it from the server: the star count in the header comes from GitHub's API, cached for an hour and shared by everyone. Your visit never reaches GitHub for it.

The header, the footer and several pages link out to GitHub, X, Figma, npm and paper.design, and the Share menu hands this site's address to whichever network you pick. Those are separate services with their own terms and their own tracking; following a link puts you on their site under their rules. The links are plain anchors, with no redirect and no tag that would tell us you clicked.

There is normally nothing to request. No account exists, nothing measured here identifies you, and the only record of a visit is a server log entry held by the host for a short period.

If you want to ask anyway, open an issue (opens in a new tab) on the repository. That tracker is public, so please do not put personal details in one: describe what you are asking for, not who you are.

The date at the top of the page is the day the policy last changed. It moves when the policy does, not when the site is deployed.

Because this page is a file in a public repository (opens in a new tab), every revision of it is in the commit history, with the reason in the message. That is a stronger record than a sentence promising to notify you, and it is checkable by anyone.