Om oss

You can send a name, a correction, a photo or a removal request without creating an account. Your own name and email are optional — leave them blank if giving them could put you at risk. Everything you send is read by a person before anything on the public site changes. Prefer the secure form on this website for files: the site says files are encrypted as soon as they arrive and are not published without your permission. If you are inside Iran, also read the tips below. See Privacy and For families.

It depends which form you use:

• Submit a name / evidence: what you chose to send about the person (name in Latin and/or Persian, city, date, age, your message, links, files). Your contact field is optional. Checkboxes (defaults on the live form): remove location data from photos before sending (on); share files with human rights organisations for verification (on); allow publishing files on the person's page (off unless you tick it); give your contact details to a verifying organisation (off unless you tick it).
• Contact: topic, message (required). Name and email are optional — leave an email only if you want a reply.
• Memorial message (on a person's page): your message, and name optional. Messages are moderated before they appear.
• Reading the site: you do not need an email. Display choices (theme, language, low-data, cookie choice, saved names) stay in your browser on your device unless you sign in.

We do not ask for home addresses or ID numbers, and /method states the archive never publishes home addresses, ID numbers or details about living relatives.

Visitors only see what is published on a person's page after review. What you send — your message, files and any contact details — can be opened only by the archive's editors and administrators, signed in with a password and two-step sign-in. Volunteers never see submissions. Files you upload are encrypted on our server as soon as they arrive, each with its own key.

Information about the person (not about you) may be shared with human rights organisations so they can verify it, if you leave that box ticked on the form. Your own contact details are never passed on unless you tick that box.

Photos and videos can carry hidden data (place, time, phone model). On the form, "Remove location data from my photos before sending" is on by default: your browser removes it before anything is sent.

On our side, every photo that editors work with or that is ever published is a fresh copy made by the server, without camera or location data. The file exactly as you sent it is kept only in encrypted form for verification and is never published. Videos are not cleaned on the server, so remove location data from videos yourself if you can.

Submissions and their files are kept, encrypted, for as long as they are needed to document and verify the record; they are not published unless you allowed it. There is no automatic deletion date yet. Your IP address is never stored — only a one-way code used to stop abuse of the forms.

To have something you sent deleted, write to info@theiranmassacre.com or use the contact form and include your submission code (shown after sending). To correct or hide a published record, use Submit — a request to hide takes it off the public site straight away while it is checked.

/privacy says: visitors' IP addresses are not kept; to stop form abuse the site stores only a one-way hash that cannot be turned back into an address. Reading the site needs no tracking cookies. Theme, language, low-data mode, saved names and cookie choice are stored on your device (not sent as TIM tracking cookies). A session cookie is set only if you sign in (tim_member), and admin sessions use tim_admin. Cloudflare may set __cf_bm / cf_clearance for attack protection. Embedded YouTube / Instagram / TikTok / Telegram content loads only after you press play and those services may then set their own cookies.

From response headers on the live site (19 Oct 2026): HTTPS with Strict-Transport-Security: max-age=31536000; a Content-Security-Policy that keeps scripts on 'self' and allows frames only for those embed hosts; X-Frame-Options: DENY; Referrer-Policy: strict-origin-when-cross-origin; Permissions-Policy disabling geolocation/camera/microphone. An anonymous GET did not set a Set-Cookie header.

Yes. No account is required. Leave name, email and contact blank. Prefer public links as sources rather than anything that identifies you. A VPN can help but does not make a submission safe on its own. Remove location data from photos when you can. Do not put your real name, phone number or home address in a submission.

For sending details of Javid Naam (victims) through social apps, prefer a private channel to the archive rather than a public post: use the website form when you can; otherwise a private message to the official accounts below — or use the Telegram submission bot @TheIranMassacreBot over posting in the public channel. Do not post victim details publicly on X or Instagram if that could put you or the family at risk.

Official accounts (from this site): X @theiranmassacre · Instagram @theiranmassacre · Telegram channel. Telegram submission bot: @TheIranMassacreBot.

Yes. The safest options, in order: the website form; then our Telegram submission bot @TheIranMassacreBot; then a private message to our official accounts — X, Instagram or the Telegram channel.

• Use only the accounts linked from this site.
• Never post victim details publicly if it could put you or the family at risk.
• For files, the website form is better: it encrypts them on arrival.

@TheIranMassacreBot is our official way to send details and photos from Telegram. Messages go to the archive team and are read by a person before anything public changes, like the website form. Open it from a person's page and the bot already knows which record you mean. Use the same care as everywhere: no real name needed, remove location data from photos if you can, and never post the same details publicly.

You do not need an account or an email to read the site. /privacy says raw IP addresses are not kept. A VPN can help but is not enough on its own — never send anything about yourself that could identify you unless it is needed. Embedded third-party videos load only after you press play.

An independent archive of people killed in the crackdown on the Dey 1404 / January 2026 protests. It is not a complete list and it does not produce a final death toll. The site also documents related repression that can be checked: a day-by-day timeline, executions and death sentences, prisoners, videos, a map and statistics, and a section on regime forces. Start from the [homepage](/) for the live count of names recorded.

A small team of volunteers. For their safety we don't publish team members' names. Every change is read by an editor before it's published. More on the How we're run tab. TIM isn't registered as an organisation yet; we'll add those details here once it is. Contact: info@theiranmassacre.com.

TIM is currently paid for by its founder. Everyone who helps does so as an unpaid volunteer. We don't take donations or have paid membership.

It is the count of names recorded here with a source, not an estimate of everyone killed. The figure changes as lists arrive and duplicates are resolved — always use the number shown today on the [homepage](/) or /stats, and say the date you saw it (see /press). Names at tier D are included in the total of names recorded but not in the confirmed (A–C) figures until verified.

The blackout, pressure on families, bodies withheld or delayed, different definitions of “killed in the protests”, and different verification methods all produce different figures. We do not hide that, and we do not average them. Other organisations' figures are quoted under their own names.

As on /method: A — two or more independent lists; B — one trusted list; C — family and witnesses; D — not yet verified (shown clearly marked so people can help). D names count in the total of names recorded, not in confirmed A–C figures, until a recognised human rights organisation verifies them. Live counts per tier are on /method and /stats — do not copy old numbers into this answer.

No. If a name is also on that list, the record says so, but the list never confirms a person on its own.

Yes, as a helper. AI tools find leads, standardise spellings, flag possible duplicates and draft translations of the site. They never publish anything: an editor approves every change.

A name that comes only from an AI-compiled list is shown at evidence level D, marked as needing verification. It is part of the total of names recorded, but not of the confirmed (A–C) figures, and it only moves up when a recognised source confirms it.

The name may not yet have a source we can check, it may be waiting to be matched, or a family may have asked for it to be hidden. You can send it through the form or, with care, through the official social channels (see Safety).

If a match is not certain, both records stay until a person reviews them. Uncertain merges are never done automatically.

A photograph is saved only when it comes from a page already about that person, on a source the site trusts. Photographs are never searched for by name alone.

The site is published in 13 languages. Open Settings for language, light/dark theme, low-data mode, account, install the app, and cookie choices. Display choices are stored on your device.

No account is needed to read or submit. If you create one, you can stay signed in (session cookie) and use Saved names to keep a private list on the device / account. Signing in is optional.

Yes, on each person's page: write a message; your name is optional. Be kind — no personal attacks, private details or phone numbers. Messages may be removed by moderators.

Persian pages show dates in the Iranian calendar; other languages use Gregorian. 8 and 9 January 2026 are 18 and 19 Dey 1404.

Use Submit (choose correction or the family removal option) or email info@theiranmassacre.com. If you are inside Iran, do not leave contact details. A request to hide a record takes it off the public site straight away, then someone reviews it. You will never be asked to prove the death or that you are family.

Some were filmed by protesters and witnesses; others are documentaries. Each video links to where it was first published.

If you quote a figure, use the count on the homepage, say the date you saw it, and link to /method. Quote other organisations' figures under their own names, not as this site's count. Questions: info@theiranmassacre.com. Logos for illustrating a report about the archive are listed on /press.

The public statistics and the CSV downloads on Statistics are licensed CC BY 4.0: reuse them with credit to "The Iran Massacre" and a link. Photos belong to their families and sources, so ask before reusing them.

There is no public API at the moment. The archive's API is open only to trusted sources we work with, with keys we issue. Please don't scrape the site; write to info@theiranmassacre.com if you need data.