Privacy in plain language.

1. What this site collects

Visitor analytics

Two analytics tags count page views so we can see which collections and tools are used and which pages need work. Neither collects your name or email.

Google Analytics 4 records the page URL, referrer, browser and device type, approximate country, and site events such as copying code or running a search (including the search words). GA4 does not log or store IP addresses. Outside the EU/EEA, the UK and Switzerland it keeps an anonymous visitor ID in first-party cookies (_ga, _ga_*). Inside those regions it stores nothing on your device: it sends cookieless measurement only. Google holds the data under its privacy policy; we only read aggregated reports.

Fullres is a cookieless analytics tag loaded from t.fullres.net. It sets no cookies, stores no persistent identifier and does no cross-site tracking. It records the page URL, referrer, browser type and approximate country. See the Fullres privacy policy.

Messages you send us

The contact form sends your message, your name and email if you give them, and your browser's user agent and screen size (to help with bug reports and spam) to the site owner's inbox through Resend. The email address is optional; without it we just can't reply. Messages stay in that inbox and are not shared.

Problem reports and suggested fixes. Each demo has a "Report a problem" button, and signed-in members can send their edited code as a suggested fix from the playground. A report stores what you wrote, the demo it's about, your browser's user agent and screen size, and the email address you choose to give (optional) or, if you're signed in, a link to your account. A suggested fix stores a copy of the code you sent, your note, and whether you agreed to be credited. Both go to a private queue that only the site admin can read, and the admin gets an email notice through Resend; nothing is shown on the site. If we use your fix and you agreed, your account name appears on the demo as "Improved by". Deleting your account removes the link between you and anything you sent.

The weekly email

If you subscribe with the newsletter form, your email address goes to Kit, which sends the weekly email; Kit asks you to confirm first. Signed-in members can subscribe with one click instead (see below). Every email has an unsubscribe link.

Stored in your browser

Some conveniences are kept in your browser's localStorage and never sent to the site unless you're signed in (noted below): your light/dark theme, the pages you save (synced to your account if you sign in), how many demos each collection had when you last opened it (for the "+N new" badges), dismissed banners, and in the playground your layout, editor settings, unsaved edits and the versions you save while signed out. Signed in, versions, editor settings and unsaved edits are kept in your account instead (below). You can clear all of it through your browser's site-data settings.

Optional account

You can sign in with GitHub or Google. Signing in is never required to read or copy anything. When you sign in, we receive and store your name, email address and profile picture from the provider you chose. We then store: the pages you save; the demos and collections you give a heart ("love"); the collection, demo, tool and generator pages you open while signed in (the newest 50); the playground versions you save, with up to 20 earlier states of each; your unsaved playground edits, so you can continue on another device; and your editor settings. Heart counts are shown publicly as totals; who loved a page is never shown. Your playground code is private to you unless you turn on a share link for a version: then anyone with that link can view and copy that version's code, without your name or email, until you turn the link off. We never receive your GitHub or Google password and never post or act on your behalf. This data is stored in a Cloudflare D1 database and used only to run your account.

Signing in does not subscribe you to anything. After your first sign-in we ask once whether you'd like the weekly email; nothing happens unless you choose "Yes", and "No thanks" means we won't ask again. If you say yes, we send your email address and first name to Kit and record when you agreed. You can turn it off in Account settings or with the link in any email. You can clear your history from Your library and delete your account, with everything attached to it, from Account settings.

2. Ads and affiliate links

EthicalAds serves the ads on CodeFronts. Ads are chosen by the topic of the page, not by who you are. EthicalAds sets no cookies and does no tracking across sites; when an ad loads it sees your IP address and browser details to show an ad suited to your country and to filter out fraud. See the EthicalAds privacy policy.

Affiliate links. Some pages recommend products such as online courses or UI kits through links labelled as affiliate links. Following one takes you to the partner's site, which may set its own cookies to record that you came from CodeFronts; we may earn a commission at no extra cost to you. We don't share anything about you with partners.

Sponsors appear as a labelled card with a link and logo. Sponsor cards run no scripts.

3. Cookies

CodeFronts sets cookies only if you sign in: a session cookie (better-auth.session_token, plus a short-lived better-auth.session_data copy) that keeps you signed in, and a short-lived security cookie while the GitHub or Google sign-in is in progress. They are strictly necessary for the account, are not used for analytics or advertising, and are removed when you sign out. Visitors who never sign in get no CodeFronts cookies. Other cookies:

• Google Analytics 4: _ga and _ga_* for anonymous visitor counting, outside the EU/EEA, UK and Switzerland only.
• Cloudflare (hosting): may set __cf_bm to tell people from bots.
• Fullres and EthicalAds: none.
• Affiliate partners: their own cookies, on their site, only after you follow one of their links.

You can block or delete cookies in your browser. Everything on CodeFronts works without them except staying signed in.

4. Services we use

Each service gets only what it needs to do its job.

• Cloudflare: hosting, CDN, security and the account database. Sees IP addresses to deliver pages and stop abuse.Policy →
• Google Analytics 4: page-view counting.Policy →
• Fullres: cookieless page-view counting.Policy →
• EthicalAds: ads chosen by page topic.Policy →
• GitHub and Google: sign-in, only if you choose it. They give us your name, email address and profile picture.GitHub policy →Google policy →
• Kit: the weekly email, only if you subscribe.Policy →
• Resend: delivers contact-form messages and problem-report notices to the site owner.Policy →
• Google Fonts: typefaces for the site and some demos. Google may log the IP address that requests a font.Policy →
• cdnjs (by Cloudflare): in the playground, the library search sends your search words to cdnjs, and libraries you add load from it.Policy →
• CodePen and StackBlitz: only when you choose "Open in CodePen" or "Open in StackBlitz", the code goes to them to open there.CodePen policy →StackBlitz policy →

5. Your rights

Wherever you live, you can:

• Ask for a copy of the personal data we hold about you: messages you sent us, and your account data if you signed in.
• Ask us to correct or delete it. If you have an account, you can delete it yourself at any time from Account settings; deletion is immediate.
• Unsubscribe from the weekly email with the link in any email, or in Account settings.
• Block analytics cookies in your browser.
• Complain to your local data protection authority.

To make a request, use the contact form and start your message with "Data request". We reply within 30 days.

6. Children

CodeFronts is a technical resource for developers. We don't knowingly collect data from anyone under 13 (16 in the EU). If you believe a child has sent us information or created an account, tell us through the contact form and we will delete it.

7. Changes to this policy

When something material changes, such as a new service or a new kind of data, we update this page and the "Last updated" date at the top.

8. Contact

Questions, requests or corrections: use the contact form. We read every message.