Privacy Policy
Last updated: Version privacy-2026-11-16
The short version
A quick summary for everyone, whatever your age. The full policy below has the details.
- What we collect. If you make an account: your email address, the price alerts you set and your settings. When you tap through to a shop, we note which product and shop, but not who you are, so we can see what people click on. Our servers keep technical logs so Beaconry works and stays safe. If you are 18 or over, we also record how you use Beaconry to help us improve it. You can tell us to stop with the “Product analytics” switch in the app’s settings or in your account settings on the website, or by emailing us.
- What we never do. We show no adverts, we do not sell your data, we do not build advertising or marketing profiles about anyone, and there are no public profiles or messaging.
- If you are under 18. We do not record how you use Beaconry for our analytics, the app does not add its device identifier when you tap through to a shop, and we do not keep your date of birth. If the app crashes, it sends a crash report about what went wrong, for everyone, whatever their age.
- Deleting your account. You can delete your account at any time from your Account page, except while your account is suspended. If so, email support@beaconry.co, and we will review your request before acting on it. Most of your data goes when your account is deleted. A few things stay for a while, and our account deletion page lists them.
Beaconry is a price tracking and comparison service for model railway and tabletop wargaming hobbyists, operated by Chief Solutions Limited (the "Company", "we", "us"). This policy explains what personal data we collect when you use the Beaconry website and mobile app, why we collect it, who we share it with, and the rights you have over it.
The data controller is Chief Solutions Limited, a company registered in England and Wales under company number 06238112, with its registered office at CCM Chichester House, 2 Chichester Street, Rochdale, OL16 2AX. If you have any questions about this policy or your data, contact us at privacy@beaconry.co. Our ICO data-protection registration number is ZC286352.
Data we collect
- Account details. When you register, we collect your email address and a password. Your credentials are stored and managed by Amazon Cognito on our behalf; we do not store your password in a form we can read. If you enable multi-factor authentication, we also process the related settings.
- Your Beaconry activity. Your subscription tier and status, notification preferences, the price alert beacons you set, and whether you told us at sign-up that you are under 18.
- Push notification token. If you turn on push notifications in the mobile app, we store the device token needed to deliver them.
- Technical and log data. To run the service securely and diagnose problems, our servers keep operational logs that may include your IP address and request metadata. Where an email address appears in these logs it is pseudonymised using a one-way keyed hash, not stored in readable form.
- How you use Beaconry. We record a small set of product events, such as a price alert being delivered to you or a tap through to a retailer, along with the subscription tier of the account involved. These are tied to a pseudonymous account identifier we generate, rather than to your name or email address. If you told the mobile app you are 18 or over, a tap through to a retailer also carries a random identifier for that app installation, whether or not you are signed in, so we can understand how people use the app, including people who are not signed in. If you told the mobile app you are 18 or over and have not objected, the app also sends Amplitude its own usage events, when each app session starts and ends, a random identifier for the installation and basic details of the device. See "Product analytics" below.
- Retailer clicks. When you tap through to a retailer to buy something, we record the listing, the retailer, whether the link carried an affiliate identifier, an inferred platform, and when it happened. The record does not say who clicked: it holds no account, device identifier, subscription tier or web address. We keep it to see what people actually click on, and to give retailers summary data through dashboards and reports in our retailer portal, which has not launched yet. Clicks recorded before we stopped storing who clicked can still carry your account, the app-installation identifier, your subscription tier and the full web address, until they expire or we remove those details.
- Essential cookies. We set a signed session cookie so you stay signed in. When you paste a link we have not seen before, we also set a short-lived cookie that expires within two minutes, or as soon as the product page loads, so that page can tell you we are still looking for other retailers; it holds no personal data. While you are signing up we set a cookie, for up to an hour, that holds only a random sign-up reference. Against that reference we keep, on our own servers, the version of the Terms you agreed to, the version of the Privacy Policy you were shown, whether you told us you are under 18, and the email address you are signing up with, so we can store that agreement and your answer when you confirm your email. When you confirm, we remove both straight away where we can; in any case the cookie expires after an hour, we stop using what we kept, and it is deleted automatically within a few days. We do not set advertising, analytics, or third-party tracking cookies. On the website, product analytics are sent from our own servers, so they do not involve cookies or any other tracking technology in your browser. The website runs no analytics in your browser. The mobile app is different: if you told it you are 18 or over and have not objected, it runs Amplitude’s analytics software, which keeps a random identifier on your device. “Product analytics” below describes it.
The sign-ups waitlist
New accounts are not open yet. While they are closed, you can leave your email address on our waitlist so we can tell you when they open. This section covers only that list. You do not need an account to be on it, and being on it does not create one.
What we store
Your email address, whether you ticked the beta tester box, which mobile platform you said you would use if you did, the campaign code in the link or QR code you arrived through (if any), and the dates you joined and last updated your choices.
Lawful basis
Your consent, given when you submit the form. You can withdraw it at any time by emailing privacy@beaconry.co, and we will erase your entry. Because the list exists before you have an account, this is the route to use: there is no account to sign into and delete.
Who we share it with
Nobody, unless you ticked the beta tester box. If you did, we will pass your email address to Apple (App Store Connect) and Google (Google Play) so they can invite you to test pre-release builds. That is a disclosure to those companies, and it happens only for people who ticked the box. If you did not tick it, your address stays with us and our email provider, and you will still get the message telling you sign-ups have opened.
How long we keep it
The waitlist is a holding record, not a mailing list. We delete your address once we have sent you the message saying sign-ups are open, or after twelve months, whichever comes first. If you go on to create an account or join the beta, the ongoing relationship lives in your account or with the testing programme, not in this list, so we still delete the waitlist entry.
What we do not do
We do not use this address for a newsletter, marketing, or anything other than telling you sign-ups have opened, and we do not sell it.
How we use your data and why
Each row below is one purpose: the data we use for it, our lawful basis under UK data protection law, and how long we keep that data. Where the basis is "legitimate interests", the interest is named. The retention column is a summary; the section "How long we keep your data" has the detail.
| Purpose | Data | Lawful basis | Retention |
|---|---|---|---|
| Create and manage your account and sign you in | Email address, password (held by Amazon Cognito), multi-factor settings | Contract: we need these to give you an account. | While your account is open; erased when you delete it. |
| Operate the core service: show prices and send the price alerts you ask for | Your beacons, notification preferences, notification history | Contract. | While your account is open; notification history expires after 13 months. |
| Send push notifications for alerts you have requested | Push notification token, a record of each push we send | Contract: the push is how we deliver the alert you asked for. You can switch push off at any time in your device's notification settings. | Token: until you delete your account or it stops working. Delivery records: 90 days. |
| Manage your subscription and confirm your access tier | Subscription tier and status, as confirmed by RevenueCat | Contract. | While your account is open. When you delete your account we ask RevenueCat to delete your subscriber record; RevenueCat may keep some data under its own retention policy, and if your store subscription is still active it can create a new record for it. We keep a record that your account was erased, holding only its random account identifier and the date, for 6 years after your account is deleted. |
| Security logging, abuse prevention and fixing faults | IP address and request details in server logs; email addresses appear only as a keyed one-way hash | Legitimate interests: keeping the service secure, preventing abuse and diagnosing faults. | Production server logs: 1 month. |
| Product analytics | Pseudonymous account identifier, product events, subscription tier | Legitimate interests: understanding which parts of the service are used so we can improve it. You can object (see "Your right to object"). We do not collect these events about accounts where you told us at sign-up that you are under 18, or where we do not know your age. | Held by Amplitude. Event data is kept for 13 months from when it was recorded. When you delete your account we ask Amplitude to remove your pseudonymous profile and its events; Amplitude completes this on its own schedule. Until the app clears your identifier when you sign out, events it sends from that installation afterwards, including after you delete your account, can still carry your identifier, and a deletion request we have already made does not cover them. |
| Understanding how people use the mobile app, including people who are not signed in | A random identifier for the app installation, sent with a tap through to a retailer (the listing, platform, whether the link carried an affiliate identifier, and the subscription tier and whether it is Lifetime Pro, if any), whether or not you are signed in. Only when you told the app you are 18 or over and have not objected. | Legitimate interests: understanding how the service is used so we can improve it. | Held by Amplitude. Event data is kept for 13 months from when it was recorded. |
| The mobile app’s own analytics | Events the app records as you use it, when each app session starts and ends, a random identifier Amplitude’s software creates for the installation, your pseudonymous account identifier if you are signed in, the app version, operating system and its version, platform, device model and language, and the IP address Amplitude receives with each connection. Only when you told the app on that device that you are 18 or over and have not objected. | Legitimate interests: understanding how the app is used so we can improve it. You can object (see “Your right to object”). | Held by Amplitude. Event data is kept for 13 months from when it was recorded. Until the app clears your identifier when you sign out, events it sends from that installation afterwards, including after you delete your account, can still carry your identifier, and a deletion request we have already made does not cover them. |
| Retailer-click records, to see what people click on and give retailers summary reports | Listing, retailer, whether the link carried an affiliate identifier, platform and time. No account, device identifier, subscription tier or web address. Older records can still carry them until they expire or we remove them. | Legitimate interests: seeing what people actually click on, and giving retailers summary data through dashboards and reports in our retailer portal, once it launches. These records are not accounting records: they cannot be matched to a sale, and the affiliate network's commission statements are our accounting record. | 395 days (about 13 months), then deleted automatically. |
| Crash diagnostics | Crash reports from the mobile app: technical details of the fault and the device. | Legitimate interests: keeping the app stable and fixing faults, for users of every age. Not used for profiling. | Held by Google (Firebase Crashlytics) for 90 days. |
| Contact you about your account or important service changes | Email address | Contract; legitimate interests for service notices. | While your account is open. |
| Check you are old enough to use Beaconry | The date of birth you enter at sign-up, and whether you are under 18 | Legitimate interests: only providing the service to people aged 13 and over, and looking after accounts of people under 18 with extra care. | Date of birth: not kept. We check it once, at sign-up, and discard it. Whether you are under 18: while your account is open; erased with it. |
| Keep a record that you agreed to our Terms and saw this policy | The version of the Terms you agreed to and of this policy you were shown at sign-up, and when | Legitimate interests: being able to defend a legal claim, by showing what you agreed to. | While your account is open, then 6 years after it is deleted, the time within which a legal claim can be brought. |
| Sign-ups waitlist | Email address, beta tester choice, platform, campaign code | Consent. You can withdraw it at any time. | Until we tell you sign-ups are open, or 12 months, whichever comes first. |
| Handle a data protection complaint | Name, email address, the account email if different, and what you tell us | Legal obligation: we must have a complaints procedure (Data Protection Act 2018). | Kept for 6 years and not removed when you delete your account. |
| Change your email address through support | Both addresses while the change is under way, then a record of it: when, who made it, our reference, and the two addresses' domains | Legal obligation: correcting your data when you ask (UK GDPR Article 16). Legitimate interests: keeping a record so a disputed change can be settled. | The addresses: until the change is made, and at most 30 days. The record: 6 years, not removed when you delete your account. |
Payments
Paid subscriptions are purchased through the Apple App Store or Google Play. Your payment and card details are handled entirely by Apple or Google; we never see or store them. We receive confirmation of your subscription status through RevenueCat, our subscription management provider, so we can grant the right access tier.
Where the store asks a parent or guardian to approve a purchase made on an under-18's account (Apple’s Ask to Buy or Google’s Family Link), the store runs that approval; we have no approval or payment step of our own for under-18s.
Retailer links and affiliate commission
When you tap through to buy from a retailer, that visit may carry an affiliate identifier so that we earn a commission if you make a purchase. This does not change the price you pay, and it does not affect which retailer we mark as having the best price. Once you leave Beaconry for a retailer's site, that retailer's own privacy policy applies to your visit.
Retailer-click records after you delete your account
The retailer-click records we make now do not say who clicked, so deleting your account has nothing to remove from them. Older records, made before we stopped storing who clicked, can carry your account, the app-installation identifier, your subscription tier and the full retailer address. When you delete your account we remove all of those, leaving only which listing and retailer were clicked, when, from which platform, and whether the link carried an affiliate identifier. What remains no longer identifies you on its own, but we do not claim it is anonymous. We keep click records to see what people actually click on, and to give retailers summary data through dashboards and reports in our retailer portal, which has not launched yet, on the basis of our legitimate interest in that, and each is deleted automatically about 395 days after the click. These records are not accounting records: they cannot be matched to a sale, and the affiliate network's commission statements are our accounting record.
Product analytics
To understand which features are worth building on, we send a small set of usage events to Amplitude, our product analytics provider. These cover things like a price alert being delivered or a tap through to a retailer, together with the subscription tier of the account involved.
Events are tied to a pseudonymous identifier we generate for your account, not to you by name. That identifier is still personal data: we can link it back to your account, so we treat it as information about you, not as anonymous. We do not send your email address to our analytics provider, and neither your password, your payment details, nor the device token used for push notifications form part of the event data. Where an event refers to a retailer, we send Amplitude only the retailer's domain, never the full web address you visited. Our own retailer-click records, described under "Data we collect" above, no longer keep the full address either.
When you delete your account we ask Amplitude to delete the events tied to your identifier; Amplitude carries the request out on its own schedule. We rely on our legitimate interest in understanding and improving the service for this processing, and you can object to it: see "Your right to object" below.
Our servers send events about an account only when we hold a record that you told us at sign-up that you are 18 or over. Accounts created before we kept this answer, or where it did not reach us, have no such record, so we do not send their events. That includes, for example, an account where you confirmed your email on a different device from the one you registered on, or that you registered in the mobile app before it sent that answer.
The mobile app also sends analytics to Amplitude itself, using Amplitude’s software, to Amplitude’s EU data centre. It does this only if you told the app on that device that you are 18 or over and you have not objected (see “Your right to object” below); it goes by that answer, not by the record our servers hold for your account. If you told it you are under 18, or it does not know your age, the app does not start Amplitude’s software at all.
What the app sends: the events it records as you use it; when each app session starts and ends, which we use to count how many people use the app each day and how many come back; a random identifier that Amplitude’s software creates for that installation; your account’s pseudonymous identifier, if you are signed in; and the app version, the operating system and its version, the platform, the device model and the device’s language.
The installation identifier is not a hardware or advertising identifier, and reinstalling the app gives you a new one. One exception: on an iPhone or iPad that already ran an earlier version of the app, Amplitude’s software may still use the identifier Apple gives our apps on that device (the “identifier for vendor”), because it keeps the identifier it chose first. Otherwise the app does not send Amplitude the device’s advertising identifiers, its identifier for vendor, its mobile network or its location, and it does not ask Amplitude’s software to record which screens you view or what you tap.
Amplitude still receives the IP address your device connects from, as any internet service does. The app tells Amplitude’s software not to send the IP address or a city, region or country with events, but we have not yet confirmed that Amplitude does not work out an approximate location from the connection itself.
Amplitude’s software can also be set, from Amplitude’s own dashboard, to capture more than this, such as which screens you view. The app cannot block that setting yet, and we do not use it. On iPhone and iPad, Amplitude’s software also fetches its settings from, and sends its own diagnostic reports to, Amplitude servers in the United States, so those servers see your device’s IP address; the events themselves go to the EU.
The app does not yet clear your account’s pseudonymous identifier from Amplitude’s software when you sign out. Until it does, events the app sends from that installation after you sign out can still be linked to your account.
A tap through to a retailer from the mobile app can carry a random identifier the app creates for that installation. The app adds it only if you told it you are 18 or over and you have not objected to product analytics; if you told it you are under 18, or it does not know your age, it sends no identifier. Our own retailer-click records do not keep it. If you are signed in, we send Amplitude an event for the tap with the listing, the platform, whether the link carried an affiliate identifier, and the subscription tier and whether it is Lifetime Pro, if any, along with your account’s pseudonymous identifier and the installation identifier, if the app added it, so we can understand how people use the app. We do not send it if your account says you are under 18, if we do not know your age, or if you have objected to product analytics. If you are signed out, our servers do not send the installation identifier, or anything else about the tap, to Amplitude. The app’s own analytics records it on your device’s side instead, and only if you told the app you are 18 or over and have not objected. If you are signed in, or sign in later on that installation, Amplitude can link those events to your account’s pseudonymous identifier.
The app keeps this identifier on your device. It uses the same identifier to register your device for the push notifications you ask for, which is needed to deliver them. For its use in product analytics, we rely on the exception in the Privacy and Electronic Communications Regulations for collecting statistics about how a service is used so it can be improved, which does not need your consent as long as we tell you clearly and give you a simple, free way to object. Amplitude’s software also keeps its own random identifier on your device, described above, and we rely on the same exception for it. Whether or not you are signed in, you can object with the “Product analytics” switch in the app’s settings, or by emailing privacy@beaconry.co.
Who we share data with
We do not sell your personal data. We share it only with the service providers that help us run Beaconry, and only as far as they need it:
- Amazon Web Services: cloud hosting, our database, authentication (Amazon Cognito) and sending our email (Amazon SES). Sign-in is by email address and password, with optional authenticator-app multi-factor authentication. We do not currently offer sign-in with Apple, Google or any other third-party account.
- Apple (APNs) and Google (Firebase Cloud Messaging): delivering push notifications to your device. They receive your device token and the notification text.
- RevenueCat: subscription status management.
- Amplitude: product analytics covering how the service is used.
- Google (Firebase Crashlytics): crash reports from the mobile app for users of every age. When the app crashes or hits an error, it sends Google a report with technical details such as the device model, operating system and app version. We use it to keep the app stable and fix faults, not to profile anyone. We do not attach your date of birth or age band to a report. Each report holds the error message and where in the app’s code it happened, the device model, processor, operating system, language and region settings, free memory and storage, the app version, and two random identifiers for that installation that Firebase creates. Firebase also records when each app session starts, with a session identifier, the device model, the operating system, the mobile network’s country and operator codes, and one of those installation identifiers. The app adds no user identifier, custom keys or logs to a report, only a label for where in the app the error came from. An error message can include the address of a request the app was making, which can contain something you typed, such as a search. Google keeps crash reports and their identifiers for 90 days, as our processor under the Firebase Data Processing Terms.
- Apple and Google: payment processing for subscriptions.
- Cloudflare: routing our short links (such as bcnry.fyi addresses used on QR codes), which means it sees the IP address of anyone following one.
- ALTCHA: the proof-of-work check on our public forms is run by us, on our own servers. It sends nothing to a third party.
- Software in the mobile app: some of the providers above supply software
that runs in the app and sends data to them directly from your device:
- Amplitude, for product analytics, only if you told the app you are 18 or over and have not objected. “Product analytics” above describes what it sends.
- RevenueCat, which the app starts on every installation, signed in or not, to check subscriptions and handle purchases. On iPhone and iPad it sends RevenueCat the identifier for vendor with every request, with the device model, operating system version, app version, language settings and App Store country; on Android, the device’s make and model, operating system, language settings and Play Store country. The app gives RevenueCat your account’s pseudonymous identifier when you buy, restore or manage a subscription. The app does not yet sign out of RevenueCat when you sign out. Every purchase, restore or subscription-management request identifies whoever is signed in at that moment first, but until then the RevenueCat software on that installation stays linked to your account’s identifier, for example in the subscription details it keeps on the device and the requests it makes by itself.
- Google Firebase: Crashlytics, described above; Firebase Installations, which creates the random installation identifiers that Crashlytics and push notifications use; and Firebase Cloud Messaging, for push notifications. The app registers your device for push notifications only once you are signed in to an account whose plan includes them, and asks Firebase to delete that registration when you sign out. If that request fails, the app does not yet try it again, and a registration still in progress when you sign out can leave your device registered.
- Amazon Cognito, in London, for signing in. When you sign up, confirm your email, sign in or reset your password, the app also sends Cognito details of the device for security checks: on iPhone and iPad, the identifier for vendor, the device’s name and model, the operating system, language, screen size, time zone and app version; on Android, the device’s build details, language, screen size and app version.
- The app does not include Google Analytics for Firebase.
We may also disclose data where we are required to by law, or to protect our rights and the safety of our users.
International transfers
Some of our providers process data outside the UK. Where they do, we need a safeguard that gives your data equivalent protection.
| Provider | Where it processes data | Transfer safeguard |
|---|---|---|
| Amazon Web Services (hosting, database, authentication, email) | The UK (London). Access by Amazon's US parent company counts as a transfer. | UK International Data Transfer Addendum in AWS's DPA |
| Amplitude (product analytics) | The European Union (EU data residency). Amplitude's parent company is in the US. On iPhone and iPad, Amplitude’s software also contacts Amplitude servers in the US for its settings and diagnostics. | UK Extension to the EU-US Data Privacy Framework |
| RevenueCat (subscription status) | United States | UK International Data Transfer Addendum in RevenueCat's DPA |
| Apple (push delivery, payments, beta testing) | United States and other countries | Apple acts as its own controller for these services, and says its transfers rely on standard contractual clauses. |
| Google (push delivery, payments, crash diagnostics, beta testing) | United States and other countries | UK Extension to the EU-US Data Privacy Framework |
| Cloudflare (short links) | Global network | UK Extension to the EU-US Data Privacy Framework |
How long we keep your data
We keep personal data only as long as we need it for the purpose in the table above. In practice:
- Account data (email, preferences, beacons, subscription status): while your account is open, and erased when you delete it. If you do not sign in for 24 months, we delete your account.
- Server logs, which include IP addresses: 1 month in production.
- Push tokens: until you delete your account or the token stops working. The record of each push we send expires after 90 days.
- Notification history shown in the app: 13 months.
- Amplitude events: Event data is kept for 13 months from when it was recorded. When you delete your account we ask Amplitude to remove your pseudonymous profile and its events; Amplitude completes this on its own schedule. Until the app clears your identifier when you sign out, events it sends from that installation afterwards, including after you delete your account, can still carry your identifier, and a deletion request we have already made does not cover them.
- Crash reports: held by Google for 90 days.
- Backups: our database keeps point-in-time recovery backups for 35 days, so deleted data can remain in a backup until that backup expires.
- Retailer-click records: 395 days (about 13 months), then deleted automatically.
- Waitlist: deleted once we have told you sign-ups are open, or after 12 months, whichever comes first.
- Sign-in sessions: up to 7 days.
- Data downloads you request from your account: deleted after 1 day.
- Complaints: Kept for 6 years and not removed when you delete your account.
- Email address changes: A record of each change support makes for you (when, who made it, our reference, and the domains of the two addresses, never the addresses) is kept for 6 years and not removed when you delete your account.
Your rights
You have the right to access, correct, delete, restrict, or object to our use of your personal data, and to request a copy of it. You can delete your account at any time from within the app or your Account page, except while your account is suspended. If so, email support@beaconry.co, and we will review your request before acting on it. Our account deletion page explains how, and "What deleting your account does" below lists what happens to each kind of data.
- Changing your email address. You can't change your email address in the app or on the website yet. Email support@beaconry.co and we will change it for you. We send a code to the new address to check it's yours, and tell your old address when the change is asked for and again once it has changed. If we're putting your address back after a change you didn't make, we don't write to the address we're replacing.
- Portability. You can download a copy of your account data from your account page, in a structured, machine-readable file you can reuse elsewhere. It does not include retailer clicks: the records we make now do not say who clicked, and older records that can still carry your account are not yet part of the download. To ask for those, email privacy@beaconry.co.
- Withdrawing consent. Where we rely on your consent (for example the waitlist), you can withdraw it at any time by emailing privacy@beaconry.co. Withdrawing does not affect what we did before you withdrew.
- Do you have to give us your data? You need an account to set price alerts, and an account needs an email address, so providing it is a requirement of the contract. You can browse prices without an account and without giving us any of it.
- Automated decisions. We do not make decisions about you based solely on automated processing that have legal or similarly significant effects.
To exercise any right, or if you would prefer we handle a deletion for you, email privacy@beaconry.co.
What deleting your account does
Erased
- Your account, including all sign-in identities, such as your Cognito login.
- The price-alert beacons you have set.
- Your notification history and delivery records.
- Saved devices and push notification tokens.
- Your notification preferences.
- Whether you told us you are under 18.
- Any waitlist entry associated with your account.
De-linked from you, but still personal data
Your older retailer-click records, made before we stopped storing who clicked. We remove your account, the app-installation identifier, your subscription tier and the full retailer address, leaving only which listing and retailer were clicked, when, from which platform, and whether the link carried an affiliate identifier. What remains no longer identifies you on its own, but we do not claim it is anonymous. Each is deleted automatically about 395 days (13 months) after the click.
Retailer-click records we make now do not say who clicked, so there is nothing in them to remove.
Kept because the law or your erasure needs it
- A data protection complaint you made. It is kept in a separate register for 6 years, because the law requires us to have a complaints procedure, and is not removed when you delete your account.
- The record of the version of the Terms you agreed to and the version of this policy you were shown, and when. We keep it for 6 years after your account is deleted, so we can show what you agreed to if there is ever a legal claim.
- A record that your account was erased: only its random account identifier and the date. It lets us recognise and ignore later notices about a subscription that is still active in the store, rather than recreating your account. We keep it for 6 years after your account is deleted, the same period as complaints.
- A record of each change support made to your email address: when, who made it, our reference, and the domains of the two addresses, never the addresses. It is kept for 6 years and is not removed when you delete your account, so a disputed change can be settled.
Still in backups or with our providers for a while
- Database backups: our database keeps point-in-time recovery backups for 35 days, so deleted data can remain in a backup until that backup expires.
- Server logs: kept for 1 month in production. They carry your random account identifier, never your email address in readable form, and age out rather than being edited.
- Database audit logs: a record of each change to our database, kept for 365 days. It names which record changed, not what it held. For your account that means its random account identifier and your sign-in identifier; for a waitlist entry, it means your email address. These age out rather than being edited.
- Amplitude (product analytics): we ask Amplitude to delete the events tied to your account, and Amplitude completes that on its own schedule. Events tied only to a random identifier for an app installation, not to your account, may not be reached by that request: the mobile app’s own events on an installation before you first signed in there, and the retailer taps our servers record from the app while you are not signed in. The app does not yet clear your account identifier when you sign out, so events it sends from that installation after you sign out, including after you delete your account, can still carry your identifier, and the request we have already made does not cover them. Amplitude keeps event data for 13 months.
- RevenueCat (in-app subscriptions): we ask RevenueCat to delete your subscriber record. RevenueCat may keep some data under its own retention policy. Deleting your account does not cancel an active App Store or Google Play subscription, and the store may keep renewing it. If it does, RevenueCat can create a new record for it, so cancel the subscription in your store account.
- Until Amplitude or RevenueCat accepts our request, we keep a note that we asked, holding only your random account identifier, which provider it is, and when we asked. We remove it once the provider accepts.
Your right to object
You can object at any time to processing we carry out on the basis of our legitimate interests, which means product analytics, security logging and retailer-click logging.
Product analytics: switch off “Product analytics” in your account settings on the Beaconry website, or in the mobile app under Settings, then Privacy. Signed in, the two switches are the same account setting: our servers stop sending events about your account to Amplitude, and the app stops sending its own analytics and stops adding its installation identifier to your retailer taps. While you are signed in, the app sends none of its own events until it has confirmed that your account allows them, or if it cannot read your setting. Signed out, the app’s switch is saved on that device and applies whenever no one is signed in on it. Neither setting is copied to the other when you sign in or out. The app’s switch is on unless you turn it off on that device, so until the app clears your identifier when you sign out, events it sends while you are signed out can still carry your account’s identifier even if you objected on your account. If you switch it off in the app, the app’s own events stop straight away. Whenever the app stops sending its own events while it is open, because you switch it off, sign in to an account that has objected or whose setting it has not yet read, object on the website, or sign out on a device whose switch is off, Amplitude’s software, if it was already running, can still send the session start and end events, and any events it was still holding, until the app is next closed and reopened. If you object on the website while the app is open, the app follows it the next time it reloads your account details, and at the latest the next time it is started. You can also object by emailing privacy@beaconry.co. Anything else: email privacy@beaconry.co and tell us what you object to. We will stop unless we can show a compelling reason that overrides your interests.
Complaints
If you are unhappy with how we have handled your personal data, tell us using our data protection complaints form. We will acknowledge your complaint by email straight away and in any case within 30 days, look into it, and reply without undue delay. If you are still unhappy, you can complain to the Information Commissioner's Office (ICO) at ico.org.uk/make-a-complaint.
Security
We take reasonable technical and organisational measures to protect your data, including managed authentication and pseudonymisation of identifiers in our logs. No online service can be completely secure, but we work to keep your data safe.
Children
Beaconry is for people aged 13 and over, including junior members of model railway clubs. We do not knowingly collect personal data from anyone under 13, and if we learn we have, we will delete it. We do not collect product analytics about signed-in accounts where you told us at sign-up that you are under 18, or where we do not know your age. The mobile app adds no identifier to your retailer clicks unless you told it you are 18 or over. Your age is what you told us; we do not verify it.
For under-18s, this is where we stand today against the ICO’s Children’s Code. We collect only what we need to run the service, and we do not keep your date of birth. The mobile app sends no product analytics for anyone under 18, or whose age it does not know. We show no advertising, we do not sell personal data, and we do not use anyone’s data, whatever their age, to build advertising or marketing profiles. Beaconry has no public profiles, messaging or social features. The mobile app adds a random identifier for your app installation to retailer clicks only if you told it you are 18 or over, signed in or not, so no such identifier is sent for anyone under 18 or whose age it does not know. We send no marketing messages, to anyone. For under-18s, Beaconry starts at its most private settings: no product analytics and no device identifier on clicks, with nothing to switch off.
Changes to this policy
We may update this policy from time to time. When we do, we will change the date at the top of this page and, where the change is significant, tell you through the service.
Contact
For any privacy or data protection question, contact us at privacy@beaconry.co.