RouteSky · Legal

RouteSky Privacy Policy.

Effective: 26 May 2026 · Last updated: 6 October 2026

This Privacy Policy explains how Alderframe Ltd ("Alderframe", "we", "us", "our") handles information in connection with the RouteSky iOS application ("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 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: hello@alderframe.co.uk (subject: RouteSky Privacy).

Alderframe Ltd is registered in England and Wales, company number 17269623, registered office 66 Paul Street, London, England, EC2A 4NA. 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 you can contact us directly at the address above, 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 reach receipts) 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. If you enable optional features, RouteSky sends route-area coordinates to the relevant data provider: TomTom and HERE (live traffic incidents), RainViewer (rain radar tiles), and OpenStreetMap’s Overpass API and Open-Meteo (optional route extras). RouteSky does not attach any Alderframe account or Community Reports identifier to these requests, although, as with any internet request, the provider receives the ordinary connection and network information involved in serving it, under its own privacy terms. All such features are off by default. Outside the optional Community Reports feature described below, RouteSky does not transmit location 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.

Weather information (WeatherKit)

RouteSky uses Apple’s WeatherKit to retrieve weather data for route planning and journey features. WeatherKit requests are handled by Apple under Apple’s applicable terms and privacy information.

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.

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.

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, how many drivers it has reached, and, if it has been hidden, when.

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;
  • reach receipts, which record that a report was shown to your installation so that the reporter can see how many drivers it reached and so that the same report is not counted twice.

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, from RouteSky 3.3, an Apple App Attest key handle, the matching public key and a counter, which let our service check that requests come from a genuine copy of RouteSky on a real Apple device. From RouteSky 3.3, 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. 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. 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 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: hello@alderframe.co.uk (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.

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

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);
  • 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, 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, 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 and HERE — if you enable live incident alerts, RouteSky requests traffic incident data for the area of your active route by sending those providers a bounding box of route coordinates (no identifiers). See the TomTom and HERE privacy policies for their handling of request data;
  • OpenStreetMap (Overpass API), Open-Meteo and RainViewer — if you enable the relevant optional features, RouteSky sends route-area coordinates to retrieve bridge names, air-quality/pollen data, or rain-radar tiles. These requests contain no identifiers and the features are off by default;
  • Supabase, Inc. — 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;
  • 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. 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 hello@alderframe.co.uk. 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 Commissioner’s Office (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. International users

RouteSky is operated from the United Kingdom. If you use RouteSky from outside the UK or EEA, please understand that any limited information processed may be transferred to, or accessed from, the United Kingdom. Where required, we put in place appropriate safeguards (such as the UK International Data Transfer Agreement or Standard Contractual Clauses) to protect international transfers.

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.

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:

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 Commissioner’s Office at any time, under section 165 of the Data Protection Act 2018: ico.org.uk/make-a-complaint — Information Commissioner’s Office, 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.

13. 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).

14. Contact

Questions about this RouteSky Privacy Policy: hello@alderframe.co.uk. For broader privacy matters, see the main Alderframe Privacy Policy.