Privacy
Last updated: 24 August 2026
tipthe.dev is built and run by Jeremy Bray, a sole trader based in Queensland, Australia. Information here is handled in line with the Australian Privacy Principles under the Privacy Act 1988 (Cth).
Two different people use this site, and the answer is different for each.
If you're a developer with a tip jar
You sign in with GitHub. From that we store your GitHub username, your display name and your avatar URL. We never see your GitHub password, and we don't ask GitHub for your repositories, your email or anything else.
To get paid you connect a Stripe account. We store its Stripe account ID so payouts can reach you. Your bank details, tax details and identity documents go to Stripe directly and never touch our servers.
Your sign-in is kept in a cookie called hdo_token, holding a signed token. It identifies you to the dashboard and does nothing else. The GitHub permission we ask for is read:user, which is your public profile and nothing further.
If you're tipping someone
You don't need an account. Card details are entered on Stripe's own checkout page, not ours, and we never receive them.
What we store for each tip is the Stripe payment reference, the amount, the developer it went to, the message you typed if you wrote one, and your email address if Stripe passed it back with the payment. The developer can see all of it, which is the point: they need to know who to thank.
If you'd rather not be identifiable to them, leave the message blank.
Who else is involved
- Stripe takes the payment and pays the developer. Their own privacy policy covers what they do with it.
- GitHub handles developer sign-in.
- Cloudflare hosts the site and the database, and stores rate-limiting counters keyed to IP addresses for a few minutes at a time.
- Progentick runs the feedback widget on the home page and dashboard, used by invited reviewers to report problems with the site.
Nothing here is sold, and there is no advertising anywhere on the site.
Analytics
There aren't any. No Google Analytics, no tracking pixels, no third-party analytics of any kind. The only cookie the site sets is the developer sign-in token described above, and the site doesn't set that unless you sign in.
The dashboard also keeps a single key, ob_dismissed, in your browser's session storage. It records that you closed the Stripe setup prompt so it doesn't reappear on every page load, and your browser discards it when you close the tab. It never leaves your machine.
The widget you embed on your own pages loads only what it needs to draw a button, and reports nothing back about who saw it.
How long we keep it
Tip records are kept while the developer's account exists, because they're that developer's payment history. Rate-limiting counters expire within minutes. Ask for your account to be removed and the developer record and its tips go with it; there's no delete button in the dashboard yet, so that request comes by email.
Your rights
You can ask what we hold about you, ask for it to be corrected, or ask for it to be deleted. Email hello@heyjeremy.com and I'll action it. Where a tip has to stay on record for accounting reasons, I'll say so rather than quietly keeping it.
Changes
If this changes, the new version goes up at this URL with a new date at the top.