Most platforms bury privacy in a menu. Steppe is building it into the beta: no ads, no behavioral trackers, and no business model that depends on your information.
Steppe's model does not sell member information. The beta is free; planned member subscriptions fund the service instead of advertising.
No third-party trackers, no advertising pixels, and no behavioral profiles. Nothing watches what you do in order to sell you something or to someone later.
The beta is not yet accepting residency proof. Before it does, deletion after review and orphan cleanup must be verified end to end. The retained record will contain only the verification result, date, and method. It will not contain the document or legal name.
Every personal field starts hidden. You choose, one at a time, whether it is visible to no one or to all members. Your verification status stays visible. If you are a moderator, that role stays visible too.
The intended app limits a conversation to its two participants and gives moderators no message reader. Reliable account deletion and session revocation remain beta launch gates. A safety excerpt another participant chooses to report may remain as report intake.
Before beta invitations, Steppe must verify that account export is complete, deletion removes ordinary account data and sent messages, sessions lose authority, and only minimized integrity records remain.
You choose whether to record technical steps for a bug report. Up to 100 events from the last 10 minutes stay in this page session until you choose to send them. These describe pages, actions, and errors without typed text, private messages, sign-in codes, or screen recordings. You can review or omit diagnostics. Submitted reports are private to designated Steppe support, expire after 30 days, and are deleted by scheduled cleanup. Reports sent while signed in are included in account export and deletion. Support email alerts contain a reference and sign-in link, without the report content. Downloaded copies and provider backups follow their own retention settings.
Only what the beta needs to run a verified community designed for member governance. Nothing is kept “just in case.”
This page describes the privacy behavior Steppe intends to verify before opening the beta, not a claim that every control is already production-ready. Gregory Chism handles member data. Ignite handles sponsored responsibilities other than member subscriptions, and either Gregory or Ignite may handle a contract when that contract names them. Residency-proof cleanup, complete export, account deletion, and session revocation remain launch gates. The full draft policy carries the formal detail.
Full policy: www.steppe.community/legal/privacy
Questions: Contact us
The full legal policy is available in English, and the English version governs.