STRING
Legal

Privacy policy

Last updated 16 November 2026

String helps you meet people who are nearby, without giving away where you are. This policy explains what we collect, why, who can see it, how long we keep it and how to delete it. We wrote it to be read, not skimmed past.

The short version. You're invisible until you start a session. While you're visible we keep one rounded position (about 30 m) and delete it when the session ends. Nobody ever sees your exact location, distance, direction, surname, phone number or email. We don't sell data, show ads or use advertising or analytics trackers.

Who we are

String is run by the String team in India. For anything about your data, write to info@string.social.

What we collect and why

DataWhyHow long
Sign-in: your Google account sign-in, handled by Google Firebase Authentication. Firebase holds your email address and name; our server keeps only the account identifier it gives us. To sign you in and keep your account secure. Until you delete your account; the Firebase sign-in is removed at the same time.
Profile: first name, date of birth, bio, up to six photos, interests, what you're here for (networking or friendship) and, if you add it, an Instagram handle. To show others who you are, check you're 18 or over, and match you with people here for the same thing. Until you change it or delete your account.
Location, only during a session you start: your position rounded to a grid of about 30 m, its accuracy, and whether your phone reports a simulated location. To show you, and show you to, people within about 300 m. We keep only your current position. Each update replaces the last, and it's deleted the moment your session ends. We keep no location history.
Session records: when a session started and ended, the length and update interval you chose, whether auto-renew was on, and how many updates arrived. No location. To run sessions, end them on time and keep the service reliable. Until you delete your account.
Venue rooms: the rooms you join and when. To show you the people in the same room. Your membership ends when you leave the room.
Requests and connections: who you sent a request to, the opener you picked and its status. To deliver requests and keep the daily limit and 24-hour expiry. Connections last until either of you cuts the string, blocks the other or deletes their account.
Messages with your connections. To deliver your chats. A message is deleted from our server once both of you have cleared it (with disappearing messages or "delete conversation"). The whole chat is deleted when the connection ends.
Blocks and reports: who you blocked; for a report, the reason and a copy of the reported person's profile and up to the last 50 messages of your chat with them. To keep blocked people apart and to review reports. Blocks last until you unblock. Report evidence is kept for safety review even after a block or deletion. If you delete your account, reports you made stay without your name.
Notification token for your phone (Firebase Cloud Messaging). To tell you about requests and messages. The notifications never name anyone or quote a message. Removed when you sign out or delete your account.
Crash reports (Firebase Crashlytics): phone model, Android version, app version, where in the code the app failed, and a random installation identifier. Never your name, account, location or messages. To find and fix crashes. Kept by Firebase for up to 90 days. Turn this off any time in Privacy and safety › Send crash reports.
Server logs: IP address, time and the address requested. No locations, tokens or message contents. Security and fixing faults. Up to 14 days.

What stays on your phone

Hidden zones (places like home or work where your session stops by itself) are stored and checked only on your phone. We never receive them. Your recent emoji and your crash-report choice stay on your phone too.

Who sees what

Location and permissions

String asks for location permission after explaining why, during sign-up (you can say "Not now") or when you first go visible, and only "while using the app". Asking reads no location and sends nothing. String never asks for background ("allow all the time") location. While you're visible a notification is always on screen, with a Stop button. Giving the permission doesn't make you visible: you're visible only during a session you start, and every session ends on its own.

Camera access is used only to scan venue and personal QR codes. Photos you add are picked by you, then re-encoded on our server, which removes hidden data such as the place the photo was taken.

Service providers

We use a small number of providers to run String. They process data only on our instructions:

We don't sell your data, share it with advertisers, or use advertising or analytics SDKs. We share data with authorities only when the law requires it, or when someone's safety is at serious risk.

Security

Data travels encrypted between the app and our server. Photos are served only through short-lived signed links. Screenshots and screen recording are blocked inside the app. Logs never contain locations, tokens or message contents. Access to safety tools is restricted and every action there is logged.

Your choices and rights

If you're in India, you can also raise a grievance with our Grievance Officer at info@string.social.

Age

String is only for people aged 18 and over. We ask for your date of birth when you sign up. If we learn that an account belongs to someone under 18, we delete it. See our child safety standards.

Changes

If we change this policy in a way that matters, we'll announce it in the app or on this page before the change applies. The date at the top always shows the latest version.