Last updated: August 4, 2026
Stramly is built so that your video, audio, and chat never pass through, or get stored on, our servers — they travel directly between your device and the stranger you're matched with (peer-to-peer WebRTC). This policy explains exactly what information the Service does and doesn't handle, and why.
Session identifier. When you open Stramly, your browser generates a random session ID, stored in sessionStorage. It exists only to match you with another waiting user during your current tab session, is not linked to your name, email, or any real-world identity, and disappears when you close the tab.
Theme preference.Whether you're using light or dark mode is saved in your browser's localStorageso it persists across visits. This is a UI preference only and contains no personal information.
Matching queue data.While you're searching for a match, our server temporarily holds your session ID and connection ID in memory to pair you with someone else. This is not written to a database — it's cleared the moment you're matched, cancel, or disconnect.
On-device content detection. During a call, your browser periodically analyzes both video feeds using an automated classifier that runs entirely on your device — this processing never sends video, images, or any data to our servers or any third party. If it flags likely explicit content, your call ends automatically and a report (timestamps and the two anonymous session IDs involved, not any image or video) is logged the same way a manual report is. This detection is automated, not perfect, and can be wrong in either direction.
IP address. Like any website or app, your IP address is visible to our server as part of the underlying network connection, and to standard hosting/infrastructure logs — we do not separately log or store it ourselves. Because video calls are peer-to-peer, the stranger you're matched with can also see your public IP address through the WebRTC connection itself — this is inherent to how peer-to-peer video calling works, not something Stramly adds. A relay server that would hide this (a “TURN” server) is planned but not yet part of the Service.
To establish a peer-to-peer connection across most home/mobile networks, Stramly uses Google's public STUN servers (stun.l.google.com) for NAT traversal. This briefly exposes your IP address to Google's STUN infrastructure as part of standard WebRTC connection setup — no account or video/audio data is shared with Google in this process. Our hosting provider(s) may also generate standard infrastructure-level access/error logs as part of normal operation.
We don't have a database of user activity to retain. Session IDs live only in your browser and in server memory for the duration of matching/a call, and are discarded once your session ends. If you report an incident to us (see Section 6), we'll keep what you send us — and anything legally required, such as a CSAM report to NCMEC under our Terms of Service — for as long as necessary to act on it or as required by law.
To report abuse, or to ask a question about how your data is handled, contact vishnudabas2@gmail.com.
Stramly is not directed at, and must not be used by, anyone under 18. We do not knowingly collect information from minors. See our Terms of Service for our full policy on age eligibility and CSAM.
Closing your browser tab ends your session ID immediately. You can clear your theme preference at any time by clearing your browser's site data for Stramly. Because we don't hold an account or profile tied to you, there is no persistent personal data to request or delete beyond what's already described above.
We may update this policy from time to time. The “Last updated” date above reflects the most recent revision.
Questions about this policy: vishnudabas2@gmail.com