Roomly · India
Privacy Policy
Effective 2026-10-28
Your calls
Roomly provides private audio and video hangouts for up to six people. We do not record audio or video calls. The optional RoomlyShot feature can compose one still image from consenting participants’ Roomly video tiles. It does not record audio or video. A photo is uploaded only when its initiator explicitly saves it to the private group gallery. Live WebRTC media is processed by participants and Cloudflare media services. Other participants may record using their own devices. Transport is encrypted; calls through the media service are not described as end-to-end encrypted against that service.
Camera, microphone and profile photo
Camera and microphone permissions are used for the calls you choose to join. Background camera capture pauses; a foreground service can keep active audio working with call controls. Leaving stops local capture. An optional profile photo is resized in private device storage and stays on your device. The Android system picker gives access only to the photo you select.
No account needed for basic joining
You can join using a nickname. Roomly does not require a real name, email address, phone number, OTP, password or contact list for basic joining. Optional Google sign-in is available only for paid account recovery where configured.
Pseudonymous device identity and security
Roomly uses a pseudonymous app/device identity, installation public key and Google Play Integrity security signals to enforce allowances, prevent fraud and keep the service reliable. Raw Android ID is not uploaded, stored or logged on the backend. Clearing app data normally reconnects to the existing server allowance. Different devices or profiles may have separate allowances. Optional Device Recall, if enabled and available, holds limited coarse anti-abuse state with Google; exact usage remains on Roomly's backend.
Usage and technical connection information
The service processes usage duration, media type, connection status, participant counts and necessary network information. The backend controls time allowances. New technical duration ledgers retain entries for a configurable period, currently 30 days. Current quota and identity records persist for continuity. Network providers process IP addresses; direct peer calls can expose network addresses to the other participant.
Private rooms, groups and games
The backend stores room/group names, chosen nicknames, invitation capabilities, membership, roles and general presence to operate private hangouts. Public invite pages do not show member lists, participant names or private presence. Games use the existing room connection and store official questions, recent question history and private aggregate scores. Spoken Truth or Dare responses are not collected by the game feature. Temporary round responses are cleared and do not become a personal response history.
Widgets, group streaks and Game Nights
An optional home-screen widget keeps a small local group summary, without authentication tokens. Count only is the default; names require a separate choice for each widget. Minimal display is available. The widget uses app synchronization and event-triggered refresh, with occasional one-time stale/schedule updates. Group streaks use backend presence observations and aggregate group dates, weekly streaks and total qualifying hangouts. Short-lived connected-member observations establish continuity and expire within two minutes. No permanent individual attendance or exact last-seen history is created for streaks. Group Game Nights store the selected games, date/time, group timezone, recurrence and members’ voluntary RSVP choices. Completed or cancelled event history is retained for up to 90 days by default and may be removed earlier by the bounded history limit. Positive group milestones retain aggregate counts, not private game answers.
Optional RoomlyShots and private gallery
Its default is Ask every time. Always hide me and Allow when I’m in the room are local preferences; even Allow requires a visible countdown. Missing consent, interruptions and Hide Me exclude that participant’s video. Hidden or camera-off tiles use initials. Capture reads only Roomly-owned video tiles, without MediaProjection, microphone audio, other apps, notifications or location metadata. Temporary frames and previews remain in memory. Discard does not upload an image. Explicitly saved photos use private Cloudflare R2 storage and authenticated current group membership; there are no permanent public photo links. Stored metadata includes the group and photo identifiers, creator and visible members’ group identifiers, hidden-member count, creation time and image dimensions/size. Group members can explicitly download or share a photo; copies exported to someone’s device cannot be recalled by Roomly. The creator, group owner or a visibly included member can remove a photo. Deletion immediately blocks new gallery reads and queues physical object cleanup with retries. Group deletion removes its gallery, streak and scheduled events. Verified account deletion removes photos created by or visibly including the deleted member. Leaving a group immediately removes gallery access; shared photos may remain for other members. Former members can contact support@roomly.sbs for removal, using the group name, approximate date and photo reference if available. Support privately verifies requests before removal. Private operator tools cannot be used by other app members. Gallery photos otherwise remain until deletion or the group’s storage limit; uploads stop when the limit is reached. RoomlyShot creation is available in paid-hosted hangouts: Plus allows two photos and Friends three photos per active session, shared by the room. Free-hosted sessions cannot create RoomlyShots. A count is consumed when the backend authorizes the final capture, including a photo later discarded or saved only to a device. Deleting a photo does not restore the session allowance.
Optional notifications
If you enable notifications, Google Firebase Cloud Messaging and Firebase Installations process delivery identifiers. Roomly stores the encrypted push token, permission state and notification preferences. Notifications use private local display by default. You may opt into fuller available details when unlocked; lock-screen public previews stay generic, subject to Android settings. Delivery payloads may contain a private group name, nickname, general activity and an expiring recipient-only link. Game Night reminder text is generic. They contain no call audio or video. You can decline notifications, mute a group or set quiet hours and still use calls. The notification SDK also processes application and SDK versions and necessary device metadata to provide and maintain message delivery. Advertising analytics and BigQuery delivery-metric export are not enabled.
Google Play subscriptions and top-ups
Google Play processes purchases. Roomly verifies purchase tokens and stores encrypted purchase references, entitlement, seat and usage records. Roomly does not receive full payment card details. Optional paid recovery stores a pseudonymous Google identity reference rather than your email, name or photo. Uninstalling does not cancel subscriptions; cancellation and platform refund requests are handled through Google Play. Google sign-in can deliver basic profile fields inside a temporary signed authentication token. Roomly keeps only the pseudonymous identity link and does not retain that token, Google email, name or profile image as a service profile.
What Roomly does not collect
Roomly does not collect IMEI, SIM serial, phone number, contacts, Wi-Fi MAC or Bluetooth MAC, or use invasive device fingerprinting. Roomly does not record call content. Its default analytics/crash adapters send no events. The website has no advertising trackers or analytics cookies. Google advertising services may process advertising identifiers and other technical data as described below.
Advertising and your choices
An advertising-enabled version of Roomly includes the Google Mobile Ads SDK and Google User Messaging Platform (UMP); other versions may not include them. If ads are enabled, Free users may see clearly labelled ads in eligible parts of the app. Plus and Friends users and participants in paid-sponsored groups are intended to have an ad-free experience. No banner, native or interstitial ads are intended to interrupt a call or game. A future optional reward feature, if introduced, would require a participant to choose it and any required policy approval; it is not currently available. Depending on configuration, device settings and your choices, Google and its advertising partners may process your advertising identifier when available, IP address and IP-derived approximate location, app and device information, ad interactions, consent choices, and diagnostic information to serve, measure, secure or improve advertising. Google and its partners process data under their own privacy terms. Roomly does not intentionally include private room names, invitation links, game answers, call audio or video, or RoomlyShot content in ad request parameters. Where required, Roomly uses Google's consent interface and offers ad privacy options in Settings. In eligible US states, the privacy options are intended to allow users to opt out of applicable sale or sharing of personal information for targeted advertising. In the EEA, the UK and Switzerland, the consent interface offers choices for applicable advertising uses. You can revisit available choices through Settings → Privacy → Ad privacy options when this entry is required. You may also control or reset your device's advertising ID through Android settings, subject to your device and Android version. Declining personalized ads does not necessarily remove all ads. Roomly is the publisher responsible for this policy. Depending on where you live, you may have rights to request access, correction, deletion, or other choices about personal information. Contact support@roomly.sbs for privacy requests. Roomly verifies requests before acting. Rights and available options depend on applicable law and the actual service configuration.
Providers and storage
Cloudflare provides backend and media infrastructure. Google provides Play Billing, Integrity, optional paid recovery, optional push delivery, advertising and consent services as configured. Local session storage is protected by Android Keystore-backed encryption and app backup is disabled. Private keys and backend service secrets are not shared in invitations.
Adults and safety reports
Roomly is intended for adults aged 18 and over. Users can report or block someone from the participant menu. Safety reports include the reason, optional submitted details and the account/room references needed to review the concern. Reports are encrypted at rest and available only to the Roomly operator. Roomly does not monitor or record private live calls. Do not send or redistribute illegal images or videos. Contact the publisher for safety or privacy concerns.
Your choices, retention and deletion
You can leave calls, change permissions, remove your local profile photo/history, mute notifications and manage subscriptions in Google Play. Clearing local storage does not erase backend records, reset quotas or cancel purchases. Use Settings → Safety & data to request account and associated data deletion, or use this website’s Delete account resource. Verified requests are processed by the operator. Profiles, memberships, scores, push tokens, recovery links, active device keys and owned room access are removed. Shared groups can remain for other members. Current-device profile data is cleared when completed status is refreshed. Encrypted purchase records are retained for up to 365 days; minimal pseudonymous purchase-ownership, quota and abuse-prevention records remain. Resolved safety reports and completed request records are removed after 90 days. Photo removal without deleting your account: https://roomly.sbs/delete-photo
Publisher and contact
Publisher: Roomly, India.
Contact: support@roomly.sbs.