Privacy is not an add-on. It is the foundation of SafeSteps.

SafeSteps shows patterns of unsafety without revealing identity, exact locations, or public descriptions of reports.

  • No account
  • No GPS
  • No public descriptions
  • Approximate zones

How SafeSteps protects your privacy

01

We do not ask for identity

No account, name, email, or phone number is required to submit a report. We never ask for a public identity or credentials that could link the report back to you.

02

You choose the location manually

SafeSteps does not use GPS and has no “current location” button. You choose the location by clicking on the map.

03

The exact point is not stored

Before storage, the location becomes an approximate area of about 100 m. Publicly, zones are shown — not precise points.

04

Descriptions are not public content

Incident descriptions are used only by moderators to review reports. Descriptions are not shown on the public map and are not used for public statistics.

05

The map shows patterns

Only approved reports appear on the public map as grouped approximate zones. The community sees patterns and counts — not individual stories or descriptions.

Technical notes

OpenStreetMap — map

The map uses OpenStreetMap tiles. Loading the map sends standard web requests to OpenStreetMap project servers.

This may reveal the IP address of the device you use to access the app. SafeSteps does not control or log this traffic.

More information: openstreetmap.org/copyright

Cloudflare Turnstile — bot protection

The report form uses Cloudflare Turnstile to protect against automated submissions. This sends limited technical data to Cloudflare when submitting the form.

Turnstile is designed not to use tracking cookies.

Technical cookies

SafeSteps may use a technical cookie to remember the selected language. This cookie is not used for tracking and does not contain report data.

SafeSteps may use a technical cookie to remember the selected visual theme. This cookie is not used for tracking and does not contain report data.

SafeSteps may use a technical cookie to remember that the welcome experience has already been shown. This cookie is not used for tracking and does not contain report data.

IP address

The app does not store user IP addresses. Rate limiting uses a temporary in-memory HMAC pseudonym instead of raw IP.

This key is not a raw IP address, is not written to disk, and is deleted after the time window expires.

Reports cannot be changed after submission

Once you submit a report, it cannot be edited or deleted by you. This protects the integrity of the record and your anonymity.

If you made a mistake, contact the SafeSteps team through the contact section below.

What does the public see?

Moderators see:

  • Description
  • Approximate location
  • Optional structured fields

The public sees:

  • Approximate zone
  • Incident category
  • Count within a group

Understand how we protect data?

Report a location