Privacy Policy

Last updated: 2026-11-10

In short

The main points of this policy, in plain words. The full policy below explains each one.

• What we collect: your account details (name, username, email and, if you add one, phone number), your location, the places and routes you add, your posts, comments and messages, the photos you add, the emergency alerts you send, receive or offer to help with, and the other things section 2 lists, such as likes, follows and reports.

• Your location: Darbil uses it while the app is open on your screen, and in the background only while you record a route or use "Direct guidance". Your latest position is saved on our server so that alerts from people near you can reach you.

• Why: only to run Darbil. There are no ads, and we do not sell or share your information with advertisers or data brokers (companies that buy and sell personal information).

• Anyone with a Darbil account can see your profile, who you follow, your posts and comments (every post is public) and the places and routes you make public. Unless you make it private, they can also see your exploration map, which shows roughly where your places are, private ones included. They never see your email address or phone number.

• Emergency alerts: people near you can see your username, the situation you chose, the photo you took, your vehicle description and how far away you are, so that they can find you. We have not checked who these people are. We do not send them your exact location, but someone using a modified app could see your alert from anywhere and work out where you are (section 6). Your username identifies your public profile. Anyone who offers to help also sees your name and profile picture.

• We, the operator of Darbil, can open anything we store, including private places and routes and your messages. The companies that run parts of Darbil for us, such as our database, our server and our photo storage, also handle your information. We may also disclose information when the law requires it, or to protect someone's safety.

• Where: our database is in India, photos are stored in Eastern Europe, and our server and its logs are in the United States, all outside Kuwait. Other services we use may handle your information in other countries.

• How long: almost nothing is deleted automatically. Your account is kept until you delete it. A post you delete is hidden, but we keep a copy until you delete your account. You cannot delete messages in the app. Your messages and emergency alerts are kept until you delete your account. Server logs are deleted after 90 days. Backup copies of our database are kept for 8 days.

• To delete your account: Settings, then "Account", then "Account Information", then "Delete Account". This deletes your places and routes (public ones too), posts, comments, messages you sent, emergency alerts and photos; section 12 lists what stays.

• Among the things that stay: reports, copies on other people's phones and our server logs. A backup copy of our database made before a removal still holds that information until it expires, 8 days after it was made.

• Questions, or a request for a copy of your data or a correction: support@darbil.app. We reply to requests within 30 days.

1. About this policy

This policy explains what Darbil collects, why, who can see it, who else receives it and how long it is kept. It describes what the app does today, including the parts we have not yet finished. "We" means the operator of Darbil.

2. What we collect

Your account

To create an account you give us your name, a username, an email address and a password. You can also add a phone number, but you do not have to: it is optional, and you can add, change or remove it later in the app (each needs your password). We store your password only as a one-way hash, so we cannot read it. Darbil does not use a phone number for anything today: we do not verify it, we send nothing to it, it plays no part in emergency alerts, and other users never see it. You can also add a country, a short bio, a profile picture and a cover picture.

We also record when your app last contacted our server while you were signed in (we update this time no more than about once every 15 minutes), and the exact time your last known position was saved. We use the first only to count how many people use Darbil each day, and we do not use the second for anything today. We never show either to anyone.

When you sign up in the app, we store which version of the Terms of Service and the Privacy Policy you accepted, and the date and time you accepted it. Other users never see it. Accounts made before the app asked for this have no such record. It is deleted with your account.

If the operator of Darbil suspends your account, we store the date of the suspension on your account. Other users never see it. While it is set, our server refuses every request your signed-in app makes except deleting the account, signing out and reading the account's state, it ends your open connection, and it ends any alert you had active. If the operator restores your account, the date is removed. It is deleted with your account.

Your location

While Darbil is open on your screen, it uses your precise location to show you on the map (unless you have turned off Precise Location for Darbil in your phone's settings). As you move, your current position is sent to our server and saved on your account as your "last known position". It is sent only while your phone is connected: positions are not saved up while you are offline and sent later. We keep only the latest one, and each new position replaces the old one. Your phone also sends its position when you open Darbil or sign in, and each time the "Nearby Alerts" list loads or refreshes, and it is saved the same way.

Darbil also uses your location in the background, but only while you are recording a route or using "Direct guidance" to a pin. During that time it keeps receiving your precise location even when the app is not on your screen, and iOS shows that an app is using your location. The points recorded in the background stay on your phone and reach our server as part of the route when it is saved. Your current position is also sent to our server during that time, as it is while Darbil is open on your screen, and saved as your last known position, so that alerts from people near you can still reach you.

For a recording, background use stops when you pause, stop, save or discard it. For Direct guidance, it stops when guidance ends: when you end it, or when you arrive while Darbil is open on your screen. If you are recording and using Direct guidance at the same time, it stops only when both have stopped. If you arrive while Darbil is in the background, your phone shows a notification if you allow notifications, but guidance, and its use of your location, may carry on until you end it or open Darbil there. Darbil never asks for "Always" location permission.

If you do not answer the "Route recording still open" reminder, which appears 3 hours after you start and 3 hours after each time you choose to continue, Darbil stops the recording about 10 minutes later and saves it to your account as a private route, or when Darbil next starts, if your phone closed it in the meantime. If the recording is paused when the reminder's deadline passes, it is stopped and saved when you resume or when Darbil next starts, if your phone closed it in the meantime. If the recording has too little movement to be a route, it is stopped and nothing is saved. If your phone closes Darbil while it is recording, the last few points may be missing.

Signing out stops a recording and any guidance, and with them Darbil's use of your location. If you have a recording that is not saved, Darbil asks first: "Save and sign out" saves it to your account as a private route (offered only when you are online), "Discard and sign out" deletes it, or you can cancel and stay signed in. If your account is suspended, Darbil does not offer to save a recording when you sign out, because a suspended account cannot save a route: you can discard it and sign out, or cancel. Before you delete your account, Darbil asks you to discard an unsaved recording, because it cannot be saved to an account that is being deleted. If you are signed out without being asked, because your session ended or after a password change, Darbil stops the recording and keeps it on this phone, and offers it back only when you sign in to that same account.

Your last known position is never shown to other users. It decides whether alerts from people near you reach you and, for an alert you were not sent, whether you can offer to help. It does not expire, signing out does not remove it, and it is deleted only when you delete your account.

Places and routes

A place you add is saved at the point you choose on the map, which is not necessarily where you are. A recorded route saves the path you travelled, with the time, altitude and speed at each point, and the name, description and route type you give it. If you import a GPX file, we save the path it contains, with any times and altitudes in the file, and the file's name. Places and routes are private unless you make them public.

Posts, comments, likes and follows

We store your posts (text, up to four photos, a public route if you share one, and your approximate location if you add it), your comments, what you like, the people you follow and the people who follow you, the ratings you give routes, and the badges you earn.

Your exploration map

Darbil builds an exploration map for you. It marks squares of about 5 km within roughly 10 km of each place you add (private places and places imported from a GPX file included), each post you add a location to, and, for a post without a location, the start of the public route it shares, even if that route is someone else's. It is not built from your route recordings or your background location. Areas it marks stay marked: deleting the place or post does not unmark them. Because any Darbil user can see your map unless you change who can (section 5), it can show other people roughly where your private places are, though not the exact spot.

Photos

Photos you add to a place, a post, your profile picture or cover picture, or an alert are stored in our image storage. A photo can contain hidden information, such as where and when it was taken. Before a photo is uploaded, your phone makes a new, smaller copy of it, and Darbil does not copy that information into the new copy. For post and alert photos, our server also removes that information before the photo is stored, and a post photo is refused if your phone could not make the copy. For place, profile and cover photos, if your phone cannot make the copy, the original photo is uploaded and stored as it is. For an alert photo, if making the copy fails or takes longer than 30 seconds, the original photo is uploaded, and our server removes that information if it can read the photo.

Messages

A conversation can only be started by someone offering to help with an emergency alert, and only with the person who sent the alert. Messages are stored on our servers so they can be delivered and shown in the conversation. They are not end-to-end encrypted. When someone starts a conversation to help you, Darbil sends a notification to your phone. Darbil can also send a notification when someone sends you a message and you do not have that conversation open. A notification shows the sender's username and never any message text. If you mute a conversation, or remove it from your inbox, Darbil sends no notification for new messages in it.

Emergency alerts

When you send an alert we store your exact location, the situation you chose (one choice is "Medical"), your vehicle description if you entered one, and the photo you took, unless the camera could not be used or the photo did not upload. We also store when you sent it and when it ended, which users it was sent to and who offered to help. If someone else's alert is sent to you, or you offer to help, your account is recorded on that alert. The time of your last alert is also saved on your account, because our server allows one alert every 30 minutes. Section 6 explains who receives it.

Reports

If you report something, we store your report: what you reported, the reason you chose and any note you write. If someone reports you or your content, that report is stored too, together with your account. We do not tell the person you report who reported them.

When three different people have an open report on the same post, comment, public place or public route, our server stores the time on that item and hides it from everyone except its author. The app tells an author when their post is hidden. The operator can restore the item, which removes the hidden mark, or take it down.

Our server also emails the operator of Darbil about new reports, at most 20 an hour, through Resend, the email service named in the list of companies below. Each email gives only the report's number, the kind of item reported, the item's number, the reason chosen, how many open reports the item has, and whether it is hidden. It never contains the note the reporter wrote, any text of the item, or any name, username, email address or phone number. If more reports come in within the hour, our server sends at most one summary email an hour, which says only how many reports were held back.

Your device

If you allow notifications, Darbil sends our server a notification token for your phone when you sign in, each time Darbil starts, when you come back to Darbil more than ten minutes after it last sent it, and when you allow notifications later, and we store it on your account. We keep one token per account, from the phone that sent it last. To create the token, your phone gives Expo, our notification provider, Apple's notification token and a random installation number; after that, Darbil's notification software sends these two to Expo again each time Darbil starts, whether or not anyone is signed in, and while you are signed in Darbil also asks Expo for the token each time you come back to it. Each time Darbil starts it also checks with Expo for app updates, sending another random installation number, the version of the app it is running and, if Darbil crashed while starting the last time, the error text. Expo receives your IP address with these requests. None of these is an advertising identifier.

When you sign out, Darbil asks our server to remove this phone's notification token from your account, and the server removes it only if it is still the token on your account — so another phone that registered since keeps its notifications. If Darbil has not sent this phone's token since it last started, it asks the server to remove whichever token your account has. If that request cannot reach us, for example because you are offline, it is not sent again: the token stays on your account, and this phone can keep receiving notifications about alerts near your last known position, about your own alerts and about new messages in your conversations, until someone signs in on this phone with notifications allowed or another phone registers for your account. The same applies when Darbil signs you out by itself because your session has ended. When your password is changed or reset, our server removes the token from your account, whichever phone it came from. Deleting your account deletes the token. If someone else signs in on this phone with notifications allowed, the token moves to their account.

What stays on your phone

While you are signed in, Darbil keeps copies on your phone so it works offline: your profile (including your email and, if you added one, your phone number), places, routes, posts, your exploration map, drafts, your recent place searches, the place and last position used for weather, and other people's posts and places you have viewed. Your sign-in key is kept in the phone's secure storage.

When you sign out or delete your account, Darbil removes these copies and the sign-in key from the phone. Your settings (such as language, units and map style) and the offline maps you downloaded stay. When you sign out, changes that have not reached our server yet also stay, and so does a recording that Darbil stopped because it signed you out without asking. They are kept for your account only: they are sent, or offered back to you, when you sign in to that account on this phone again, and other accounts on the phone cannot see them. Deleting your account removes this phone's unsent changes and any recording in progress.

Photos you picked or took in Darbil, route files you exported, pictures you viewed and map images of areas you looked at can stay in the phone's temporary storage until iOS clears it; Darbil clears its stored map images about every 14 days. Deleting the app removes what Darbil stored, but iOS may keep the sign-in key, if you were signed in, and the installation number used for notifications.

3. What we do not do

Darbil has no advertising, and we have added no analytics or crash-reporting service. Darbil itself sends no crash reports: the only error information it sends is the error text described in section 2, which Expo's update system sends if Darbil crashes while starting. From the update checks described in section 2, Expo gives us statistics about app updates that do not identify you. If you have allowed your iPhone to share analytics with app developers, Apple may also send us crash reports through its own system. We do not track you across other companies' apps or websites, and we do not sell or share your information with advertisers or data brokers. Darbil does not read your contacts, your calendar or the iPhone Health app.

4. Why we use it

We use your information only to run Darbil:

• Maps, your position, recording routes and guiding you to places.

• Sending your emergency alerts to people near you, and sending you theirs.

• Posts, comments, likes, follows, ratings, badges and your exploration map.

• Messages and notifications.

• Keeping Darbil safe: reviewing reports, checking what you write against a list of words that are not allowed, hiding content, suspending accounts, enforcing blocks and limiting abuse.

• Weather, place search, offline use, password reset, and counting how many people use Darbil.

5. What other people can see

Anyone who signs up to Darbil is an "other user". Other users can see:

• Your name, username, profile picture, bio, country and the date you joined. Your cover picture is shown only to you.

• Who you follow, who follows you, and the numbers. Anyone can follow you without your approval, and you cannot remove a follower. Blocking someone stops them following you again, but does not remove their follow: other users still see them among your followers, and you will see them there again if you unblock them.

• Your badges and when you earned them. The "Explorer" and "Wanderer" badges come from your exploration map, so only people who can see your map can see them.

• Your posts, and your comments on posts and on public places and routes. Every post is public; there are no private posts. If you add a location to a post, your phone takes the last position it knows and rounds it to about 1 km. That rounded point is sent with the post to other users' apps and puts the post in "Near me" for people near it, although Darbil does not display the point.

• The ratings you have given routes. Other users' apps receive each rating with your account number and when you gave it, although Darbil shows only a route's average rating and how many ratings it has.

• The places and routes you make public. A public route gives other users its whole path, with the time, altitude and speed at each point, and its name and description, and every signed-in Darbil app downloads all public routes in full when it starts. For an imported route, other users' apps also receive the name of the GPX file, although Darbil does not display it. Other users can save your public places and routes and export them as GPX files to keep.

• Your exploration map. By default any Darbil user can see it. To change this, tap the map at the top of your Profile to open "My Exploration", tap "Who can see my map?", and choose "Followers" (anyone who follows you, and anyone can follow you) or "Private" (only you).

• The posts, places and routes you have liked, and when you liked each one, which another user's app can request from our server, although Darbil does not display them.

• In a conversation: your name, username and picture, and whether you have opened their messages. Darbil marks them as read as soon as you open the conversation, and tells the other person at once.

The map can show how many people have, in the past week, posted with a location or added a public place in the area on screen. It shows a number only, never who. It can also mark public places in that area that were added or commented on in the past week.

Other users never see your email address, your phone number or your last known position.

Blocking someone stops you reaching each other through alerts, messages and the feed, and hides each other's places, comments and exploration maps. They can still see your basic profile and your public routes, save those routes and export them as GPX files. If they have saved one of your routes, you cannot delete it. You can make it private: it then leaves their "Saved" list in Darbil, and our server stops sending it to them. A copy their phone already holds may stay until their app next refreshes.

The operator of Darbil can open any place, route, post, comment, message, alert or account, even if it is private or has been removed. This is meant for reviewing reports, but our server does not check that the item was reported. For a message, it also shows up to five messages before and five after it, and the names of both people in the conversation. For an account, it shows only what other users can see, plus how many public places, public routes and alerts it has. Each time an item is opened this way, our server log records which operator account opened which item. Viewing the list of reports, which shows who made each report and the first 140 characters of each reported message, post or comment, is not recorded in our server log. The operator can also read our database directly, and our server log does not record that. MongoDB Atlas, our database provider, keeps a record of access to our database account, but on our plan not of each time data is read. Only the operator has this access.

6. Emergency alerts — who receives what

This is the most sensitive thing Darbil does. People you have never met, whose identity we have not checked, can learn that you need help and how far away you are, and can see the photo you took and your vehicle description. We do not send them your exact location, but this information is there to help them find you. That is the purpose of the feature, and it is why the app shows you your alert to review before you send it.

Your alert goes out in widening circles around the place you sent it from: first 1 km, then 10 km, then 15 km. It reaches Darbil users whose last known position is inside the circle and whose phone has registered for notifications from Darbil (section 11). They do not need to have the app open, and their last known position may be out of date. If nobody offers help, the next circle follows after about two minutes, or at once if nobody is inside a circle. Until your alert ends or someone offers help, people whose last known position later comes within 15 km are alerted too. Users you have blocked, and users who have blocked you, do not receive it and cannot see it. You see how many people it was sent to, never who they are; that number can include phones that no longer show Darbil's notifications. Your alert stays active for about two hours unless you cancel it first ("Cancel SOS"). While it is active, any other signed-in user within 30 km of the position their phone sends can see it in the "Nearby Alerts" list. Our server does not check that position, so someone using a modified app could see the alerts in any area and, by asking from several places, could work out where you are. We limit how often each account can ask, which slows this down but does not prevent it.

The phones of people who receive your alert, or see it in the "Nearby Alerts" list, get your username and account number, the situation you chose, your vehicle description, the photo you took and the time you sent the alert. They do not get your exact location or your profile picture. When someone opens the "Nearby Alerts" list, our server tells their phone how far you are from the position it sends, and the app shows that distance, not a map. The app does not link the alert to your profile, but your username and account number identify your public profile (section 5). Anyone who offers to help also sees your name and profile picture in their messages. The notification on their phone shows your username and can appear on a locked screen; it never contains your location. Your phone number and email address are never shared.

When someone offers to help, you see their name, username and picture in your messages, and if you offer help on someone else's alert, they see yours. Other people who see the alert see only how many people have offered help, not who. Once someone has offered, your alert stops being sent to more people until everyone who offered has withdrawn ("Cancel Help Offer"), but it stays in the "Nearby Alerts" list until it ends. We cannot check that someone who offers help is really coming, and only they can withdraw their offer; if they delete their account, their offer is removed too, but signing out does not remove it. Withdrawing does not remove the conversation.

7. Companies and services involved

These companies run parts of Darbil for us:

• MongoDB Atlas — our database. It holds everything this policy says we store, except the photo files themselves.

• Railway — runs our server, so every request the app sends to our server passes through it. Railway's own request logs record each request's IP address, the address requested, which may include your location — for example when the app asks for the alerts near you, or for the places in the area of the map on screen — and the versions of the app and of your phone's system that the request carries. They do not record what you send. Our own server logs record your account number with the time of actions such as location updates (without the coordinates), your IP address or account number when you hit a rate limit, each time the operator opens an item to review a report, and technical errors, which can include details you submitted. Railway keeps all of these logs for 90 days.

• Cloudflare R2 — stores photos. Photos are uploaded through our server; your phone then downloads them directly from Cloudflare, so Cloudflare receives your IP address when you view a photo.

• Expo — delivers notifications, through Apple's notification service, and delivers app updates. The text of each notification, which can include a username, passes through Expo and Apple.

• Resend — sends the email when you ask to reset your password. It receives your email address and the one-time code. It also sends the operator of Darbil a message about new reports (the Reports paragraph above says what it holds) and a message when removing an account's content fails. The second gives the account number and technical details of the failed step, such as its name and the number of attempts. Neither contains a name, username, email address or phone number.

• Stadia Maps — supplies the map styles other than the default, the map on a route's page and when you import a GPX file, and offline maps. Your phone requests these map images directly, so Stadia receives your IP address and the area of the map, including the whole area you download for offline use.

Each of these companies handles your information under its own standard terms of service. We have not signed a separate data-processing agreement with any of them.

Your phone also contacts these services directly. Their own privacy policies apply:

• Apple — the default map, and the map of your exploration, are Apple Maps, so Apple receives your IP address and the area of the map.

• MET Norway — for weather, your IP address and your location rounded to about 10 metres, or the place you chose.

• OpenStreetMap (Nominatim) — when you search for a place, your IP address and the words you type.

• Apple Maps or Google Maps — when you choose "Open in Apple Maps" or "Open in Google Maps" (under "Go to this pin"), the place's coordinates are handed to that app or website.

• Google — while Darbil is running, your phone checks its internet connection by contacting a Google address, so Google receives your IP address: about once a minute while the connection works, every 5 to 20 seconds while your phone is connected to a network that does not reach the internet, and again whenever the connection changes.

When you email us, your message passes through Cloudflare's email routing to our mailbox.

We may also disclose information when the law requires it, or when it is needed to protect someone's safety.

8. Where your information is held

Our database is held by MongoDB Atlas in Mumbai, India. Photos are stored by Cloudflare R2 in Eastern Europe. Our server runs on Railway in the United States (its US West region), and Railway keeps our logs there too. The other companies and services named above handle your information where they operate, which may be in other countries. All of this is outside Kuwait. MongoDB Atlas also keeps the backup copies of our database in Asia; it does not say in which country.

9. How long we keep things

Today almost nothing is deleted automatically. Specifically:

• Your account and last known position: until you delete your account.

• Places and routes: until you delete them or delete your account. Once another user has saved your route, you cannot delete it by itself, but you can make it private. Darbil then stops showing it in the library of anyone who saved it, and our server stops sending it to them; a copy a phone already holds may stay until the app there next refreshes. The route comes back to their library if you make it public again. Deleting your account deletes all your places and routes, saved by others or not.

• Posts and comments: when you delete one, it is hidden from everyone, but we keep a copy until you delete your account. A post's photos are kept until then too.

• Messages: you cannot delete them in the app. Deleting a conversation removes it from your own inbox only. Deleting your account removes the messages you sent.

• Emergency alerts, with their location, photo, the list of people alerted and the people who offered help: kept until the person who sent them deletes their account. Someone who deletes their account is removed from the people who offered help and from the people alerted.

• Ratings and older route comments: you cannot remove them one by one. They are deleted if the route is deleted (including when its owner deletes their account), or if the person who wrote them deletes their account.

• Photo files: deleted when you delete the place or route they belong to. When you delete your account, the photo files still linked to it are deleted too: your profile and cover pictures, and the photos of your places, routes, posts and alerts. Pictures you have replaced and photos you removed from a place are kept.

• Your exploration map: until you delete your account.

• Reports: kept. The copies our server keeps of changes your phone sent after being offline (such as a route or place you created offline): kept until you delete your account.

• Content we remove for breaking our Terms is hidden, not erased, until the account that made it is deleted. The exception is a bio we clear after a report, which is erased; the files of a profile or cover picture we clear stay in our storage, even after the account is deleted.

• A password-reset code stops working 15 minutes after it is sent, or once it has been used. We store only a one-way hash of it.

• Server logs: Railway keeps them for 90 days, then deletes them.

• Backups: MongoDB Atlas, our database provider, backs up our database once a day, and each backup copy is kept in Asia for 8 days. We use these copies only to restore the database after a failure. If the database were lost or damaged, it could be restored from one of those copies, but changes made after that copy might be lost.

We know much of this is kept longer than it should be. When that changes, this page will change too.

10. How we protect your information

The app talks to our server over encrypted connections. Passwords are stored only as one-way hashes. Your sign-in key is kept in your phone's secure storage. Photos are kept in private storage and reached only through signed links that stop working within about an hour and a half; anyone you forward such a link to can open it until then. Only the operator of Darbil holds access to our database, our server, our photo storage and our app-update account.

No service can promise perfect security. If a security breach affects your information, we will tell you as soon as we reasonably can.

11. Your choices

In the app you can:

• Change your name, bio, country and pictures. Once you add a bio, country or picture, you can change it but not remove it.

• Change your username (once every 30 days) or your email address, or add, change or remove your phone number. Each of these needs your password.

• Choose who can see your exploration map.

• Block other users.

• Export a route or a place as a GPX file, one at a time, from its page.

• Delete your account (section 12).

You can turn off location or notifications for Darbil in your phone's settings. Without location you cannot record a route or see yourself on the map, and alerts from people near you are matched to the last position we received from you, which becomes out of date. An alert you send needs a position your phone found in the last two minutes; without one, the alert is not sent. Without notifications you may not be told about alerts from people near you, about someone offering to help with your alert, or about a new message.

Notifications reach only one phone per account: the last one to register with our server. A phone registers when you sign in on it, each time Darbil starts on it, when you come back to Darbil more than ten minutes after it last registered, and after you allow notifications for Darbil, as long as notifications are allowed. So using Darbil on another phone, or someone else signing in to Darbil on this phone, can stop this phone receiving them. Signing out on a phone removes the registered phone from your account only if it is that phone, or if that phone has not registered since Darbil last started on it; an older version of Darbil removes it in every case. Then none of your phones receives them until one registers again — unless the sign-out could not reach our server, or Darbil signed you out by itself because your session ended; then the registered phone stays, unless your password was changed or reset, which removes it whichever phone it is.

To ask for a copy of your data, to correct something or to ask us to delete something, email support@darbil.app. We will reply within 30 days.

12. Deleting your account — exactly what happens today

You can delete your account in the app: Settings, then "Account", then "Account Information", then "Delete Account". Here is what that does today.

Removed:

• Your account: name, username, email, phone number, bio, country, password, notification token, last known position, and your profile and cover pictures.

• Your posts and their photos, and every comment and like on them, including those from other people. Your comments (older route comments too), your ratings, the likes you gave, who you follow and who follows you, your exploration map and your badges.

• Your places and routes, public ones too, with their paths, descriptions and photos. Other people's "Saved" entries for them are removed, and so are the likes and comments on them. Other people's posts that linked to them stay, without the link.

• The places and routes you saved, your folders, and the copies our server kept of changes your phone sent after being offline.

• Emergency alerts you sent, with their location, situation, vehicle description and photo. If one is still active, it is ended first. Your account number is also removed from the lists of people alerted and people who offered help on other people's alerts.

• The messages you sent, in every conversation. You leave those conversations; the other person keeps the messages they sent. A conversation with no messages left is deleted.

• On this phone: your sign-in key, the copies of your account's data that Darbil saved here, such as places, routes, posts and your exploration map, and changes not yet sent.

Important — not removed today:

• Reports. Reports about you stay. Only the operator of Darbil can see them, and the operator can see who made each one. Reports you made about other people stay too, without your note, and still carry your account number.

• A record that your account was deleted: its account number and the date. It holds no name, email address or phone number. Until the deletion is finished and checked, the record also lists the reference numbers of the content it removes; after that, only the account number and the date remain.

• Messages other people sent you, which stay with them.

• Photo files that were no longer linked to your account before you deleted it, for example a picture you had replaced or a photo you had removed from a place.

• Copies on other people's phones, until their app refreshes, and offline maps you downloaded on your own phone. On another phone where you used your account, the changes it had not sent and any recording it stopped when it signed you out stay until Darbil is deleted from that phone; if that phone is still signed in, the copies of your account's data also stay on it until Darbil there next reaches our server.

• Our server logs, which record your account number with the time of actions such as location updates, and the request logs of Railway, our server host, which record your IP address and each address the app requested, which may include your location. Railway keeps both for 90 days and then deletes them.

Our database is backed up once a day. The backup copies are not changed when something is removed, so a copy made before a removal still holds that information until the copy expires, 8 days after it was made. If removing part of your content cannot be finished at once, your account is still deleted and Darbil keeps trying.

13. Children

Darbil is not for anyone under 18. We do not verify age. If you believe a child has an account, email support@darbil.app. There is no in-app tool for removing someone else's account, so the operator of Darbil looks into it and can delete the account by hand.

14. Changes to this policy

When this policy changes, we post the updated date at the top of this page. The date changes only when the text changes.

15. Contact us

Questions about this policy or your data: support@darbil.app