Privacy Policy

Last updated: 1 November 2026

Tablamigo is an app that helps solo travelers find and join plans with other travelers nearby. It is operated by Hookstep, a sole proprietorship registered in India ("we", "us"). This policy explains what we collect, why, and the choices you have. It covers the Android app, the web app at tablamigo.hookstep.in/app and this website. Questions: support@hookstep.in.

The short version. We collect what is needed to show you plans nearby and let you chat. Other people see only a distance rounded to 0.5 km, not your exact position, unless you choose to share your live location in a chat. We don't sell your data. The Android app shows free accounts an ad banner from Google AdMob, which can use your phone's advertising ID; Plus members see no ads, and the web app has none. Some travel guides on this website show ads from Google AdSense, which can use cookies (section 3). We don't offer government ID verification and don't collect ID documents. You can delete your account from inside the app at any time.

1. What we collect

Data	Why, and what we do with it	Who can see it
Email address	To sign you in (we email you a one-time code, or you use Google) and to send you the emails listed below.	Only us.
Google sign-in details (only if you choose Google: the "Continue with Google" button, or your account in Google's "Continue as" prompt)	Google tells us your verified email address and your name. Your email finds or creates your account, and your name pre-fills your profile. Google's sign-in token can also carry your profile picture; we don't use or store it. We get no other access to your Google account.	Only us.
Profile: name, profile photos, bio, home country, languages, interests, travel styles, countries visited, profile prompts, Instagram handle	Your public profile, so other travelers know who they are meeting. Photos are stored as described under "Photos you upload" below.	Signed-in Tablamigo users who open your profile see your name, photos, bio, age, home country, current city, languages, interests, travel styles, countries visited, prompts, verified badge, the date you joined, how often you reply to direct messages (a percentage), and counts such as plans joined, connections and thumbs-ups. They see your plan history unless you hide it. Your Instagram handle is shown only to people who share a plan with you or have Plus.
Date of birth	To confirm you are 18 or older.	Only us. Other users see your age, not your birth date.
Gender (woman, man, non-binary or unspecified)	To decide who can see and join women-only plans and chats, and who can use the women-only travelers filter. You can change it at any time and we don't check it. It is not shown on your profile.	Only us.
Your location while the app is open	Your phone sends your current position when you open the map, tap the locate button, finish sign-up or share live location. We keep your latest position and the time it was sent in your account, replacing it each time, and use it to find plans and travelers near you and to work out your city. While the map is open the app also asks for nearby plans about every 45 seconds, and those requests (like the one for nearby travelers) carry your coordinates, so they appear in our server logs (see Server logs below). We do not collect location in the background.	Other users see your city and a distance rounded to 0.5 km (never less than 500 m), not your position. The Travelers list shows people whose position was sent in the last 3 days, and marks as active those whose position was sent in the last 30 minutes.
Live location you choose to share in a chat	Only if you tap share in a plan chat or direct message (it is never offered in city or trip chats), for 15 minutes, 1 hour or 8 hours. Your exact coordinates are shared with everyone in that chat until the share ends or you stop it, and are refreshed about every 30 seconds while you keep that chat open. After that the message shows only that you shared your location; no coordinates are returned, and the stored point is deleted 7 days later. People you have blocked, or who have blocked you, never receive it.	The members of that chat, while the share is live.
Plans you host or join, meeting places, check-ins	The core of the service. A host picks the meeting place (name, address and map point) and the time. If you tap check-in, your phone sends your position so our server can check you are near the meeting place. We store the time you checked in, not the position you sent.	People who can see the plan: the plan, the meeting place, who is going (name, photo, home country) and who has checked in. Women-only plans are shown only to women and to people already in them.
Trips you add (city and dates)	To show who will be in the same city on your dates, and for city chats and trip chats. We also email a weekly digest to people with a trip coming up.	Other signed-in users who look at that city or have overlapping dates see your name, photo, age, home country and trip dates. People who have connected with you (the Connect button) can see your upcoming trips in their trips feed. The digest email can show another traveler's first name, photo, age and home country.
Moments you post (photo, caption, category, city) and their location (optional)	To show your moment in the feed for its city and to travelers nearby. If you allow location when you post, we store that point rounded to a grid of about 1 km, never your exact spot. We use it to work out the city and to include your moment when someone browses moments near a place (never closer than 5 km). Deleting a moment hides it in the app; the record and its photo file stay in our storage until you delete your account, and an admin looking into a report about it can still read what was reported.	Anyone, including people who are not signed in or have no account. They can see your moment's photo, caption, category and city, the plan it links to (if any), the likes and comments count, and your name, profile photo, home country and verified badge. The stored point is never shown, but someone browsing "nearby" can tell your moment was posted within the distance they chose.
Comments and likes on moments	To let people react to a moment.	Anyone, including people who are not signed in. A comment is shown with the commenter's name and profile photo. Likes are counted, not listed.
City tips (title, text, place)	To share local tips for a city.	Anyone, including people who are not signed in. A tip is shown with your name, profile photo, home country and verified badge.
Questions and comments on plans, plan photos, thumbs-ups, host ratings	To let people talk about a plan and build trust. A host rating is 1 to 5 stars with optional tags and a comment.	Comments and photos: people who can see the plan, with your name and photo. Thumbs-ups: shown on your profile as a count. A rating you give: only the host sees it, with your name and photo; everyone sees a host's average and number of ratings.
Profiles you open	"Who viewed your profile" is a Plus feature. When you open someone's profile we record that you did, at most once a day per profile, unless you are snoozed or have incognito browsing on (Plus).	The person whose profile you opened. Free accounts see only how many people viewed them; Plus members see who.
Profile Boost (Plus)	If you use Profile Boost, you are shown first in the Travelers list for 24 hours. We store when the boost ends.	Other users see a boosted mark on your profile, in the Travelers list and on your moments while it lasts.
"Here now" (off unless you opt in)	To list travelers who are in a city right now. It is off for every account until you turn it on, and you can add a short status text (up to 80 characters).	If it is on for your account, signed-in users looking at that city's page see your name, photo, age, home country, verified and Plus badges, travel styles and status text. People who are snoozed, or browsing as incognito (Plus), are never listed, and neither is anyone on either side of a block with the viewer.
Invite codes (referrals)	If you sign up from someone's invite link, or redeem their invite code in your first 14 days, we record who invited you and you get 7 days of Plus; the person who invited you gets 7 days too for each of their first 10 invites.	The person who invited you gets a notice with your name (until they reach the 10-reward limit), and sees how many people they invited.
Host rewards	If you host a plan that at least 2 other travelers check in at, we record the plan, how many checked in and the days of Plus we gave you (7 days, at most twice in 30 days).	Nobody else. The travelers who went are not told.
Trusted contacts and emergency contact (name, phone number, relationship)	Only people you add yourself, so you can reach them in an emergency. If you press SOS in a plan, we save an alert (the plan, the GPS point your phone sent or the plan's meeting place, and a short note the app adds), email you a copy with a map link and the local emergency numbers, and the app shows buttons to dial the local police and ambulance numbers and ready-made WhatsApp and SMS messages for your trusted contacts that you send yourself from your phone. Our servers never send anything to your contacts, and we don't contact emergency services. Please only add people who are happy for you to share their number.	Only you (and us, to run the feature).
Plan share link (optional)	If you create a share link for a plan you are in, we store a random token, your optional note and an expiry time. The link expires automatically after the plan. The page it opens is the plan's details at the moment it is opened, not your live position.	Anyone who has the link, without signing in: the plan (title, description, place, address, map point, time), who is going (name, photo, home country, verified badge, whether they checked in), your name, photo and note, and local emergency numbers.
Verification selfie (optional)	To give you the verified badge. You take the selfie with your camera. Our own servers detect the face in it, compare it with your profile photo and check the head pose we asked for. No outside face-recognition service is used and no face template is stored. We keep the selfie file, the result (approved or not, and the reason) and the check's scores (similarity, faces found, head angles, a copy check, timing). Our admins can open the selfie in the admin panel, for example to recheck a decision. The badge shows that the selfie matched your profile photo, not your gender.	Not shown to other users.
Messages and photos you send in chats, and buddy-request notes	To deliver them. Text in group, city and trip chats, poll questions, comments, moment captions, city tips and buddy-request notes is checked by an AI moderation service before it posts (see "Who we share data with"); direct messages are not. Messages in direct, city and trip chats, and buddy-request notes, are also scanned on our servers for phone numbers, email addresses and social handles (together with your last few messages from the past 30 minutes), and a message that contains one is refused, except in a direct message when you have Plus or share a plan with the person. Plan chats are not scanned this way. Deleting a message hides it from the chat; its text stays in our database until you delete your account, and an admin looking into a report about it can still read it.	Members of that chat. In a plan chat that is the people in the plan; in city and trip chats it is other travelers who join, who may be strangers; in a direct message it is the other person. We open a message only to look into a report, and an admin sees a reported message's text with the report.
Photos you upload (profile photos, plan photos, chat photos, moments, verification selfies)	Stored in Tablamigo's own private storage at Cloudflare (R2) and served through our API (tablamigo-api.hookstep.in). Each file's address contains a random code, but anyone who has the exact address can open the file without signing in. A removed photo can stay in Cloudflare's cache for a few hours. Removing a photo or a moment in the app removes it from the app, not the file: files are deleted only when you delete your account.	The address is shown inside the app to people who can see the item. Anyone who has the address can open the file.
Reports and blocks	To keep the community safe. A report becomes a support ticket that stores the reason, your details text and your email address as the reply address, and we email a copy to our support inbox.	Only us. The person you report or block is not told.
Subscription and purchase records	To give you Tablamigo Plus or a Trip Pass. In the Android app from Google Play, Google processes the payment; our server asks Google to confirm the purchase and we keep the purchase token, product, order ID, status and dates. On the website and web app, including when you add it to your home screen or desktop, Razorpay processes the payment; we keep the Razorpay subscription, order and payment IDs, status, amount and dates, and the record Razorpay returns for the payment. For a Trip Pass bought on the web, that record can include the email address, phone number and UPI ID or other payment-method reference you gave Razorpay at checkout. We never receive full card numbers.	Only us, and Google or Razorpay for the payments they process.
Notification token	To send notifications you've allowed (new messages, someone joined your plan, reminders before a plan you joined). On Android it is an FCM registration token; in a browser it is the browser's push subscription (an address at your browser's push service and its keys). The notification text, for example the start of a message, passes through Google's Firebase Cloud Messaging or your browser's push service. On Android, the Firebase software that delivers notifications also creates an installation ID for the app on your phone and sends it, with details of the Firebase software, to Google; that part is Google's, and it is described in Google's Firebase data disclosure. A token is deleted when you delete your account, or when the push service tells us it is no longer valid.	Only us.
Emails we send you	Service emails, which have no unsubscribe link: sign-in codes, a welcome email, verification results, Plus and Trip Pass receipts, payment-problem, cancellation and refund notices, replies to your reports, and the confirmation when you delete your account. Optional emails, each with an unsubscribe link: reminders that Plus or a Trip Pass is ending or has ended, "someone joined your plan", and a weekly trip digest. We keep a log of the emails we send you (type, date, address).	Only us.
How you found us (recorded once)	To see which links, sites and app stores bring people to Tablamigo. When your account is created (for an older account, the next time you sign in) we store the campaign tags in the link you came from (if any), the site that sent you, the page you landed on, the kind of device (Android, iPhone, or a browser on Windows or Mac), the country Cloudflare reports for your connection, and your IP address at that moment. During sign-up we also ask "How did you hear about us?"; you can tap one answer or skip it, and we keep the answer with your account. If you delete your account we remove the IP address and the referring site; the channel, device kind and country stay with the anonymised account so we can count sign-ups by source.	Only us.
Ads in the Android app (Google AdMob)	Free accounts in the Android app see one ad banner, at the end of the list of plans on the Explore tab. Plus members see no ads, and there are none in the web app, or on the sign-in, chat, direct message and payment screens. The banner comes from Google AdMob, Google's ad service, through Google's Mobile Ads software in the app, not from us. Google says this software collects your phone's advertising ID, an app set ID and, where applicable, other identifiers of accounts signed in on the phone, your IP address (which can be used to estimate your general location), app interactions such as launches, taps and video views, and diagnostic information about the app's performance, and uses them for advertising, analytics and fraud prevention. You can reset or delete your advertising ID in your phone's settings. The software also asks Android for its ad-services features (ad topics, ad measurement and the advertising ID through Android's ad services); on phones that offer them, you control them in Android's ad privacy settings. Where the law requires consent, for example in the EEA and the UK, the app shows Google's consent form before any ad loads, and you can change your choice later under Profile → Ad privacy choices; whether the ads you see are personalised depends on those choices. We don't pass Google your name, email address, profile, messages or position, and we never receive your advertising ID.	Google, under its own policies (how Google uses information in ads). We see only totals, such as how many ads were shown, in our AdMob account.
Website and web app visit statistics (Cloudflare Web Analytics)	To see which pages are read and which load slowly. The pages of this website and the web app load Cloudflare's Web Analytics script after the page has finished loading; the Android app itself does not. For each visit it reports the page, how long the page took to load and respond (load time and Core Web Vitals), the site that sent you, your country, and your browser, operating system and device type. Cloudflare says this script uses no cookies or local storage, does not fingerprint visitors and does not track individuals across websites. The report is sent to Cloudflare at cloudflareinsights.com, and, like any request your browser makes, it carries your IP address. We do not give the script your name, email or any account ID, so we cannot match a visit to your account. You can block the script with a content blocker; the website and app work the same without it.	Only us, as totals and charts in Cloudflare's dashboard.
App usage events and last-active time	To see which features people use and fix what doesn't work. Examples: finishing sign-up, creating or joining a plan, checking in, adding a trip, sending a message (the chat and its kind, never the text), posting or sharing a moment, opening the upgrade screen. We record these ourselves, on our own servers. The only third-party advertising or analytics software in the Android app is Google's ad software, described in the ads row above. The only third-party measurement in the web app is the Cloudflare Web Analytics row above; on this website there is also the ad measurement Google AdSense does on some travel guides (section 3). Events are linked to your account when you're signed in, and are recorded without an account when you're not. We also store when you were last active. Events are deleted automatically 180 days after they are recorded.	Only us.
Partnership enquiries (website form)	If a business sends the form on our partnerships page, we store the name, work email, business, city and message it typed, and email them to our team so we can reply. We send a confirmation to the address typed in the form.	Only us.
Server logs	Our servers log each request: the time, the IP address, the address requested and any error. The address requested can include coordinates your app sends when it looks for nearby plans, IDs of plans, chats or people, and the text of a chat search. We use logs for security, abuse prevention and fixing bugs. IP addresses also limit how fast requests can come in.	Only us.

We do not read your phone's contacts, call logs or SMS, and we don't collect microphone audio. The Android app uses your camera only to take the verification selfie, and opens your photo library only for photos you choose to upload. Google Play also lists two permissions that Android or Google's notification service require rather than features that look at your files: on Android 9 and older, the camera library the app uses (expo-image-picker) asks for storage permission before it can hand the selfie back to the app (the app does not use it to read your photos or files), and Google's notification service (Firebase) holds a wake lock so notifications can be processed while the phone is idle. Trusted contacts are only the names and numbers you type in yourself. We don't offer government ID verification, we don't ask for ID documents, and the app has no way to upload one.

2. Legal bases (EEA/UK users)

We process your data to perform our contract with you (running your account and the features you use), on the basis of your consent (location and notifications, which you can switch off in your phone settings, and the ad choices you make in Google's consent form in the Android app), and for our legitimate interests in keeping Tablamigo safe and working (moderation, security logs, fraud prevention). We keep purchase records where the law requires it.

3. Who we share data with

We don't sell or rent personal data. The Android app's ad banner comes from Google AdMob (below). Some of this website's travel guides show ads from Google AdSense, described below. We use these service providers, only for the purposes listed:

Google Cloud — server hosting. Our servers and database are in Singapore.
Cloudflare — stores and serves the files you upload (R2), sits in front of our website and API, so it handles the traffic to them, and provides Cloudflare Web Analytics, which counts visits to the website and web app (see the row about visit statistics above).
Resend — sends all our emails (sign-in codes, receipts, replies, notifications and the digest). It receives your email address and the email text.
Google — Sign in with Google (if you choose it), Google Play billing for purchases in the Android app from Google Play and, if you allow notifications, Firebase Cloud Messaging, which delivers notifications to Android phones and sees the notification text. In a browser, notifications go through your browser maker's push service instead. When you aren't signed in to Tablamigo in your browser, the pages of this website (except the legal pages, such as this policy and the terms) and the web app's sign-in screen load Google's sign-in script from accounts.google.com. On the website it loads only after your first scroll, tap, click or key press on a page, never on a timer. If you're signed in to Google in that browser, Google may show a prompt offering to continue to Tablamigo with your Google account. As with any file fetched from Google, loading the script gives Google your IP address and browser details, and to show the prompt Google checks which Google accounts you're signed in to; Google handles this under its own privacy policy. We receive nothing from the prompt unless you pick your account in it, which signs you in, or creates your account, the same way "Continue with Google" does. You can close the prompt or ignore it, and after you close it Google waits a while before showing it again.
Razorpay — payments on the website and web app (cards, UPI and other methods Razorpay offers). Razorpay receives your payment details, your email address and an internal account ID; we receive the payment status and IDs.
OpenAI — used for two things. (1) Moderation: before they post, we send the text of messages in group, city and trip chats, poll questions and options, comments on moments and plans, moment captions, city tips and buddy-request notes to OpenAI's moderation service, which flags harassment, hate, sexual content, graphic violence and self-harm instructions. We send the text only, not your name or account. Direct messages are not sent. If the check fails or takes longer than 2.5 seconds, the text posts without being checked. (2) Plan ideas: we send the city, the vibe you typed (if any) and your profile interests, never your name, email or exact location.
OpenStreetMap-based services (Nominatim, Photon, OpenFreeMap) — our server sends coordinates to Nominatim to look up a city name (your position when your phone reports it or you open a city chat, the meeting point of a plan you post, and the point of a moment you post) and a place name and nearby point to Photon for plan ideas. Your phone contacts Photon directly when you search for a place (the app sends your search text and, for a plan's place search, your position) and OpenFreeMap directly to load the map, so those services see your device's IP address and the map area you look at.
Google AdSense — shows ads on some of this website's travel guides: our how-to guides, and the city guides under tablamigo.hookstep.in/solo-travel/ that name sourced places where travelers stay or meet. Nowhere else: not on the home page, the download page, the app comparisons, the safety page, these legal pages, the web app or the Android app. On those guides your browser loads Google's ad script from googlesyndication.com after your first scroll, tap, click or key press. Before it does, the page asks Cloudflare, which runs in front of this website, which country your connection comes from. If it is in the EEA, the UK or Switzerland, or the country can't be told, the script isn't loaded and you see no ads. Third-party vendors, including Google, use cookies to serve ads based on your prior visits to this website or other websites. Google's use of advertising cookies enables it and its partners to serve ads to you based on your visits to this and other sites on the internet. Google may also let other ad companies show and measure ads here (Google's list of ad technology partners). Google and those companies receive your IP address, browser details and the page you are reading. You can opt out of personalised advertising in Google's Ads Settings, and opt out of many other companies' cookies for personalised advertising at aboutads.info or, in Europe, youronlinechoices.eu. See how Google uses information from sites that use its services. We don't give Google your name, email or any account ID. You can block the ads with a content blocker or your browser's cookie settings; the guides work the same without them.
Google AdMob — the ad banner that free accounts see in the Android app. Google's Mobile Ads software in the app sends Google the data described in the ads row above, and Google uses it under its own policies to show and measure ads and to prevent fraud. We don't send Google anything from your Tablamigo account.

We may disclose data if the law requires it, or to protect someone's safety when we believe in good faith that there is a serious risk of harm.

4. International transfers

Our servers are in Singapore and some providers process data in the United States and elsewhere. Where the law requires, transfers rely on the provider's standard contractual clauses or an equivalent safeguard.

5. How long we keep data

We delete automatically, once a day: unused sign-in codes 1 day after they expire, sign-in sessions 30 days after they expire, in-app notifications 90 days after they are created, usage events 180 days after they are recorded, and live-location shares and expired plan share links 7 days after they end. Everything else stays until you remove it or delete your account, apart from backups and logs, described below.

Your account and profile: until you delete your account. We don't delete inactive accounts automatically.
Your location: the latest position replaces the one before. A live location you shared keeps its stored point for 7 days after the share ends, then it is deleted; it is not shown to anyone after the share ends.
Things you remove in the app: trusted contacts, trips, saved plans, plan comments, plan photos and profile photos are removed from our database when you remove them (the photo files stay in storage, see above). Messages and moments are hidden, not erased: their text, captions and photo addresses stay until you delete your account. City tips, thumbs-ups and ratings can only be removed by deleting your account.
Safety records: SOS alerts (with their GPS points) stay until you delete your account. Plan share links are deleted 7 days after they expire.
When you delete your account: we remove your profile (including your email address, Instagram handle and location), every file you uploaded, your trips, plan and chat memberships, your moments with their likes and comments, city tips, plan comments, plan photos and ratings, saved plans and private notes, share links, SOS records, trusted and emergency contacts, connections, blocks, notifications, buddy requests, profile views, thumbs-ups, sign-in code, and your sign-in sessions are closed. Your messages are replaced with "[deleted]". Usage events keep their counts but lose your user ID and details until they are deleted at 180 days. Plans you hosted are cancelled. A web (Razorpay) subscription is cancelled for you; a Google Play subscription is not, so cancel it in Google Play first. Deleted photos can stay in Cloudflare's cache for a few hours. The full list is on the deletion page.
Kept after deletion: purchase records (Plus subscriptions and Trip Passes you paid for, with the payment records Google or Razorpay returned), reports you made or that were made about you with their support tickets and replies (which hold your email address as the reply address), a log of the service emails we sent you, and a few account details on the anonymised account (when you joined, when you were last active, when your Plus ended, your referral code and who referred you, and your email-notification and display settings). We keep them on the anonymised account for as long as the law requires and no longer than we need them. No automatic deletion date is set yet, and you can ask us to remove them sooner at support@hookstep.in. None of them is shown to other users.
Backups: we back up our database every 6 hours. We keep the 10 most recent backups (about two and a half days) on our server and in private off-site storage; older ones are deleted automatically, so data you delete can stay in a backup for up to about 3 days. Backups hold the database only, not uploaded files.
Sign-in codes: a code stops working after 10 minutes. We store only a hash of it, and delete it when you sign in, when you delete your account, or automatically a day after it expires.
Partnership enquiries and server logs: no automatic deletion period is set. Server logs are not part of your account data, so deleting your account does not change them.

6. Your rights and choices

Access, correct, or delete: edit your profile in the app, or delete your account under Profile → Delete account. See how to delete your account.
Location and notifications: switch them off at any time in your phone's settings. The app still opens without location, but the map then shows a default area and not where you are.
Ads on this website: turn off personalised ads in Google's Ads Settings, or opt out of many ad companies' personalised ads at aboutads.info or youronlinechoices.eu. A content blocker, or blocking cookies in your browser, also works; the guides read the same without ads.
Ads in the Android app: Plus has no ads. Where Google's consent form applies, change your choice under Profile → Ad privacy choices in the Android app. You can reset or delete your phone's advertising ID in its settings.
Emails: unsubscribe from optional emails with the link in them. Sign-in codes, receipts and account notices still arrive.
Copy of your data or objection: email support@hookstep.in. We reply within 30 days.
If you are in the EEA or UK, you can complain to your local data protection authority. In India, you may contact us as the data fiduciary under the Digital Personal Data Protection Act, 2023.

7. Age limit

Tablamigo is only for people aged 18 and over. We don't knowingly collect data from anyone younger. If we learn an account belongs to someone under 18, we close it. See our child safety standards.

8. Security

Data is encrypted in transit (HTTPS). Sign-in uses one-time codes, not passwords, and sessions can be revoked by logging out. No system is perfectly secure; if a breach affects you, we will tell you as the law requires.

9. Changes

If we change this policy in a meaningful way, we'll tell you in the app before the change takes effect.

10. Contact

Hookstep · support@hookstep.in