Last updated: 9 May 2026

Privacy Policy

This policy explains what Beeline collects, how it is used, where it is stored, and how to request access or deletion. It is written for the hosted web app, the Android package, and the public leaderboard service.

UK-based developer First-party analytics only Android post-clear ads at launch Google Mobile Ads SDK in Android app Google AdSense for hosted web ads Manual deletion requests supported

Who we are

Beeline is published by Breyd. For privacy questions or data requests, contact beeline@breyd.com.

What we collect

Beeline is designed to keep data collection light. Most run history and board state stays on your device unless you post a completed, eligible run to the public leaderboard, Beeline sends limited first-party gameplay analytics, or the Android app requests the ad-delivery data needed to show one post-clear interstitial. The hosted web app may also request ad-delivery data when a desktop Daily sidebar ad is enabled.

Data stored on your device

Your local trail name and local player identifier.
Your saved run history, queued score posts, and cached daily boards.
Your run options and audio preference.

Data sent to our server

Generated trail names reserved through the alias service.
Public leaderboard submissions, including your trail name, player identifier, run date, seed, score, time, battery remaining, chest count, hint use, mode settings, and completion timestamp.
IP address and routine request metadata used for security, rate-limiting, and normal hosting operations.
First-party gameplay analytics events for session starts, session finishes, and answer reveals. These may include run date, mode settings, outcome, score, time, battery, chest count, platform, locale, time zone, and a coarse country hint.
Raw player and session identifiers are hashed server-side before they are stored in analytics tables.
In the Android app, Google Mobile Ads SDK may process device, advertising, and app-interaction identifiers needed to deliver, limit, and measure the single post-clear interstitial.
In the hosted web app, Google AdSense may process browser, device, ad-delivery, and interaction data when the desktop Daily sidebar ad is enabled.
Any information you include if you contact us by email.

How we use the data

To load and cache daily boards and restore your local progress.
To post completed runs to the public leaderboard.
To keep leaderboard entries tied to the same device profile.
To understand starts, clears, failures, and answer reveals over time.
To compare mode, platform, and coarse regional usage trends.
To deliver one full-screen ad after a completed run in the Android app.
To deliver a desktop sidebar ad in the hosted web Daily view.
To prevent abuse, replay spam, and obviously invalid score posts.
To operate, secure, and troubleshoot the hosted service.
To respond to support, privacy, or deletion requests.

Our legal bases

Contract or steps taken at your request: providing gameplay, serving daily boards, and processing optional leaderboard posts.
Legitimate interests: securing the service, preventing abuse, maintaining leaderboards, and responding to operational requests.
Legal obligations: retaining or disclosing information when lawfully required.

Sharing and processors

We do not sell personal data. Beeline's gameplay analytics is first-party and stored on our own backend. At launch, the Android app includes Google Mobile Ads SDK to show one full-screen ad after completed runs. The hosted web build can load Google AdSense for a desktop Daily sidebar ad when that rollout is enabled.

Render hosts the public Beeline web service and leaderboard database, including first-party analytics storage, as our infrastructure provider.
Google Mobile Ads may process device or advertising identifiers, app activity, and ad interaction data under Google's own terms and policies in order to serve and measure ads in the Android app.
Google AdSense may process browser, device, ad-delivery, and ad interaction data under Google's own terms and policies in order to serve and measure hosted web ads.
Google Play distributes the Android package and may process store, billing, or policy information under its own terms.
If we add third-party analytics providers or a later one-time No Ads purchase, we will update this policy and the in-app disclosures before rollout.

International transfers

Our hosting or infrastructure providers may process data outside the UK. Where that happens, we rely on the provider's contractual and technical safeguards and keep the data we send as limited as we can.

Retention

Local device data remains on your device until you clear it in the app, clear browser or app storage, or uninstall the app.
Public leaderboard entries and reserved trail names are retained while they are needed to operate the public daily archive, unless you ask us to delete them sooner.
First-party analytics events are retained for up to 365 days by default, subject to a configurable server retention window.
Routine server and security logs are retained only as long as needed for operational and abuse-prevention purposes, subject to provider defaults.
Support emails are retained for as long as needed to resolve the request and keep an audit trail of the outcome.

Your rights

Depending on your location and the circumstances, you may have rights to request access, correction, deletion, restriction, objection, or a copy of the data we hold about you.

To clear device-only data, use the in-app clear-runs control or remove the app's local storage.
To request removal of a public leaderboard entry, email beeline@breyd.com with your trail name and the approximate run date.
To ask about first-party analytics linked to your device profile, email the same address and include your trail name plus the rough dates involved.
If you are in the UK and are unhappy with our response, you can make a complaint to the Information Commissioner's Office.

Security

The hosted service is intended to run over HTTPS.
Leaderboard inputs are validated server-side before acceptance.
We use generated trail names to keep the public board tidy and reduce oversharing.
The Android ad hook stays limited to one post-clear interstitial after a completed run.
We keep the launch package free of third-party analytics SDKs.
Analytics storage uses hashed player and session identifiers instead of raw IDs.

Changes to this policy

We may update this policy when Beeline's features, providers, or legal obligations change. If the change materially affects how data is used, we will update the in-app link and the hosted policy before the new processing starts.