Privacy Policy

Ride-In-Sight is provided by RIS TECHNOLOGIES LTD, a company registered in England and Wales, company number 17524939 ("RiS Technologies Ltd", "we", "us"). Our registered office is 5 Brayford Square, London E1 0SG, United Kingdom. We decide how and why your personal data is used, so we are its controller under UK data protection law. We develop the Ride-In-Sight apps and sell them on Google Play. On the App Store, the iPhone app is currently published under our founder's individual developer account while it moves to our company account; these terms and our Privacy Policy apply to it in the same way.

For any privacy question or request, email support@rideinsight.app. You can also phone us on +44 7340 594844. We have not appointed a Data Protection Officer.

• Ride-In-Sight is a tool for people who drive or deliver for ride-hail and delivery platforms. It is not directed at children.
• The apps read ride offers on your phone. Ride-In-Sight never uploads pictures of your screen by itself, and the text read from an offer stays on your phone except for the items listed in section 6. The only exception is what you choose to send us through Share & Improve: one screenshot that the app has masked and you have checked, or the details of one offer you report (section 12b).
• Each offer the app checks is recorded with your account: which driver or delivery app and when, not what the offer said. On Lite this counts towards your daily allowance; Pro has no daily limit.
• The apps do not upload your offer history, offer screenshots or documents. On our website you can choose to send us a screenshot or file to help us support more platforms (section 12a). In the app you can choose to send us feedback, a screenshot or a report about an offer to help us fix a problem (section 12b).
• Your phone's GPS position is not sent to us.
• We do not show adverts, sell your data, use your phone's advertising identifier, or track you across other companies' apps or websites.
• You can close your account in the app, on our website or by email. After 30 days it is permanently deleted, apart from the limited records described in section 16.

Creating an account in the Android app

We collect your name and email address. You may optionally provide a phone number. We do not verify your phone number, call you or text you. We also collect your market (country, region and city); the kind of driving you do and your vehicle; the type of phone you signed up from; and the referral code you joined with, if any. The iPhone app cannot create an account: you sign in with an account you already have. If that account has not been set up yet, the iPhone app asks for the same details (name, an optional phone number, market, the kind of driving you do and your vehicle) to finish setting it up.

Creating an account or applying on our website

We collect the same details, plus a password you choose. If you apply as a partner or affiliate, we also collect the business name, handle, category and web address you give us.

Signing in

The apps sign you in with a link or a 6-digit code that we email to you; they do not ask for a password. When the Android app creates your account it sends our sign-up system a random value in place of a password; it is not kept on your phone and cannot be used to sign in.

We use these details to create and run your account, set the app up for your market and credit referrals. You need an email address to have an account; the other sign-up details are used to set the app up for you.

We email you to sign you in and about your account, your referrals, closing your account and anything you send us. We do not send marketing email.

If you use Contact support in the app, your own email app opens with our address filled in and the app's version and your phone's system version in the draft. You decide whether to send it.

You can also use Share & Improve in the app to tell us about a problem, with one screenshot or a report about an offer if you choose. Nothing is sent until you check it and confirm. Section 12b explains what is sent and how long we keep it.

Ride-In-Sight shows what a ride offer is worth to you. To do that, it reads the offer on your screen.

• On Android it uses an Accessibility service you switch on yourself, limited to supported driver and courier apps (for example Uber Driver, Bolt Driver, FREENOW, Deliveroo Rider and Just Eat Courier). The app lists them when you switch the service on, and it never reads customer ordering apps or any other app. It reads the offer card (fare, distance, time, pickup and drop-off) only while you have offer checks on, whether or not a shift is running. It never taps, types or changes anything in another app. It can also use display over other apps, to show our rating on top of the offer, and screen capture, which you start, when an offer cannot be read through the Accessibility service.
• On iPhone it uses a screen broadcast that you start and can stop at any time.

Text recognition runs on your phone: Google ML Kit's on-device model on Android, Apple's Vision on iPhone. An offer can show passenger details such as a first name and rating. These are used on your phone to assess the offer and are never sent.

Two separate things can leave your phone. Nothing else about an offer does.

a. The offer record (every member)

For each offer the app checks automatically, it records against your account which driver or delivery app it came from (when the app recognised it), when, and a one-way code for that offer, so one offer is not counted twice. The code is not made from the offer's places or wording and cannot be turned back into them. On Lite these records count towards your daily allowance of offer checks; Pro has no daily limit. You cannot switch this record off, because the allowance depends on it. We keep the records until your account is deleted.

b. Intelligence look-ups (only if you accept Intelligence)

Where Intelligence is available in your app and you have accepted it, the app sends our server the place it needs to place on the map: a destination you type, or the drop-off shown on an offer. When your phone has no recent GPS position, it can also send the pickup shown on the offer, so the destination check can measure from there instead; your phone's GPS position itself is never sent. A full postcode is sent as shown; an address with a house number is cut down to its postcode area (for example "E1"); a place or street name is sent as read. Places found in the list built into the app are not sent.

The request carries your sign-in, so at that moment our server knows which account asked. Our server keeps the place and its map position, without your account, so the next look-up is faster. If it does not already know the place, it asks our map provider, OpenCage, using the place text and country alone. Stored places do not yet have a fixed deletion period.

On iPhone, offers appear on a floating card (Picture in Picture) on your phone. Nothing is sent to show an offer there.

What Ride-In-Sight does not send

Ride-In-Sight does not send screen pictures, offer screenshots (section 8), your offer history or the text read from offers (other than above), unless you choose to send a screenshot or a report about an offer through Share & Improve (section 12b).

The apps use your phone's location to judge whether an offer takes you towards where you want to finish and, if you turn on shift distance, to measure the distance you drive during a shift you started, including when another app is open or your phone is locked. It pauses on a break and stops when the shift ends. Your position is not sent to us or anyone else; only the distance total is kept, on your phone.

The market you chose at sign-up (country, region and city) is kept with your account.

Saving offer screenshots is off when you install the app. It starts only if you accept the explanation in the app and switch saving on. The app never uploads screenshots by itself. A screenshot you choose to send us is covered by section 12a (on our website) or section 12b (Share & Improve in the app); in the app, only a masked copy you have checked is ever sent.

• Unmasked on your phone, masked when exported. Trip screenshots are stored unmasked on your phone. Images exported through RiS are masked. The unmasked pictures are kept only in the app's own private storage on your phone, which other apps cannot open, and are left out of your phone's cloud and computer backups. Every picture that leaves the app, whether you share it or save it, is a masked copy made on your phone at that moment: the passenger's name, door numbers and road names of home addresses, and the second half of full postcodes (in the United States and Canada, street names and the last part of the postal code) are covered. If a screenshot cannot be masked reliably, it is not kept, and if a copy cannot be masked, nothing is shared or saved. The original is never shared or saved anywhere else.
• Hidden from screen capture. On Android, the Trip Offers screen and its picture viewer are blocked from screenshots and screen recordings while they are open. On iPhone, the offer pictures in the Offers list and the picture viewer are hidden from screenshots and screen recordings using the method iOS makes available; iOS does not guarantee it for every way of capturing the screen.
• When they are deleted. Screenshots are kept for 7 days unless you choose 14 or 30 days or to keep them. A screenshot is also deleted, with the information used to mask it, when you delete its offer or your offer history, when its offer is no longer among your latest 500 offers, and when you close your account in the app. A masked copy made for sharing is not deleted while you may still be sending it: on Android it is removed by your next share, the next time the app starts, or once it is more than an hour old; on iPhone the app does not write a copy to share.
• Saving a masked copy. In the picture viewer you can choose to save a masked copy to your photo library (Photos on iPhone, Gallery on Android). Ride-In-Sight saves only when you ask, and on iPhone it asks only for permission to add photos, never to read them. A copy you save or share belongs to you: Ride-In-Sight does not delete it, and from there you can share it yourself, other apps with photo access can see it, and your phone's photo or cloud backup service may copy it.
• iPhone working copy. While offer checks run, the screen broadcast passes the unmasked picture of each offer to the app through protected storage on your phone, left out of backups. It is deleted once the offer is processed, or after 12 hours at most, and is never uploaded.

Your offer history (your latest 500 offers, including the pickup and drop-off as shown), your saved destinations, your offer screenshots and your documents stay on your phone and are not sent to us, except a screenshot or offer report you choose to send through Share & Improve (section 12b). Documents leave your phone only when you send them yourself, by email or another app.

You can delete a single offer or your whole offer history, documents and saved destinations in the app. Closing your account in the app also deletes the screenshots kept in the app on that phone. Signing out does not delete what is on your phone; uninstalling the app does, except pictures in your photo library. Offer history, screenshots kept in the app and documents are left out of your phone's backups.

To protect your account and your plan, we register each phone you use: a one-way identifier made from the phone's system identifier, an identifier for this installation of the app, the phone's make and model, and the app version.

We keep the settings you choose with your account so they follow you between phones, such as your vehicle, offer thresholds and pickup limits. We also record when you first used the app and how many offers it has read for you (a count only), and on Android when you signed in, to run your membership and referral progress.

• Android crash reports (on unless you turn them off). If the Android app crashes or hits a serious error, it prepares a crash report and sends it to Google Firebase Crashlytics, which we use only to find and fix faults in the app. A report contains what went wrong and where, the app version, your phone's model and system version, whether the rating overlay and screen capture were running, and short technical markers (for example, which step of signing in the app had reached). Reports do not include your account or any offer, but Crashlytics links them to an identifier for this installation of the app, and it keeps the report and that identifier on your phone until the report is sent. You can turn crash reports off at any time in Settings › Privacy & data › Send crash reports. Turning them off stops new reports and deletes any report still waiting on your phone without sending it; a report the app has already passed to Google for sending cannot be recalled.
• Android usage reports (off unless you turn them on). If you turn on usage reports in Settings › Privacy & data, the app sends Google Firebase Analytics events such as an offer being detected or read, the overlay being shown, a shift starting or ending, and periodic counts, with the ride app's name. They never include fares, addresses or your account. Turning them off stops new reports; it does not delete reports already sent.
• Text recognition (only if you allow it). On Android, automatic offer reading uses Google ML Kit, and it starts only after you choose Allow. ML Kit keeps an identifier for this installation on your phone and stores empty diagnostic records; Ride-In-Sight blocks their upload. When your phone is online, these records are usually deleted within a minute, without being sent. Any record older than seven days is deleted the next time Ride-In-Sight runs its cleanup: when the app starts, when you turn automatic offer reading off, and in the background about every six hours, online or offline. Android may delay background work, and the cleanup cannot run while your phone is switched off or the app has been force-stopped; it runs again when the phone or the app next starts. The screen image and the text read stay on your phone. You can turn automatic offer reading off in Settings › Privacy & data; this deletes ML Kit's identifier.
• iPhone. The iPhone app contains no third-party crash-reporting or analytics software.

The Android app does not use the advertising identifier: the permission is removed and Firebase is set not to collect it.

We keep your referral code, the referrals made with it, and the points and progress they earn. Points have no cash value and are explained in our Terms of Use. If you join through another member's referral, that member and the two members above them in the referral chain can see your referral code, your referral status, how many people you have referred and the points your activity earned them. They cannot see your name, email address or phone number. Your referral QR code is drawn on your phone or on the page from your referral link; we do not store QR images or send your link to a QR service. You can add a membership card to Apple Wallet or Google Wallet from Membership & Wallet in the app or from your member page on our website. The card shows your name, your role, your membership status, your points and your referral code, with a code that opens your referral link; it can also show a campaign you are in, how many people you have referred and your Driver League position. We update the card when you open your member page on our website; other changes, such as new points or a store purchase, appear the next time you do. For Apple Wallet, your iPhone gives us a device identifier and a notification token so that we can send the update, and we delete them when you remove the card. A Google Wallet card is held by Google, under Google's privacy policy, in your Google account. If you close your account, a card may stay saved in your Wallet, but it is no longer valid. When an account closes, we keep the card's identifier and, for Apple Wallet, your iPhone's notification details for up to 7 days, then delete them.

On our website you can send us an offer screenshot or a supporting file (an image or a PDF, up to 10 MB) with a Community Research contribution, to help us check whether Ride-In-Sight can support a platform. Sending one is always your choice; the apps never do it for you.

• What we receive: the file, and what you type with it (a title, notes, the category, your country and, if you choose one, the platform), linked to your account.
• Who can see it: only the Ride-In-Sight team reviewing contributions. Files are stored privately with Supabase in London (section 15); they are never public and are opened only through a link that expires after 5 minutes.
• Other people's details: please hide passenger names, phone numbers and addresses before you send a screenshot. If a file still shows someone else's details, we use it only to review the offer and delete it on the schedule below.
• How long we keep it: a file you upload but do not submit is deleted after 24 hours; a submitted file is deleted 90 days after we approve or reject the contribution. The contribution itself (title, notes, our decision and any points) stays with your account. If you close your account, your contributions are deleted with it and their files within a day.

In the app, Share & Improve lets you show us a problem with Ride-In-Sight, such as an incorrect fare, missing trip information, a delayed assessment or an offer it could not read. You can send a written description, one screenshot or image you choose from your phone, or a report about one offer saved in the app. Sending is always your choice: nothing is sent automatically, and nothing is sent until you have checked it and agreed.

Ordinary RiS offer screenshots remain on-device unless you separately choose to submit a reviewed image through Share & Improve.

• What we receive: the provider, whether it was rideshare or delivery, the kind of problem and anything you write (up to 1,000 characters); the app's version and build, and a reference number for the submission. The country is not something you choose: we take it from the country registered on your Ride-In-Sight account. A report about an offer adds the details the app assessed: the provider and service type, fare, distance, duration, stars, the verdict and its reason, the settings it was judged against, and when (to the minute). It never includes the pickup or drop-off, addresses, postcodes, the passenger's name or the text read from the offer. All of this is linked to your account.
• Screenshots are masked on your phone first. Before anything is sent, the app automatically covers names, phone numbers, house numbers and full postcodes (for a UK postcode such as "E1 6AN", the "6AN" part). It leaves visible what we need to look into the problem: the fare and other offer figures, times, distances and ratings, and area-level places such as the postcode district, town, station, airport, landmark or a street name without its number. The automatic masking is an aid, not a guarantee: it does not reliably cover email addresses, notifications or offer layouts it does not know. You then check the masked picture, can cover anything else personal by hand, and confirm you have checked it; the app's own covers cannot be removed. If automatic masking is not available for a picture, the app tells you, and you cover details by hand before you confirm. Only that masked copy is sent; the original is never uploaded. The picture is saved again as a JPEG, which removes hidden details such as its location.
• Other people's details: only send what you are allowed to share. If a screenshot still shows someone else's details, we use it only to look into the problem and delete it on the schedule below.
• How many you can send: up to 5 an hour and 20 a day, of which up to 10 a day may include a picture.
• What we use it for: only to investigate the problem, fix it and improve how Ride-In-Sight works with driver and delivery apps. We do not publish it or use it for marketing or advertising, and sending it earns no points or rewards.
• Who can see it: only the Ride-In-Sight team reviewing these reports. Screenshots are stored privately with our database provider, Supabase, in the UK (section 15); they are never public, they are opened only through a link that expires after 5 minutes, and each opening is recorded.
• How long we keep it: a screenshot is deleted 90 days after we close the report, and never kept longer than 180 days. A screenshot that never joins a report is deleted after 24 hours. The report itself (what you wrote and any offer details) is kept for up to 12 months after you send it, then deleted.
• Deleting it: you can delete a report in the app, or ask us by email at support@rideinsight.app. What you wrote and the offer details are removed straight away, and the screenshot is deleted by our next hourly deletion run. An empty record, with nothing you wrote or sent, is kept for up to 24 hours so that deleting a report does not reset the daily limit. If you close your account, your reports are deleted with it and their screenshots within about a day.

Ride-In-Sight Pro is bought in the apps through the App Store or Google Play. Apple or Google takes the payment; we never receive your card details. We receive a record of the purchase (the product, price, currency and country, the transaction or order reference and the subscription period) so we can give you access, and we keep it as a financial record (section 16).

We do not currently sell subscriptions on our website.

Closing your account does not cancel a subscription. Cancel it in the App Store or Google Play.

Our website uses only cookies and browser storage it needs to work:

• sign-in cookies, which keep you signed in for your session;
• referral_code and referral_origin, which remember the referral link you followed for 30 days so the member who referred you is credited;
• browser storage for your sign-up progress, referral and display preferences, and for your sign-in if you sign in on our account deletion page.
• browser session storage noting how your visit began (the campaign tags in the link you followed, the name of the website that sent you, and the first page you opened). It is deleted when you close the tab.

How you found us. If you register, we save that note with your account: the campaign tags, the sending website's name (not the full address), the first page, and the country and type of device (phone, tablet or computer) your request came from. We use it only to see which of our posts and links bring people to Ride-In-Sight. We do not save your IP address or browser details with it, and it is separate from referral credit. It is deleted with your account.

We do not use advertising or analytics cookies. Our website host keeps short-lived server logs of requests; logs of sign-up requests can include the contact details you entered.

We do not sell your personal data or share it for advertising. These providers process it on our behalf, under contracts that limit them to our instructions and require them to protect it:

Apple and Google receive data as independent organisations under their own privacy policies when you use their services through Ride-In-Sight: App Store and Google Play purchases; Apple's push notification service for Apple Wallet card updates; and Google Wallet, if you add a card to it.

We may also disclose data where the law requires it, or to protect our members or the service.

How we protect it. Data sent between the apps, our website and our servers is encrypted in transit. Access to our database is limited to the people and systems that need it, and the identifiers we keep for your phones are one-way codes.

Transfers outside the UK. Germany and Finland (OpenCage) are covered by UK adequacy regulations. For providers in the USA we rely on the UK Extension to the EU-US Data Privacy Framework where the provider is certified (Vercel, Postmark, Resend and Google), and otherwise on the UK Addendum to the EU Standard Contractual Clauses in the provider's data processing terms (Supabase, and the others as a fallback). You can ask us for a copy.

• Your account, offer records, registered phones and settings: while you have an account.
• After you close your account: you have 30 days to change your mind. After 30 days, your account and profile are permanently deleted. Some records are kept for set periods, as our Privacy Policy explains: sign-in security records, which include your email address, payment records linked to your former account ID, and copies in backups and email logs for a short time. The deletion is done by an automatic job that runs once a day, so it happens on the first run after the 30 days end. Referral, points and activity records are kept so other members' rewards still add up. They are pseudonymised, not anonymous: your name and contact details are deleted, but the records keep the referral code used, who referred whom and, in some records, your former account ID.
• Payment and other financial records: 6 years, as HMRC requires. They stay linked to your former account ID. Apple and Google keep their own records of store purchases under their own policies.
• Screenshots and files you send us (section 12a): 24 hours if not submitted; 90 days after we review a submitted contribution; within a day of your account being deleted.
• Share & Improve (section 12b): screenshots 90 days after we close the report and never more than 180 days; a screenshot that never joins a report, 24 hours; the report itself, up to 12 months. When you delete a report, its content at once and its screenshot on the next hourly deletion run; within about a day of your account being deleted.
• Fraud and risk records: 24 months after your account is closed.
• Security and audit records: 24 months after the event they record, or 24 months after your account is closed if that is later. Records of sign-ins include your email address, so it stays in them for that time.
• Backups: deleted data can remain in our database backups for about 7 to 8 days.
• Wallet card cancellation: when an erased account had a membership card in Apple Wallet or Google Wallet, we keep only what is needed to cancel that card (the card's identifier and, for Apple Wallet, the phone's Wallet registration) until the cancellation is delivered, and for 7 days at most. It contains no trip or offer data.
• Places stored for Intelligence: kept without any link to you; no fixed period yet.
• Server logs: 7 days; website logs: no more than 30 days; sign-in emails: up to 45 days; map look-ups: OpenCage keeps its request logs for up to 6 months.
• Firebase (Android): crash reports for 90 days; usage reports for up to 14 months.
• On your phone: until you delete it, the limits above remove it, or you uninstall the app.

You can close your account in the app (Settings, then Close your account), on our website after signing in with a code we email you, or by asking us by email. Either way you have 30 days to change your mind by signing in and choosing Restore. After 30 days, your account and profile are permanently deleted. Some records are kept for set periods, as our Privacy Policy explains: sign-in security records, which include your email address, payment records linked to your former account ID, and copies in backups and email logs for a short time. The deletion is done by an automatic job that runs once a day, so it happens on the first run after the 30 days end.

We keep only the records the law or fraud prevention requires. How to ask, what is deleted, what is kept and for how long are set out on Delete your Ride-In-Sight account.

Storing and reading information on your phone. This is a separate legal rule from the bases above. Sign-in and your settings store information on your phone without asking, because this is strictly necessary for the app. Android crash reports store information on your phone only to detect technical faults in the app; we tell you about them here, and you can turn them off in Settings › Privacy & data. Google ML Kit, which reads offers on Android, stores an identifier for this installation and empty diagnostic records on your phone only if you allow automatic offer reading; Ride-In-Sight never sends them. Usage reports and offer screenshots are stored only if you turn them on.

We do not make decisions about you based solely on automated processing that have legal or similarly significant effects.

You can stop the app reading your screen (turn offer checks off, stop screen capture or the screen broadcast, or switch off the Accessibility service), switch screenshots, Intelligence and Android usage reports and crash reports on or off in Settings › Privacy & data, and stop the app using your location in your phone's settings.

Under UK data protection law you can ask for a copy of your data, and ask us to correct or delete it, restrict how we use it, or give it to you in a portable format. Where we rely on consent you can withdraw it at any time.

Your right to object. You can object at any time to our use of your data based on legitimate interests. For Android crash reports, the quickest way is the Send crash reports switch in Settings › Privacy & data; you can also email us.

To use any of these rights, email support@rideinsight.app. We reply within one month.

Complaints. If you are unhappy with how we have used your data, email us first: we acknowledge complaints within 30 days and tell you the outcome. You can also complain to the Information Commissioner's Office at ico.org.uk or on 0303 123 1113.

Users in the United States. You can ask us for a copy of your data, or ask us to correct or delete it, by emailing support@rideinsight.app. We do not sell your personal data or share it for targeted advertising. Our website and apps do not respond to "Do Not Track" browser signals, because we do not track you across other companies' websites or apps.

Users in Canada. RiS Technologies Ltd is accountable for how Ride-In-Sight handles personal data. Contact us at support@rideinsight.app. Your data is stored in the United Kingdom and processed by the providers in section 15, some in the United States and other countries, where it may be accessed by courts and government bodies under local law. You can ask to see and correct your data. If you are not satisfied with our answer, you can complain to the Office of the Privacy Commissioner of Canada at priv.gc.ca.

Ride-In-Sight is a tool for people who drive or deliver for ride-hail and delivery platforms; using those platforms is subject to their own eligibility rules. Ride-In-Sight is not directed at children. We do not knowingly collect personal data from children under 13 in the United States, or below the age of digital consent where they live (13 in the United Kingdom). If you believe a child has given us data, contact us and we will delete it.

We update this page when what we collect or how we use it changes, and change the date at the top. If a change matters, we tell you in the app or by email before it takes effect.