Your conversations stay off our server.
Screenr connects you to your friends. Calls, screen shares and messages travel directly between your devices, with end-to-end encryption. Our server handles account and connection details, but never receives your conversations.
Where your conversation goes.
Screenr uses direct connections. The second diagram shows a server-routed model; other apps may use either approach or a mix of both.
- Metadata only: your username, friends list, which room you are in
- Voice, video, screen and messages, straight from device to device
- Calls and messages pass through the provider’s servers
- Encryption and storage depend on the service
What’s stored, and where.
An overview of account data and device storage. See the privacy policy for full details and retention periods.
- Username and password
- The password is stored only as an Argon2 hash. No email, no phone number, no real name.
- Signed-in devices
- A device ID, name and session details let you manage signed-in devices in Settings → Account. Sessions expire after 30 days of inactivity.
- Two-factor sign-in
- If enabled, your authenticator secret, setup and last-used details, and hashed recovery codes.
- Friends and invites
- Who you are friends with, and requests that are still pending.
- Servers, rooms and channels
- Names, owners, memberships and invites. Channel messages stay on participants’ devices.
- Presence
- Your status and last-seen time. While invisible, your last-seen time does not change.
- Current room
- Your room and screen-sharing status, held only while you are connected.
- Web server logs
- IP addresses, request times and requested URLs, kept for 7 days.
- Operational logs
- Connection events with user and device IDs, kept for 7 days for troubleshooting. No message or call content.
- Messages and reactions
- On the devices of the people in the conversation, encrypted on disk with a key from your operating system's keychain.
- Encryption keys
- Generated on each device. Other devices remember the key when they first connect directly.
- Your sign-in token and settings
- Stored locally, with the sign-in token encrypted by your operating system.
Screenr does not record calls or screen shares. Participants can still record with other software.
What to look for in a chat app.
Apps handle privacy differently. Here’s how Screenr works and what to check when comparing services.
Less data on our server
Screenr’s server has no copy of your conversations. It does hold account data and operational logs, as described above. Check each service’s privacy policy for its storage and retention practices.
What to know before you connect.
Direct connections affect who can see your IP address and when messages arrive. Calls may fail on networks that block direct connections.
People you connect to can see your IP address
People you call or message can see your IP address because their devices connect directly to yours. Only connect with people you trust with it.
Connection services see your IP too
Screenr uses Google or Cloudflare STUN servers to find your public address. They see your IP address and the lookup request, but not your conversations.
Offline messages need a device online
An offline recipient gets a message when they connect while a device with a copy is also online. For direct messages, that means one of your devices; for channels, any member’s device can deliver it.
Manage your devices and data.
Sign out a device
Go to Settings → Account to see your signed-in devices and sign any of them out.
Delete local message history
Remove Screenr and its data folder to delete history from that computer. Copies on other participants’ devices remain.
Delete your account
You can remove your account from within the app. The account, its sessions, friendships and memberships are then removed from the database. Under the GDPR you can also ask for a copy of everything above by emailing emil@codeboss.se.
Last updated 23 September 2026. Changes to data handling are included in the release notes. Read the privacy policy for full details.