Share only what you want to
A profile, an intent, a request, a conversation and an agreement are enough to begin. Do not enter documents, payment information or other sensitive details.
Your data is stored on the server. Closing the tab does not delete these records.
Private ideas and publications have different visibility
Saving a private intent does not publish a card. Once you explicitly publish it, other participants in that environment can see the details shown on the card.
Use a general area instead of your home address. Agree the exact meeting point and time in the contextual conversation after a request is accepted. Other participants can independently save messages they receive.
What the service stores
The environment can retain profile information and settings, published intents, requests and decisions, messages, proposed meeting details, outcome confirmations, blocks and reports.
A cookie containing a session identifier that JavaScript cannot read is used to maintain the session. It identifies the current session rather than tracking people for advertising. The final list of technical data and retention periods must be checked against the environment before launch.
The map loads only when you choose it
You can explicitly load an OpenStreetMap map to choose a convenient place. The third-party provider then receives technical requests for map tiles; these can reveal your IP address and the area you are viewing.
Message text and the exact place label are not sent to the map provider in this flow. The viewed map area may still indicate the meeting neighborhood. You can instead enter a place and coordinates manually without loading the map. The precise agreement stays available to accepted participants; the public card shows only the general area.
Controls in settings
The service provides settings, an export of your own data and profile deactivation. Deactivation should not be read as immediate erasure of every record: final retention and deletion rules still need to be defined.
Blocking stops further permitted contact in the product. It does not recall copies of text another person may already have saved. Optional analytics requires separate consent; message text is not input to those events.
What must be completed before public launch
The owner must identify the operator and a contact for requests, applicable legal bases, specific retention periods, infrastructure providers, processing locations and procedures for exercising user rights.
Confirmed procedures are also needed for handling reports, team access to data and incident response. This draft does not claim legal compliance, anonymity or end-to-end encryption.