Who we are
Captain Aetos is developed and operated by Nsr Elmtagr for Digital Marketing LLC (شركة نسر المتاجر للتسويق الإلكتروني), an Egyptian limited liability company, commercial register 11501 (Ismailia Investment Registry). Privacy contact: admin@nsrelmtagr.com.
What the app does
Captain Aetos is a decision assistant for ride-hailing captains using the inDrive, Uber and DiDi apps. It reads the request cards visible on your screen and shows a verdict over them according to rules you set (price per km, distance caps, minimum rider rating and trip count, request age, areas). The app is read-only: it never taps, accepts, rejects or negotiates on your behalf.
Captain Aetos is independent: it is not affiliated with, endorsed by or partnered with inDrive, Uber or DiDi. "inDrive", "Uber" and "DiDi" are trademarks of their owners and are named here for identification only. Every request remains your decision; the verdict shown is guidance built from your rules and what is on screen, and it can misread.
AccessibilityService
Captain Aetos uses Android's AccessibilityService API for one purpose: reading the ride requests on screen inside the supported ride apps only (inDrive, Uber and DiDi): request price, pickup and trip distance and time, rider rating and trip count, payment method, request age and the addresses shown. In inDrive it reads the text on screen and captures the map region of the request detail screen to read route distance and time. Uber and DiDi draw their request cards as pictures whose text cannot be read, so the app takes a screen capture in the moment only while DiDi is on screen, while Uber's request screen is open (even before a request card shows on it), or while an Uber request card floats over another app, and reads it on the phone. Captain Aetos is not an accessibility tool for people with disabilities; this is disclosed to you in the app and your explicit consent is required before the service can be enabled. The app reads no other app and takes no screen captures at any other time.
iPhone version
The iPhone version does not use an accessibility service, which iPhone does not offer. It uses Apple's screen broadcast (ReplayKit), which you start yourself inside the app and can stop at any time from the red indicator at the top of the screen.
While the broadcast runs, the app reads the screen text on the phone with Apple's text recognition (Vision). When it finds a request card of inDrive, Uber or DiDi it sends you a local notification with the verdict by your rules. The picture and screen text do not leave the phone for this reading.
Your rules (fare per km, distances, rating, payment methods) are stored on the phone.
Pictures of unread requests: if the app recognises a request card of inDrive, Uber or DiDi but cannot read it, it sends our server a picture of that screen on its own, only after you accepted the welcome screen that says so. The picture is scaled down to at most 720 points wide and the top of the screen (about 17%) is painted grey because notifications appear there. It may show the rider's name, the addresses and the fare. It comes with the ride app, the failure kind, the app language, the picture size, the Aetos version, the iPhone model, the iOS version and a random identifier. At most 10 pictures a day per ride app. Their only purpose is finding why reading failed, fixing it and testing the fix, and we delete them once we no longer need them and in any case after 90 days at most.
Usage analytics: the app sends fixed words such as a screen opened, a verdict result or a ride app seen, and approximate bands of your rules, never their exact values, with the Aetos version, the iPhone model, the language and a random identifier made on the phone. They contain no name, number, address, fare or screen text.
The app also sends a diagnostic report each time reading stops, after you accepted the welcome screen: its duration, how many screens were read and how many had text or a fare, how many times each ride app was recognised, how many verdicts and unread requests there were, the slowest reading time, memory, screen size, iOS version and iPhone model. If the screen shows inDrive request controls ("Accept for" in its lower half with "Offer your fare" under it) and the app cannot tell which ride app it is, it sends one picture of that screen per reading session with the top band greyed; it may show the rider's name, addresses and fare. If the number field in «Tell us about you» refuses the number you typed, the app sends the text you typed as it is. The only purpose is finding and fixing errors.
If you are trying a TestFlight build and send feedback or a screenshot from the TestFlight app yourself, it goes to Apple and reaches us through Apple, under Apple's privacy policy as well.
From build 1004 the app asks for your name, WhatsApp number and governorate on a "Tell us who you are" screen and sends them to our server so we can follow up on any problem and reply to you. If you send a report from inside the app, we receive the problem type, the text you write and one picture only if you pick it yourself. If you turn on "Heading home", the app asks Apple's place service built into the iPhone where the pickup and drop-off addresses are (with the name of your governorate and country), so the address text reaches Apple under its privacy policy; it does not pass through our servers and we do not keep it.
To stop all of this, stop the broadcast or delete the app.
What we collect and what we do not
- Request and rider data is processed in your phone's memory to show the verdict and then discarded. It is never stored persistently on the phone and never sent to any third party, except the pickup and drop-off address text, which goes to the place service on your phone when you yourself turn on "Heading home", as described in the next item. The only parts that reach our servers are the request numbers and the failure pictures described under "Failure pictures" below, and an Uber or DiDi picture may show the rider's name and the addresses.
- "Heading home" and the place service: this feature is optional and off until you turn it on and set where your home is. While it is on, the app takes the pickup address text and the drop-off address text as the ride app prints them (with the name of your governorate and country) and asks the place service built into Android on your phone where each address is, then works out whether the request takes you closer to home and by what share. That service is run by your phone's services provider (Google on most phones), so the address text reaches that provider under its own privacy policy. The text does not pass through our servers and we do not keep it; no rider name, price or identifier of ours is sent with it, and the answers stay in the phone's memory for a while and are never written to storage. Your home (the point and the name you picked) is kept on your phone only, never reaches our server, and you can remove it from the same page at any time. The feature does not use GPS and asks for no location permission: the pickup place printed on the request stands for where you are. The text you type to find your home is asked about the same way.
- Screen and map captures are read by on-device text recognition (on Android Tesseract and Google ML Kit running on the device, on iPhone Apple's Vision library), kept in memory for the moment of reading and then deleted, and are never saved on the phone. None of them is uploaded, except the failure pictures described in the next item.
- Failure pictures: in inDrive, if the app cannot read the route distance or time from the map on the request detail screen, it sends our server, on its own, a picture of the map region only (not the whole screen); it shows the route and the pickup and drop-off points and contains no rider name, though a notification or another app's floating bubble lying over the map at that moment would show in it. In Uber and DiDi, if the app cannot read a request card, or the card goes away before it is read, it sends the screen as it was at that moment, which may show the rider's name, the addresses and any notification or floating bubble of another app that was on your screen. Also in Uber and DiDi, if a request was read in full but its values look impossible for a real request (a price per km outside the sane range, or a speed that cannot fit the distance and time), the app sends a picture of that request: the request card in Uber and the screen as it was in DiDi, and a fixed word for the kind of odd value goes with the usage analytics. Such a picture may show the rider's name and the addresses, and it falls under the same consent and the same daily limits described in this item. Each picture comes with the request's numbers and codes (price, distances, rating, trips, request age, failure code, and a fixed word for the kind of any other window greyed on it, such as a floating or picture-in-picture window, never that app's name), the request's random code described under usage analytics, your phone's display settings (system language, font size, screen size and density), the app version, phone model, Android version and ride app. This happens only after you give explicit consent in the in-app disclosure that names it, and at most 30 pictures a day per device, of which at most 10 each for Uber and DiDi. Its only purpose is finding why reading failed, fixing it and testing the fix. We do not share these pictures with any third party or use them for anything else, and we keep a picture only as long as we need it to fix the reading and test the fix, then delete it. To stop it, turn off the accessibility service or uninstall the app.
- Activity and free-plan counting: for one day, the app keeps a short irreversible hash of each marked card locally so the activity summary does not count it twice. The free plan offers unlimited list verdicts and counts five successful detail analyses per day. The hash contains no request text and is not sent to our server.
- App usage analytics: the app sends our server a fixed category of events, such as opening a screen, a list verdict, a detail-analysis result, an alert playback or a subscription attempt, together with the categorical result, ride app, Aetos version, interface language, market and governorate, and derived device identifier. Each request also gets a random code that links its events together and says nothing about the rider, and how long its card stayed in front of you is sent in bands (for example under 2 seconds). This includes how many requests were read and how many were not, with the category of the missing part (fare, distance or numbers). With the license check the app also sends the phone maker and model, the Android version and the versions of the supported ride apps you have installed (inDrive, Uber and DiDi only, and only after you accepted the in-app disclosure), so we can tell whether a reading problem is general or tied to one phone or version. Repeated events are grouped locally before upload. Analytics contain no rider name, phone number, address, request text, screenshot, fare or the exact values of your rules. We use them to find reading failures, understand journeys, improve the product and measure conversion. We do not use them for ads or sell them to a third party.
- Your opinion of the app and the Google rating: after the app has answered real requests for you on at least two days, it asks you once "How useful is Captain Aetos to you?" with five choices. Your answer reaches our server as one word with the usage analytics, and if you pick "Poor" or "Very poor" the "Report a problem" screen opens so you can tell us what happened if you wish. On a later visit, whatever you answered, the app shows Google Play's own rating card; Google runs that card and we never receive your rating or comment from it, and we give no reward for a rating.
- Your rules and settings (price per km, caps, areas, language, bar opacity) are stored in full on your phone and excluded from cloud backup.
- An aggregated summary of your settings: as part of usage analytics the app sends a summary of your settings in categories only, such as your price-per-km band (for example 6 to 8, not the number itself), how many areas you avoid or prefer but not their names, and whether alerts are on. It never sends area names or exact values. We read these categories aggregated across all captains to improve the default settings and build new features. We do not use them for ads or sell them. They are deleted with the other usage events after 90 days.
- Problem reports: when you tap the flag on the bar or send "Report a problem", our server receives the problem type, the text you write, one picture only if you pick it yourself from your gallery, the map-region picture of that request when there is one and you accepted the disclosure (the app takes no whole-screen capture for this), the numbers and codes of that request (price, distances, rating, trips, request age, state code), the reader's last steps in codes and numbers only, and the app and Android versions. You can open "Report a problem" from the bar or from the reader notification. The screen asks you not to write names or phone numbers. Purpose: fixing the problem and replying to you. The phone also keeps the last 20 numeric reports locally.
- License data (sent to our server): a derived device identifier (the first 128 bits of an irreversible SHA-256 hash of the Android ID), app version, distribution channel, the app's signing-certificate fingerprint, a discount code if you entered one, the Google Play install referrer (only the fields of the link that opened the store, such as a partner's code in their invite link, sent until our server has it once), interface language, market and governorate, and your license key or Google Play purchase token when you subscribe. Purpose: running the trial, the free plan, subscription verification and blocking tampered copies. The app contacts the server about every 3 hours and on activation, and retries sooner when a contact fails.
- Contact details: on a "Tell us who you are" screen before setup starts, the app asks for your WhatsApp number, country and governorate, which are required to continue using the app. Your name on the same screen is optional from version 26 (it was required from version 0.9.2); if you type it, it is sent with the number. You can change the name and number at any time in the support card. The app sends them to our server with your device record so we can reach you about a problem with the app or your account, and ask about your experience so we can improve the app. We do not share them with anyone else, they are not included in app usage analytics events, and you can ask us to delete them as described on this page.
- Market and governorate: the country and governorate you pick on the "Tell us who you are" screen and in settings are sent to the server to show the price and messages for your area. The app uses no GPS and does not ask for the location permission.
- We do not collect: your precise or device location, contacts, any picture other than one you picked for a report or the failure pictures described above, microphone, advertising ID, or anything for advertising. The app contains no ads and no third-party analytics or tracking SDKs, apart from the technical data the Google ML Kit library sends in the Android version, described under Third parties. A link to this policy is inside the app (home screen and subscription screen).
The captainaetos.com website
- This section is about the website only, not the app. The site asks for no sign-up, name or number, and the numbers you type into its calculators are worked out in your browser and never reach us.
- On the site we use Google Analytics and Google Tag Manager from Google and Microsoft Clarity from Microsoft to learn how many people visit, which pages they open, where they came from and which button they pressed, such as the app download button, using a tool or opening a question. Microsoft Clarity also records page movement, clicks and scrolling to show us how a page is used. These tools use cookies, a random browser identifier, the IP address, device and browser type and the approximate country, under Google's and Microsoft's privacy policies. On the payment page Microsoft Clarity hides everything you type, the receipt picture and the code, so none of them reaches Microsoft.
- On the site we use the Meta Pixel from Meta (Facebook and Instagram) to measure our ads there: whether a visitor came from an ad, which page they opened and whether they pressed the download button. It uses cookies, a browser identifier, the IP address and device type, under Meta's privacy policy. Meta may use this data to show our ads to people similar to the site's visitors. We do not send Meta anything you type on the site, nor your name or number.
- When you arrive from an ad or post link that carries a campaign name, our server counts the visit: the campaign name, the page, its load time, how long the site was visible and how many times the download button was pressed, with a random identifier your browser keeps for that session only. No IP address, cookie or device identifier is stored, and these records are deleted after 90 days.
- We do not use site visit data to identify you, we do not link it to your device in the app and we do not sell it. You can block it by blocking cookies in your browser or with Google's Google Analytics opt-out add-on.
Third parties
- Google Play Billing handles payment and subscriptions under Google's privacy policy; we never see your card details.
- Apple In-App Purchase: when you subscribe on iPhone, payment is handled by Apple under Apple's privacy policy and we never see your card details. The app sends our server the transaction signed by Apple together with your device's random identifier, to activate your plan.
- Cloudflare hosts the license server (Workers and D1); license requests pass through Cloudflare's network.
- Google ML Kit (Android version only) is Google's on-device text recognition library. The library does not send the images to Google, but it sends Google technical data about its own operation: device maker, model and OS version, app package and version, a per-installation identifier that does not identify a person, performance metrics and error codes, encrypted over HTTPS and not transferred by Google to third parties (https://developers.google.com/ml-kit/android-data-disclosure).
- Android place service (Android Geocoder) is the system service on your phone, run by your phone's services provider (Google on most phones). It receives the pickup and drop-off address text only while the "Heading home" feature is on, and answers with the place of that address. We do not own this service, pay for it, or send it any key or identifier of ours.
- Google Play Developer API is used to verify your subscription (purchase token, order id, expiry). When you cancel, it also gives us the reason you picked in Google Play's cancellation survey and, only if you picked «Other» and typed something, the words you typed. We keep them with your subscription record after hiding any phone number or email address in them, read them ourselves only to understand why people cancel and improve the app, and never share them.
- Telegram: our team receives short alerts on Telegram. When you send us a subscription problem report, Telegram receives the problem type, the app version, your country and governorate and the words you wrote in the report, with a note that a picture exists but not the picture itself. Telegram does not receive your name, your WhatsApp number or your device identifier. This text is subject to Telegram's privacy policy.
Retention and deletion
- The server-side device record (derived id, verification times, trial state, market and governorate, interface language, phone model, Android version and ride app versions, name and WhatsApp number if you saved them, discount code if entered, subscription records: purchase token, order id, expiry, cancellation reason and your words in the cancellation survey if you wrote any) is kept while you use the app and for 12 months after the last contact, for accounting and support, then deleted automatically. Problem reports are deleted automatically 12 months after they are sent; any picture attached to a report (one you picked or a failure picture) is kept only as long as we need it to solve the problem or to fix the reading and test the fix, then deleted. Usage events are automatically deleted after 90 days.
- You can ask for your data to be deleted at any time with the steps on the data deletion page: captainaetos.com/delete-data . We delete your device record, its subscription records, reports, pictures and usage events within 30 days. Uninstalling the app deletes all local data.
Security
Server traffic is HTTPS only; server answers are digitally signed and verified by the app. The app requests only: draw over other apps (for the bar), the accessibility service (for reading), notifications (one notification showing whether the reader is on, which you can silence in settings), vibration (for the good-request alert, only if you turn it on), internet and network state (for licensing), and Google Play's billing permission (for the subscription). The reader switches itself off after a period you choose without a ride app on screen, and you can stop it at once from the home screen.
Your rights
Under Egypt's Personal Data Protection Law No. 151 of 2020 and comparable laws, you may access, correct and delete your data with us, object to its processing and withdraw consent (by disabling the accessibility service or uninstalling the app). The legal basis for license data is the performance of our contract with you (running the trial and the subscription); for screen reading and sending failure pictures it is your explicit in-app consent. Requests go to admin@nsrelmtagr.com and are answered within 30 days.
Children
The app is intended for adult ride-hailing captains and is not directed at anyone under 18.
Changes
When this policy changes we update the date above and publish the new version at the same URL; when a change touches what is read or sent, the app shows the disclosure again and the new item does not apply before you accept it.