Effective date: 31 October 2026

Who we are

Arrivly is provided by CRLT17 Studios, a brand of HORSEXPERIENCES LIMITED, 71–75 Shelton Street, London, WC2H 9JQ, United Kingdom.

For privacy questions, rights requests, or support, email support@horsexperiences.com.

Your local profile and journeys

No account is required.

Your optional display name, destination text and coordinates, initial travel estimate and distance, journey timestamps, arrival window, link details, and private journey-management token are stored on your device.

Android application backup is disabled. Your profile name is not sent to the Arrivly server or shown on arrival pages.

You can clear your name from the Profile screen. Uninstalling removes the app’s local data.

Location and permissions

Arrivly explains its location use before requesting Android permission.

Precise location access is required for automatic journey progress and arrival detection. Coarse location can span several kilometres and cannot reliably confirm arrival within roughly 150 metres. An initial one-time reading cannot follow progress throughout a journey.

The foreground service uses location readings during a journey you deliberately start, including while the app is minimised or the screen is locked. It displays an ongoing notification with a Stop action.

Arrivly does not request Android’s separate all-the-time background-location permission.

Your current coordinates are processed on the device. Arrivly does not save a GPS-position history or route. Coordinates, destination, and route are not sent to the arrival server or added to AdMob requests.

Android’s address lookup service may process the destination query through a platform provider.

The recipient page does not request location access.

Notification permission allows journey status to be displayed. You can stop the journey in the app or notification and control permissions in Android settings.

What is shared

The Arrivly server receives an estimated range of minutes until arrival, a random link ID, a secret token authorising updates, journey status, and timestamps. This information operates the arrival-link service.

The hosting provider processes technical network information, including IP addresses, to deliver and secure requests. The application server temporarily holds IP addresses in memory for rate limiting. Hosting and security logs may be handled by the selected hosting provider under its own retention practices.

Recipients can access the approximate arrival window, whether the link is active or closed, and related update and expiry information. They do not receive your profile name, destination, coordinates, route, or private management token.

Anyone who has the link can open or forward it. You decide who receives it using Android’s share sheet.

If you choose WhatsApp, SMS, or another app, that service handles the message and link under its own privacy policy. Arrivly does not read your contacts or send messages automatically.

Advertising and privacy choices

Arrivly integrates Google AdMob for banner advertising.

When ads are enabled, Google’s Mobile Ads SDK processes IP addresses, which can indicate approximate location, device or advertising identifiers, product interactions, diagnostic information, and other data described in Google’s SDK data disclosure:

https://developers.google.com/admob/android/privacy/play-data-disclosure

This processing supports advertising, measurement, analytics, security, and fraud prevention.

Arrivly does not send journey GPS coordinates, destinations, routes, or profile names to AdMob.

Where required, Google’s User Messaging Platform requests privacy choices before ads can be requested. You can revisit available choices through the app’s Ad privacy options. Consent requirements depend on your region.

Google Privacy Policy:
https://policies.google.com/privacy

How Google uses information from partner services:
https://policies.google.com/technologies/partner-sites

Third-party retention follows the provider’s applicable policy.

Retention, deletion, and security

Arrivly stops its location service when you stop the journey, arrival is confirmed, or the link’s 12-hour lifetime ends.

Link closure requires a successful server request. If you are offline, the public link may remain active until you retry closure or it expires.

Server journey records are eligible for deletion 24 hours after closure or expiry and are removed by an hourly cleanup while the service is operating.

Local journey data is cleared after successful closure, or at expiry while the app or service is running. If closure fails, the local journey record, including its destination and management token, is retained so you can retry. Expired local records are also cleared when the app next reads them.

Arrival detection and updates depend on location services, accuracy, network access, and the journey service remaining available. Estimates can be delayed or inaccurate.

Public services use HTTPS. Random link IDs make links difficult to guess, and a separate private token is required to change a journey. No system can guarantee complete security.

To request assistance deleting service data, contact us and provide the relevant journey link if available. We may need to verify that you control the journey. We do not require you to publish the private owner token.

Your rights and this website

Depending on your location, you may have rights to access, correct, delete, restrict, or object to processing, obtain a copy of your data, or withdraw consent.

Contact support@horsexperiences.com to exercise those rights. You may also complain to your local data protection authority.

We use information to provide requested functionality, protect the service, meet legal duties, and, where applicable, process advertising choices based on consent.

The Arrivly static landing page and arrival page contain no advertising SDK or analytics scripts and do not themselves set cookies or browser storage. Hosting providers process technical requests and security information.

A privacy policy published on Google Sites is also subject to Google’s platform privacy practices.

Contact us if you believe a child has provided personal information.

We will update this policy as the service changes and revise its effective date.