Privacy.

You do not need an account to use CallsAlert. We do not sell data, we do not run advertising trackers, and we do not publish anything that identifies the person who filed a report.

We do keep the content of reports, and we do keep limited technical information needed to run the service and stop abuse. The rest of this page explains exactly what that means.

When you submit a report we store what you entered:

• the phone number you are reporting
• the category of call you selected
• roughly when the call happened, as the option you chose
• whether you answered
• your description of what happened

We do not ask for your name, email address or phone number when you submit a report, and there is no field in which to provide them. Please do not put personal information into the description — if you do, a moderator will reject the report.

The contact form is the one place on this site that asks who you are. It is separate from reporting a number, and using it is entirely your choice.

When you send a message we store the topic you chose, your email address, the phone number you tell us the message is about if you give one, and what you wrote. Your email address is stored as you typed it, because replying to you is the only reason we ask for it. We do not add you to a mailing list and we do not pass your address to anyone else.

Messages are read by the same moderators who review reports. They are not published, they never appear on a number page, and nothing you write here becomes a report.

Your message carries the same irreversible hash of your IP address described below, so repeated misuse of the form can be recognised without anyone seeing an address.

Like any web service, CallsAlert sees the network requests made to it. We use this for abuse prevention and to keep the service running.

• Your IP address is used to rate-limit searches and report submissions and to detect duplicate submissions. It is stored only as a keyed, irreversible hash — never in a readable form, and never shown on any page.
• The web server keeps standard access logs, which include IP addresses, for a short period so we can diagnose faults and investigate abuse.
• We record which reports were approved or rejected, and by which moderator, so moderation decisions are accountable.

Whether this site measures visits or shows advertising depends on how it has been configured, and you can tell which by whether you were asked for consent.

If you were not asked, neither is switched on. The public site then loads nothing from a third party and sets no cookies at all.

If you were asked, CallsAlert loads Google Analytics, Google AdSense, or both. They arrive with every storage, advertising and personalisation signal set to denied, and they stay denied unless you accept. Declining is a complete answer, and the site behaves the same either way. Your answer is kept in a single cookie so you are not asked again on every page; it holds nothing but that answer.

Administrators who sign in to the moderation tools receive a single session cookie. It is strictly necessary for signing in, contains only an opaque random token, and is not used for tracking.

Because reports are anonymous, we apply rate limits and duplicate detection to keep the service usable. These rely on the hashed IP described above. If the site is configured to use a challenge such as Cloudflare Turnstile, that provider will also see your IP address as part of serving the challenge.

An approved report is published showing its category, description, approximate date, and whether the call was answered. Nothing that identifies you is published alongside it.

Reports that originate from an imported dataset rather than a member of the public are labelled as such on the page.

If a moderator edits a report — usually to remove personal information someone included — the report is labelled as edited, and the previous wording is not retained. Keeping it would preserve the very detail the edit removed, in our database and in every backup of it.

Moderators can see the full content of submitted reports, including those still pending or already rejected, and the hashed identifier attached to a submission. They cannot see raw IP addresses through the application.

• Approved reports are kept for as long as the number page exists, since they are the service.
• Rejected reports are kept for a limited period so the same submission is not repeatedly re-reviewed, then removed.
• Rate-limiting records expire automatically, typically within an hour.
• Server access logs are rotated and deleted on a short cycle.
• Messages sent through the contact form, and the email addresses attached to them, are deleted within 12 months of being resolved.

If a number belongs to you and you believe a report about it is inaccurate, or you would like a page removed, contact us and explain the situation. We will review the reports in question and remove anything that fails our moderation standards.

Because reports are anonymous, we generally cannot locate a specific report on your behalf from your details alone — telling us the number and roughly when the report appeared helps.

If this policy changes materially, the date at the top of this page will change with it.