Privacy, explained.
What the site stores, what other people can see, and which services make it work.
Browsing the collection
You can explore buttons, edit a preview locally, and download code without signing in. Your appearance preference is stored in your browser. Drafts and saved collections also use browser storage. Dismissing the community follow and star prompt saves a browser-local preference so it stays closed on future visits. Collections can be exported as a JSON backup. Clearing browser data removes local drafts and collections.
Your GitHub account
Sign-in is handled by GitHub through Firebase Authentication. Your GitHub username, display name, profile image, and bio are used for your community profile. Firebase maintains your authentication session.
Contributions and public information
Submitted code, creator details, profiles, and likes are stored in Firebase Firestore. Approved buttons and creator profiles are public. A contribution’s likes may identify the GitHub usernames of people who liked it.
Creators can view their own submissions and edit their profile bio. Administrators can review submissions. Removing a published button cannot recall copies that other visitors have already downloaded.
Services used by the site
Firebase handles sign-in and community data. GitHub serves public profile images and repository statistics. The hosting service delivers the website. Button previews may request external fonts, scripts, or images chosen by their creators.
When enabled, Cloudflare Web Analytics measures page views without analytics cookies. The Sponsors counter saves cumulative counts by public page path without storing IP addresses, account identifiers, or query strings.
Your playground edits
Editing code updates the preview and autosaves a draft on this browser. The app server receives code to validate its structure and compile Tailwind styles; this does not create a public contribution. The site saves a contribution to Firebase when you choose to submit it or save changes to a button you manage.
Sponsorship checkout
Dodo collects payment and billing details on its hosted checkout. We use your order and submitted brand details to review and fulfill your placement. The earlier checkout flow stores brand details as Dodo order metadata. The payment-first flow stores them in our private order database and uses a cookie to let you return in the same browser. Approved sponsor names, logos and links are public. Payment status and receipts are not published on the site.
Questions about your data
Contact the project maintainer through the repository if you have a question about your profile or contributions.
Updated .