Last updated: 17 August 2026
ARIVD respects your privacy and aims to be clear about what information is collected, why it is needed and when it may be shared.
This Privacy Policy applies to:
ARIVD is designed around an important distinction: using information inside the app to support a journey is not the same as continuously sharing your location with other people.
During a normal journey, your trusted contacts do not need to follow you on a live map. Location is shared with trusted contacts when ARIVD’s safety process is triggered or when you deliberately choose to share your location.
ARIVD is operated by:
MATTHEW ADRIAN NESBITT
United Kingdom.
For data-protection enquiries, contact:
privacy@arivd.app
For general support:
For the purposes of UK data-protection law, MATTHEW ADRIAN NESBITT is the controller of personal information processed through ARIVD.
The ICO requires a privacy notice to identify the controller and provide suitable contact details.
The information ARIVD processes depends on which parts of the website or app you use.
If you join the ARIVD Early Access list, we collect:
We use this information to manage the Early Access list and send ARIVD launch, beta and related product updates that you have requested.
When you create or use an ARIVD account, information may include:
We use this information to provide and operate your ARIVD account.
ARIVD allows users to select trusted contacts.
Information relating to a trusted contact may include:
If you add another person as a trusted contact, you should only provide information you are entitled to provide and should make them aware that you have selected them as an ARIVD contact.
When you use ARIVD for a journey, we may process information including:
This information is used to provide the journey-monitoring and alert features you have requested.
Location is an important part of ARIVD, but ARIVD is not designed around continuously giving your contacts a live view of every normal journey.
Depending on the journey mode and features being used, ARIVD may access or process location information from your device during an active journey.
This can include GPS or other device-derived location information.
Location information is personal information when it can be linked to an identifiable individual. The ICO specifically recognises geolocation data from devices, including GPS information, as personal information.
ARIVD may use movement or location information internally to support features such as journey monitoring and vehicle/travel-mode checks.
Your trusted contacts do not need to receive a continuously updated live map of your journey.
If:
ARIVD may begin sharing your current location with the trusted contacts selected for that journey.
Location may continue to update while the emergency alert remains active.
You can also choose to use SHARE LOCATION.
When you do so, ARIVD shares your location with the trusted contacts selected for that journey without waiting for the timer or another safety process to trigger.
During supported journeys, ARIVD may use information from your device’s movement or activity sensors to determine whether the device appears to have remained stationary for an unusual period.
If prolonged inactivity is detected, ARIVD may ask:
“Are you OK?”
If you respond, the journey can continue normally.
If you do not respond, ARIVD may escalate the journey, alert your selected trusted contacts and share your location.
ARIVD is detecting behaviour of the device. It does not independently know whether you have physically stopped, whether you are injured or whether you are in danger.
Movement information is used to provide this functionality and is not intended to create a general record of your physical activity.
When a trusted contact opens an ARIVD emergency map, the ARIVD app may request access to that contact’s own device location.
This may be used to:
Access to the trusted contact’s device location is subject to the permissions they grant on their device.
When ARIVD enters its emergency process, information relating to the alert may be shared with the trusted contacts selected for the journey.
This may include:
Once emergency location sharing has begun, ARIVD is designed so that the traveller cannot simply end the emergency from their own ARIVD app.
A trusted contact can confirm that the traveller is safe, allowing the alert to be resolved and emergency location sharing to stop.
ARIVD uses automatic rules to operate some safety features.
For example, the app can react automatically when:
These systems decide whether ARIVD’s predefined alert process should begin.
They do not determine that you are actually in danger, diagnose an emergency, assess your health or make decisions on behalf of emergency services.
We may use personal information to:
UK data-protection law requires us to have a lawful basis for processing personal information. The appropriate basis depends on why the information is being used.
We expect to rely principally on the following bases.
Where processing is necessary to provide ARIVD functionality that you have requested, such as:
The ICO confirms that the contractual basis should only be used where the processing is objectively necessary to perform the relevant contract or requested service.
We may rely on our legitimate interests where appropriate for purposes including:
Where we rely on legitimate interests, we consider whether those interests are outweighed by the rights and interests of the individuals concerned.
We may rely on consent where it is legally appropriate, including for Early Access or marketing communications where consent is required.
You may withdraw consent at any time.
Where UK electronic-marketing rules require consent, the ICO advises that consent will generally also be the appropriate UK GDPR basis for the associated personal-data processing.
We may process information where required to comply with legal or regulatory obligations, respond to lawful requests or establish, exercise or defend legal claims.
ARIVD may request device permissions including:
Android permission choices are controlled through your device.
Granting an operating-system permission allows the app to access the relevant device capability. It does not mean that ARIVD will use that information for purposes unrelated to the feature for which it was requested.
Some ARIVD functionality may not work correctly if required permissions are disabled.
ARIVD uses push notifications to provide features including:
To deliver push notifications, ARIVD may process a device notification token or similar technical identifier.
ARIVD currently uses Google’s Firebase services for parts of its backend and notification infrastructure. Google states that, for many Firebase services used by customers under GDPR, Google generally acts as a processor of customer data on the customer’s behalf.
If you enter your email address on arivd.app to join the ARIVD Early Access list, we use it to send information relating to:
You can ask us to stop sending these messages at any time.
We will not sell your email address to advertisers.
We do not sell your personal information.
Information may be shared where necessary with:
When required to provide ARIVD’s journey, notification, location-sharing or safety functionality.
We may use suppliers that help us provide ARIVD, such as:
At present, ARIVD uses services from Google/Firebase, including backend, database, authentication and/or push-notification services depending on the feature being used.
Firebase provides data-processing and security terms covering customer data processed through its services.
The ARIVD website is hosted using Hostinger.
We may disclose information where we are legally required to do so or where disclosure is necessary to establish, exercise or defend legal rights.
Some of the technology providers used by ARIVD are international organisations and may process information outside the United Kingdom.
Where personal information is transferred outside the UK and UK transfer rules apply, we will use an appropriate lawful transfer mechanism.
Depending on the destination and provider, this may include:
The ICO’s current guidance confirms that restricted international transfers require an appropriate transfer mechanism or safeguard where no applicable adequacy arrangement exists.
We do not intend to keep personal information for longer than is reasonably necessary for the purpose for which it was collected.
Before publishing this policy, ARIVD’s actual database deletion rules should be matched to the retention periods stated here.
I recommend using the following as the starting schedule:
Until you:
For as long as your ARIVD account remains active, then for:
up to 30 days after account deletion
except where information must be retained longer for legal, security or dispute purposes.
For as long as it remains associated with an active account or journey, subject to:
[CONFIRM RETENTION/DELETION RULE]
For:
12 months
unless:
For only as long as reasonably necessary to provide and maintain the relevant emergency/alert record, subject to:
[CONFIRM LOCATION RETENTION PERIOD]
For:
90 days unless needed longer to investigate a security or technical incident
Backup copies may remain for a limited additional period before being automatically overwritten.
The ICO requires organisations either to state retention periods or explain the criteria used to determine them.
We take reasonable technical and organisational measures intended to protect personal information from:
ARIVD uses authenticated accounts and cloud-based infrastructure and is designed to restrict access to information according to the functionality being provided.
No internet-connected system can guarantee absolute security.
Depending on the circumstances and the lawful basis being used, UK data-protection law may give you rights including:
These rights are not absolute and which rights apply can depend on the lawful basis and circumstances of the processing.
To exercise a privacy right, contact:
privacy@arivd.app
We may need to verify your identity before fulfilling a request.
A person may appear in ARIVD because an ARIVD user has selected them as a trusted contact.
In that situation, ARIVD may receive information such as the person’s:
We use this information only as reasonably necessary to provide the trusted-contact and safety functionality.
If you believe your information has been added to ARIVD without an appropriate reason, contact us at:
privacy@arivd.app
and we will review the request.
ARIVD may be used by young people aged 13 and over.
ARIVD recognises that children and young people merit particular protection when their personal information is used, especially information relating to their location.
Where a user is under 18, ARIVD aims to apply privacy-protective settings and provide information about location, trusted contacts and data sharing in language appropriate to younger users.
During an active journey, ARIVD may use movement or location information where this is necessary to provide the journey-safety features being used. Trusted contacts do not need to receive continuous live-location information during a normal journey. Location may be shared when ARIVD’s safety process is triggered or when the user deliberately chooses to share their location.
ARIVD does not currently offer accounts to children under 13. If this changes, we will introduce appropriate parental-authorisation and age-assurance measures and update this Privacy Policy before making the service available to younger children.
The ARIVD website may use cookies or similar technologies that are necessary to:
If we introduce non-essential analytics, advertising or other tracking technologies, we will provide appropriate information and, where required, obtain consent before those technologies are used.
UK rules for non-essential cookies and similar technologies can require informed consent; putting cookie information only in a privacy policy is not by itself sufficient where consent is required.
The generic WordPress wording about comments, Gravatar, user logins and publishing cookies has intentionally been removed because it should only appear if those visitor-facing functions are actually used.
ARIVD may provide links to third-party services, such as Google Maps for directions.
Third-party services operate under their own privacy practices and terms.
ARIVD is not responsible for how an independent third-party service processes information after you choose to use that service.
ARIVD may update this Privacy Policy when:
The latest version will be published on arivd.app and the date at the top of this policy will be updated.
Where a change materially affects how we use personal information, we will take appropriate steps to bring the change to users’ attention.
If you have a question about this Privacy Policy, ARIVD or the personal information we hold about you, contact:
[FULL LEGAL NAME OR COMPANY NAME]
Email: [PRIVACY EMAIL ADDRESS]
Support: support@arivd.app
If you have concerns about how ARIVD handles your personal information, please contact us first so that we can try to resolve the issue.
You also have the right to complain to the Information Commissioner’s Office (ICO), the UK’s data-protection regulator.
The ICO’s right-to-be-informed guidance requires people to be told about their right to make a complaint to the supervisory authority.
Privacy Policy
Privacy Policy