Privacy

What we keep about you

As little as we can. There are no accounts, no cookies and no advertising trackers on this site.

Reading the site

  • No cookies. We set none, and no third-party tracker runs on our pages.
  • Page counts. We count how many times each page is opened per day. The count is the page address and a number: no IP address, no browser details, nothing that tells one visitor from another.
  • Fonts. Our typeface is loaded from Google Fonts, so your browser asks Google's servers for the font files and Google sees your IP address when it does.
  • City photos are served from our database provider's file storage.
  • Pictures beside news reports come from the publisher's article. We keep a small copy in the same file storage, so your browser never contacts the publisher to show it; following a source link takes you to the publisher's site.

The two community questions on city pages

When you answer “Would you wear a Magen David here?” or “Could you be visibly observant here?”, we store the city, the question, your answer and a one-way marker made from your network address and browser type with a secret key. The marker lets us count one answer per device. It cannot be turned back into your address, and we do not store the address itself.

What you send us

  • Asking us to add a city: the city, the country and, if you give it, your email, so we can tell you when the city is live.
  • The contact form: your name if you give it, your email and your message, so we can reply.
  • Reporting an incident: where and when it happened, what kind of incident, your description and, if you give it, your email. Only our review team reads it. If we publish the incident on the feed, we publish where, when and what kind of incident it was, never your words or your email.
  • The weekly email: your email, the cities you chose, when you confirmed and, if you leave, when you unsubscribed, plus a record of each weekly email we sent you. Every email has an unsubscribe link, and unsubscribing stops the emails at once.

Each of these is stored in our database and copied by email to our team's shared inbox. To stop the same network flooding a form, we keep the network address of each form post in memory for ten minutes; it is never written down.

Who handles it for us

  • Railway runs the website.
  • Supabase holds the database, the city photos and the news-report pictures.
  • Resend sends our emails.
  • Google Fonts serves the typeface (see above).

We do not sell or share what you send us with anyone else, and we never use it for advertising.

Seeing or deleting your data

To see what we hold about you, correct it or have it deleted, write to us through the contact page.