RouteSky Privacy Policy.

This Privacy Policy explains how Alderframe Ltd ("Alderframe", "we", "us", "our") handles information in connection with the RouteSky apps for iPhone (with CarPlay and Apple Watch) and for Android ("RouteSky" or the "App"). It supplements, and should be read alongside, the main Alderframe Privacy Policy. Where this RouteSky Privacy Policy differs from the main policy in relation to RouteSky, this RouteSky policy prevails.

What changed on 22 October 2026. We added section 13, RouteSky for Android, which describes version 1.0 of the Android app. It works differently from the iPhone app. Sections 2 to 12 describe RouteSky for iPhone, CarPlay and Apple Watch; section 13 describes RouteSky for Android. Section 1, the complaints section and sections 14 and 15 apply to both.

What changed on 14 October 2026 for RouteSky 3.3. We describe the services RouteSky 3.3 uses that earlier versions did not: traffic incidents from TomTom during navigation, speed limits, lane guidance and speed enforcement alerts made from OpenStreetMap road data, UK fuel prices, the settings RouteSky fetches when it opens, our server logs, and the e-mail notice our moderators receive. We also record that the rain radar, backup forecast, bridge and air-quality notes and their providers were removed in RouteSky 3.3.

What changed on 6 October 2026. We expanded the Community Reports section so it lists every category of information involved, including the interactions, moderation records and anti-abuse identifiers the feature uses; corrected wording that described reports as anonymous; restated the lawful bases we rely on; corrected the retention periods to match how the service actually works; and updated the section on children.

1. Who we are

RouteSky is developed and published by Alderframe Ltd, a company registered in England and Wales. For any privacy questions about RouteSky, contact: [email protected] (subject: RouteSky Privacy).

Alderframe Ltd is registered in England and Wales, company number 17269623, registered office 66 Paul Street, London, England, EC2A 4NA. We are registered with the UK Information Commission under reference ZC267105 (view on the ICO register). We have no establishment in the European Union; we have not yet appointed our representative under Article 27 of the EU GDPR. We are taking steps to complete the appointment and will publish the representative’s details here once appointed. In the meantime, people in the EU can use their rights directly with us at the address above. We handle their requests with the same priority as requests from the UK and reply within one month, as set out in Information for people in the European Union, and you keep the right to complain to your national supervisory authority.

2. Overview

• No account. RouteSky does not require you to create an account or sign in to use the App.
• No advertising or cross-app tracking. RouteSky does not use third-party advertising SDKs or cross-app tracking, and we do not implement Apple’s App Tracking Transparency framework because RouteSky does not track you across apps and websites owned by other companies. If you turn on Community Reports, RouteSky does keep the limited operational records described in that section (a pseudonymous installation identifier and an App Attest key record) so the feature can work.
• No sale of personal data. We do not sell or rent your personal information.
• No third-party advertising SDKs. RouteSky does not embed third-party advertising or analytics SDKs that profile you.

3. Information processed by RouteSky

Depending on which features you use and the permissions you grant, RouteSky may process the following categories of information:

Location

RouteSky uses your device location to plan routes, provide turn-by-turn guidance (including on CarPlay), and show route weather context. During an active journey, location can continue in the background so guidance doesn’t stop when your phone locks; this ends at arrival or when you end the route. Location is processed on your device by iOS, MapKit and WeatherKit, and is sent to Apple for maps, directions, search and weather (see below). Where RouteSky uses another service during a drive, it sends an area rather than your position: a rectangle around the road ahead for traffic incidents (TomTom), and the road tiles and speed-enforcement files your route crosses (RouteSky’s own server). These requests carry no identifier for you or your device, although, as with any internet request, the service receives the ordinary connection information involved in serving it. Outside the optional Community Reports feature, RouteSky does not send your exact position to any Alderframe-operated service, and it never uses location for advertising or profiling.

Route and journey information

Route inputs (origin, destination, waypoints), saved trips, and trip metadata (such as estimated arrival time and Journey Score) are stored locally on your device. If iCloud sync is enabled, this information may be stored in your iCloud under your Apple ID and is not accessible to Alderframe.

Maps and weather (Apple)

RouteSky uses Apple Maps (MapKit) for directions, search, Look Around and map tiles, and Apple Weather (WeatherKit) for forecasts and official weather warnings along your route. To do that, your iPhone sends Apple your position, your destination and stops, what you type into search, and points along your route. Apple handles these requests under its own terms and privacy policy. If you save a commute, RouteSky checks the weather and the route for it once each morning in the background, which sends the commute’s two ends to Apple.

Traffic incidents (TomTom)

While you navigate, RouteSky checks for traffic incidents (closures, collisions, roadworks and queues) on the road ahead with TomTom. About every two minutes, and straight away when a drive starts or the route changes, your iPhone sends TomTom a rectangle around the next part of your route (up to about 40 km ahead) with its corners rounded to a grid of about 2 km, together with RouteSky’s TomTom key and your language. It does not send your exact position, your route line, your destination or any identifier for you or your device; as with any internet request, TomTom also receives your connection’s IP address. RouteSky makes the same kind of request for alternative routes it compares during a drive and, if you turn on the commute check (it is off unless you switch it on), for your commute’s area before you leave. Which incidents are on your route is worked out on your iPhone. TomTom (TomTom Global Content B.V., Amsterdam) answers these requests on our behalf, as our processor, under its developer terms and data processing schedule. Those terms also let TomTom collect usage information (including IP addresses) to improve its developer portal and products, and use the request data in aggregated, de-identified or anonymised form for its own analytics and product improvement; for those uses TomTom decides how the data is used and is responsible for it as a controller under its own privacy notice (tomtom.com/privacy). TomTom uses sub-processors including Amazon Web Services, Microsoft Azure and Scalyr, and its schedule allows operations staff at TomTom group companies and service partners outside the European Economic Area to have access, protected by Standard Contractual Clauses. TomTom does not publish a fixed period for keeping request records; it returns or deletes the data it holds for us when our agreement with it ends. They are on by default because they are part of navigation; you can turn them off in Profile → Traffic & incidents.

Speed limits, lane guidance and speed enforcement alerts

Speed limits and lane guidance (on by default; Profile → Road signs) come from road tiles: squares of the OpenStreetMap road map about 10 km across, the same for everyone, published by RouteSky about once a month (road data © OpenStreetMap contributors, under the Open Database Licence). When a drive starts or its route changes, your iPhone downloads the tiles the route crosses that it doesn’t already have — all at once, in a fixed order, with no key and no identifier — and keeps them for about a month. Your route, position and progress are never sent: which road you’re on, and its limit, is worked out on your iPhone, and a drive over roads you’ve driven before downloads no tiles. The tiles requested do show roughly the area a new drive covers, to within a tile, and the server sees your network’s IP address (see Server logs). You can instead download a whole region on Wi-Fi in Profile → Road signs; while a complete region is on your iPhone, drives inside it download no road data.

Speed enforcement alerts (on by default where permitted by local law, and only for your route) use fixed speed cameras and average-speed zones from OpenStreetMap, published by RouteSky as static files beside the road tiles. When a drive starts or its route changes, your iPhone downloads, with no key and no identifier, the files for the large map blocks (about 5° by 6°) that the planned route passes through and that it doesn’t already have. Whether a camera applies to your road and direction, and whether such alerts are allowed where you are driving, is worked out on your iPhone. No location is sent for this. With the Road signs switches off nothing is downloaded, and deleting all RouteSky data removes the tiles, regions and files.

Fuel prices (UK)

RouteSky fetches the UK’s national fuel price list through its own server, which obtains it from the government’s Fuel Finder service. The request carries no location; Fuel Finder sees only RouteSky’s server, never you. Your iPhone ranks the stations itself.

Settings RouteSky fetches

When RouteSky opens, and when you return to it (at most every 15 minutes), it asks RouteSky’s server for its current settings. The request carries the app version, the kind of device, your language and region (for example en-GB), the release channel and a rollout group — a number from 0 to 99 that about one install in a hundred shares. It carries no location and no identifier. Versions before 3.3 also sent a random per-install number with this request; our server ignores it, but until those installations update it can appear in the server logs below.

Server logs

RouteSky’s server is a Supabase project hosted in the EU (Paris) and operated for Alderframe by Supabase as our processor. Like most web services, it keeps a log of each request for 7 days: the time, your IP address, an approximate location derived from it (town, region and country) and your network provider’s name, the app and iOS version, and the address requested. For road data the address names the tile, so these logs show roughly the area a drive covered; they do not contain the body of a request, such as a report. We use them only to run, secure and fix the service.

Purchases (StoreKit)

If you subscribe to RouteSky Pro or make any in-app purchase, the transaction is processed by Apple through the App Store using StoreKit. We receive a transaction receipt that allows us to validate your entitlement (whether RouteSky Pro is active, by subscription or by a one-time Lifetime purchase). We do not receive your credit card number, banking details, or full Apple ID.

On-device journey data

Your trips, saved places, preferences, and hazard reports are stored on your device (some in an App Group container). RouteSky has no account system, and unless you turn on the optional Community Reports feature described below, hazard reports never leave your device. This data stays with you and is deleted with the app or via Profile → Delete all RouteSky data on this device, which also removes RouteSky’s community key and random identifier, the saved trips Spotlight and Siri know about, downloaded road tiles and regions, and asks RouteSky’s server to delete the record of your community key. Reports you have already shared stay on the server until they are removed as described under Community Reports; after the erase they can no longer be linked to you. RouteSky keeps the newest 500 of your own hazard reports and the newest 200 weather-hazard records on your iPhone, and cached route forecasts are never shown once they are more than 6 hours old.

Ask RouteSky (on-device)

On iPhones where Apple Intelligence is available and switched on, you can ask RouteSky questions about a planned drive, in the app or through Siri. Your question and the answer are processed on your device by Apple’s on-device language model, using only the route and forecast information RouteSky already holds on your iPhone. Nothing you ask is sent to Alderframe or stored by us. More detail is in how we use AI.

Community Reports (optional, off by default)

Community Reports have been available in RouteSky since version 1.1.0 (23 August 2026) and have been off by default since launch. Nothing in this section applies unless you deliberately turn Community Reports on in Profile and accept the Community Guidelines. If you do, information is sent to a RouteSky database operated for Alderframe Ltd by Supabase (hosted in the EU, Paris region) so that drivers nearby can see your reports on their route, and theirs appear on yours.

Pseudonymous, not anonymous. Community Reports do not display your name, contact details or a public profile, and they contain no free text, photos, video or audio. They are linked internally to a pseudonymous installation identifier — a random value RouteSky generates on your device when the feature is set up — for operation, security and abuse prevention. Because that identifier stays the same for as long as the app is installed, reports and interactions from the same installation can be linked to each other, which is what lets us rate-limit abuse and lets other drivers block a source of bad reports. The identifier itself does not contain your name or contact details, and Alderframe does not use it to identify you by name; we nevertheless treat everything in this section as personal data and protect it as such.

Mobile speed checks. Where local law permits, a report can be a mobile speed check (a speed camera van or temporary roadside check). It goes through exactly the same path, safeguards and retention as any other report, except that it is shown for about 45 minutes, each “Still there” keeps it for about 45 minutes from that answer, and never for longer than 4 hours after it was made.

What a Community Report contains. Each report you share may include:

• the hazard type, chosen from a fixed list (for example ice, fog, flooding, closure);
• the report location as latitude and longitude, and your direction of travel where available;
• a short forecast or context note generated automatically by the app from the weather for that spot — never written by you — which gives other drivers context but is not needed for the report itself to work;
• your pseudonymous installation identifier;
• the time the report was made and the time it expires (30 minutes to 6 hours depending on type);
• moderation counts and status: how many installations have confirmed it, how many have flagged it, for reports made with versions before 3.3, how many drivers it reached; and, if it has been hidden, when.

Seeing other drivers’ reports. While you navigate with Community Reports on, RouteSky asks for the reports in the whole map squares your planned route crosses (one degree of latitude by one of longitude, about 111 by 69 km; larger five-degree squares on very long journeys), all from the start of the drive, so the requests don’t show where you are along the route. These requests carry no identifier and no position, and RouteSky 3.3 records nothing about which reports were shown to you.

Interactions with other drivers’ reports. When you respond to a report, that response is stored against your own pseudonymous installation identifier, separately from the report itself:

• Still there / Gone confirmations;
• flags, with the preset reason you choose (not there, wrong kind, spam, abusive, other);
• blocks, which hide all reports from a particular installation for you;
• in versions before 3.3 only, reach receipts, which record that a report was shown to an installation so that the same report is not counted twice. RouteSky 3.3 no longer creates them; installations still running an earlier version can, until they update.

Anti-abuse and integrity information. To keep the feature usable we also process: rate-limit counters for reporting and flagging; a record of any temporary suspension of community sharing for an installation (applied automatically when three of its reports are hidden within 24 hours, for 7 days); and an Apple App Attest key handle, the matching public key, a counter and when it was created and last used, which let our service check that a report, confirmation or flag comes from a genuine copy of RouteSky on a real Apple device. It is used only to file your reports, apply rate limits and suspend abuse, and is never combined with route history, used for analytics or shared. If the check can’t be made, your report stays only on your iPhone. Rate limiting also uses a scrambled value derived from your network address that changes every day; the network address itself is not stored.

How moderation uses this information. Moderation is automated: you cannot flag your own report; flagging is rate limited; a report is hidden automatically after three flags from different installations; and an installation whose reports are hidden three times within 24 hours is suspended from sharing for 7 days. When a report is flagged, hidden automatically after three flags, or its source is suspended automatically, a person at Alderframe is told by e-mail, sent through Resend (Plus Five Five, Inc., trading as Resend, as our processor). The e-mail carries only the kind of event, the report’s random ID and the time — never a position, identifier or note; the event record is deleted 90 days after the e-mail. A person may look at reports, flags and related records when we investigate a concern you raise with us or when the law requires it. If a person reviews a report, the decision, its reasons and any complaint about it are kept in a case record for 12 months after the case closes (longer only for a documented legal reason), holding the report’s ID and kind but not its position or author. See the RouteSky Terms for the rules that apply.

Retention. Reports expire automatically (30 minutes to 6 hours depending on type). A daily clean-up removes each report, together with its confirmations, flags, reach receipts and moderation counts, once 5 days have passed since the report expired or was hidden. A record of a temporary sharing suspension is removed 5 days after the suspension ends. A block you place on another installation’s reports is kept until you remove it in the app. Rate-limit windows are kept for 2 days; the daily network-derived value is replaced every day. App Attest records for an installation are removed after 90 days without use.

Lawful basis. Community Reports is an optional feature you choose to turn on. Once you have turned it on, processing the information needed to submit, transmit and display your reports (hazard type, location, direction and timestamps) and to carry out the actions you ask for (confirmations, flags and blocks) is necessary to provide the feature you have requested, so we rely on performance of a contract (UK GDPR Art. 6(1)(b)). The short forecast context note attached to a report, rate limits, moderation counts, automatic hiding, temporary suspensions, the App Attest check, the daily network-derived value and, for versions before 3.3, reach receipts (which stop a report being counted twice and let us measure how far reports travel) are processed on the basis of our legitimate interests (Art. 6(1)(f)) in making reports more useful to other drivers and in keeping the service secure and free of abuse, assessed with particular regard to younger users and recorded in our legitimate interests assessment. You can object to any of this processing by emailing us; the practical way to stop it is to turn Community Reports off. Turning the feature off stops new processing; see Retention for what happens to what has already been shared.

Your choices. You can turn sharing off at any time in Profile; this stops new reports and interactions being sent, but does not remove what you have already shared, which expires within hours and is removed from the database on the schedule above. RouteSky does not currently offer a control that deletes your already-shared reports from the server. If you want a report removed sooner, email us (see below) with the approximate time and place and we will remove it. Reinstalling RouteSky generates a new identifier and permanently severs the link between the new installation and earlier reports.

Questions or concerns about a Community Report, including online-safety or moderation concerns: [email protected] (subject: RouteSky Online Safety Complaint). To send a formal notice that a report contains illegal content, see how to report illegal content.

Diagnostics

If you choose to share analytics and diagnostics data with app developers in iOS (Settings → Privacy & Security → Analytics & Improvements), Apple makes crash and diagnostic information about RouteSky available to us in line with those settings and Apple’s privacy information. We use it only to identify and fix issues.

Services removed in RouteSky 3.3

Earlier versions offered optional live incident alerts from HERE (RouteSky 3.3 asks TomTom only, a choice built into the app that settings cannot change), a fallback forecast and air-quality, pollen, sea-state and soil notes (Open-Meteo), bridge names and public Wi-Fi places (OpenStreetMap’s Overpass service) and a rain radar (RainViewer). RouteSky 3.3 doesn’t include those features and sends those services nothing; anything they left on your iPhone (a network cache) is deleted when you update. If you used them in an earlier version, each provider handled your requests under its own policy.

Apple Watch, CarPlay, Siri and your other devices

RouteSky shares your drive with your Apple Watch (the road ahead, your position and destination; when not driving, your saved places and recent destinations) and with your car through CarPlay. Siri, Spotlight, Handoff, widgets, Live Activities and notifications show RouteSky information through iOS on your devices. This stays between your devices and iOS; Delete all RouteSky data clears what RouteSky put there.

4. What RouteSky does not collect

• We do not require an account, email address or password to use RouteSky.
• We do not collect or upload your contacts, photos, microphone or camera data.
• We do not use third-party advertising or marketing SDKs.
• We do not track you across apps and websites owned by other companies.
• We do not sell, rent or trade personal information.
• We do not knowingly process special category data (such as health, biometric or political information) through RouteSky.

5. How we use information

You don’t have to give us any personal data, and nothing here is a statutory requirement. Some features can’t work without the information they use: for example, navigation needs your location, and a Community Report needs its position.

Where information is processed at all, it is used to:

• Provide and operate RouteSky’s planning, mapping, navigation, journey, weather and Community Reports features that you choose to use;
• Provide turn-by-turn guidance on your iPhone and on CarPlay;
• Validate RouteSky Pro entitlements via Apple’s StoreKit;
• Operate the automated safeguards that keep Community Reports usable (rate limits, flag thresholds, hiding, temporary suspensions, App Attest checks). These are automated, but they decide only whether a report is shown or whether an installation can share for a short time; they have no legal or similarly significant effect on you, and you can ask a person at Alderframe to review any of them by emailing us;
• Diagnose and fix bugs and improve stability;
• Respond to support, privacy and accessibility requests you send us; and
• Comply with applicable legal obligations.

6. Legal basis (UK GDPR)

Where RouteSky processes personal data of users in the United Kingdom or European Economic Area, we rely on the following lawful bases under the UK GDPR / EU GDPR:

• Performance of a contract (Article 6(1)(b)) — where processing is necessary to provide a RouteSky feature you have asked for: core route planning and navigation (including traffic incidents, speed limits, lane guidance, speed enforcement alerts and fuel prices during a drive), RouteSky Pro features you have purchased, and, once you have deliberately turned Community Reports on, submitting, transmitting and displaying your reports and carrying out the confirmations, flags and blocks you request;
• Legitimate interests (Article 6(1)(f)) — for proportionate service security, abuse-prevention and integrity measures (rate limits, moderation counts, automatic hiding and suspensions, App Attest, the daily network-derived anti-abuse value and reach receipts), for the forecast context note attached to Community Reports, for the settings request and server logs that keep the service working and secure, for moderation notices and case records, and to fix bugs and improve the product. We balance these interests against your rights and interests, taking particular account of younger users;
• Consent (Article 6(1)(a)) — only where we genuinely ask for your consent as the lawful basis for a specific processing activity. We do not currently rely on consent for any RouteSky processing. The permissions you grant in iOS (for example, Location) and the feature switches in the app are controls over what RouteSky may do on your device; they are explained in Your choices and rights below and are separate from the lawful basis;
• Compliance with legal obligation (Article 6(1)(c)) — where required by law.

7. Sharing

We do not sell personal data, and we do not share personal data with third parties for their own marketing. We may share information with:

• Apple — through built-in iOS frameworks (MapKit, WeatherKit, StoreKit, CarPlay, iCloud). Apple’s use of any data exchanged via these frameworks is governed by Apple’s terms and privacy policy;
• TomTom (TomTom Global Content B.V.) — during navigation, RouteSky requests traffic incident data for a rounded rectangle around the road ahead (no identifier, no exact position). TomTom acts as our processor for answering these requests and as a separate controller for its own de-identified analytics and product improvement. See Traffic incidents;
• Supabase — RouteSky’s server (settings, road tiles, speed-enforcement files, fuel prices and request logs) is a Supabase project, operated for Alderframe by Supabase as our processor. If you turn on the optional Community Reports feature, shared reports and the related interactions, moderation and anti-abuse records listed above are stored in an EU-hosted (Paris region) Postgres database operated for Alderframe by Supabase, acting as our processor under data-protection terms. They carry no name, account or contact detail — reports are linked to a pseudonymous installation identifier.;
• Resend (Plus Five Five, Inc., trading as Resend) — sends the moderation notices described under Community Reports to Alderframe, as our processor. They contain no position, identifier or note;
• Service providers who help us operate the App (for example, infrastructure hosting for the marketing website and email), under written confidentiality and data-protection terms;
• Authorities and others where required by law, regulation, lawful process, or to protect the rights, property or safety of Alderframe, our users or the public.

8. Retention

Information processed in RouteSky is held only for as long as is needed for the purposes set out above. Locally stored data (such as saved trips) is retained on your device until you delete it or uninstall the App. Shared Community Reports expire automatically (30 minutes to 6 hours depending on type) and are removed from the community database, with their confirmations, flags, reach receipts and moderation counts, by a daily clean-up once 5 days have passed since they expired or were hidden; suspension records are removed 5 days after the suspension ends, and the other periods are set out in the Community Reports section. Server logs are kept for 7 days. Moderation notice records are deleted 90 days after the notice; case records 12 months after a case closes. Road tiles and speed-enforcement files stay on your iPhone for about a month or until you delete all RouteSky data. Our database provider’s daily disaster-recovery backups can keep a copy of database records for up to 7 more days; backups are never used as live app data. Resend keeps its copy of each moderation e-mail and its delivery records for 30 days. Support correspondence is retained for a reasonable period and then deleted. Transaction records held via Apple are retained according to Apple’s policies.

9. Your choices and rights

You can manage many privacy choices directly in iOS:

• Location: Settings → Privacy & Security → Location Services → RouteSky;
• Notifications: Settings → RouteSky → Notifications;
• Subscriptions: Settings → [your name] → Subscriptions;
• Community Reports: turn sharing on or off at any time in Profile → Community Reports; reports already shared expire and are removed as described in Retention, or email us to have one removed sooner;
• Local data: delete the App to remove its on-device data, or use any reset options inside the App.

Where applicable law (such as the UK GDPR, EU GDPR or California Consumer Privacy Act) gives you rights to access, correct, delete, restrict or object to processing of personal data we hold about you, you can exercise those rights by emailing [email protected]. We will respond in line with applicable law. Because Community Reports carry only a pseudonymous installation identifier — not your name or contact details — if you ask us to delete a specific report, please quote the approximate time and place of the report so we can locate it. You also have the right to complain to the UK Information Commission (ico.org.uk) or your local data-protection authority.

10. Children

RouteSky is not intended for children under 13. Users aged 13 to 17 may use RouteSky subject to the RouteSky Terms and any higher minimum age required by applicable law. We recognise that users under 18 are children for data-protection and online-safety purposes. Community Reports are therefore designed with privacy-protective defaults: the feature is off by default, there are no public profiles or free-text posts, and shared reports are retained only for short periods. If we become aware that a child below the permitted minimum age is using a feature contrary to these rules, we may take appropriate steps to restrict the feature or delete relevant information. If you believe that has happened, please contact us.

11. Where your information goes

RouteSky is operated from the United Kingdom. The services it uses process information in these places:

• Supabase — RouteSky’s database, files and logs are hosted in the European Union (Paris). Supabase’s contracting company is in Singapore and its group operates from outside the UK, so access for support and operations is protected by the EU Standard Contractual Clauses with the UK’s International Data Transfer Addendum, as set out in Supabase’s data processing agreement.
• TomTom — TomTom is based in the Netherlands. Its data processing schedule names Amazon Web Services, Microsoft Azure and Scalyr as sub-processors (it states EU data-centre locations for Scalyr) and protects any transfer outside the European Economic Area, including access by TomTom group companies and service partners, with the EU Standard Contractual Clauses (2021).
• Resend — moderation e-mails, and Resend’s records of them, are stored in the United States. Plus Five Five, Inc. (Resend) is certified under the EU–U.S. Data Privacy Framework and its UK Extension (checked on the official Data Privacy Framework list on 14 October 2026), so transfers from the UK rely on the UK’s adequacy regulations for those certified organisations (the “UK–US data bridge”). Resend’s data processing agreement also includes the EU Standard Contractual Clauses with the UK Addendum.
• Apple — maps, weather, purchases and iCloud are handled by Apple under its own terms and privacy policy.

You can ask us for a copy of the safeguards for any of these transfers by emailing [email protected].

12. Security

We use reasonable technical and organisational measures appropriate to the limited categories of information processed by RouteSky. However, no system can be guaranteed completely secure, and we cannot promise absolute security.

13. RouteSky for Android

This section covers RouteSky for Android, version 1.0. Sections 2 to 12 above describe the iPhone app and do not apply to it.

No account, no ads, no tracking

• There is no sign-in and no account.
• There are no ads, and RouteSky does not use your advertising ID.
• There is no analytics, crash-reporting or tracking software in the app.
• We do not sell data, share it for advertising, or build profiles.

What stays on your phone

Your location (GPS), your searches, your destinations, routes and turn-by-turn guidance, your journey history and your settings are worked out and stored on your phone. None of them is sent to us. Spoken directions use your phone’s own offline speech engine.

Location

RouteSky uses your location while you plan and navigate. During guidance it shows an ongoing notification, because guidance runs as a foreground service that you start. RouteSky does not ask for background location (“Allow all the time”), and your precise location is never sent to us.

One exception. If you are driving in an area that none of your downloaded regions covers, the app may fetch road information, such as speed limits, for that area from our server. That request names a map cell of about 11 × 10 km, which shows roughly where you are. It carries no ID, name or account. If you turn on On-device only in Settings, this request is never made.

What reaches our servers, and why

1. Map downloads. When you download or update a region, the app first asks our server for a short-lived, anonymous download pass. The pass lasts up to 15 minutes and is kept only in your phone’s memory. The app then downloads the region’s files. It sends the platform (“android”) and the app version, and then the requests for the region’s files. It never sends your location, an ID or anything else about you. Update maps automatically and Nearby maps can start downloads without you tapping. Both are optional, Nearby maps is off by default, and neither runs while On-device only is on.
2. Road information outside your downloaded regions, as described under Location.

Nothing else is sent. Weather, traffic and road-incident features are switched off in this version and make no requests.

We use this information only to provide the map downloads and road information you use (UK GDPR Article 6(1)(b)), and to keep the service secure and protected from abuse (Article 6(1)(f)).

What our servers keep, and for how long

• Download passes. We keep nothing about you. We keep a monthly count of the passes issued, as a number only.
• Abuse protection. To limit abuse, we count requests per hour against a scrambled (one-way hashed) form of your network address. It is reduced to the /24 (IPv4) or /48 (IPv6) network, with a key that changes daily, and your IP address is not stored in it.
• Provider request logs. Our hosting providers keep standard request logs for up to 7 days, then delete them automatically. Each entry holds the request, the time, the result and technical details, which can include your IP address. The log line we write for a download holds the status, the file path, the pass’s random ID, the size and the duration. It never holds the pass itself, an address or coordinates.
• On your phone. Everything RouteSky stores stays on your phone until you clear RouteSky’s storage or uninstall the app.

Who handles it, and where

• Supabase runs the download-pass service and stores the road information. Our Supabase project is hosted in the EU (Paris).
• Cloudflare (Cloudflare, Inc.) delivers the map files, from Cloudflare R2 storage through a Cloudflare Worker.

Both act for us as processors. They may process requests outside the UK, including in the United States, under their standard data-processing terms and transfer safeguards. Their details are on our subprocessors page.

Google Play Data safety

Our Data safety answers for Google Play match this section. They declare one data type, approximate location. It is collected only for app functionality (road information for an area that none of your downloaded regions covers). It is not shared. It is not processed only in transit, because provider request logs keep it for up to 7 days. It is optional, because On-device only turns it off. All data is encrypted in transit. Precise location, personal information, app activity, app diagnostics and device or other IDs are not collected.

Your choices and deleting data

• On-device only (in Settings) stops every automatic request. Only downloads you start yourself can then leave your phone.
• Clearing RouteSky’s storage, or uninstalling the app, deletes everything RouteSky holds on your phone. See Deleting your data.
• There is no account, and nothing we keep is linked to you, so there is nothing on our side to delete on request. Server logs delete themselves within 7 days.

Under UK data protection law you can ask us for access to, correction or erasure of personal data we hold about you, and you can object to or restrict its use. Email [email protected]. You can also complain to us or to the Information Commission, as described below.

Age, and where it is offered

RouteSky for Android is for drivers aged 18 and over. It is not directed at children. It is offered in the United Kingdom only, and covers England, Wales, Scotland and Northern Ireland.

Not in this version

RouteSky for Android 1.0 has no weather; no traffic, incidents or road events; no speed cameras; no community reports; no purchases or subscriptions; and no sign-in. If any of these is added later, we will update this section before that release.

Questions about RouteSky for Android and privacy: [email protected].

Android and Google Play are trademarks of Google LLC.

Complaints about how we use your personal information

If you are unhappy with how Alderframe Ltd has handled your personal information, you have the right to complain to us under section 164A of the Data Protection Act 2018. You can:

• use our data protection complaint form;
• email [email protected] with “Data protection complaint” in the subject line; or
• write to us at Alderframe Ltd, 66 Paul Street, London, England, EC2A 4NA, United Kingdom.

You do not have to use the form — we will accept a complaint made in any clear way. We will acknowledge your complaint within 30 days of receiving it, look into it, keep you informed of progress, and tell you the outcome without undue delay.

You can also complain to the Information Commission at any time, under section 165 of the Data Protection Act 2018: ico.org.uk/make-a-complaint — Information Commission, Wycliffe House, Water Lane, Wilmslow, Cheshire SK9 5AF; telephone 0303 123 1113. If you are in the EEA, you may also complain to the supervisory authority in your country.

14. Changes to this policy

We may update this RouteSky Privacy Policy from time to time. The "Effective" and "Last updated" dates above show when it was last revised. If a change is material, we will take reasonable steps to notify you in advance (for example, in-app or on this page).

15. Contact

Questions about this RouteSky Privacy Policy: [email protected]. For broader privacy matters, see the main Alderframe Privacy Policy.