Skip to content

Takedown and correction requests

If you appear in our data and believe something we've published about you is wrong, no longer accurate, or shouldn't be there at all, this page tells you what to do.

We treat takedown requests seriously. We also treat the public record seriously. Most of what we publish — Hansard speeches, voting records, roster information from official legislature websites, social-media posts from public accounts of public officials — falls squarely within the public interest. We aren't going to remove that on request.

But we make mistakes, and people who used to be public officials sometimes have a fair case for not having stale content surfaced about them. Here's how we handle it.

What's eligible for removal

We will remove or substantially edit content in any of these cases:

  • It's factually wrong and you can show us what it should say. (See submitting corrections — that flow exists specifically for this.)
  • It's not actually you. Mistaken-identity attributions, especially for common surnames, do happen.
  • The upstream source has retracted, redacted, or corrected the original. Hansard sometimes issues corrections; we follow upstream.
  • You're a private citizen who was incidentally mentioned. If you show up in a speech transcript because an MP named you in the House, and you'd prefer the text not be indexed for search against your name, we'll honour reasonable requests to redact your name (the speech itself stays — it's part of the official record — but your name becomes unsearchable).
  • The content is unlawful to host — defamation, court-ordered publication ban, etc. Send us the order or the basis.
  • You've withdrawn social-media posts upstream. If a public official deletes a tweet and a paying subscriber of ours had previously scraped it into our system, we'll remove the captured copy on request from the original poster.
  • Office contact info (email, phone, fax, office addresses) — when there's an active harassment / safety case. We expose the same email/phone/office addresses that every legislature publishes on their member pages and that Open North redistributes, but we make bulk programmatic access easier. If you're a public official facing an active threat and need a contact channel pulled from our API while the underlying upstream is being addressed, we'll honour that. Because our data is mirrored from Open North, we will also forward your request to them as the canonical source — a takedown on our side is effective immediately for /api/public/v1/* consumers but the data remains available at Open North until they process the same request.

What we won't remove on request

  • Hansard speech text — these are the official record of the legislature. We'll fix transcription errors when the upstream Hansard does, but we won't delete what was said in the House because the speaker has since changed their mind. Hansard is forever.
  • Voting records of sitting or former legislators on legislation, motions, or committee business.
  • Roster history — that someone held a seat, when, and for what party — when that information was published by the legislature.
  • Material published by the official's own current public account (website, X / Twitter, Bluesky, etc.) for as long as that account remains public. We don't host primary content for very long; we preview it and link to the source.
  • Requests from third parties about a public official's public record. If you aren't the subject (or their counsel), we usually won't act on third-hand asks — write to us with more context if you think we should.

How to request

Email admin@thebunkerops.ca with:

  • The URL(s) of the page(s) in question.
  • A short description of what you want removed or corrected.
  • The basis (factual error, mistaken identity, upstream retraction, legal order, etc.).
  • If you're the subject, enough context for us to verify you are who you say you are — usually your parliamentary or legislature email is enough. If you're acting on behalf of someone else (lawyer, staff member), tell us in what capacity.

Subject line: Takedown request — [your name] or [issue summary].

Response time and process

  • Acknowledgement: within 3 business days. If a request looks urgent (court order, ongoing harassment, etc.), sooner.
  • Substantive response: within 10 business days. For straightforward factual corrections this usually means "we fixed it"; for harder cases this might mean "here's our position, here's the next step."
  • Court-ordered removals: we act on these as fast as practicable once we've verified the order. Send the document itself.

We log every accepted request in our admin audit trail so that if a correction or removal is challenged later we can show what we did and when. We don't publish the audit log.

Disagreement

If we decline a removal and you think we're wrong, you can:

  1. Reply with new information — court order, additional context, evidence we missed.
  2. Escalate to the Privacy Commissioner of Canada (or your province's privacy regulator) for matters covered by privacy law. PIPEDA and most provincial regimes have a formal complaint process that compels our response.
  3. Public pressure / press — we'd rather not get there, but we recognize you have that lever.

Sources we publish from

For transparency about what we hold:

  • Hansard — primary text of speeches in legislatures (federal + provincial). Public record, indefinite retention.
  • Bills, motions, votes — official legislative business records. Public record.
  • Politician profiles — name, party, constituency, term dates, social-media handles, official website, photo, biographical detail drawn from official sources.
  • Social-media content — public posts from politicians' public accounts, captured via paid scrape jobs run by individual subscribers. See the scraped-content disclaimer for the full framing of how and when we capture this.
  • User-submitted corrections — kept in our audit log per the privacy notice.

If you're trying to figure out where a specific piece of content came from, link us to the page and we'll tell you the upstream source.