BreakPointBack to the court

Effective August 30, 2026

Privacy without guesswork.

BreakPoint collects only what it needs to keep your private tennis memory connected and help you find players in areas you deliberately choose.

What we collect

Account identifiers and email from your sign-in provider; your chosen username and, if you choose to add them, your first name and last initial; playing level; cities, postal area, courts, and availability you enter; private journal entries and rival notes; confirmed league results; support and safety reports; and limited reliability events. Profile images are stored privately.

What other players see

Your public playing card may show the username or first name and last initial you chose, approximate playing level, city, recognizable court, broad availability, public note, league honors, and qualifying community descriptors. With the combined display choice, players see your username until you accept a hit together or both add each other as rivals; those connected players can then see your first name and last initial. Exact postal codes, private journal entries, rival notes, travel-city lists, email, and match videos are not placed on another player’s feed.

How we use information

We use it to run your journal, sync devices, form local player results and leagues, prevent fraud and abuse, respond to support, and improve reliability. BreakPoint does not use GPS or background location.

No individual usage tracking

The beta does not create analytics IDs or individual activity histories, track return visits, record sessions, fingerprint devices, or run advertising trackers. There is no individual-tracking opt-in. We do not use private journals, rival notes, messages, names, locations, videos, or screenshots to analyze player behavior.

Measurement is limited to three site-wide counters: new session entries saved, setups completed, and hit requests accepted. Each counter stores only a month, an action category, and a total—no account, request, session, or device identifier and no event-level record. Earlier activity is not backfilled. The admin view displays completed months in bands of ten and hides small totals. It cannot show unique-player counts, retention, individual histories, or location breakdowns.

Essential service data

Accounts, journal synchronization, scheduling, league records, and safety controls still need their normal functional data. These are not repurposed for individual usage analysis. Our hosting and identity providers process technical information needed to deliver and protect the service. The beta’s browser event reporter and per-request Worker logging are disabled. Reports and screenshots are provided only when you deliberately submit them for support or safety review.

Sharing and service providers

Data is processed by infrastructure and identity providers needed to operate BreakPoint, including Cloudflare and Supabase. YouTube processes requests when you play an embedded video. Advertising scripts do not load in this beta.

Cookies and local storage

Essential cookies keep signed-in sessions secure. Device storage remembers display preferences, drafts, pending journal synchronization, and installation choices. These are functional storage, not analytics identifiers.

Retention, export, and deletion

You can export your account data or delete your account from Account & sync. Deletion erases private notes and assets and removes your playing card from discovery. Confirmed league results may remain in anonymized form to preserve the integrity of standings and awards. Safety records may be retained where reasonably necessary to protect the community or meet legal obligations.

Your choices

You can hide your playing card, edit your information, block players, report concerns, refuse advertising cookies, export data, and request deletion. For privacy questions email privacy@breakpoint.love.