Legal
Last updated: June 10, 2026
DeskGM collects the minimum data needed to provide account access, personalize baseball intelligence, operate notifications, improve reliability, and protect the service. This policy explains what we store, why we store it, and how you can request deletion.
When you create or use an account, DeskGM may store your email address, display name if you provide one, authentication provider, Supabase user ID, session metadata, favorite team, saved preferences, notification settings, privacy choices, and last login or session activity.
We use this information to sign you in, secure your account, remember your team and product preferences, support account recovery, and keep your experience consistent across devices.
DeskGM may collect anonymous or pseudonymous usage information to improve the product, such as screens visited, features used, session activity, performance signals, and error diagnostics.
Analytics are not used to collect passwords, OAuth tokens, private messages, payment details, or sensitive personal information. Optional analytics only run when enabled and allowed by your privacy choice.
If you opt in to notifications, we may store notification preferences and push notification token references so we can send requested alerts, daily briefings, roster movement, injury updates, or other baseball intelligence notifications.
You can change notification preferences in account settings. Push identifiers are removed or disconnected when you opt out where supported or delete your account.
DeskGM uses AI-assisted analysis to generate briefings, summaries, recommendations, and explanations. AI requests are intended to use baseball context and product inputs, not passwords, OAuth tokens, or unnecessary personal information.
Saved AI-generated content may remain in your account until you delete it, delete your account, or a retention policy removes it.
Examples: Supabase user ID, email address, display name if provided, authentication provider, session metadata, last login signals
Purpose: create accounts, keep sessions secure, support account recovery, and enforce user/admin access
Storage: Supabase Auth and Supabase Postgres. Service-role access is server-only.
Retention: kept while the account is active; removed through in-app deletion unless legally required to retain a minimal request/audit record
Examples: favorite team, saved briefings, saved preferences, notification preferences, privacy choices
Purpose: personalize the app and honor user choices
Storage: Supabase Postgres tables protected by RLS and server-side authorization checks
Retention: kept until changed, withdrawn, expired by retention policy, or deleted with the account
Examples: screens visited, features used, session activity, API health, error metadata, performance signals, request metadata
Purpose: measure reliability, diagnose bugs, prevent abuse, and keep the service secure
Storage: Vercel/Sentry/internal logs only when enabled; payloads must be scrubbed before logging
Retention: short operational window only; no emails, OAuth codes, tokens, or raw provider payloads in logs
Examples: push subscription IDs, device push token references, notification opt-in flags
Purpose: send requested alerts and daily briefings
Storage: Supabase and Apple/Google/OneSignal push infrastructure when enabled
Retention: kept only while push is enabled; removed on opt-out, disconnect, or account deletion
Examples: AI-assisted analysis, AI-generated briefings, summaries, recommendations, explanations, saved output, redacted prompt previews
Purpose: provide explainable baseball insights and improve user-requested recommendations
Storage: Supabase for saved output; transient AI provider requests only after guardrails sanitize inputs
Retention: kept only while useful for the feature; deleted on account deletion or AI history deletion
Examples: provider ID, league/team IDs, read-only roster/standings cache
Purpose: future fantasy decision support after explicit opt-in
Storage: not enabled for broad beta; future provider tokens must be encrypted server-side
Retention: cache expires automatically and is removed on disconnect or account deletion
| Field | Classification | Store? | Purpose |
|---|---|---|---|
| auth.users.id / profiles.id | Internal identifier | Yes | Primary account key and row ownership |
| profiles.email | PII | Yes | Authentication, account support, privacy request verification |
| profiles.display_name | PII optional | Optional | Friendly account display; never required for core use |
| profiles.favorite_team | Non-sensitive preference | Yes | Personalize baseball content |
| privacy_consents.*_opt_in | Consent record | Yes | Honor and prove privacy choices |
| privacy_requests.email | PII | Yes | Verify and respond to privacy requests |
| push_subscriptions.token_hash / provider id | PII-linked | Yes, protected | Send requested push notifications |
| ai_history.prompt_preview | Potential PII | Strictly controlled | Debug AI privacy without storing raw prompts |
| fantasy_connections.provider_account_id | PII-linked | Later | Future read-only fantasy integration after explicit opt-in |
| fantasy_connections.oauth_token_ciphertext | Secret | Avoid unless required; encrypt | Future provider refresh only if no safer option exists |
| birthdate/address/phone/payment/children data | Sensitive or unnecessary | No | Not required for DeskGM beta |
| logs | Potential PII | Redacted only | Security and diagnostics without raw identifiers or secrets |
Database/Auth: Supabase. Region: Set DATA_REGION in production to the exact Supabase project region.
Hosting: Vercel. Region: Vercel-managed serverless region unless pinned in project settings.
Object storage: Supabase Storage if object storage is enabled
Analytics/monitoring: Vercel Analytics/Speed Insights; Sentry only when configured
DeskGM uses essential cookies or local storage for sign-in, preferences, security, and app operation. Optional analytics may collect usage and performance information, such as screens visited, features used, and session activity, to improve reliability and product decisions. In regions that require consent for non-essential analytics cookies, analytics should be disabled until consent is captured.
Current optional analytics choice: not set
You can request account deletion from the Privacy Center, the account settings page, the privacy request form, or by contacting [email protected]. Account deletion removes app-owned profile data, saved preferences, saved briefings, notification subscriptions, privacy choices, AI history, and related user records where technically and legally possible.
Some minimal records may be retained if required for security, fraud prevention, legal compliance, or to document that a deletion request was completed. Depending on your location, including the EU/UK or California, you may request access, correction, deletion, export, objection to processing, or restriction of processing.
Privacy questions or deletion requests can be sent to [email protected].