Privacy Policy – Roam

Last updated: 26 October 2026

At Interact Group Private Limited ("Roam"), your privacy is our priority. This Privacy Policy explains how we collect, use and share your data when you use the Roam mobile app ("App") and website ("Website"), together called the "Platform."

Who We Are: References to "we," "us," or "our" mean Interact Group Private Limited and/or the Platform. "You" or "user" refers to anyone using our Platform.

Your Choices: This policy explains how we handle personal information. Optional device access has separate choices. Content you share, upload or send to Roam to find places is processed automatically, as described under "External Retrieval and AI Processing". You can turn import processing off in Settings and still browse or save places manually.

Using Your Information: We use and share your information only as described in this Privacy Policy. We won't disclose your information without your consent, except as explained here.

We never post for you: Roam never posts anything on your behalf, on Instagram or anywhere else. When you message our Instagram account, our account may send automatic replies in that conversation (for example, to confirm a code or the status of an import); these come from our account, not yours.

This Privacy Policy works alongside our Terms of Use and Community Guidelines. If there is a conflict, this Privacy Policy takes precedence. It is published in accordance with the Digital Personal Data Protection Act, 2023 ("DPDP Act"), the Information Technology Act, 2000 and the rules made under it.

HOW DO WE USE YOUR INFORMATION

The following table lists the information we collect from you and how we use it:

Information collected	How we use it
Account Information: the unique account identifier, name and email supplied by Google Sign-In or Sign in with Apple, a Google profile image when provided, your optional uploaded avatar, and your age group and eligibility confirmation. Apple does not provide a profile photo. An Apple private relay email can be used. We do not require a separate Roam password. Instagram sign-in (optional): if you sign in by sending a one-time code from Instagram to our Instagram account, we receive your Instagram account's app-scoped identifier for our account and look up your Instagram username through Meta. We store these with digests (not the plain values) of the code and of a verifier kept on your device, timestamps, failed-attempt counts and a keyed hash of your IP address used for rate limiting. An account created this way has no email address and uses your Instagram username as its name.	To create and manage your account. To sign you in with Instagram when you choose to, and to protect sign-in from abuse. To confirm you are eligible to use Roam. To contact you about your account.
Profile Information: username (handle), home area and city.	To show your profile to friends and other users. To personalise hotspots and lists for your city.
Location Data (with your permission): your precise device location while you use the App. Optional background location (only in App versions that offer it): only if you turn it on in Settings and allow "Allow all the time" / "Always" location access, the App receives location updates when it is in the background or closed. Earlier App versions do not offer this and do not use location in the background. In Android versions that offer automatic visits, the only background use is automatic visits and saved-place reminders, described below. Automatic visits and saved-place reminders (optional, off by default, only in App versions and on our servers where they are available): only if you turn them on in Settings, accept the in-app disclosure and allow "Allow all the time" location access, the App collects your precise location in the background, including when the App is closed or not in use. Android shows an ongoing notification while this is on. Each location update (coordinates, accuracy, fix time, speed, time-zone offset and whether the device reports a simulated location) is sent to our server.	To show hotspots near you. To recenter the map when you choose. Visits are marked by you unless you turn on automatic visits. Automatic visits (optional): our server compares each location update with the places you saved. To check which venues are nearby, our server sends your coordinates to Google Places (Google Maps Platform). When you stay at one of your saved places for a sustained period, we record a private automatic visit: the place, arrival time, time last seen there and how long you stayed. Only you can see it. If you choose "Keep", it becomes a regular visit, which friends can see as described below; "Undo" removes it. Saved-place reminders (optional, turned on separately; also needs notification permission): a notification created on your device (not a push notification) after our server checks a location update, shown when you are near a place you saved and have not visited in the last 30 days, at most 3 a day and not between 10 pm and 8 am. We keep a record of which place we reminded you about and when, to limit reminders. We do not store the coordinates from these updates in our database or build a route history from them (see "Data retention"). To show your progress in each area. Keeping your map position current (optional; iOS and earlier Android versions only, not offered by Android versions with automatic visits): the App keeps only your latest position on your device (not a history) and uses it when you next open the map. Background updates in this mode are not sent to our server. You can turn any of these options off in Settings, or remove "Allow all the time" / "Always" location access in your phone settings, at any time. Signing out or deleting your account stops background location on that device. Turning automatic visits off does not delete visits already recorded; you can undo them one by one or delete all automatic visits in Settings.
Visit History: places you mark as visited, visit counts and dates, and optional private visit-journal photos you choose to save.	To show visited places and visit counts. To build your interests and rank top visitors at a place.
Saves and Lists: places you save and lists you create.	To show your saves and lists. To sort your places into automatic lists.
Google Maps and Timeline Exports You Upload (optional): a saved-places CSV or GeoJSON file, or a Timeline JSON file, that you exported yourself and choose in the App (up to 2 MB and 500 records). From it we keep place names, notes, coordinates, Google Maps links and place identifiers, and for Timeline place visits the visit start time. Route and activity records are excluded. We keep a fingerprint (hash) of the file to recognise repeat uploads; we do not keep the original file.	To show you a private preview, and to save places or mark visits only for the rows you select and confirm. Signing in with Google does not give Roam access to your Google Maps lists or Timeline; we only read the file you choose. If you search for a place to match a row, the search text and any exported coordinates are sent to Google Places. Imported rows are private and are not posted to your circle.
Content You Share: public reel or post URLs pasted or shared to the app; captions, location tags, notes, available transcripts, selected photos/carousel slides, and videos (including their audio) or sampled video frames; text you type with an import; and photos or videos you upload to Roam. Retrieval and transcript availability varies; we cannot guarantee access to every post. Public post links (in App versions and on our servers where it is available): when you paste or share a link to a single public Instagram reel or post with nothing else added, Roam reads only that post, as described below. This applies only if you have confirmed your age and are eligible to use Roam, and you have not turned import processing off. Share text that only repeats the same link is not added to the import. Instagram direct messages to our account: if you link your Instagram account or sign in with Instagram, you can send reels, posts or links to our Instagram professional account by direct message. We receive, through Meta, the messages people send to that account: the sender's app-scoped Instagram identifier, message identifier and time, message text (up to 5,000 characters) and shared attachments such as reel or post links, titles and media. Linking stores your app-scoped Instagram identifier with your Roam account.	To find the places mentioned in a reel and add them to your saves and lists. To keep your chosen imports in your Roam account. Google/Apple login does not identify your Instagram account. We do not retrieve all your saved Instagram collections. Public post links: only the post link is sent for retrieval. The post's caption, transcript, audio, video or photos, a limited sample of its public comments, its tagged accounts and its location tag may be retrieved and sent to the retrieval, AI and map services described below, to find the places in it. Your name, email and other account details, any notes, uploads, your home city and your device location are not sent, and we do not look up the creator's profile for these imports. If the post is private, deleted or unavailable, the import stops and nothing more is retrieved. Public posts can still contain personal information about the creator or people shown. Anything else you add, such as typed text, a different link or uploads, is processed automatically as described under "External Retrieval and AI Processing". To link your Instagram account when you send us a one-time code, and to turn reels, posts, links, text, photos and videos you send to our Instagram account into imports in your Roam account. Messages that contain only a code are used for linking or sign-in, and their text is then cleared. If you send content before linking, we hold it for up to 7 days so it can be added to your account if you link; otherwise it is not processed. We only receive messages that are sent to our own Instagram account. We do not access your personal Instagram inbox, other conversations, feed or followers, and we do not post or comment on Instagram.
Selected Photo Metadata (with your permission): location, capture time and selected asset identifier used for travel stamps.	To fill your travel stamps: countries, cities and photo counts. The travel-stamp scan reads selected photos on your device and sends selected metadata to our server; that metadata is stored for stamps. Separately, images you choose to upload for imports, avatars or private journals are uploaded and stored for those features. We do not automatically post them.
Device address book: this version does not collect phone numbers or email addresses from your contacts.	Find friends through the in-app discovery and request flow. We do not match or message people from your device contacts.
Friends: friend requests you send, receive, accept or decline, and your friends list.	To let you connect with friends and decide what each person can see.
Device and Network Data: information needed by our hosting, authentication and maps services, such as IP address, device/OS details and app version. Included SDKs may process identifiers, coarse location, usage and diagnostic information according to their documentation. Optional reel-ready notifications are sent through Google Firebase Cloud Messaging as described below. We do not use a separate crash-reporting service. Optional saved-place reminders are notifications created on your device.	To optimise the Platform for your device. To display in-app notifications and service status. To enhance security and detect fraud, fake visits and abuse.
Reel-ready notifications (optional, off until you turn on reel alerts in the App; in App versions and on our servers where it is available; also needs notification permission): your device's Firebase Cloud Messaging registration token, an installation identifier created by the App, the device platform (Android or iOS) and the sign-in session the alerts were turned on from. For each notification we record which import it is about, its delivery status, attempts and times and, when the App reports it, when it was received and opened.	To tell you when a reel or post you imported is ready. Our server sends the notification through Google Firebase Cloud Messaging (for iPhones, Firebase passes it to the Apple Push Notification service). The notification shows a fixed message ("Your reel is ready") and carries only what the App needs to open the right screen: your Roam account number, your age group and content setting, the import and notification identifiers and our server address. It does not include place names, captions or your location. Notifications are sent only to devices whose sign-in session to your account is still active. A notification that cannot be sent within 1 hour is dropped. You can turn reel alerts off in the App, or turn off notifications in your phone settings.
Usage and Service Data: searches, saves, lists, visits, imports and actions submitted to our API. Included authentication/maps SDKs may process usage data; we do not separately track screen views for analytics.	To fix problems and improve features. To understand how the Platform is used.
Place Information from third parties: names, addresses, ratings, photos and opening hours from Google Maps and similar providers.	To show place details, maps and curated lists.

We do not use your information to show you advertisements in this version of the App, and we do not sell your personal information.

EXTERNAL RETRIEVAL AND AI PROCESSING

When you paste, share, upload or send content to Roam to import places, Roam processes it automatically: the link and what the post carries, any text you add, and photos or videos you upload or send to our Instagram account are sent to the external services below to find and match places. Instagram posts are retrieved without signing in to any Instagram account, so a link can only be read if the post is publicly available; otherwise Roam processes only the photos or videos you choose to upload or send. Your notes, account details (such as name and email), home city and device location are not sent for these imports. The content may contain personal information. ScrapeCreators or Apify may retrieve Instagram content, including public captions, comments, transcripts and media, when used for your import. Media attached to direct messages is downloaded from Meta's servers. OpenRouter routes extraction to an external AI model provider, and Google Maps / Places receives extracted place names and city hints for matching. Each import records which action sent it; this is not recorded as a separate permission. If you gave the separate processing permission (for example by tapping "allow processing" or "resume processing" in the App, or in earlier App versions), your imports are processed under that permission, which can also use your home city and the creator's public profile details to improve matching.

Turning import processing off leaves browsing and manual saves available. You can review matches and correct or reject them. Results are generated automatically and may be inaccurate.

YOUR RIGHTS

Removing Content or Deleting Your Account: You can remove any visit, automatic visit, save, list, Instagram import or export import record, or delete your account at any time (see "Deleting Your Account and Data" below).

Updating Your Information: You can update your username, photo and area in the App.

Accessing and Correcting Data: To access a summary of the personal data we hold about you, or to correct it, email security@lifeatsocial.com.

Declining or Withdrawing Consent: You can refuse or revoke device permissions in phone settings. Turn off import processing in Roam settings to pause queued imports and future provider calls, and to stop automatic processing of content you send afterwards; those imports wait until you turn it back on. A request already sent cannot be recalled. Existing results are not automatically deleted when you turn it off. Turning off automatic visits and saved-place reminders in Roam settings stops location updates being sent to our server for those features and clears the in-progress stay we were measuring; location updates already sent cannot be recalled. You may also email security@lifeatsocial.com for other consent or data-rights requests; please allow up to 30 days for those requests. Declining optional processing may limit the related features.

Unlinking Instagram: Where the App offers it, you can unlink Instagram in Settings. Unlinking ends Instagram sign-in sessions; your existing imports stay in your account until you remove them. If Instagram is your only sign-in method, add Google or Apple sign-in first or delete your account. Unlinking does not by itself clear stored direct-message records; deleting your account clears the text and attachments of messages linked to your account, or you can contact security@lifeatsocial.com.

Nominating Someone: You may nominate another person to exercise your rights if you die or become unable to. If your grievance is not resolved by us, you may approach the Data Protection Board of India.

DELETING YOUR ACCOUNT AND DATA

In the App: go to Profile → ⋯ → Settings → Delete account, and confirm.

Without the App: email security@lifeatsocial.com with the subject "Delete my Roam account" from the email linked to your account.

Imported Instagram content: remove the import in the app, delete your account, or contact security@lifeatsocial.com for assistance.

Instagram direct messages and sign-in records: deleting your account removes your Instagram link and clears the text and attachments of direct messages linked to your imports or your linked Instagram account. Message identifiers, sender identifiers, timestamps and processing status, records of our automatic replies, and Instagram sign-in attempt records (app-scoped identifier, username and timestamps) are not currently removed automatically and may remain after you delete your account. Message text that was never linked to a Roam account is not currently cleared automatically. Contact security@lifeatsocial.com to request removal of these records.

Deleting your account disables it and removes personal profile fields, sign-in identities and sessions, owned saves, lists, imports, visits (including automatic visits and saved-place reminder records), friendships, journals, stamps and associated private files through the deletion workflow. A minimal inactive operational record remains: internal account number, deletion time and the generic label "Deleted account". It contains no provider identity or former profile details and cannot restore your account. Signing in again with the same Google or Apple account creates a new account with no previous content. This minimal record has no automatic expiry. Necessary safety or legally required records may be retained separately. Apple grant revocation may retain an encrypted revocation credential for retry for up to 30 days; it is cleared on success or expiry, and an Apple outage does not prevent local account deletion. Storage failures, vendor copies and backups require separate handling. Contact security@lifeatsocial.com if you need help with a deletion request or information about retained records.

ANDROID APP MARKETING MEASUREMENT

In Android versions that include Meta App Events, we use Meta Platforms to measure Roam app campaigns and understand registration, sign-in, Instagram connection, reels saved and import outcomes. Marketing measurement starts only after your existing age-group check identifies you as an eligible adult. It is not enabled for unknown age groups, users who identify as under 18, or App Review demo sessions. This means it does not measure every download or first launch.

Meta receives a pseudonymous Roam account identifier, event times, sign-in method, counts of profile fields filled and reels or places saved, Instagram connection status, app version and device/network attributes supplied by its SDK, including an advertising identifier where your Android settings permit it. A field count does not include that field’s contents. We do not pass your name, email, date of birth, precise location, reel links, photos, private messages, Instagram username or Instagram DM sender identifier as marketing event parameters. We do not read or generate a Facebook login identifier for users who have not signed in with Facebook.

Meta may use the data for campaign attribution, measurement and advertising optimization under its Privacy Policy and applicable business terms. This processing may take place outside India. You can manage or delete your advertising identifier in Android’s privacy settings; this restricts identifier-based advertising measurement but does not by itself disable all event measurement. For questions or a request concerning your marketing data, contact security@lifeatsocial.com. Signing out clears the SDK’s current Roam user association; events already shared remain subject to Meta’s retention and deletion processes.

HOW YOUR INFORMATION IS SHARED

Information visible to other users

Information	Visibility in this version
Profile name, avatar and permitted profile summary	Discoverable when you enable discovery, subject to blocking and profile access rules.
Visit history, counts and place visitor information	Yourself and accepted, unblocked friends through the permitted circle views. Not a public global visitor history.
Current device location	Used for your map interaction and, if you enable them, automatic visits and saved-place reminders; sent to our server and Google Places as described above; not broadcast as live friend location.
Automatic visits	Private to you; not shown to friends or counted in visit counts or visitor rankings unless you choose "Keep", which adds a regular visit.
Private journals, saved lists, imports (including uploaded export rows), email and selected gallery metadata	Private account data; not exposed as a public feed. External providers receive only relevant data for the feature and permitted processing.

You can unfriend anyone at any time; they are not notified.

How we share data within our group

We may share your data with our affiliated companies for safety (a ban on one of our platforms may apply across our platforms), operations (hosting, support, analytics and security) and legitimate business needs such as audits.

Sharing with third parties

Who	Why
Google (Sign-In, Maps and Places)	To sign you in, show place information and maps, match places from imports and, if you enable automatic visits or saved-place reminders, find places near your current location (our server sends your current coordinates to Google Places)
Google (Firebase Cloud Messaging)	If you turn on reel alerts, to deliver reel-ready notifications to your device: the registration token and the notification content and data described above (for iPhones, Firebase passes them to Apple Push Notification service)
Apple (Sign in with Apple)	To sign you in
Service providers	Companies that help us run the Platform, such as cloud hosting, data processing (including finding place names in public reel content), analytics and customer support. They receive only the data needed for their task
Authorities	If required by law, or to address fraud, safety or security concerns
A successor business	If the company is acquired, merged or reorganised. We will notify you in advance and give you the option to delete your account

Provider processing is governed by applicable provider terms and our arrangements with them. The service providers are described in this policy; content you send for import is processed automatically as described above. We do not make a blanket claim that every provider has zero retention or never uses submitted data for training.

Data retention

We retain profile, saves, lists, visits, private journals, extracted results and stamp metadata until you delete them or your account, unless an applicable retention exception applies. Cleanup rules remove uploaded import media after 24 hours following completed or review outcomes, or 7 days after failure or cancellation; processing workers execute this cleanup. Retrieved temporary media uses a separate cleanup path. These raw-import rules do not apply to saved private journal photos. Unconfirmed export-file previews expire 24 hours after upload; an expired preview is no longer shown and is deleted by routine cleanup, normally within about an hour (later if our servers are unavailable). When you confirm an export import, unselected rows are discarded; selected rows, including rows still waiting for a place match, stay in a private import record until you delete it or your account. Saves and visits you confirm stay until you remove them. We do not keep a background location trail or route history. Optional map-position updates keep only your latest position on your device. For automatic visits and saved-place reminders, coordinates you send are used to process that update and are not written to our database; nearby-venue results from Google Places (place identifiers, locations and types) are held only in server memory for up to 30 minutes. While you are at a saved place, we keep one in-progress record (the candidate place and update times, without coordinates), replaced on each update and deleted 30 minutes after the last update, or straight away when you turn the feature off, sign out or delete your account. Automatic visits stay until you undo them, delete them or delete your account; undone automatic visits are deleted after 1 day and saved-place reminder records after 7 days. Routine cleanup normally runs hourly (later if our servers are unavailable). Kept automatic visits become regular visits and follow the visit rules above. Public post link imports follow the same import and media rules as other imports. For reel alerts, the registration token is stored encrypted and is deleted when you turn reel alerts off or sign out, when another account turns on alerts on the same device or token, when Firebase reports the token is no longer valid, or when you have more than 10 devices with alerts on (the oldest is replaced). If the App could not tell our server to turn alerts off when you signed out, the encrypted token can stay until you turn on alerts again on that device, another account turns them on there, Firebase reports the token is no longer valid, or you delete your account. The rest of the device record (installation identifier, platform, a keyed hash of the token and times) and the notification records stay until you delete your account; notification records about an import are also deleted when you delete that import. We keep the time of each change to your alert registration to limit registrations; entries older than a day are removed the next time you change it. We do not collect your contact book in this version. Necessary safety or legal records and backups may be retained separately.

Children

Roam is intended for users aged 13 and above. Users under 18 need a parent or legal guardian’s permission as described in our Terms. We use age-group information to check eligibility; signing in with Google or Apple does not verify age or parental permission. Roam is not intended for children under 13. If we learn that an account belongs to a child under 13, we will close the account and delete associated personal information, except records we must retain for legal or safety purposes. Parents or guardians can contact security@lifeatsocial.com to report an underage account or request assistance with their child’s information.

For users who identify their age group as 13–17, Roam filters recommendations to limit alcohol-related and sexual content. Social and import features remain available. Automated filtering may make mistakes; please report inappropriate content.

Third-party links

Our Platform links to third-party services such as Google Maps and Instagram. They have their own privacy policies, and we are not responsible for their practices.

Changes to this policy

We may update this Privacy Policy from time to time. If we make major changes that affect you, we will notify you in the App and ask for your consent where required.

SECURITY PRACTICES

We have security measures in place to protect the information we collect, including encryption in transit and access controls, as required under the Information Technology (Reasonable Security Practices and Procedures and Sensitive Personal Data or Information) Rules, 2011. If a personal data breach affects you, we will notify you and the Data Protection Board of India as required by the DPDP Act. You are responsible for keeping access to your Google or Apple account secure.

COMMUNICATIONS FROM US

We display in-app notifications such as import status and friend requests. If you turn on reel alerts, in App versions and on our servers where they are available, we send a phone push notification through Google Firebase Cloud Messaging when an import is ready; otherwise phone push notifications are not used. In App versions that offer them, optional saved-place reminders are notifications created on your device, limited to 3 per day and not shown between 10 pm and 8 am. We may contact you about necessary security or account matters using available account contact information. Phone-level notification controls do not substitute for in-app processing consent.

WHERE WE STORE YOUR PERSONAL INFORMATION

We host Roam in India. External services, including Google, Apple, retrieval providers, OpenRouter and its routed model provider, may process information outside India. We do not represent that every copy or provider request stays in India.

DISCLAIMER

While we take all necessary steps to protect your personal information, transmitting data over the internet is never fully secure. We cannot guarantee the security of your information during transmission, but once we receive it, we apply strong security measures to protect it.

COOKIE POLICY

Our Website and App use cookies, local storage and similar technologies (including software development kits from our service providers) to keep you signed in, remember your preferences, measure performance and understand how the Platform is used. Android versions with Meta App Events also use the limited adult marketing measurement described above. Other app features continue to use storage and SDKs for their stated purposes. You can manage cookies in your browser settings and tracking permissions in your phone settings; disabling them may limit some features.

GRIEVANCE OFFICER AND CONTACT

For any questions, concerns or grievances about this Privacy Policy or your personal information, please contact:

Field	Details
Name	Mr. S Surana
Designation	Grievance Officer
Company	Interact Group Private Limited
Address	Bengaluru, Karnataka India, 560102
Email	grievance.officer@lifeatsocial.com

Complaints will be acknowledged within 24 hours and resolved within 15 days of receipt.