Privacy

In short

  • We count visits and actions anonymously to improve the site. We never track you as a person. Browsing events needs no account and tells us nothing about you.

What we never do

  • You never need an account to browse or RSVP (churches have accounts to post events; see below). We use no tracking cookies, advertising pixels, Google Analytics, session recording or heatmaps.
  • We never store or pass on your IP address. Fonts and images are served from this site: event photos from church websites are fetched by our server, so your browser never contacts those sites until you choose to follow a link.
  • Your location: you choose a city or neighborhood, or tap “Use my current location”. Your browser then shares your position with this page once; we round it to about a kilometre and keep it in a cookie on your device so we can show distances. It is never stored on our servers or sent anywhere else.
  • The Map view loads map images from OpenFreeMap, a free map service built on OpenStreetMap. When you open the map, your browser contacts their servers, which see your IP address and the area you are looking at. The rest of the site never contacts them.
  • Our visit counts run on our own analytics server and contain only which page was viewed and simple actions such as "a form was sent". If your browser asks sites not to track you, we count nothing at all.

What the contact form collects

  • An optional name, your email, the topic you choose and your message.
  • Your name, email and message are encrypted on our server before they are saved. The website itself cannot read them back; only a separate key held for our team can.
  • To stop spam we use Cloudflare Turnstile on forms, and short-lived rate limits keyed on a scrambled, irreversible form of your network address that we never store.

“I’m going”

  • You do not need an account. The first time you tap “I’m going”, we create an anonymous ID for this device (no name, email or phone) and keep it in a cookie. Your RSVPs are linked only to that ID, so the Going tab works and events can show how many people are going.
  • Clearing your browser data removes the ID from your device; the RSVPs left behind cannot be linked back to you.

Adding an event or inviting a church

  • We ask for your email so we can check the event or reach the church. It is encrypted before it is saved and is never shown on the site.
  • Rejected submissions are deleted after 30 days.

Church accounts

  • Only churches need an account, to post events and manage their church page. Visitors never do.
  • We keep the account email and a password handled by our sign-in provider (Supabase); we never see the password.
  • To verify a church we ask for your name, your role, a phone number and an optional note. These are encrypted before they are saved and only our review team can read them. The church name, address, website and service times you give are shown publicly on the church page once approved.
  • Rejected applications are deleted 90 days after review. For approved ones, your name, role, phone and note are deleted 30 days after approval. You can ask us to delete your account at any time.

Church events we list

  • Events come from public church web pages and calendars, and from churches and visitors who submit them. Every event links back to its original source.
  • Our crawler identifies itself, respects robots.txt and waits between requests. Churches can ask us to stop listing them at any time (see the For churches page).

When it is deleted

  • Messages are deleted 90 days after we handle them. Messages left untouched are archived after 180 days.
  • Anonymous feedback is deleted after one year.

Contact

  • Questions about privacy: hello@example.com