What this page covers, and what it does not
This document is about the app — Driftstone on Google Play — and nothing else.
Executive Travel Ascot Limited is a private-hire company, and a private-hire company plainly does handle personal data: names, pick-up addresses, flight numbers, payment details. None of that is described here, because none of it has anything to do with the app, which cannot reach it and never sees it. If you are a passenger rather than a player, ask the company for the booking privacy notice; it is a separate document about a separate set of records.
What follows applies solely to the software, and the whole of it comes to this: nothing about you is collected by it, because nothing in it opens a connection.
Who publishes it and who reads the post
EXECUTIVE TRAVEL ASCOT LIMITED
Francesco Daulerio
8 Crossways, Crossways Village, Silwood Road
Ascot SL5 0PY, United Kingdom
Mail: pebble@travelascot.yachts
Under the UK GDPR the company is the controller for whatever Driftstone might process. No processor acts on its instructions for the app, nobody shares the decisions, and no representative has been appointed abroad, because there is no processing for any of those arrangements to govern. The mailbox above is the route for privacy questions about the app, and it is read by a person.
What the app keeps, and where it keeps it
Driftstone saves your best height and score for each of its modes, the mode and backdrop you last used, and your sound and vibration settings. That is the entire list, and all of it lives in the private storage area Android gives the app on your own device.
Android walls that area off around the application that owns it, so other software installed on the handset cannot look inside. Nor can we: nothing in the build accepts an instruction from outside, there being nothing in it that opens a connection in the first place. A score is a number on your phone and nowhere else, which also means it cannot be transferred to a new handset by us, recovered if you clear it, or compared with anyone.
One movement of files is the platform's rather than ours. Android runs an automatic backup bound to a Google account; where someone has it switched on, the system may copy an app's files into that person's own Google Drive so a replacement handset can restore them. That is done by Android under the account holder's settings. We take no part in it, cannot read what it carries and cannot switch it off for anybody — the control sits per app in Android's settings.
Uninstalling removes the folder with everything in it, and the "clear data" control in Android's app settings empties the folder without taking the app off the phone.
The parts that were never built in
There is no advertising framework in the release, no analytics or attribution package, no crash reporter, no sign-in provider and no payment component. Those are absences from the package rather than options inside it — nothing is waiting to be switched off, and no server anywhere has the standing to switch it back on. Item by item, the app at no point reads, works out or sends:
- a name, an email, a number or an address — nothing by which you could be identified or reached;
- whichever string Android currently uses for advertising, the Android ID, a handset serial or a hardware address;
- where the device is, by any method at all;
- who is in your contacts, what is in your calendar, who has written to you or rung you, and nothing at all through the microphone or the lens;
- how long you play, how often, or which mode you prefer;
- photographs or any other file already stored on the phone.
Stones and backdrops come down inside the installer rather than being fetched afterwards, so the app is finished the moment installation is, and flight mode changes nothing about how it behaves.
Permissions, and Google's separate part
Almost nothing is declared in the manifest, and the camera, microphone, location, contacts and telephone permissions are not declared at all, so the dialogue asking you to grant them has no reason to appear.
Downloading or updating through Google Play is an arrangement you enter into with Google, governed by Google's own terms, and no part of the account or device data it involves is routed via this company. The developer console hands us country-level install counts, crash rates and star ratings, already aggregated, with no way back to a person — and there is no second source of information about anybody.
Children
Balancing stones is about as harmless as software gets. Driftstone carries no advertising, no chat, no links out, no contact between players and no screen that asks for money, and since nothing is gathered from anyone it is gathered from a child either. Where a child's consent would be the basis for processing, Article 8 and the age of thirteen set in the Data Protection Act 2018 would come into play — but consent is not the basis for anything here, so the question does not open. A parent who would like that confirmed in writing is welcome to ask.
The law, and the regulator
The company is registered in England, so the instruments are the UK GDPR and the Data Protection Act 2018, and the supervisory authority is the Information Commissioner's Office at ico.org.uk.
Better said outright than left to be discovered: a company that collects nothing still owes a few things. The controller has to be identifiable under Article 13 whether or not any data is taken, hence a second band that names a registered company, a named individual and a postal address rather than a logo; and under Article 5(2) it falls to us to show that we comply, never to you to show that we do not. What this page cannot offer is the usual reassurance about years of careful stewardship — there are no such years, because there is nothing being looked after. It is the smaller claim and the sturdier one.
Driftstone is listed worldwide, so it is installed across the European Union as well. A resident of an EU state is covered by the General Data Protection Regulation in its European form and may take any complaint to the supervisory authority of the country they live in, without having written to us first. Writing first is simply quicker.
What you may ask, and what you will be told
Articles 15 to 21 give you sight of what is held, correction, erasure, a restriction on use, a portable copy, and the right to object to processing altogether. Article 77 adds a complaint to the Commissioner, and no sentence on a page like this one can weaken it.
Write to pebble@travelascot.yachts and you will have an answer well inside the one month Article 12(3) allows. It will be brief, because there is no file under your name to show you, correct, erase, suspend or pass on. No identity check will be asked for first: nothing is stored for such a check to protect, and requesting a photograph of somebody's passport in order to report an empty folder would put more at risk than the rest of the exchange together. If the answer leaves you unconvinced, say so once and it will be looked at again; after that the Commissioner is the right address.
If this page is written again
Should a later build of Driftstone take on anything that touches personal data — scores that sync between devices or onto a leaderboard, a crash reporter, stone sets or backdrops sold for money, advertising in any form — this text is rewritten and published before that build is rolled out, not after it. The edition line under the title moves at the same moment, and the substance goes into the Play release notes so it reaches people who never come to this address.
The address stays put while the app is listed, and the edition line is the fastest way to tell whether the wording has shifted since you last read it.