last updated 2026-07-28

Fast Break privacy policy

What this covers

This policy covers the Fast Break app on iOS and Android: what it collects, why it collects it, and who else sees it.

The Azera Labs website is separate and has its own policy. If you want to know what azeralabs.dev collects, read the site policy instead.

What Fast Break collects

This is the full list. Each entry says what the data is and why it exists.

Email address
Your account identity and how you sign in. Stored in Fast Break's account database.
Google or Apple account identifier
When you sign in with Google instead of an email address, Google gives Fast Break an account identifier, which is stored so your account can be matched to you the next time you open the app. Google sees the sign-in happen. Sign in with Apple isn't in the app yet; when it ships it works the same way, with Apple as the other party.
Device push token
The address a notification gets delivered to. It's stored alongside your account, and a push delivery service sends breaking-news notifications to it.
Team and league selections
The teams and leagues you follow, which is what decides the stories in your feed. Stored in Fast Break's account database.
Notification preferences and quiet hours
Your notification settings and the hours you don't want to be interrupted. They decide whether a notification may be sent and when. Stored in Fast Break's account database.
Saved articles, recently-read history, and interactions
What you save, what you've read lately, and how you interact with stories. This fills the saved and recently-read screens and shapes what the feed shows you. Stored in Fast Break's account database.
Device model, OS version, and locale
Used to format the app for your device, and included with crash reports so they can be understood in context.
Approximate location — country, region, city, and time zone
Worked out from the network address your requests arrive on, and attached to analytics events so it's possible to tell roughly where the app is being used. The address itself is discarded rather than stored. This is city-level at best and is never your precise location — Fast Break doesn't ask for or receive GPS.
Crash reports and stack traces
When Fast Break fails, the error and the stack trace go to Fast Break's crash reporting service so the cause can be found and fixed. Crash reports carry no personal information and no network address: the only thing tying one to you is the random account identifier described below.
Product analytics events
Ten events, and no others: starting and finishing onboarding, signing up, signing in, selecting teams, answering the notifications prompt, opening the app, viewing a story, refreshing the feed, and opening a push notification. They go to Fast Break's analytics service and answer which parts of the app get used.
What those events carry
The sport and league of a story, whether it was breaking, how many articles it drew from, and which screen you opened it from. Which sign-in method you used. How many teams you picked. Whether you allowed notifications. No message content, no search terms, and nothing you typed.
A random account identifier
Analytics and crash reports are tied to the random identifier your account already has, never to your email address or your name. Signing out unlinks it, so a shared device doesn't blend two people together.
Advertising identifiers
Only when advertising is enabled, and only if you agree to it. The identifier goes to Google's AdMob to deliver ads and measure them. Decline, and it isn't shared.

What Fast Break doesn't collect

None of this is collected:

If that ever changes, this page changes with it.

Advertising and tracking

Fast Break can show ads through Google AdMob. Ads sit behind a feature flag, so they may be switched off entirely. While they're off, no advertising identifier leaves your device.

When ads are shown on iOS, the system asks whether Fast Break may track you across other companies' apps and websites. That's Apple's App Tracking Transparency prompt, and the answer is yours. Decline it and your advertising identifier isn't shared with AdMob.

Declining costs you nothing. Every feature keeps working and no part of the app is held back.

Third parties

Fast Break relies on a few outside services, each doing one job and getting only the data it needs to do that job:

The specific companies behind the first four are available on request — email support@azeralabs.dev.

One thing worth stating plainly: Fast Break groups reports about the same event and writes a short summary of each story. That work runs on the server, on the text of published articles. No user data is sent to the language model — not your email, not your teams, not what you've read.

How long data is kept

Account data — your email, your teams, your settings, and what you've saved — is kept while the account exists. Delete the account and it goes with it.

Fixed retention periods for crash reports and analytics events aren't set yet. They'll be written into this section once they are, rather than left vague.

Your rights

You can:

Two pages do the work: privacy choices handles access, correction, and a copy of your data, and account deletion removes the account and the data attached to it.

The GDPR requires these rights in Europe and the CCPA requires them in California. Fast Break offers them to everyone, wherever you live, rather than checking your address first.

Children

Fast Break isn't directed at children under 13 and doesn't knowingly collect data from them. If you believe a child has given Fast Break personal information, email support@azeralabs.dev and it'll be deleted.

Changes to this policy

Changes get posted on this page, and the last updated date at the top moves with them. If a change affects what's collected or who receives it, this page says so rather than absorbing it quietly.

Contact

Questions about this policy, or about the data Fast Break holds on you: support@azeralabs.dev.

Azera Labs
Nashville, Tennessee