Privacy

Bin Day Alerts is run by Adder Analytics Limited, a company registered in England and Wales. We are the data controller for everything described below. For anything to do with privacy, email privacy@bindayalerts.co.uk.

There are two products under this name, and they work differently. The website sends bin reminders by email, so it has to remember your email address. The mobile app has no accounts and no email at all — your phone schedules its own reminders. Each section below says which one it is about.

We do not maintain a database of bin days. Every schedule is read from your own council’s website at the moment it is asked for, using the readers maintained by the open-source BinDays project. That means the dates are as accurate as what your council publishes, and no more.

Those requests go out from our server, not from your browser or your phone, so your council sees us asking rather than you.

This applies to both products. To answer “what are the bin days at this address?” we need a postcode, and then which address on it you picked. Nothing identifying you is attached to that question: no account, no cookie, no device identifier.

We cache the answers so that a hundred people on the same street do not mean a hundred trips to the council’s website. The cache is keyed on the postcode and expires on its own — 30 days for which council covers a postcode, 7 days for the list of addresses on it, and 6 hours for the collection dates themselves. It is not linked to a person, an account or an install, and there is nothing to delete because it deletes itself.

When a lookup fails, the postcode is included in the error report emailed to our developer. That is how a broken council reader gets noticed and fixed. It is a postcode and an error message, nothing else, and it only happens when something has already gone wrong.

Our servers keep short-lived request logs and rate-limiting counters, which include the IP address the request came from. That is ordinary abuse prevention — it stops one script hammering a council’s website through us — and those counters expire within the hour.

When you sign up for reminders on this website we store:

• your email address;
• the address you chose — its postcode, the council, and the address line as the council writes it;
• the hour of the evening you want the reminder;
• the collection schedule we last read for that address;
• a random token, which is what the confirm and unsubscribe links in your emails carry instead of your email address;
• which reminders we have already sent, so a retry cannot email you the same thing twice.

Nothing is sent to you until you click the confirmation link, which expires after 48 hours. If you never click it, nothing more is ever sent.

If you tap the “something wrong?” link in a reminder, we record what you said was wrong and what a fresh check of the council’s site found at that moment. We look at those in aggregate, by council, to work out which readers need fixing.

This lives in a hosted Postgres database, and the reminders are delivered by Resend, our email provider. Neither is used for anything else.

The lawful basis is your consent, which you gave by confirming, and which you can withdraw at any time.

Every reminder has an unsubscribe link, and your mail client’s own unsubscribe button works too. One click stops the emails immediately — there is no login and nothing to confirm.

Unsubscribing stops the sending but leaves the record in place. If you want it deleted outright, email privacy@bindayalerts.co.uk from the address you subscribed with and we will remove it.

The app has no accounts, no sign-in and no email address. The places you add, their schedules and your reminder settings are stored on your phone and nowhere else. We have no copy of them.

Reminders are scheduled by your phone, not sent to it. There is no push server and no list of who to notify — which is also why they still work with no signal.

The app makes exactly two kinds of network request, both of them the postcode lookup described above, and both only when a schedule is being fetched or refreshed. They carry no account, no device identifier and no advertising ID.

Deleting a place removes its schedule and cancels its pending reminders. Deleting the app removes everything it stored on your phone. There is no account to close and no subscription to unsubscribe from; the cached lookups on our side expire on their own, and nothing marks them as having been yours.

When the app crashes it sends the error and enough about the phone to make sense of it — model, OS version, app version — to Sentry, our crash reporting provider. Nothing is sent while the app is working normally.

No IP address and no user identifier is attached, and there is no user identifier to attach. Postcodes are stripped and address fields redacted before anything leaves the phone, because a home address is the one thing in this app that would genuinely identify somebody.

In App Store terms, this is Diagnostics → Crash Data: not linked to your identity, and not used for tracking.

No advertising. No advertising or tracking SDKs in the app. Nothing sold, rented or shared for marketing, ever. No profiles built about you, and no attempt to follow you between sites or apps.

The website counts page views using Vercel Web Analytics, which is aggregate, cookieless, and cannot follow you to another site.

Under UK data protection law you can ask us for a copy of what we hold about you, ask us to correct it, or ask us to delete it. Email privacy@bindayalerts.co.uk and we will do it.

In practice, for the app there is nothing to ask for — we hold nothing that identifies you. For the email reminders, what we hold is your email address and the address you chose, and either the unsubscribe link or one email removes it.

If you think we have got this wrong, you can complain to the Information Commissioner’s Office at ico.org.uk. We would rather you told us first.

Neither product is aimed at children, and neither asks for a date of birth, because nothing about a bin collection depends on one.

If this changes we will update the date at the top. Anything that meaningfully widens what we collect will be announced in the app and by email to subscribers before it takes effect, rather than slipped into a new version of this page.

This version is dated 13 August 2026. Back to Bin Day Alerts.