Local Reports

Who we are

Local Reports is run by Cllr George Martin and operated by Cestrian Digital Ltd (company number 17290507, registered office 1 Ardenfield Close, Radcliffe M26 1UP) on behalf of the Reform UK group on Bury Metropolitan Borough Council. Cestrian Digital Ltd is the data controller for everything described on this page and is registered with the Information Commissioner's Office under number ZC206993. Each councillor is the data controller in their own right for the casework they take forward with Bury Council on your behalf. Elected representatives are exempt from the ICO fee for that work, but have the same duties to you under data protection law. It is not a Bury Council service. If you have any question about your data, email privacy@localreports.co.uk.

This service is for people aged 16 or over. We do not check age, so if you are under 16 please do not create an account. We do not knowingly hold data about anyone younger; if you think we do, email the address above and we will delete it.

What we collect, and what we deliberately do not

When you create an account we store your name, your email address and your ward, plus your choice about update emails, the dates you created your account and last signed in, whether a councillor has approved your account, and the reports you follow. If sending a report fails, we keep a short technical record of the error (the page, the error message and your browser type) to fix the fault. We do not ask for your phone number or anything about your circumstances.

If you start a report about something already reported nearby, you can follow the existing report instead and get update emails when it changes. The list of reports you follow is kept with your account and removed with it.

We do ask for your postcode when you sign up, and we want to be clear about it because a postcode is a small enough area to count as a home address. We use it once and then throw it away. Your browser sends it to postcodes.io, a free public lookup, which tells us which ward it falls in. We keep the ward. The postcode is never sent to our database and is never stored anywhere. We ask because reports go to Bury councillors, who cannot raise anything with another council, so somebody signing up from outside the borough would get a service that cannot help them.

When you report an issue we store what you tell us: the category, the location you drop the pin on, your description, and any photos you attach. Local Reports only takes reports about public places, so a report should never need to say anything about your home life. Please do not include other people's personal details, faces or number plates in descriptions or photos.

Abandoned vehicles are the one exception on number plates. The council cannot trace the keeper of an abandoned vehicle without the registration, so that category asks for it. It is stored in its own field, passed to the council with the report, shown only to the councillors handling the case, and never shown on the Nearby map or to any other resident. It is removed when the report is anonymised (see the table below).

Photos are stripped of their hidden information (the position they were taken at, the device and the time) before they are stored, so a photo can never reveal where you were standing.

To help councillors spot false reports, we note two things when you send a report: whether the pin came from your device's position (a simple yes or no), and roughly how far your device was from the pin, to the nearest kilometre. We never store your device's location itself, only that distance. New accounts cannot send a report from about ten miles or more away from the pin; the limit is lifted once your first few reports have been accepted. If you decline the location prompt, nothing is recorded and filing works exactly the same; reporting something from home is always fine.

Special category data (anything about health, ethnicity, religion, politics, sexuality or similar, about you or anyone else) is not something we need and not something we want. We ask you not to include it, and if it appears in a report we remove it during review. The original wording is kept on file with a record of the edit, so the report stays honest about what was changed.

Why we are allowed to use it

Our lawful basis under UK GDPR is legitimate interests: residents want street issues raised with the council and fixed, their councillor needs a small amount of information to do that, and this is exactly the use anyone filing a report would expect. We collect the minimum (name, email, ward and the report itself), we do not use it for anything else, and you can object at any time (see your rights below). Where the law requires us to share something, the lawful basis for that sharing is legal obligation.

What we use it for

Your report goes to the councillor it is assigned to, who raises it with Bury Council and chases it. Your email address is used to sign you in and to send you updates on your reports. Nothing else: no marketing lists, and your details are never sold or shared with the Reform UK party for campaigning. You can turn update emails off at any time on your profile page, and still see everything in the app. Sign-in codes are sent either way, because they are how you get into your account.

We may publish anonymous figures about the reports we have handled, such as how many potholes were fixed in a ward this year, to show the work done. They never identify you, and we will not use your photos for this without asking you first.

If you choose to sign in with Google, Google confirms who you are and passes us the same two details: your name and your email address. We keep only your name and email address. Our sign-in provider also keeps the Google account identifier and profile picture link that Google sends with each sign-in; we do not use or display them. We cannot see, post or change anything on your Google account. Signing in with an emailed code works exactly as before.

No decision with a legal or similarly significant effect is made about you automatically. Some rules are automatic: a daily limit on how many reports an account can file, a limit on photos, refusing sign-up from disposable or previously blocked email addresses, and sending a report to the councillor for its ward. Reports from residents a councillor has approved can skip the review step. A new account can file 5 reports a day, and 15 once a councillor has approved it, with up to 60 photos in total. A person decides whether a report is taken forward and whether an account is blocked. There is no profiling.

Who sees it

Councillors. The councillor your report is assigned to. Until a report is claimed, any Reform councillor on Bury Council can see it. The group's administrator (also a councillor) and Cestrian Digital's administrator account can see every report, to run the service. Every councillor can see a one-line summary of every report (the type of issue, ward, street and status), but not your name, email or what you wrote. Every councillor account needs two-step verification to sign in, and every time a councillor opens or changes a report it is logged. Updates on your report's timeline show the name of the councillor who wrote them, and that name stays with the report until it is anonymised.

Bury Council. When a councillor raises your report with the council, the report itself goes across so they can act on it: what you reported, the date and time you filed it, the exact location with map links, any photos you sent, and for an abandoned vehicle the registration. It also includes a link that opens the report, its map and photos without a login. The link works for six months and the council may pass it to its contractors. Your name and email address are not included. The councillor stays your point of contact and passes on what the council say.

Other residents. People who are signed in can see open reports, and reports filed in the last two years that have since been resolved, on the Nearby map, but only the pin, the type of issue, the street and the status: not the house number, not your description or photos, not any registration, and not who filed it.

If a report is rejected or merged with another report of the same problem, you are told on the report's page and by email, unless you have turned update emails off. For a report that is not taken forward we explain the kinds of reason a report is closed, not which one applied. For a merged report we tell you which report it was merged into.

Who helps us run it

A few companies process your data on our behalf, under contract, and only to make the service work. None of them may use it for their own purposes.

  • Supabase hosts the database and photo storage, in its London region.
  • Vercel hosts the website and provides anonymous, cookieless visitor counts, and anonymous counts of how many people reach each step of the report form.
  • Supabase, our sign-in provider, sends sign-in codes. Resend sends the update emails about your reports.
  • Cloudflare provides the security check on the sign-up page that tells real people apart from automated scripts, and routes email sent to our addresses.
  • Google confirms who you are if you choose to sign in with Google, and nothing more.

International transfers. Vercel, Resend, Cloudflare and Google are US companies. The database and photos are held in the UK, but these providers may handle some of it (the website request that carries it, the email that carries a code or an update, the sign-in check) outside the UK. Each transfer is covered by the UK-US Data Bridge where the provider is certified under it, and otherwise by the International Data Transfer Agreement or the UK Addendum to the EU standard contractual clauses, which are the safeguards UK law recognises.

Two public services receive data from your browser but store nothing for us and are not under contract with us:

  • postcodes.io receives the postcode you type at sign-up, any postcode you type into the report form's location search, and the pin's position to look up its postcode, with your IP address as part of each request.
  • OpenStreetMap (its Nominatim service) receives the coordinates of the pin you drop and any street or address you type into the location search, with your IP address as part of the request, and answers with the street name and postcode shown on the report. Map pictures come from OpenStreetMap, or from Ordnance Survey if OpenStreetMap is unavailable.

How long we keep it

WhatHow long
Your account (name, email, ward)Until you ask us to delete it, or 24 months after your last sign-in. We email a warning at 23 months; signing in once keeps the account.
Open reportsFor as long as the report is open.
Closed reportsAnonymised 2 years after closing: the link to your account, the description, any house-level location detail, any registration, any remaining photos, internal notes, edit history, follows and council links are removed. The pin, street, category, ward, dates and status are kept for statistics. A report closed as not genuine is instead deleted outright 90 days after closing, photos included. Only an anonymous record that a report with that reference and category was deleted, and why, is kept.
PhotosDeleted 30 days after the report is closed.
Blocked accountsDeleted 24 months after being blocked. A one-way hash of the email address is kept so the same address cannot sign up again; the address itself is not.
Unfinished sign-upsDeleted after 7 days if the sign-in code was never entered.
Councillor audit logKept with the report. It records which councillor did what and when, never anything new about you.
Technical error records (when sending a report fails)Deleted after 90 days.

Ask at the address above and we will delete your account and your reports sooner, without fuss. A report that has already been sent to the council stays on the council's own records, which we cannot recall.

How we keep it safe

The database and photos are held in the UK. Data is encrypted in transit and at rest. Access to resident details is limited to councillors, who need two-step verification (an authenticator app as well as their email) to sign in, and every councillor view of and change to a report is logged. Every write to the database goes through the server, and the database itself enforces who may read each row.

Cookies

Only the cookies that keep you signed in, plus one that remembers you have dismissed the prompt to add Local Reports to your home screen. The bot check on the sign-up page, run by Cloudflare, may set its own cookie while you complete it. No advertising or tracking cookies.

Your rights

You can ask us, by emailing the address above, to:

  • give you a copy of what we hold about you (access);
  • correct anything that is wrong (rectification);
  • delete your account and reports (erasure);
  • stop using your data while a question about it is settled (restriction);
  • stop using your data at all, where we rely on legitimate interests (objection);
  • give you your data in a form you can take elsewhere (portability).

You cannot delete your account or a report yourself in the app. Email privacy@localreports.co.uk and we will do it.

We answer within one month. No decision with a significant effect on you is made automatically. You also have the right to complain to the Information Commissioner's Office (ico.org.uk, 0303 123 1113) if you think we have handled your data badly; we would rather you told us first, so we can put it right.

Last updated 31 October 2026: anonymous figures and photos clarified; who can see a report, cookies, retention wording and rejection notices corrected; automatic rules, data held, the council handover link, map and analytics providers clarified. Earlier the same day: retention periods published, lawful basis, international transfers and the abandoned-vehicle registration field. This notice describes Local Reports as it works today and is updated when the service changes.

Terms of use · Accessibility · Back to Local Reports