Privacy policy
This page explains what the app collects, why, who can see it, how long it is kept and what your rights are under Thailand’s Personal Data Protection Act B.E. 2562 (2019). We try to keep it plain and to match how the app really works. If anything is unclear, ask us (section 18).
- You can browse the map without signing in. Your GPS position is used on your phone to work out distances; the app only sends a rough area to our server to get the shops around it, and it is not recorded.
- Signing in with Google is needed (on iPhone you can also use Sign in with Apple) to run a shop, call a shop over, make an in-app call, see a shop’s phone number or tap “I’d like … around here”. We do not keep your name or email in readable form, only one-way coded values.
- Shop details are public (name, menu, photo and the shop’s location while it is open). A shop’s phone number is shown only to signed-in users.
- When you call a shop, the vendor you call sees your display name and phone number, and sees your meeting pin only after tapping “On my way”. Our server does not store meeting pins or chat messages.
- Free internet calls (beta) use the microphone only during a call. The audio is encrypted and goes directly between the phones or through a Cloudflare relay. We do not record or keep any audio, and neither side sees the other’s phone number.
- We keep a traffic log for 90 days (account, encrypted IP address, time, type of request) for signed-in use only, for safety and because the law requires it. No location and no chat content.
- No ads, no analytics, no selling or renting of data · You can delete your account in the app — see Delete your account.
1. Who is responsible
The data controller is the developer of RotRe (“รถเร่ใกล้ฉัน”) in Thailand. Developer name on Google Play: PONG Developer · email kampanatth0222@gmail.com. On this page “we” and “our team” mean the developer.
2. Browsing the map without signing in (everyone)
- Your GPS position (if you allow it) is used on your phone to show you on the map, compute distances, sort nearby shops and check whether a shop you set a reminder for is near. Browsing the map does not send your GPS coordinates to our servers. The map works without location access. (Calling a shop and “I’d like … around here” are different — see sections 6 and 8.)
- What the app sends to get shop lists: the ID of the roughly 20 km map area you are viewing (and, if you follow shops, the area around you); the centre of the map rounded to about 1 km; and at times the IDs of the shop you are viewing or following, to receive that shop’s live position. All of this stays in server memory only while the app is connected, is not recorded, and is gone when you disconnect.
- Random install ID: the app creates a random ID not linked to any name or account, used to limit abuse and stop repeat reports. The server keeps only a one-way coded value of it, with a key that changes daily, for at most 48 hours, then deletes it.
- Kept only on your phone: favourite shops, shops you hid, language, night mode, the “Remind me” bells you set, the last position the app uses to work out distances for alerts, and a call in progress (so the app can resume it) · On Android, auto-backup is disabled, so none of this is copied to the cloud · On iPhone, this data may be included in the iPhone’s own backup (iCloud or a computer, as you set it up), except the app’s sign-in keys, which stay in the phone’s keychain and never move to another device · Clear the app’s data or uninstall to remove it.
- Call / Navigate: tapping Call opens your phone’s dialer with the number (the app never places calls itself); Navigate opens Google Maps. Those apps’ own policies then apply.
3. Alerts
- “Remind me” bells come in 3 kinds: this shop is near (100 m to 1 km) · this shop opened within 1–5 km · a cart of the chosen category is near. A bell rings once and then turns itself off. Distances are computed on your phone from the last position your phone knows. Your GPS coordinates are not sent to our servers.
- News that a cart moved or a shop opened is delivered through Google’s notification service (Firebase Cloud Messaging) as “topics”. Your phone subscribes directly with Google: to the topic of each shop with an “opened” bell, and to the topics of the roughly 1 km area cells around you × shop category (for “near” bells). Our server does not know who subscribes to which topic and does not know where you are. A message carries only the shop ID, category, a rounded shop position (about 100 m) and the time (an “opened” message also has the shop name); your phone decides whether to ring.
- When a cart gets close to your distance (about 400 m before it), the phone watches that cart for a few more minutes over the same public live stream the map uses, sending the cart’s rounded position, not yours, with a separate random ID and no account · As a backup, the phone downloads the public shop-list files of the area around you from time to time (about every 60 minutes, or every 30 minutes if Google’s notification service is not available) — the same files everyone sees on the map — which does not tell us who you are.
- Android: the app never asks customers for background location; bells use your last position from when you had the app open (if you yourself turned on “Allow all the time” for the app in your phone settings, the app also reads the system’s last known position).
- iPhone: Google’s messages are passed on by the Apple Push Notification service as silent messages; the app wakes up, decides by itself and shows its own notification (iOS may delay or drop some messages) · While a “near” bell or a category bell is on and you allowed location, the app keeps receiving your position in the background (started while the app is on screen, so “While Using the App” is enough; the iPhone shows the blue location indicator) so it can ring on time. Meanwhile the app keeps the public live stream around you open, as the map does on screen (it sends the roughly 1 km area and the IDs of shops you set bells for, with a separate random ID, no account, not recorded — as in section 2); your exact GPS position stays on the phone · It stops when no such bell is left on (it rang or you turned it off) · The app never asks customers for “Always”.
- Google (and on iPhone, Apple) can see that a phone (identified by a notification token) is subscribed to certain topics. The app creates this token only when it is needed — when you set a bell (and on Android, while you have a call job in progress, to receive the shop calling you back, section 7, or have reported a problem, section 9) — and deletes it when none of these is left.
- You can turn bells off in the app, or turn notifications off in your phone’s settings.
4. Signing in with Google or Apple (vendors and customers)
Every phone can sign in with a Google account. On iPhone there is also a “Sign in with Apple” button (Android does not have it).
| Data | Stored in | Purpose | Visible to |
|---|---|---|---|
| Your Google account ID or Apple user ID, and email, as one-way coded values (cannot be turned back into the ID or email) | Our database on Cloudflare | Recognise your account, let only owners edit their shop, keep banned accounts out | Nobody |
| Apple: Apple sends an email only if you choose to share it; if you choose “Hide My Email” it is an Apple relay address (ending in privaterelay.appleid.com), which we also keep only as a one-way coded value · You can use the app without sharing an email · Apple does not include your name in the sign-in token | Database on Cloudflare (one-way coded only) | As above | Nobody |
| Google name, email and profile photo · the name and email Apple gives (Apple gives the name only on the first sign-in, so the app remembers it on the phone) | On your phone (a Google account is also in the old system during the transition — section 14 · Apple sign-ins are not sent to the old system) | Show which account you are signed in with; the starting display name when you call a shop | You only |
| App sign-in keys (stored as one-way coded values, expire automatically), phone platform (Android or iPhone), last use | Database on Cloudflare | Stay signed in | Nobody |
When you sign in, the app asks Google Play (Android) or Apple’s App Attest (iPhone) to confirm it is the genuine app installed from the app store (to stop fake sign-ups) · When you delete an account that signed in with Apple, the app asks you to confirm with Apple once more, and we then ask Apple to end the “Sign in with Apple” link with this app (if the app is still listed, you can remove it yourself in Settings > your name > Sign in with Apple).
5. Vendors and shops
| Data | Visible to | Notes |
|---|---|---|
| Shop name, category, menu and prices (up to 20 items) | Public | An edited name or menu that trips the automatic word check waits for our team; customers see the previous version meanwhile |
| Shop phone number (must be a Thai number) | Signed-in users only | No longer in the public files; shown in the app to signed-in users, at most 60 lookups per account per day, never between people who blocked each other |
| Shop photo and menu photos (optional · one per menu item): the app crops them square (the shop photo to a circle), makes 640 px and 160 px versions and removes hidden data (such as where it was taken and the phone model) before upload | Public after the check | Every photo goes through an automatic image check by our cloud provider (Cloudflare Workers AI), which looks at whether it shows food / a cart / a stall and whether it contains forbidden items or contact details · Passed = served from cdn.rotre.app within seconds · Photos the check doubts, or could not check, are kept in private storage and wait for a team check · Photos customers report are checked by the team too · Old photos that are replaced or removed are deleted from storage |
| Open/closed flag, random install ID, the roughly 20 km area the shop is in, open/close/last-contact times | Open/closed is public | No coordinates · the install ID tells which phone is sending the location |
| Shop location, speed, heading, accuracy | Public, only while open | See “How shop location works” below |
| Weekly schedule: days, times and days off | You only (customers never see it) | Stored on our server so it survives a new phone; used only for reminders to open, which run on your phone · The app never opens your shop by itself; you tap to open |
| The “Take customer calls” switch and internal call counters (accepted, arrived, unanswered, declined, expired, no-show) | Our team only | Never shown to customers or anyone else; used to spot problems such as repeatedly accepting and not coming |
| Which version of the terms you accepted, and changes waiting for review (what changed, reason for a rejection) | You and our team | Rejection reasons are kept for 30 days |
| Banned accounts (only accounts that were banned): one-way coded account and email, time, reason | Our team only | Stops that account from coming back, even after it was deleted in the app |
How shop location works
- Location is shared as the shop’s position only between tapping “Open shop” and “Close shop”. On Android, a persistent notification with a “Close shop” button is shown the whole time · on iPhone, the system shows the blue location indicator in the corner of the screen the whole time.
- The exact position is kept only in server memory and is never written to a database. The public shop-list file holds only an approximate position (about 100 m) that is overwritten each time. We do not record where you have been.
- A shop set to sell “in one place” (customers see “at a usual spot”): when you open, the app takes one GPS fix and that becomes the still green pin customers see (no spot name or landmark). While open, the app does not track GPS continuously: it uses low-power location (Wi-Fi or cell towers) about once a minute only to confirm the phone is still on, and takes one precise GPS fix about once an hour; if you are more than about 150 m from the pin, the pin simply moves to the new position (no question asked). This pin is kept in server memory like any shop position and is not stored. Shops that sell “on the move” send a GPS position every few seconds while open.
- Closing the shop removes its location from the server within seconds and from the public file within about 20 seconds. If you close while offline, the app sends the close command when the connection returns.
- If the phone disconnects, the app is swiped away or the phone dies, the shop can stay on the map for up to about 10 minutes, then its location is removed. If no new position arrives for 20 minutes, the shop is closed automatically. Signing out on the phone that is sending location closes the shop first.
- Background location (“Allow all the time”) is requested from vendors only, after an in-app explanation, only so an open shop keeps updating with the screen off (on iPhone it also lets the system relaunch the app to keep sending if the app was closed while the shop is open). You can refuse and still open a shop · Customers are never asked for it (for bells on iPhone, see section 3).
- Places where people tapped “I’d like … around here” are shown to vendors as rough areas with a head count — no names or phone numbers. Street names come from your phone’s own place-name lookup service.
- Read-aloud and speak-to-type: call details are read aloud with your phone’s text-to-speech · On Android, if you tap the microphone button to reply or search by voice, the app hands over to your phone’s voice typing (for example Google’s, depending on your phone settings), which listens by itself and returns text. This button does not use the app’s microphone permission and the app does not record audio · The app’s own microphone is used only for in-app calls (section 7).
6. Calling a shop (“Ask this shop to come to me”)
| Data | Visible to | How long |
|---|---|---|
| Your display name (starts from your Google name on the phone, editable, up to 30 characters) and phone number | The vendor you call, during the job (removed from the vendor’s screen when the job ends) · the app tells you this before you enter the number | The phone number is deleted automatically after 6 months without calls (you enter it again on your next call) · the name is kept until you delete your account |
| Meeting pin = your GPS position when you call | Before the vendor taps “On my way”, they see only a rough area (about 100 m, with a 150 m circle) · the exact pin is sent to the vendor only after they accept | Not written to any storage; held in the memory of the live connection during the job and gone when it ends |
| What you want to buy, quantities, budget and a short note | The vendor you call | Inside the call only; gone when the job ends |
| Call state (account, name, phone, note, times, status — no coordinates) | The system | Deleted when the job ends · the reason it ended is kept for 30 minutes · account and name (no phone, note or pin) kept for 24 hours so problems can still be reported |
| Cancellation, no-show and suspension history, and call counts | Our team · you see your own suspension status in the app | Cancellations count over the last 30 days · suspensions as shown in the app · permanent suspensions and totals until you delete your account · used under the terms of use |
- During a call the customer’s app on Android keeps running in the background (with a visible notification) to show the status and the cart approaching; it stops when the job ends.
- The server decides “the vendor has arrived” by comparing the cart’s real position with the meeting pin held in memory.
- Meet by the road or in a public place. Vendors do not come into customers’ homes, rooms or hotels.
7. In-app chat and calls
Chat
- Chat is available from the vendor’s “On my way” until the job ends. Messages are relayed instantly over the existing connection; our server does not store chat messages. If a message cannot be delivered, the sender sees “not delivered yet”.
- Messages stay on both phones until the job ends. The vendor’s phone remembers the customer’s name and the chat of recently finished jobs for 24 hours so problems can be reported (cleared on sign-out).
- An automatic word check blocks forbidden words and messages asking for money in advance (from 14 October 2026 phone numbers, LINE IDs and links may be sent in chat). If a message contains doubtful words, our team is told only which category — not the text.
- Automatic translation: messages the other side typed in a language other than your app’s are sent to our cloud provider’s AI (Cloudflare Workers AI) to be translated and are not recorded. A translation may sit in the server’s cache for up to 6 hours (no name or account attached). You can turn translation off with the translate button in the chat.
- Photos in chat: the app shrinks a photo to at most 1,280 pixels and removes hidden data (such as where it was taken) before sending. Photos are kept in private file storage, can only be opened by signed-in users who have the photo’s code (the people in the chat), and are deleted automatically after 24 hours. Every photo goes through the automatic image check (Cloudflare Workers AI); nudity, drugs or weapons are removed at once. Our team may look at reported photos or photos the check could not look at; reported photos are kept for up to 30 days.
- When you report a problem, you may attach the latest chat messages from your own phone (you see them first and can untick them) — see section 9.
Free internet calls (beta)
- Who can call whom: a signed-in customer can call a shop that is open right now (vendors can turn these calls off in the “Let customers call you” card in the app), but not if either side has blocked the other or the customer is suspended from calling · A vendor can call only the customer of a call job they accepted · A shop has one call at a time; a call nobody answers ends after 45 seconds.
- What each side sees: the vendor sees the calling customer’s display name, the customer sees the shop name. Neither side sees the other’s phone number.
- Microphone: used only during a call (on Android a “Talking” notification is shown during the call · on iPhone the system’s microphone indicator).
- Where the audio goes: the audio is encrypted all the way (WebRTC standard) and goes directly between the two phones or, when a direct connection is not possible, through a Cloudflare relay that forwards the encrypted audio without decrypting it · We do not record, listen to or keep any audio · With a direct connection, the other phone learns your IP address, as with any internet calling app.
- What the server does: it passes the call set-up data between the two sides (technical data for connecting the audio, which includes the phones’ IP addresses) and does not record it · During a call it keeps only the call state (call ID, who called, the customer’s account, the job concerned, times) and deletes it when the call ends · Opening a call connection is counted in the traffic log (section 10) the same way as a call job, with no audio.
- After a call the app sends call-quality figures: call length, direct or relayed, the mobile carrier name (Android), time to connect, delay, audio dropouts, network changes during the call and your answer to “Was the sound clear?”. They are kept only as monthly totals, not linked to an account, phone number or location, to watch quality and cost, and are deleted after about 2 months.
- Incoming calls when the app is not open (Android): a vendor with an open shop gets a full-screen incoming call even with the screen off or the app in the background · A customer with a call job in progress whose app is closed: when the shop calls back, we send a wake-up message through Firebase Cloud Messaging to your account’s private topic (the topic name is a one-way coded value; Google sees only that value). The message has only the call ID, the shop ID and the shop name — no phone number, location or your name. The app subscribes to this topic only while you have a job with a shop and unsubscribes when it ends · On iPhone there is no full-screen incoming call and no wake-up message; incoming calls show inside the app only.
- This is a trial feature. We may switch free calls off for everyone if quality or cost does not work out; calling by phone number keeps working.
8. “I’d like … around here”
- Requires signing in (so the “people waiting” number reflects real people). The app sends your position, the category and the shop you chose (if any). The server keeps only a coarse square of about 220 m, never your coordinates, plus a one-way coded value of your account (not your account ID itself) to count people once.
- A request expires after 40 minutes · vendors see only “around … · N people waiting”, never your name or number · the daily counter (up to 10 per account) is deleted after 2 days.
9. Reports, blocking and content checks
- Reporting a shop from its page (no sign-in needed): we keep the shop ID, reason, any text you type and the time — nothing that identifies you (only a one-way coded install ID for up to 48 hours to stop repeat reports). The app asks Google Play (Android) or Apple’s App Attest (iPhone) to confirm it is genuine before sending.
- Report / block during a call or in chat: we keep the reporter’s account, the reported person, the call concerned, the reason, your text and any chat messages you chose to attach (up to the latest 30 from your phone). The reported or blocked person is never told who reported them.
- Reports and attached chat are kept until our team closes the case, plus 90 days, then deleted (cases never closed are deleted after 400 days). Only our team can read them.
- Reporting a problem with the app (the “Report” button on the map · sign-in needed · up to 5 reports a day per account): we keep the reporter’s account, whether you reported from customer or vendor mode, the kind of problem, the text you type (up to 1,000 characters), photos you choose to attach (up to 3), the app version, phone model and Android or iOS version, the screen you reported from and the time — no location, no phone number. The photos, app version and phone model are seen by our team only. Photos are kept in private storage and deleted 30 days after the case is closed; the whole report is deleted 365 days after the case is closed. If you delete your account, your reports are unlinked from it and can no longer be traced to you. When our team takes, fixes or answers your report, the app notifies you. The page rotre.app/ปัญหา publicly lists every report: its number, kind, whether it came from a customer or a vendor, each step with its time, the title and fix written by our team, how many people reported the same thing, and the text you typed once it passed an automatic check (our word check, then only the text — no account or identity — goes to Cloudflare Workers AI to look for rude words, names, phone numbers, addresses, links or other personal details). Text that does not pass shows only the kind of problem until our team has looked at it, and our team can hide the text or the whole report at any time — never your photos, name, phone number or account. The report sheet in the app says this before you send.
- Block list: who blocked whom and the name seen at the time, kept until you unblock or delete your account. A signed-in customer who hides a shop also blocks it.
- An automatic word check covers shop names, menus, prices, the shop phone field, display names, notes and chat. Forbidden content cannot be saved or sent; doubtful content goes to our team.
- Our moderation log (what was reported, when, what we did, when) is kept for 400 days to show that we acted in time as the law requires. It contains no reporter identity and no chat text. See the notice and takedown policy.
10. Traffic log (90 days)
Thailand’s Computer Crime Act requires service providers to keep computer traffic data, so we keep a minimal traffic log:
- What: the hour, your account ID in our system, the type of request (sign-in, shop, customer, report/block, account, vendor live connection, call jobs and in-app calls), your IP address (stored encrypted), the first and last time in that hour, and a count.
- Not kept: location, chat content, call audio or the details of individual requests · people browsing the map without signing in and anonymous shop reports are not logged at all.
- Who can open it: only on a formal written request from an authority with legal power, and every opening is recorded (those records are kept for 400 days).
- Deleted automatically after 90 days · Cloudflare’s database keeps an automatic recovery copy of deleted rows for up to 30 more days (this cannot be turned off) · the log is not in our own backups.
- Separately, Cloudflare sees the IP address of everyone using the app and website in order to deliver data and block attacks, under Cloudflare’s own policy.
11. What other people can see
12. Phone permissions
When you first open the app (right after choosing a language), it shows one page listing the permissions it will ask for and why: location, notifications, microphone, camera and photos. Tap “Allow all” and the phone asks for each one in turn. You can refuse any of them and still use the app; only the features that need that permission will not work until you turn it on in your phone settings (on Android, camera and photos need no permission, so the page shows them as “Allowed”).
Android
| Permission | Why |
|---|---|
INTERNET | Load maps and shop lists; send shop location, calls and chat |
ACCESS_FINE_LOCATION, ACCESS_COARSE_LOCATION | Customers: distances on the phone, the meeting pin when calling · Vendors: share the shop’s location while open |
ACCESS_BACKGROUND_LOCATION | Vendors only: keep updating with the screen off while open · requested after an in-app explanation |
FOREGROUND_SERVICE, FOREGROUND_SERVICE_LOCATION | Tasks with a visible notification: sending the shop’s location while open · customers during a call job |
POST_NOTIFICATIONS | “Remind me” bells (shop near, shop opened), call jobs, chat, incoming in-app calls, news about problems you reported, and vendor shop-status notifications |
RECORD_AUDIO | Microphone, for free internet calls (beta) only; used only during a call, never recorded · asked on the permissions page when you first open the app; if not allowed then, the app asks again when you make or answer a call |
MODIFY_AUDIO_SETTINGS | During an in-app call: switch the sound between the speaker, earpiece or a Bluetooth headset, and put the phone in conversation mode |
FOREGROUND_SERVICE_MICROPHONE | Keeps the call audio going when you switch apps or the screen turns off during a call, with a “Talking” notification · starts when the call connects, stops when you hang up |
USE_FULL_SCREEN_INTENT | Full screen over the lock screen only for things that need an answer right away: an incoming in-app call, and (vendors) a customer calling the shop over while the screen is off, so you can answer/decline or tap “On my way / Not now” · the app never unlocks the phone for you · without this permission a normal notification is shown instead |
BLUETOOTH_CONNECT | Play in-app call audio through a Bluetooth headset you have already connected · not used to scan for or track nearby devices |
WAKE_LOCK, RECEIVE_BOOT_COMPLETED | Deliver pending commands (such as “close shop”) when the connection returns · resume sending or re-arm schedule reminders after a restart (does nothing if the shop is closed and no schedule is set) |
SCHEDULE_EXACT_ALARM | Vendors: close the shop at the time you set and show schedule reminders on time (you grant it yourself) |
REQUEST_IGNORE_BATTERY_OPTIMIZATIONS | Vendors: ask the battery saver not to stop the app while the shop is open (so customers keep seeing it) |
ACCESS_NETWORK_STATE, ACCESS_WIFI_STATE, VIBRATE, com.google.android.c2dm.permission.RECEIVE, READ_GSERVICES | Ordinary permissions added by Google’s components (sign-in, notifications) and the map component: check whether there is a connection, vibrate for notifications, and receive notifications through Firebase Cloud Messaging |
USE_BIOMETRIC, USE_FINGERPRINT | Come with a Google component the app uses. The app never uses fingerprint or face scanning. |
| (No camera or photo-library permission) | For a photo the app opens the system camera or photo picker and receives only the photo you choose · speak-to-type uses your phone’s voice typing, not the app’s microphone permission |
Android auto-backup is disabled (allowBackup=false), so on-device data is not copied elsewhere.
iPhone
| Permission | Why |
|---|---|
| Location “While Using the App” | Customers: show you on the map, compute distances on the phone, the meeting pin when calling a shop over, and “Remind me” bells (they may continue in the background when started while the app is on screen — section 3) · Vendors: share the shop’s location while open · If you turned off “Precise Location”, the app asks for precise location once when you open the shop so the pin matches where you really sell |
| Location “Always” | Vendors only, asked when opening the shop after an in-app explanation, so an open shop keeps sending its position with the screen off or after the app was closed; stops when you close the shop · You can refuse and still open a shop · Customers are never asked for it |
| Notifications | “Remind me” bells, call jobs, chat and shop status · messages from our server go through Firebase Cloud Messaging to Apple’s notification service |
| Microphone | Free internet calls (beta) only; used only during a call, never recorded |
| Local Network | Lets an in-app call connect directly when both phones are on the same Wi-Fi, for clearer sound · not used to discover or list devices in your home |
| Camera | Take shop photos, menu photos and photos to send in chat |
| Photos | Pick a shop photo, menu photo or a photo to send in chat · the app uses only the photos you pick and never reads or uploads anything else from your library · you can choose “Limit Access” |
| Background modes | Location: an open shop and customers’ bells (section 3) · Audio: call audio keeps going when you leave the app, and call jobs are read aloud to vendors with the screen locked · Silent notifications and background refresh: let bells decide on the phone and run the backup check of the public shop-list files |
The iPhone app does not track you across other apps or websites, so it does not ask for “Allow Tracking”, and it does not ask for contacts or Bluetooth.
13. Legal bases
- Consent — device location, notifications, microphone and camera/photos; give or withdraw it at any time in your phone settings, or by closing the shop / turning a bell off.
- Providing the service you ask for (contract) — accounts, shop details, schedules, call jobs (including passing your name, phone number and meeting pin to the vendor you call) and in-app calls.
- Legitimate interests — the safety of users and the system: server checks on every command, request limits, app genuineness checks, word and photo checks, reports and blocks, cancellation and suspension history.
- Legal obligations — the 90-day traffic log, the moderation log for reported content, and answering formal written requests from authorities.
We do not use data for advertising or profiling, and we do not sell, rent or share it for marketing.
14. Service providers
- Cloudflare, Inc. — servers, database, file storage, the automatic image check (Workers AI) and the relay that forwards encrypted in-app call audio (Cloudflare Realtime) for the app and this website. Servers may be outside Thailand, in the Asia-Pacific region or elsewhere. Cloudflare processes data as our service provider.
- Google — sign-in with a Google account · Google Play checking that the app is genuine on Android (at sign-in and when reporting a shop) · topic notifications (Firebase Cloud Messaging, section 3, and incoming calls, section 7) · fonts (Google Fonts), which see your IP address as with any web request · Google Maps, only when you tap Navigate.
- Apple (iPhone only) — Sign in with Apple (section 4) · App Attest checking that the app is genuine (at sign-in and when reporting a shop) · the Apple Push Notification service, which delivers notifications from Firebase Cloud Messaging to your iPhone.
- OpenFreeMap (tiles.openfreemap.org) — map images; receives requests for the area you are viewing and your IP address, like any web request. It does not receive your GPS position.
- Telegram — sends our team a message when a shop waits for review or a problem is reported. The message says only which shop/account and what kind of issue — no reporter identity, phone numbers or chat text.
- Services on your own phone — the dialer, text-to-speech, voice typing and place-name lookup, working under your phone’s settings.
- Transition period: the old system on Google Firebase (Singapore) is still running as an emergency backup and for older app versions, and still holds shop data from before the move. Anyone who signs in with Google in the current app is also signed in to the old system (Google name, email and profile photo · Apple sign-ins are not sent to the old system). When the old system is shut down, all data in it will be deleted and we will update this page.
The app contains no advertising or analytics SDK. We disclose data to authorities only on a lawful written request, and only what is asked (see notice and takedown policy, section 7).
This website uses no tracking cookies or analytics. It is served by Cloudflare and uses fonts stored on this website itself, not loaded from another provider. The site only remembers the language and colour theme you picked, in your own browser.
15. How long we keep data
| Data | Kept for |
|---|---|
| Rough area sent while browsing the map | Only while connected; not recorded |
| One-way coded install ID and IP address (abuse limits, repeat-report check) | At most 48 hours |
| Shop location | Only while open; removed on closing (within about 20 seconds), signing out, account deletion or after the silence limits in section 5 · no route history |
| Shop details, menu, photo and schedule | Until you edit or delete them, or delete your account |
| Content waiting for review (new text or photo) | Until our team decides · rejection reasons 30 days |
| Account (one-way coded values) | Until you delete it in the app or ask us to · sign-in keys expire 60 days after last use |
| Customer display name | Until you delete your account |
| Customer phone number | Deleted automatically after 6 months without calls (counted from when you last entered it or last called), or on account deletion |
| Meeting pin, order and call details | Until the job ends (end reason 30 minutes · account and name of a recent call 24 hours for reporting) |
| Chat messages | Not stored on the server · on phones until the job ends (vendor’s phone 24 hours) · anything attached to a report follows the report |
| In-app calls | Audio and call set-up data are not kept · call state until the call ends · monthly call-quality totals (not linked to an account) about 2 months |
| “I’d like … around here” | 40 minutes · daily counter 2 days |
| Cancellation, no-show and call-suspension history | Cancellations count over 30 days · suspensions for the period shown in the app · permanent suspensions and totals until account deletion |
| Block list | Until you unblock or delete your account |
| Reports (including attached chat) | Until closed, plus 90 days · cases never closed at most 400 days |
| Moderation log | 400 days |
| Traffic log (encrypted IP addresses) | 90 days (plus up to 30 days in the database’s recovery copy) |
| Record of who opened the traffic log | 400 days |
| Banned-account list | Until our team lifts the ban; kept even after the account is deleted in the app |
| Backups | Cloudflare’s database keeps automatic recovery copies for 30 days (cannot be turned off) · our own daily backups 14 days · deletion/ban records and shop-photo copies at most 35 days · no backup contains shop locations |
| Data on your phone | Until you clear the app’s data or uninstall |
| Old Firebase system (transition) | All deleted when the old system is shut down |
16. Security
- All data travels over encrypted connections (HTTPS, and encrypted connections for live location, call jobs, chat and in-app call audio).
- The server checks every command; only the owner can edit or delete a shop · we do not store readable emails or Google / Apple account IDs on the server · IP addresses in the traffic log are stored encrypted.
- No system is 100% secure. If a data breach puts you at risk, we will notify as the Personal Data Protection Act requires.
17. Your rights
You may request access to and a copy of your data, data portability, correction, deletion, restriction, objection, and withdraw consent at any time (withdrawal does not affect what was done before).
- In the app, right away: edit your shop, menu and schedule · close the shop to stop and remove location · turn call jobs off · turn free internet calls off · turn bells off · unblock · sign out · delete your account and data · turn off location, notifications and the microphone in your phone settings.
- Other requests: contact us (section 18). We reply within 30 days and may ask you to confirm you own the account.
- If you think a call suspension or a hidden shop is a mistake, contact our team to check again.
- You may complain to Thailand’s Office of the Personal Data Protection Committee (PDPC).
Children and young people
The app has no age limit and is not designed specifically for children. For users aged 10 or younger, a parent or guardian should sign in, enter the phone number and make calls for them. Parents can contact us (section 18) to see or delete a child’s data.
Changes to this policy
We will update this page and the effective date when the policy changes, and tell you in the app or ask for new consent where needed for significant changes.
18. Contact
- Message the Facebook Page “รถเร่ใกล้ฉัน” (RotRe)
- Email kampanatth0222@gmail.com (privacy requests: access, correction or deletion of your data)
Read next: Terms of use · Notice and takedown policy · Delete account and data