Gameday Pulse Privacy Policy

Last updated: October 21, 2026

About this policy

This policy describes how Gameday Pulse handles information. “We,” “us,” and “our” mean Chase Friedman, the developer of Gameday Pulse. For support or privacy requests, contact chase@sudokuhero.app.

Release-specific features: The upcoming ad-free update removes advertising, advertising consent and tracking prompts, and the Remove Ads purchase. Until that update is installed, earlier builds may retain those features as described below. Publishing this policy does not update an installed app. Basic aggregate statistics and optional detailed Amplitude analytics remain: basic statistics defaults on with a notice and an off switch; detailed analytics begins only after you allow it. Existing choices to turn all analytics off are respected. Yahoo integration remains unreleased, and Sentry crash reporting is not integrated.

Fantasy leagues and provider connections

Gameday Pulse processes fantasy-league information such as league and team identifiers, team names, rosters, matchups, standings, player statistics, scores, and available projections. It uses this information to display your selected leagues, follow matchups, and generate scoring updates and animations. You do not need a separate Gameday Pulse account. The built-in sample league uses simulated data and can be explored without connecting a personal fantasy account.

ESPN

When you sign in through the app’s embedded browser, your password is entered on ESPN’s website. The app reads the ESPN session cookies needed to access private leagues, including SWID and espn_s2, and saves connection information using secure storage on native devices. Private ESPN score requests are made directly from the native app to ESPN. The embedded sign-in browser also maintains its own session storage. Public leagues can be accessed without a private-league sign-in.

Sleeper and public sports data

Sleeper connections use a league identifier, league link, or public username lookup. They do not require a Sleeper password. League and player information is requested from Sleeper’s public services. Public ESPN services also supply NFL game context and related information. Providers may receive technical request information, including your IP address, when the app or embedded browser connects to them. Their own privacy policies apply to information they collect.

Optional browser-preview helper

The optional computer helper for browser previews reads ESPN data on the computer running it and sends league information to paired viewers. Private ESPN session values are used by that helper rather than sent to viewers. This helper is separate from the native phone connection. Its form-entered sessions are held in memory and are cleared when the helper restarts; manually configured credentials are controlled by the person running the helper.

Information stored on your device

The app stores league selections, team and watch preferences, local scoring and notification history, read receipts, and replay-related state on your device. Native connection credentials use secure device storage. Browser previews use browser storage, with connection credentials held in session storage. The operating system may include some app data in backups according to your settings.

Diagnostics and support

The optional live-test log records technical timing and error information, scoring changes, player names, roster membership, and animation events. It is stored locally and can persist when you reopen the app. Recording this log does not automatically upload it. If you choose to share a log, the recipient receives the exported information. These logs are not described as anonymous.

If you email us or send a diagnostic report, we receive your email address and the information you choose to provide. We use correspondence to respond, troubleshoot, and handle privacy requests. Email is processed by the services used to send and receive it. Please do not send passwords, provider session cookies, or connection tokens.

Planned Yahoo integration

Yahoo integration is not yet released. Its planned design uses Yahoo sign-in and a Cloudflare-hosted service to obtain read-only fantasy access, handle authorization tokens, and retrieve league information. Before introducing it, we will update this policy to describe the actual data processed, server storage and retention, disconnect behavior, and provider choices. No Yahoo functionality or current Yahoo collection is implied by this notice.

Advertising removal and earlier builds

The upcoming ad-free update contains no Google Mobile Ads SDK, banner requests, advertising identifiers, advertising consent flow or advertising tracking prompt. All app features are available without a Remove Ads purchase, and this update does not query purchase entitlements or send new purchase or advertising analytics. This change does not stop the separate usage analytics described below or delete information previously received by a service.

Earlier builds that include Google AdMob may still display banners and process IP addresses, approximate location, device and app identifiers, ad interactions, diagnostics and consent choices through Google and its partners. Those builds use Google's consent flow and, where applicable, Apple's tracking permission; limited or non-personalized ads may still process data. Their Remove Ads purchase is processed by Apple, with entitlement information checked and cached by the app. We do not receive payment card details. Detailed analytics in those builds, when allowed, may include purchase offers, attempts and outcomes, product and offered price/currency, restore outcomes, and aggregate banner counts. Installing the ad-free update stops these app integrations; it does not erase historical provider records. Contact us for questions about prior purchases or data, and use provider privacy controls where applicable.

Basic usage statistics and your right to object

In the release with basic statistics, this feature is on by default for new installations. A prominent notice explains it before collection starts. You can turn it off in that notice or at any time using “Basic usage statistics” in Settings > Privacy, free of charge and without losing any app features. Privacy is at the bottom of Settings and starts collapsed; tap its heading to open the section and view the controls. If you previously turned all analytics off, basic statistics remains off unless you change that choice. Detailed analytics has a separate choice. Basic collection remains disabled in builds where the aggregation service is not configured.

Basic statistics is used solely to understand and improve the app: broad screen visits, whole minutes spent on generic screens, sample-league and player-stat screen opens, game selection and sample replay-control counts, and fixed technical error counts. It excludes purchase and advertising data, notification activity, fantasy details, installation or session identifiers, provider names, app/device metadata, and individual event histories.

The app combines these actions into integer counters in memory. It sends only those counters to our Cloudflare-hosted aggregation service, which immediately adds them into app-wide daily totals. The service does not store individual submissions or client IP addresses, and application request logging is disabled. Cloudflare still processes network information, including IP addresses, to deliver and protect its service. Client IP addresses and request headers are not forwarded to Amplitude. No installation identifier is created or sent by this basic path.

Amplitude receives only daily totals using a constant identifier for the combined dataset, never a person or device. Small counter totals with fewer than 20 contributing reports are omitted; this is a report threshold, not a count of distinct people. We do not join these totals to detailed analytics, create individual profiles, make decisions about individuals, or use them for advertising. Counts are approximate and do not measure unique users.

We rely on the UK statistical-purposes exception for this limited service-improvement use. Where transient processing involves personal data, our intended lawful basis is our legitimate interest in improving app usability and reliability, balanced against your privacy through minimization, immediate aggregation and the right to object. Turning basic statistics off clears unsent counters, stops further collection and cancels outstanding requests where possible. Already combined totals cannot be located or deleted by person. We keep your choice and a local upload budget on the device, but do not persist a basic activity history. Pending aggregate buckets are removed after export or within three days; platform backups may retain aggregate snapshots under Cloudflare’s retention arrangements. Amplitude retains combined statistics under our service arrangements. Cloudflare and Amplitude may process information outside your country; their privacy notices describe international processing and safeguards.

Optional detailed Amplitude analytics

Detailed analytics is off until you choose “Allow detailed analytics.” You can decline and use the app, or change “Share detailed analytics” in Settings > Privacy at any time. We use Amplitude to understand app usage and improve features and reliability. This choice is independent of basic usage statistics.

If you opt in, we send a randomly generated installation ID, session identifiers and timestamps; app version and build, iOS version and phone/tablet category; generic screen visits and active time; sample-league use; provider connection attempts and outcomes; league switches and disconnects; matchup pinning and player-stat screen opens; game selection counts and sample replay controls; selected animation, character-style, haptic and keep-awake settings; and a small set of fixed technical error categories.

Analytics does not include names, email addresses, fantasy account, league, team, player or game identifiers, rosters, scores, provider credentials, cookies, purchase receipts, payment details, typed text, raw error messages, precise location, accessibility settings or notification activity. We do not use Amplitude session recordings, screenshots, automatic interaction capture, advertising IDs or Apple’s vendor ID. The installation ID is pseudonymous, not a promise of complete anonymity. It is not shared with advertising providers or used to link activity across our apps.

We send only explicitly selected events to Amplitude’s US ingestion service. IP addresses and location fields are omitted from analytics event payloads, and we do not request IP-based location enrichment. As with other internet services, Amplitude’s infrastructure receives network information such as the originating IP address when handling a connection. Amplitude may process data outside your country, including in the United States; its privacy notice describes its processing and international-transfer safeguards.

Turning detailed analytics off stops new detailed collection, discards unsent detailed events and cancels outstanding uploads where possible. A request already received by Amplitude cannot be recalled. Unsent events are held only in memory, in a bounded queue, and expire after five minutes; closing the app can discard them sooner. We retain your choice and random ID locally so the preference survives restarting the app and you can identify previously sent data in a privacy request. The basic-statistics switch is separate. Turning detailed analytics off or uninstalling the app does not automatically delete previously uploaded records. To request access or deletion, email us and include the analytics ID shown in Settings > Privacy before clearing app data. Amplitude records are retained under our service arrangements until deleted or expired; we use them only for the purposes described here. No Sentry crash-reporting integration is included.

Retention, deletion, and security

Local information remains until removed, replaced, or cleared through available app or device controls. Disconnect controls remove the saved connection they manage. The native ESPN session-clearing flow deletes its saved session and clears the app’s embedded ESPN browser session; it does not sign you out of Safari, Chrome, or your ESPN account elsewhere.

Secure storage on iOS uses the Keychain and may survive uninstalling the app. Do not rely on uninstalling alone to remove every credential. Use the app’s disconnect controls and your provider’s account or session controls where appropriate. Device backups may retain copies separately.

Removing local data or logs does not delete copies you previously shared, support correspondence, or records held by fantasy providers or other services. We retain correspondence as needed to respond and handle related requests. Provider records and retention are governed by their policies and applicable arrangements. No method of storage or transmission can be guaranteed completely secure.

Privacy requests

Depending on your location, you may have rights concerning personal information, including access, correction, deletion, restriction, or objection to processing. Email chase@sudokuhero.app with requests concerning information held by us. We may need information to locate the relevant records and verify your request. For information controlled by ESPN, Sleeper, or another provider, use that provider’s privacy controls or request channels. You may also contact your local data protection authority.

Provider policies and this website

This policy website is hosted on GitHub Pages. We have not added website analytics or advertising scripts to this page. GitHub may process visitor IP addresses and technical request information to operate and secure hosting. External websites and services have their own privacy practices.

Changes

We may update this policy as the app or its services change. Updates will appear on this page with a revised date. The planned services above will be described according to their actual implementation when introduced.