Last updated 2 October 2026.
Who we are
The operator and data controller for this website is DeveloperData.net (Developer Data), Empire Tower, 41st Floor, Unit 4106-7, South Sathorn Road, Yannawa, Sathorn, Bangkok 10120, Thailand. Contact: [email protected], or support on this site.
What we keep
- Your account: your name and email address from Google when you sign in, the Google account number that links the two, and your plan. We never see your Google password.
- What you put in: the councils, committees and topics you follow, your alerts and briefings, the questions you ask the archive, your team and the people you invite, and your settings.
- API keys: only a fingerprint of each key and its first few characters, never the key itself.
- How you use CouncilMonitor: each paper you download (which paper, its size and when), what you search for, the links and buttons you click, and how many calls your API key makes each day. Before you have an account, the same is kept against a random visitor number in a cookie; when you sign in, that history joins your account.
- Partner referrals: if you arrive from a partner's link, a first-party cookie (ap_click) remembers which partner sent you, for 60 days, so they can be credited if you subscribe. It holds no personal details, and a newer partner link replaces it.
- Support: what you write in support tickets, refund and removal requests, and our replies.
- Page and API logs: each page you load and each call to our MCP server, with your full internet address, browser type and country, for security and traffic figures. Usage records keep a shortened address, with the last part removed.
Card details
Card details are never held by us. Stripe takes the payment and keeps the card. We keep your plan, invoices and payment status. Card charges appear as DEVELOPERDATA.NET.
Why we keep it
- To run CouncilMonitor: sign you in, send the alerts and briefings you ask for, and deliver the papers you download.
- To bill it: take payment for your plan and keep the records the law requires.
- To answer support and refund and removal requests.
- To stop abuse and keep it secure: run the free allowance (3 papers without an account, 20 a month on a free account) and spot automated bulk downloading or getting round it.
- To improve it and tell you about it: see which councils, papers and features people use, and keep a profile of the councils, committees, topics and papers you are interested in, which we use to choose what we show you and to tell you about our paid plans. You can object to this at any time.
Nothing is sold, and there is no advertising tracking. We do not use your information for decisions with legal effects on you.
Where UK or EU data protection law applies, we rely on contract to provide the account and plan you signed up for; legitimate interests to secure and improve the service, run the free allowance, keep your profile and tell you about our paid plans, which we balance against your interests; and consent where the law requires it.
Turn off offers and news by email under "Offers and news by email" in your account, or with the link in any such email. Your alerts are separate and carry on until you stop them.
Who else handles it
- Stripe, for payments.
- Cloudflare, for our network and security.
- Our email provider, through Developer Data, for alerts, briefings and account emails.
- Our AI model provider, through Developer Data, for summaries and for answers to the questions you ask the archive.
- Google, for signing in, and for our fonts: Google receives your internet address when a page loads.
- Our hosting company, which runs our servers in France.
Each works for us and may use your information only to provide their service to us. Where law requires it, we may also share information with professional advisers or authorities. Developer Data is based in Thailand; where your information leaves the UK or EU, we protect it with the safeguards the law requires, such as standard contractual clauses.
Cookies
We set our own cookies only, each listed here. There are no third-party analytics or advertising cookies. When you first arrive we ask whether to allow analytics; until you accept, we do not count your visits, record which pages you use, or log your clicks. The necessary cookies below work either way, because they keep you signed in and run your free-paper allowance. You can change your choice at any time from the Cookies link in the footer.
| Cookie | What it does | How long |
|---|---|---|
cm_s | Keeps you signed in | 60 days |
cm_cc | Remembers your cookie choice (analytics accepted, or necessary only) | 1 year |
cm_v | A random visitor number: counts your free papers and links your history to your account when you sign in | 2 years |
cm_csrf | Protects forms from being sent by other sites | 30 days |
cm_next, cm_next_hold | Returns you to the page or paper you wanted after signing in | Up to 1 hour |
cm_plan | Carries on to payment after signing in, if you chose a plan first | 30 minutes |
cm_ask, cm_ask_ref | Carries a council you asked us to add through signing in, then shows its reference | Up to 1 hour |
cm_gstate | Protects the Google sign-in step | Minutes |
cm_flash and the other cm_…flash cookies | Shows a one-off message, such as "saved" | Minutes |
How long we keep it
- Your account and what you put in: while your account is open.
- How you use CouncilMonitor, once joined to your account: while your account is open.
- History that never joined an account: 12 months.
- After your account is deleted: gone within 30 days, backups included.
- Billing records (invoices, payments): as long as tax and accounting law requires, even after your account is deleted.
- Page, API and security logs: 30 days.
- Support tickets: while your account is open, then deleted with it. A removal request, and what it hides, is kept for as long as the removal applies, so the paper or name stays hidden.
Your rights
You can see what we hold about you, have it corrected, take a copy, or have it deleted. You can also restrict how we use it, and object to our using it, including for your profile and offers. Ask through support; we answer within 30 days. If a council paper on CouncilMonitor names you or shows your details, use the removal form. If you are in the UK and unhappy with our answer, you can complain to the Information Commissioner's Office (ico.org.uk).
Deleting your account
Delete your account yourself in your account, under Delete my account. When you do:
- your plan is cancelled at once, and the unused part is not refunded;
- every API key stops working at once;
- you are signed out;
- your account and what you put in are deleted within 30 days;
- billing records stay as the law requires, tied to the payment record at Stripe, not to a live account.
We email you when it is done. If you cannot sign in, ask through support and we will do it for you.
Children
CouncilMonitor is not for anyone under 18.
Changes
A new version is posted here with its date. A change that matters is emailed to members before it applies.