If you are in immediate danger, call emergency services immediately. In Austria and across the EU the emergency number is 112.

πŸ—„οΈ Safety Hub

Data Governance: Privacy Architecture & Zero Tracking

How Double Stop handles your data β€” from the database schema to the nightly deletion job.

Last updated: May 2026

The most important privacy decision on Double Stop is not in the Privacy Policy. It is in the database schema.

When you place a pin on the map during post creation, two coordinate values are stored: latitude and longitude. These are used for exactly one purpose β€” rendering the approximate area on a map so a nearby person can get a sense of your general neighbourhood. They are never passed to an advertising network. They are never cross-referenced with your device ID or browsing history. They are never sold. They disappear, along with the rest of your post, after one hour.

The location data visible to other users is entirely text-based. Before anyone chooses to unlock a post, they see only a city name and country. Nothing more. The detailed location field β€” the table number, the bench in the park, the coffee shop on the corner β€” remains locked behind the unlock interaction until someone actively chooses to engage. This is the specific inversion of how most location-based apps are designed. Most apps share everything by default and let you opt out. Double Stop shares nothing by default and lets you opt in.

There are no tracking cookies on this platform. The only cookie in use is the session token β€” an httpOnly value that identifies you if you have chosen to create an account. It carries no advertising identifiers and cannot be read by third-party scripts. If you use the app without an account, no cookie is set at all.

The automated data lifecycle is equally straightforward. Posts expire after one hour and vanish from the public feed. The underlying record is moved to a private archive and retained for exactly 90 days under Austrian law for potential law enforcement cooperation, then permanently deleted. A scheduled job runs at 03:00 UTC every night β€” automatically, without exception, and without manual override.

No analytics fingerprinting. No pixel tracking. No third-party data enrichment. The engineering constraint is simple: collect only what is necessary for the product to function, and delete it on a fixed, non-negotiable schedule.

That is the complete data model. There is nothing hidden in it.

β€” Aki

By using Double Stop you accept full responsibility for your own safety during any in-person interaction. Double Stop is a neutral platform and is not liable for the actions of any user. For full details see our Terms of Service and Privacy Policy.