Account And Data Deletion

Last updated: September 7, 2026

Choose whether to delete selected data while keeping your Today's Brief account, or delete your account and associated data. Support contact: ppltech26@gmail.com.

Delete Data Without Deleting Your Account

You can request deletion of selected data while keeping your Today's Brief account. Email Request data deletion — keep my account or write directly to ppltech26@gmail.com. You do not need to reinstall the app to submit a request.

  1. State that you want to keep your account open.
  2. Identify the data you want deleted, such as a feedback submission.
  3. Include your sign-in email or phone number and any available Support ID from Settings.

Do not send your password, one-time verification codes, or payment-card details.

Supported Data And Controls

What Stays And What Happens Next

Your account, sign-in details, subscription status, and data outside the confirmed request remain. Removing a task, saved article, or saved quote in the app can retain its content in server-side deletion records; it is not a guarantee of permanent erasure. Describe any further erasure request in your email so support can assess its scope.

We may ask for ownership verification before acting. Support will confirm the supported scope, expected completion time, and any retention exceptions, and notify you of the outcome. We cannot individually erase records that cannot be reliably matched or subtract your contribution from deidentified aggregate statistics. The retention periods and exceptions below still apply; not all user data is automatically deleted within 90 days.

How To Request Account Deletion

You can request account deletion inside the app:

  1. Open Settings.
  2. Open Account.
  3. Choose Delete account and follow the confirmation steps.

You can also request deletion by emailing ppltech26@gmail.com. Include the email or phone number used for sign-in and any Support ID shown in Settings so we can verify ownership.

The in-app control applies to a signed-in account. If you used Today's Brief without creating an account, there is no account profile to delete and the app does not currently provide an anonymous self-service deletion control. You may email support with the Support ID shown in Settings and ask us to assess whether any eligible device-linked server records can be reliably matched. Support may request additional verification or an additional identifier; only eligible records that can be reliably matched can be handled.

Android referral rewards are unavailable, but invitation tracking and statistics remain. Removing reward offers or progress displays does not automatically delete attribution, event, or reward-status records. Account-linked and device-linked records remain covered by the deletion scope and exceptions below. For details about Android reward availability, see Android Invitations And Referral Rewards.

What Account Deletion Removes

When applicable, deletion covers your Today's Brief account profile, the password hash and passkey public credentials, sessions and device links, Today's Brief's server-side push-token registrations, synced saved items, preferences, watchlists, custom Today Ideas topics, task records, saved commute place IDs and labels, account-associated reading or listening history, user-submitted feedback and content reports, referral attribution, event, and reward records linked to your account or to a device registered to your account, account-linked first-party analytics delivery records, and entitlement, trial, quota, rate-limit, or other usage-governance records that are not subject to a retention exception below.

Referral-code-only records that cannot be authoritatively linked to the deleting account are not deleted through account deletion. They may remain as pseudonymous attribution or reward records, subject to the retention and legal exceptions below.

What Account Deletion Does Not Delete

Removing Today's Brief's server-side push-token registration is not the same as deleting a Firebase Installation ID. Account deletion does not itself call the Firebase Installations deletion API, delete or rotate the SDK-managed device-local Firebase Installation ID, or erase Firebase crash or session records that already contain it. Clearing app data or uninstalling removes local app state; Firebase-controlled records remain subject to Firebase's documented identifier lifecycle and retention. Crashlytics records and associated identifiers follow the separate 90-day period described below.

What May Be Retained

Google Play controls and retains its billing records. We may retain a limited record when required or permitted for fraud or security prevention, billing or transaction reconciliation, tax or legal compliance, enforcement of one-time trial or abuse-prevention rules, or resolution of a dispute. Records retained under an exception are restricted to that purpose and are not kept as an active user profile.

For an already-used one-time trial, Today's Brief retains only keyed, one-way tokens for the former device and, when applicable, account identifiers, plus a consumed status. The tokens are used only to prevent the same device or account from receiving another one-time trial; they are not used to restore a profile, personalize content, advertise, or measure usage. Trial dates, entitlement details, Integrity verdicts, source, and timestamps are deleted.

Any historical account-linked first-party analytics delivery records are deleted with the account. New first-party delivery records deliberately contain no account ID, are browser- or installation-pseudonymous, and normally expire after 90 days, so they ordinarily cannot be located through account deletion. Today's Brief does not set Google Analytics User-ID or send a Today's Brief account identifier to Google Analytics. Pseudonymous events already processed by Google Analytics may therefore not be individually identifiable for account deletion. They remain subject to the configured two-month user and event retention period, with reset-on-new-activity disabled, and Google's applicable terms; that retention control does not remove standard aggregated reports. While optional Analytics is on, Crashlytics may copy recent Analytics screen or custom-event breadcrumbs and parameters—including a dedicated broad regional-cell parameter when that event occurred in the same session—into a crash, non-fatal, or ANR report. That copy follows Crashlytics' separate 90-day retention. Turning Analytics off stops future optional event collection but does not delete a breadcrumb already copied into a submitted Crashlytics report. Include the Support ID in a request so we can assess reliably matchable crash records.

Required deidentified feature-use rows and rolling aggregate statistics contain no account, device, request, IP, or location identifier and are not joined to account records. They therefore cannot be located or have one person's contribution subtracted through account deletion. Every administrator read excludes feature-use rows older than the exact rolling 90-day window even if database cleanup is delayed, and the database timestamp index is configured with a 90-day expiry. Persisted aggregate snapshots automatically retain only the current UTC date and the preceding 89 dates.

User-submitted feedback and content-report records are normally deleted 180 days after submission. Application-level request and security logs are normally deleted within 90 days. An applicable verified deletion request may remove a linked record earlier. We may retain a restricted record longer when necessary for an open security, abuse, billing, tax, legal, or dispute matter.

Verification

We may verify account ownership before deletion. Requests that cannot be matched to an account or verified may require additional information.