Privacy
Letsgoout is a board for plans happening tonight. This page describes the data used by the account service, the public board, and private messages.
Your account and backups
The account service stores your email address, username, a password hash, account creation time, email verification status, a hash of your current password recovery code, and your linked Nostr public key. Your password and recovery code are not stored in readable form. The code is shown when you sign up and after a password reset; each reset replaces it.
Your Nostr secret key is generated or imported on your device. On the web, an encrypted copy is stored in this browser using a password-derived key. The unlocked key is held in this tab’s session storage for up to 24 hours. The Nostr secret key is not sent to the account service. Keep its nsec backup: a password reset cannot decrypt an existing browser copy without the old password and cannot restore the key on a new device.
The account service issues a session token to sign you in. On the web it uses a secure HTTP-only cookie where the browser accepts it, with a token kept only in tab session storage for browsers that block the cross-site cookie. Signing out clears the local session and asks the server to revoke it.
Plans and location
Board posts contain the text and profile details you choose to publish, your public key, a time, and a coarse location cell used to show plans within about 50 miles. You may also add a place label and photo. The board does not publish your precise device coordinates. Posts expire after 24 hours and the relay removes expired events in its regular cleanup cycle.
Private messages
Message text is encrypted on your device before it reaches the relay. The relay stores encrypted messages and delivery information, including recipient tags and timestamps; it cannot read the message text. The web client requests the latest 14 days of messages. The current relay cleanup may remove encrypted messages after 7 days, so message history is not a backup.
Safety and operation
Blocking creates a list tied to your public key so it can work across devices; the relay operator can see that list. Reports you send to the operator contain the reported public key, optional event ID, reason, time, and network address. Reports are removed from the relay database after 90 days. The service also processes network addresses to operate and rate-limit requests.
Local browser settings, including your saved area, profile answers, filters, photo, and read marks, remain in your browser under your Nostr public key. Published profile answers and photos are included in posts when you choose to post. Clearing this site’s browser storage removes local copies but does not erase data already sent to the relay or account service.