EVS Customer Portal — Privacy Policy (Mobile App)

Published 15/09/2026

1. Who we are and how to contact us

This app is operated by Electric Vehicle Services L.L.C., a company registered in the Emirate of Dubai, United Arab Emirates, trade licence number 976771, registered office Al Qooz ind 3 - warehouse S01-B, Dubai, United Arab Emirates ("EVS", "we", "us", "our").

We decide what personal data this app collects and why. We are the data controller.

The app is published on the Apple App Store and Google Play by Digital Cubic Smart Solutions L.L.C., trade licence number 1245018, which built the app and runs its servers for us, on our instructions. It is our service provider and it does not decide how your data is used. Where a store listing names it as the seller, the service described in this policy is EVS's. Section 7 sets out what it can reach.

Support, for any question about the app: hussein.eldomor@evsuae.com
Phone: 800 3877
Privacy and data requests — asking about your data, correcting it, obtaining a copy, erasing it, deleting your account if you cannot sign in, or complaining: hussein.eldomor@evsuae.com

We aim to respond within one week.

2. What this policy covers

This policy covers the EVS Customer Portal mobile app for iOS and Android, and the EVS servers the app talks to. The mobile app is the only customer-facing surface of this service.

It does not cover:

The EVS website at evsuae.com, which publishes its own separate privacy policy. That policy covers the website; this one covers the app.
The records EVS creates about you and your vehicle in the workshop itself, outside this app. This policy describes what the app sends to EVS's workshop management system and what it takes back — see sections 7, 9 and 12 — but the workshop's own record of the work it does for you is wider than the app.
Other companies' services that we send data to. Section 7 names them.

3. Summary

You sign in with your UAE mobile number and a code sent by SMS. There is no password.
We collect your name, your mobile number, an optional email address, your vehicles, photographs of your vehicle registration card, your bookings, your messages with our staff, your feedback survey answers, and technical records about your sign-in sessions and your device.
EVS staff read the messages you send and the notes you write on a booking. They are part of the service record, not a private channel.
We share data with our SMS provider, our email provider, our push-notification provider, our cloud host, Microsoft's document-reading service, and EVS's own workshop management system (Odoo). Your vehicle record and copies of your registration card photographs are placed into that workshop system.
We do not run any analytics, advertising or crash-reporting software in the app. We do not track you across other apps or websites. We do not collect your location.
Most of your data is kept until you delete your account, and some of it is kept after that — including the vehicle record and the registration card copies inside EVS's workshop system. Section 9 and section 12 explain exactly what.

4. Where your data comes from

From you. What you type or upload in the app: your name, your mobile number, an optional email, your vehicles, photographs of your vehicle registration card, booking notes, messages and files, and survey answers.

From your device. Technical data described in section 5.9, created automatically when you use the app.

From EVS's own systems. The app shows you records EVS holds about you in its workshop management system, and copies of those records are stored on our servers so the app can display them. These include your contact record, your repair orders (including the description and the advisor's name), your vehicles held by EVS, workshop calendar entries, your advisor's messages, and records of orders and invoices where these exist. This release of the app does not display invoice or order records, but they may still be held.

Signing up does not join your account to an EVS customer record that already existed. When you register, a new customer record is created for you in EVS's workshop management system, marked as created from the app. What EVS records about you after that — a repair order, or a vehicle staff enter against that new record — is copied back into the app, so records you did not enter yourself can appear in the app.

A record for your mobile number may nonetheless already exist on our servers, created by an earlier version of our systems from EVS's workshop data. Registering with that number re-uses the record for the number alone: its link to EVS's existing customer record is removed, the email address on it is cleared, and any vehicles that came from EVS's records on it stop being shown. If you register through Sign Up, the name and email address you type replace what was there. The one remaining route by which an account can be joined to an EVS customer record that already existed is a manual review by staff — see section 5.1.

5. What we collect, and why

5.1 Account and identity

Data	How we get it	Why we use it
Full name (required)	You enter it at sign-up; you can change it later	To identify you to workshop staff on bookings, repair orders and messages; it is written to your contact record in EVS's workshop system and appears in the title of the workshop calendar entry for each booking
UAE mobile number (required)	You enter it at sign-up	This is your account identity. It is how you sign in, how we send your one-time code, and how EVS staff and the workshop system recognise you
Email address (optional)	You enter it at sign-up or later	A second way to contact you and to send you service emails. If you change it, we send a confirmation link to the new address and only apply the change when you click it
Language preference (English or Arabic)	You choose it in the app	To show the app, and to send notifications, in your language
One-time sign-in codes	Generated by us and sent to you by SMS	To confirm you control the mobile number. We store only an irreversible hash of the code, never the code itself
Account status and workshop-system link	Created by us	To connect your app account to its own customer record in EVS's workshop system. A new account is given a new record there, marked as created from the app; it is not joined to a customer record EVS already held. Where staff reviewed an uncertain match between an app account and an existing EVS record before that process was withdrawn, that review is kept as a separate record — see section 12. No new reviews of this kind are created. A review raised before the withdrawal can still be resolved by staff, and approving one joins that account to the EVS record named in it
Your acceptance of the EVS warranty terms	Recorded when you tick the box at sign-up	To evidence that you agreed to the warranty terms, and to which edition of them. The record holds the document, its version, the language you read it in, and the date and time — not a copy of the text and nothing else about you

5.2 Vehicles

Data	How we get it	Why we use it
Vehicle make, model, year, colour, licence plate, emirate, VIN (chassis number), registration expiry date	You enter or confirm them; or they come from EVS's workshop system	To identify the vehicle for bookings, repairs, service history and warranty
Name of the registered owner shown on the registration card	Read from the photograph of your registration card. There is no field in the app for typing it in, so a scan is the only way it reaches us	To record who the vehicle is registered to. This may be someone other than you — for example a company car or a family member's vehicle
Vehicles EVS holds for you	From EVS's workshop system	So you can see the vehicles EVS has recorded for you, and their history, without re-entering them. These records are managed by EVS and cannot be edited or removed in the app

5.3 Registration card ("Mulkiya") photographs

When you add a vehicle, you can photograph the front and back of its registration card instead of typing the details.

Data	How we get it	Why we use it
Photographs of the front and back of your vehicle registration card	You take them with the camera or choose them from your photo library	To read the vehicle's details automatically, and to give the workshop a copy of the registration document for your service record
The details read from the card: registered owner's name, plate number, chassis number (VIN), make and model, year, colour, expiry date, emirate	Read automatically from the photograph	To fill in the vehicle form so you do not have to type them

You are never required to scan the card. You can always type your vehicle details in by hand.

What happens to the photograph. The photograph is converted to a standard JPEG on our server and stored in private cloud storage. It is not published and no public link to it is ever created. It is then sent to Microsoft Azure AI Document Intelligence, a Microsoft service, which reads the text on it and returns the fields listed above.

A copy goes to the workshop. When you first book an appointment for that vehicle, a vehicle record is created for it in EVS's workshop management system and copies of both photographs are attached to that record, so workshop staff can see the registration document. Two things follow from this that you should know:

Those copies are not removed when you delete your account. See section 12.
If you later retake or correct a card photograph, the copy already in the workshop system is not replaced. The workshop can therefore hold an earlier version of the image.

If a vehicle with the same chassis number already exists in EVS's workshop system under a different customer, no new record is created for you and no photograph is copied there.

If a scan does not work. If we cannot read the card and you abandon the process, or if you retake the photograph, the earlier image has already been stored. It stays in our storage until you delete your account — see section 9. Deleting the vehicle itself removes only the images attached to that vehicle's record — an image from a scan you abandoned or retook is not attached to any vehicle, so it is removed only when you delete your account.

5.4 Bookings

Data	How we get it	Why we use it
The service centre, service type, date and time slot, and the vehicle	You choose them in the app	To reserve the appointment and tell the workshop what is arriving and when
Booking notes — free text, up to 500 characters	You type them	So you can tell the service advisor what you want done. These notes are copied into the workshop calendar entry and are read by EVS staff. Please do not put anything in them you would not want workshop staff to see
Cancellation time and reason	You provide the reason if you choose to; the time is recorded automatically	To manage the appointment and free the slot

5.5 Repairs, service history and warranty

Data	How we get it	Why we use it
Repair orders: reference, status, dates, the assigned advisor's name, the job description	From EVS's workshop system	To show you the progress of work on your vehicle
Warranty booklet records, completed service milestones, odometer readings, and staff notes on those milestones	Recorded by EVS staff against your vehicle	To show you your warranty status and service milestones

Internal staff notes attached to repair orders are stored on our servers but are not shown in the app.

5.6 Messages with your service advisor

The app lets you message the advisor handling an open repair order. There is no way to message other customers, and no way to start a conversation unless EVS has opened a repair order for you.

Data	How we get it	Why we use it
Message text, up to 2,000 characters	You type it	So you and your advisor can discuss the repair
Your name as it was when you sent the message	Copied automatically onto each message	So staff know who is writing
One file per message: images, PDF or Word documents, up to 10 MB	You choose it	So you can send photographs of a fault, or documents
The original file name of anything you attach	Taken from the file	To display it to you and to staff

Messages are not private between you and the app. EVS staff read them, and they appear live on an internal staff console. When you send a message, we send an email alert to your advisor. That alert says only that there is a new message on your repair — it does not contain your message text.

5.7 Notifications

Data	How we get it	Why we use it
Push notification token for your device	Created by Google's push service when you allow notifications	To deliver notifications to the right device
Your device's operating system name and version (for example "ios Version 17.5 (Build 21F79)")	Sent by the app with the token	To deliver notifications correctly and diagnose delivery problems
A record of every notification we send you, including its title and text	Created by us when we send it	To power the notification list inside the app, to avoid sending you the same thing twice, and to investigate delivery failures
Whether push notifications are switched on	Your choice in the app	To decide whether to send them

Notification titles and texts contain real details about your service — for example the service centre name, your appointment date and time, your repair reference and its current stage. These pass through Google's push service, and on iPhone through Apple's push service, and can be displayed on your lock screen.

5.8 Feedback survey

After a repair, we may ask you to rate the service.

Data	How we get it	Why we use it
Your score out of 10, an experience rating, a service factor, and a free-text comment of up to 500 characters	You provide them if you choose to	To measure service quality by branch and advisor and to follow up with unhappy customers
How many times we prompted you and how many times you dismissed the survey	Recorded automatically	To stop asking after three dismissals

The survey is not anonymous. It is stored against your account and your repair. If you give a low score, we email the branch manager an alert containing your score, your advisor's name and your comment, word for word.

5.9 Device, session and technical data

Data	How we get it	Why we use it
Sign-in session records: an irreversible hash of your sign-in token, an irreversible hash of a device value, whether biometric unlock is enabled, and when the session was created, last used and expires	Created when you sign in	To keep you signed in, to end sessions safely, and to make sure biometric unlock only works on the device where you set it up
A device value the app itself creates	The app generates 32 random bytes the first time you use it and keeps them in your device's secure storage	To tell your installation apart from any other, so a biometric unlock cannot be replayed from a different device. This is not a hardware identifier, a serial number, or an advertising identifier. Our servers store only an irreversible hash of it
Your IP address	Read from your connection when you enter a sign-in code	Only to limit how many times a code can be guessed from one network. It is held briefly in a short-lived cache and is not saved to your account record
Records in our diagnostic logs	Created automatically as our servers run, and when something fails	To investigate faults and delivery problems. Some of these records contain your mobile number or your email address. They are held separately from your account record and are not shown to you in the app

Face ID and Touch ID. If you turn on biometric unlock, the check is done by your phone's operating system. The app receives only a yes-or-no answer. No fingerprint, face data or any other biometric information ever reaches the app or our servers, and we store nothing about it except a single yes/no flag on your session.

Data stored on your phone. The app keeps your sign-in tokens and settings in the platform's secure storage (the iOS Keychain, or Android encrypted preferences). It also keeps a short-lived local copy of recently viewed account data — your profile, your vehicles, your dashboard and your repairs — so it can show them when you are offline. That copy is not encrypted by the app beyond the protection your phone's operating system gives to app files, it is discarded after 24 hours, and it is deleted when you sign out. Files you open from a message are saved to the app's temporary storage and are not automatically cleared.

5.10 What we do not collect

Your location. The app never asks for location permission and never collects it. The maps on the service-centre screen show the fixed positions of our branches, not yours.
Analytics or tracking. The app contains no analytics software, no advertising software, and no crash-reporting software. We do not track you across other companies' apps or websites, and the app never shows the "Ask App Not to Track" prompt because it has nothing to ask about.
Payment or card details, rewards and referrals. This release of the app does not take payments and does not show rewards, loyalty points or referrals. No card details are collected anywhere in the app.
Contacts, microphone or calendar. The app never requests access to any of these.

6. Device permissions

The app asks for four operating-system permissions, and no others. Each is asked for at the moment you first use the feature it belongs to, except the notification permission, which is asked for when you sign in.

Permission	What it is used for
Camera	To photograph your vehicle registration card when adding a vehicle. This is the only thing the app uses the camera for
Photo library	To choose a photo or document to attach to a message with your advisor, or to choose a photo of your registration card
Face ID / Touch ID	To unlock the app without re-entering an SMS code
Notifications	To send you booking, repair and message alerts. You are asked the first time you sign in, because push notifications are switched on by default inside the app — your phone's prompt is the only thing standing between the default and a notification being sent

You can refuse any of them, and change your mind later in your phone's settings. Refusing photo access means you cannot attach files to messages, and refusing camera or photo access means you type your vehicle details by hand. Refusing biometrics means you sign in with an SMS code. Refusing notifications means we cannot send push notifications to that device; your notifications still appear in the notification list inside the app.

7. Who we share your data with

We do not sell your data and we do not share it for advertising.

We share it with the service providers listed below, and with EVS's own workshop management system.

Who	What they receive	Why
EVS workshop management system (Odoo), hosted on Amazon Web Services in Bahrain	A contact record holding your name, email, mobile number and a note that it was created from the app; a calendar entry for every booking, containing your name in its title, your vehicle's plate and chassis number, your booking notes and the service centre name; a vehicle record holding your car's make, model, year, colour, licence plate, emirate and chassis number; and copies of your registration card photographs, attached to that vehicle record	This is EVS's operational system of record. Workshop staff work from it. A booking cannot be made without it
Amazon Web Services, Bahrain region	The hosting infrastructure for the workshop system above, and therefore everything held in it	Hosting of EVS's workshop management system
e& / Etisalat (United Arab Emirates)	Your mobile number and the text of the SMS containing your one-time code	To deliver your sign-in code
Microsoft Azure Communication Services	The recipient address, subject and body of each email we send	To deliver service emails and internal alerts about low survey scores
Twilio SendGrid	The recipient address, subject and body of the emails it delivers	A second email path exists in the system alongside Azure Communication Services. It delivers the confirmation link sent when you change your email address, and sign-in links for EVS staff. Whether it is live depends on whether a SendGrid key is set in the production configuration, which we cannot read from here
Google (Firebase Cloud Messaging)	Your device's push token and the full title and text of each notification, plus a link identifying the repair, appointment or conversation it refers to	To deliver push notifications to your device. Google's push software also creates and sends Google its own identifier for your app installation
Apple (Apple Push Notification service) — iPhone and iPad only	The notification title and text	Apple carries every push notification delivered to an iPhone or iPad
Microsoft (Azure), UAE North	Everything we store: our servers, database, cache, file storage and diagnostic logs run on Microsoft Azure. The diagnostic logs are the records described in section 5.9, some of which contain your mobile number or your email address	Hosting, and diagnosing faults
Microsoft (Azure AI Document Intelligence)	A copy of your registration card photograph	To read the text on the card automatically
Digital Cubic Smart Solutions L.L.C. — the company that built the app and publishes it on the App Store and Google Play	Its staff hold administrative access to the Microsoft Azure infrastructure, to the release pipeline and to the production database and file storage, so in practice they can reach everything described in this policy. Support and privacy email sent to the address in section 1 is received by them	Building, publishing, hosting, administering and supporting the app on our instructions
Google (Google Fonts)	Your device's IP address and standard connection information	The app downloads its display font from Google's font service when it starts. This happens as the app opens, before you sign in or agree to anything. No account data is sent
CARTO	Your device's IP address, and the map coordinates of the EVS branch being displayed — not your location	To draw the small map images on the service centre screen, after you have signed in

Equal protection. We require every provider named above to protect your data to a standard at least equal to the one described in this policy, to handle it only on our instructions and only in order to provide the service they provide to us, and not to use it for their own purposes. The same requirement applies to Digital Cubic Smart Solutions L.L.C., which administers our systems on our behalf. We do not permit any of them to sell your data or to use it for advertising.

We may also disclose data where we are required to by law, or to establish or defend legal claims.

8. Where your data is processed and stored

Our servers, database and file storage run on Microsoft Azure in the UAE North region.

Our diagnostic logs, including the records described in section 5.9 that contain your mobile number or email address, are held in Microsoft Azure's monitoring service in the UAE North region.

Section 7 names every provider we send data to. This is where each of them processes it:

e& / Etisalat processes your mobile number in the United Arab Emirates.
Microsoft Azure Communication Services processes email content in the United Arab Emirates. The service is configured to keep email data in the UAE.
Twilio SendGrid, where it is in use, processes email content in the United States.
Google and Apple process push notification content on their own global infrastructure. We cannot choose where.
Microsoft Azure AI Document Intelligence processes your registration card photograph in the UAE North region.
EVS's workshop management system is hosted on Amazon Web Services in Bahrain, so your contact record, your booking calendar entries, your vehicle record and the copies of your registration card photographs are held there.

So three of these providers process data outside the UAE: SendGrid in the United States, Apple and Google wherever their networks take a notification, and EVS's workshop management system in Bahrain.

On what basis these transfers are made.

Where your data leaves the UAE, we make the transfer on one of two grounds, and usually on both.

Because the transfer is necessary to do the thing you asked us to do. A booking cannot be made unless it is written into EVS's workshop system, and a push notification cannot reach your phone unless Apple or Google carries it. Those transfers are necessary to provide you with the service you signed up for and to keep EVS's record of the work done on your vehicle.
Because we have put the recipient under obligations that travel with the data. As section 7 says, we require every provider we name to protect your data to a standard at least equal to the one described in this policy, to handle it only on our instructions and only in order to provide the service they provide to us, not to use it for their own purposes, not to sell it, and not to use it for advertising. Those obligations apply wherever the provider does the processing.

Three further points, so that nothing here misleads you:

We do not rely on your consent for these transfers. You are not asked to agree to them separately, and refusing would not change how the service works. The one real control you have is over push notifications: if you refuse or withdraw the notification permission on your phone, we stop sending notification content to Apple or Google for that device. It does not stop everything — as section 7 explains, Google's push software still creates and sends Google its own identifier for your app installation, and the app fetches its display font from Google as it opens. Neither of those is something we can switch off for you.
We cannot choose where Apple or Google handles a push notification. They run global infrastructure and we have no say in which country a notification passes through. If that matters to you, turn push notifications off — sections 6 and 11 explain how — and read your notifications in the app instead.
The choice of UAE law and Dubai courts in our Terms of Service is an agreement between you and us about disputes. It is not the basis for any of these transfers, and it does not mean your data stays in the UAE. Sending data abroad and agreeing which law governs a dispute are two different things, and we do not want the one to be read as the other.

Wherever your data is processed, this policy keeps applying to it, and so do the rights in section 11. If you want to know more about the arrangements behind a particular transfer, ask us at hussein.eldomor@evsuae.com.

9. How long we keep your data

We keep your data for as long as we need it for the purposes described in this policy. We do not delete it on a fixed schedule.

While your account is open, we keep the records described in section 5 so the app can show you your vehicles, your bookings, the progress of work on your car, your messages and your service history.

When you delete your account, we close it permanently and remove the details that identify you from your account record: your name is replaced with an internal reference code, and your email address and phone number are removed. We also delete your sign-in sessions on every device, your push notification registrations, any sign-in code still outstanding, and the registration card photographs held in our own storage. Section 12 sets this out in full.

Some records are kept after your account is closed. They are:

your bookings and service history — the appointments you made, when, at which service centre, and the notes you wrote on them;
your vehicle records — make, model, year, colour, plate, emirate and chassis number — because service history follows the vehicle rather than the app account;
your warranty records and completed service milestones, including odometer readings, for the same reason;
the workshop's records — your contact record and your vehicle's record in EVS's workshop management system, and the copies of your registration card photographs attached to that vehicle record — because that system is EVS's own record of the work it did for you;
your messages with EVS staff, the files you attached to them, and your name as it appeared on them, as part of that record;
your notification history and your feedback survey answers;
backups, until each backup copy ages out and can no longer be restored;
diagnostic logs, some of which contain your mobile number or your email address, so we can investigate faults and misuse.

We keep these for as long as they are needed for the purposes described above — the service history of your vehicle, your warranty, the workshop's record of the work it did for you, and the technical operation and security of the service. They are not anonymous: your vehicle's chassis number and plate, and your name inside old messages, still identify you.

You can ask us to remove more than the Delete Account button removes, including the copies held in EVS's workshop management system. Email hussein.eldomor@evsuae.com and we will deal with it as an individual request. We will ask you to verify your identity using your UAE national ID (Emirates ID) before we act on the request, and we aim to respond within one week.

How to ask us to delete your account. Open the app, go to More, and tap Delete Account. If you cannot sign in, email hussein.eldomor@evsuae.com or call 800 3877 and we will do it for you. Section 12 explains exactly what deletion removes and what it leaves behind.

Records the system removes on its own

A few technical records are removed automatically, without anyone asking:

Data	How long
One-time sign-in codes	Stored only as an irreversible hash and valid for 10 minutes. The record of the request, which contains your mobile number, is deleted within about 24 hours
Sign-in session records	A session lasts 30 days from your last use of it. The record is deleted 90 days after it expires — about 120 days at most
Integration logs (records of syncing with EVS's workshop system)	90 days. This clean-up only runs while the workshop-system integration is switched on
Background job records held in our cache	Our default is to remove a job record about 24 hours after it succeeds and about 7 days after it fails. Some job types are instead capped by number rather than by age, so a small number of recent records can be held for longer

10. Security

We protect your data with the following measures. We have deliberately limited this list to what we can actually demonstrate.

Sign-in codes. Generated using a cryptographically secure random source, stored only as an irreversible hash, valid for 10 minutes, usable once, and rate-limited so a code cannot be guessed by repeated attempts.
Session tokens. Your app is issued a short-lived access token valid for 15 minutes. Your longer-lived sign-in token is never stored by us — only an irreversible hash of it — and it is replaced every time it is used. You are signed out automatically after 30 days without using the app.
Transport. All communication between the app and our servers uses HTTPS. Release builds of the app refuse to run against a non-HTTPS address.
On your device. Sign-in tokens and settings are held in the platform's secure storage — the iOS Keychain or Android encrypted preferences. On Android, the app is excluded from device backups.
Biometrics. The biometric check runs on your phone. We never receive biometric data. A biometric unlock only works on the device where you enabled it.
Stored files. Registration card photographs are stored privately, under a path tied to your customer account, and no public or shareable link to them is ever created. Message attachments are only released after we check that the conversation belongs to you. Files you attach to a message are checked so that a file cannot pretend to be a different type from its real contents. Photographs you upload are accepted only in standard image formats and are converted to a standard JPEG on our server.
Rate limits and input checks. Sensitive endpoints are rate-limited to reduce abuse, and all incoming data is validated and unexpected fields rejected. Registration card scanning is limited to 10 scans a minute and 50 a day for each account.
Access control. Every request that returns personal data requires a valid, unexpired, non-cancelled session, and is scoped to the account that session belongs to.

We cannot guarantee the security of data transmitted over the internet, and no system is completely secure.

11. Your rights and how to use them

What you can do yourself, in the app

Right	How
Correct your name, email address or language	More → Edit Profile, and the language switch under Preferences
Confirm a new email address	We email you a confirmation link; the change only takes effect when you click it
Turn push notifications off	More → Preferences → Push Notifications. Push notifications are on by default. This switch applies only to the device you are using — turning it off on one phone does not turn it off on another
Withdraw camera, photo, Face ID or notification permission	In your phone's own settings
Delete your account	More → Delete Account. See section 12

Two limitations you should know about.

Changing the phone number shown in your profile updates the number we use to contact you. It does not change the number you sign in with. If you change your mobile number, contact us so we can update your sign-in identity.
If you did not give us an email address when you signed up, the Edit Profile screen currently requires you to enter one before it will save any change, including a change to your name. If this affects you, contact us and we will make the correction for you.

What you have to ask us for

There is no download or export button in the app. To ask for any of the following, email hussein.eldomor@evsuae.com from your registered email address, or call 800 3877 from your registered mobile number:

Right	What we do
A copy of your data	We assemble it and send it to you. Because there is no self-service export, this is handled by a person
Correction of anything you cannot edit yourself — including vehicle records created by EVS, repair records and warranty records	We correct it in our systems
Deletion beyond what the in-app Delete Account button does — including the copies held in EVS's workshop management system	See section 12 for what the button does and does not do, and what we can do on request
Objection or restriction	We consider the request and tell you the outcome

Verifying who you are, and how long we take. Before we act on any of these requests we will ask you to verify your identity using your UAE national ID (Emirates ID). We aim to respond within one week.

Turning off emails. There is currently no in-app switch to stop service emails. If you do not want them, contact us and we will remove or change your email address on your account.

Withdrawing your agreement. Apart from the controls listed above — your phone's permissions, the push notification switch, and deleting your account — the app gives you no way to withdraw your agreement to the processing described in this policy. If you want to withdraw it, contact us at hussein.eldomor@evsuae.com and we will tell you what we can and cannot stop.

12. Deleting your account

You can delete your account at any time: open the app, go to More, and tap Delete Account at the bottom of the screen.

A full explanation is on our account deletion page at https://evslegal.z1.web.core.windows.net/delete-account, which you can read without installing the app.

We want to be accurate about what deletion does. It closes your account permanently and removes the details that identify you from your account record. It does not erase every record connected to you.

Deleted immediately	Kept
All your sign-in sessions, on every device	Your account record itself, with your name replaced by an internal reference code and your email and phone number removed
Your push notification registrations, so notifications stop	Your vehicle records, including make, model, plate number, chassis number (VIN), emirate and registration expiry date
Any sign-in codes still outstanding	Your bookings, including the notes you wrote on them. Future appointments are cancelled
The registration card photographs we hold, and the owner name read from them	Your messages, the files you attached to them, and your name as it appeared on those messages at the time you sent them
The data cached on your phone by the app	Your notification history, including the title and text of each notification
Your email address and phone number are removed from your account record, and your name there is replaced with an internal reference code	Your survey scores and comments
	Your warranty and service milestone records
	Any match review record about you: where staff reviewed an uncertain match between your app account and an existing EVS customer record, the review is kept separately from your account record, including the confidence score and any note staff wrote. The match details on your own account record are removed. No new reviews of this kind are created — see section 5.1
	Your contact record in EVS's workshop management system, holding your name, email and mobile number
	The vehicle record held for your car in EVS's workshop management system, holding its make, model, year, colour, licence plate, emirate and chassis number. Deleting your app account does not delete or change it
	The copies of your registration card photographs attached to that vehicle record in EVS's workshop management system. Nothing in the app or on our servers removes them
	Copies of EVS workshop records about you held on our servers
	Records in our diagnostic logs that contain your mobile number or email address
	Any payment, loyalty-points or referral records our servers hold for you, none of which this release of the app creates or displays
	Point-in-time backups, until each backup copy ages out and can no longer be restored
	The record of your acceptance of the EVS warranty terms: the document, its version, the language and the date

A few further points, so there is no misunderstanding:

The records we keep are not anonymous. Your vehicle's chassis number and plate number, and your name inside old messages, still identify you. We keep them because they form the service history of the vehicle and the workshop's record of the work done.
Your registration card is not fully removed by deleting your account. The app deletes the copies it holds. The copies attached to your vehicle in EVS's workshop management system remain, and there is no automatic route that removes them. To have those removed, ask us — see the last point below.
You can sign up again with the same mobile number. You will get a completely new account with no bookings, vehicles, messages or history from before.
Deletion is not instantaneous in every case. If part of the clean-up fails — for example if our file storage is briefly unavailable — the account is still closed, and the remaining items are removed manually afterwards.
To have more removed than the button removes, including the copies in EVS's workshop management system, contact us at hussein.eldomor@evsuae.com and we will deal with it as an individual request.
Your phone keeps two settings and one random app-generated value after deletion. Uninstalling the app removes them.

13. Children

This app is not intended for children. You must be at least 18 years old to create an account.

We do not knowingly collect data from anyone under that age, and the app does not verify age. If you believe a child has created an account, contact us at hussein.eldomor@evsuae.com and we will close it and delete the data as described in section 12.

14. Changes to this policy

We may update this policy. The date at the top always shows when it last changed.

The current version is always available at https://evslegal.z1.web.core.windows.net/privacy-policy, from the app's welcome screen, and from More → Legal & Privacy inside the app.

How we tell you about changes, and when a change takes effect.

Please read this part carefully, because it describes a limit in the app rather than a promise.

The app does not tell you when this policy changes. There is no in-app notice, no alert and no step that asks you to agree again, and you are not shown this policy again when you sign in. The published page is the only place a change appears. Please look at it from time to time.

A change takes effect on the day it is published. The date at the top of the page is the day this policy last changed.

For a significant change we do more. If we change this policy in a way that significantly reduces the protection given to your data, significantly widens how we use it, or adds a new recipient of it, then:

we will publish the new version at least 30 days before it takes effect, and the page will say the date it takes effect; and
where we hold an email address for you, we will email you before that date. We do not hold an email address for every customer — it is optional, and most of our customers have given us a mobile number only — so an email will not reach everyone. That is why the published page, and not an alert, is the place to look.

If you want to know what changed, email hussein.eldomor@evsuae.com and we will tell you what is different from the previous version and when it changed. We aim to respond within one week.

Your agreement is not what makes this policy apply. We do not treat your continued use of the app as consent to the handling described here, and we do not keep a record of you accepting this policy. We do keep a record of you accepting the EVS warranty terms, which you are asked to agree to when you create your account — that is a separate document about your vehicle's warranty, and section 5.1 sets out exactly what that record holds. If you do not want us to handle your data in the way a new version describes, what you can do is set out in section 11 — contact us, or delete your account.