Home

BeefedUp

Privacy Policy

Version: July 30, 2026

This policy explains what BeefedUp collects, why it is used, which providers process it, how long it is kept, and the choices available to you. It applies to the BeefedUp mobile and web app, support, and related services.

1. Data We Collect

Account and profile

If you choose Sign in with Apple, Apple provides an account identifier and may provide your name and email the first time. If you choose Hide My Email, BeefedUp receives and uses Apple's private relay email address instead of your personal address.

Fantasy gameplay and purchases

Apple App Store and Google Play process supported mobile purchases. Xsolla processes supported web purchases as the merchant of record. BeefedUp does not receive payment-card numbers. Money collection for league entry fees, cash wagers, pots, or escrow is disabled in public releases.

Messages, social content, and media

BEEF AI

When you choose BEEF AI, the question and bounded fantasy context needed to answer it are sent for the current request. Context can include rosters, player results, scoring settings, week, projections, injuries, and matchups. BeefedUp does not save BEEF AI question text or response history to your account during ordinary use. If you explicitly report an AI response, the reported question, answer, reason, request identifier, and limited request context are saved in the moderation report so authorized reviewers can investigate it. Operational records can otherwise include user ID, feature context, provider/model, timing, status, and token totals without the question or answer text.

Support

Support requests can include category, subject, description, reply email, selected league, and bounded diagnostics such as app version, build, platform, OS version, device model/type, locale, time zone, and relevant purchase identifiers or status. We hash network-address information for abuse rate-limiting. Do not send passwords, sign-in codes, unrelated private messages, or payment-card information.

App activity, advertising, and diagnostics

The app keeps bounded device caches so recently viewed pages can open quickly. Account-bound roster, league, feed, draft, outbox, and message state is scoped to the signed-in account, encrypted at rest in the native app, and purged on sign-out or account deletion. Browser copies expire after no more than 24 hours and use the same account purge. Public player, projection, score, and schedule caches are not account data and can remain after sign-out.

2. How We Use Data

BeefedUp does not sell personal information for money.

3. Providers and Disclosures

Data is disclosed to providers only as needed for the functions described here, subject to provider terms and configuration:

Some public or league-scoped content is disclosed to the other users you choose to interact with. Reports can be disclosed to authorized moderators.

4. Advertising and Tracking Choices

Where required, BeefedUp gathers advertising consent before initializing ads and provides advertising privacy choices. Public iOS store builds keep AdMob ads disabled and delay native app measurement unless and until the applicable consent and disclosure requirements are met. On Android, AdMob does not initialize until an eligible account age category is available. Accounts in the 13–17 category receive Google's teen age-restricted and under-age-of-consent treatment; Android ad requests remain non-personalized. Eligible browser users may receive AdSense ads according to their consent and Google advertising settings. Personalized, non-personalized, and limited advertising can still involve cookies or local storage, identifiers, measurement, fraud prevention, and contextual advertising.

KLIPY GIF search is optional and off for each account until the user confirms they are 18 or older and accepts an in-app disclosure. That choice is saved to the BeefedUp account and remains active across sign-out, reinstall, and devices until the user turns it off. On iOS, BeefedUp also requests App Tracking Transparency permission before contacting KLIPY; if permission is denied, KLIPY remains off. On other platforms, the in-app disclosure remains required. You can stop future KLIPY requests at any time in Profile, Settings, Account actions, KLIPY GIF search. BeefedUp remains usable without KLIPY.

5. Retention

Retention depends on the record and the reason it is needed:

We may retain limited security, fraud, moderation, transaction, legal, or dispute records longer where reasonably required. Retention rules may pause for a legal hold.

6. Account and Data Deletion

Delete your account in Profile, Settings, Delete Account or follow the web process at Delete Account. Valid verified requests are actioned within 30 days.

Deletion removes or overwrites profile data, authored messages and social content, memberships, push data, support records in the application database, covered uploaded files, and the account link on retained Xsolla event or subscription records. It requests deletion of the identified RevenueCat customer. It does not cancel an App Store, Google Play, or Xsolla subscription; cancel recurring billing before deleting your account.

Some gameplay, scoring, draft, transaction, security, and audit history can remain in de-identified form as “Deleted User” to preserve league integrity, prevent fraud, resolve disputes, or meet legal obligations. Account deletion erases the account's keyed, pseudonymous raw-error archive prefix; deduplicated diagnostic summaries can remain unlinked until their 30-day expiration. Provider and support-mailbox copies can follow separate retention schedules. BeefedUp does not give KLIPY an account ID, so BeefedUp account deletion cannot identify or automatically erase KLIPY records associated only with network or device information; use KLIPY's privacy-request process or ask BeefedUp support for help. Cleanup steps are retried during deletion; if a storage or Apple revocation step still fails after the account is disabled, the deletion result includes a cleanup warning so you can request support follow-up.

7. Access, Correction, Export, and Specific Deletion

Use Profile, Settings, Privacy & data choices or visit Privacy & Data Requests to request:

We may verify account control and redact another person's data, security-sensitive material, provider-only records, or information we must retain. We generally respond to valid requests within 30 days, subject to applicable law.

8. Email and Push Choices

BeefedUp currently sends authentication, security, purchase-support, and support-reply email rather than marketing newsletters. Transactional messages do not include a marketing unsubscribe. If marketing email is introduced, BeefedUp will add the required consent and unsubscribe controls first.

Push notifications can be disabled globally, by category, and for supported league events in Settings. Disabling push suppresses delivery but may not immediately delete the token; tokens are removed or deactivated on sign-out, invalidation, inactivity cleanup, or account deletion.

9. Age Eligibility

BeefedUp is intended for people age 13 and older. Account creation uses a neutral, blank birthday entry. The app checks that entry on the device and does not transmit or retain the exact birthday. People who are not eligible cannot create or continue with a BeefedUp account. Only the resulting 13–17 or 18+ category is stored so BeefedUp can enforce age eligibility and apply age-appropriate privacy and advertising treatment. If we learn that an account belongs to a child under 13, contact us so we can investigate and delete the account as appropriate.

KLIPY GIF search is separately limited to people who confirm they are 18 or older because KLIPY states that users under 18 may use its service only with parent or guardian involvement. Users who do not complete that confirmation can continue using the rest of BeefedUp.

10. Security and International Processing

We use access controls, encryption in transit, native encryption for account-bound device caches, row-level authorization, rate limits, audit records, and account-security measures designed to protect data. No system is completely secure. Providers may process data in the United States or other countries where they operate, subject to applicable safeguards.

11. Changes

We may update this policy. Material changes will be identified by a new version date and, where appropriate, an in-app notice or renewed acknowledgment.

12. Contact

Privacy requests:

General support: