LedgerNorth LLC
Privacy policy
Effective October 29, 2026.
The Come Up is provided by LedgerNorth LLC, a Texas limited liability company. Contact support@thecomeup.app for support, privacy requests or legal notices.
Who the game is for
The Come Up is for adults aged 18 or older in the United States. The game is not directed to children. On each native app launch, we request an age category from the app store where supported. We use only the derived category and consent status to apply age protections, keep it in memory, and do not send it to our server or logs. When the store identifies a minor or a check is pending, accounts, online play, purchases, notifications and feedback uploads stay disabled; offline local play remains available. The website does not request native store age signals.
Accounts and local play
Local gameplay does not require an email account and can work offline. Online play and opted-in notifications can create or reuse a guest identity. Opening Account does not create a guest identity. When online, opening Locker or equipping earned items can create or reuse one to synchronize cosmetic access. A guest identity can also synchronize progression with our service; create an email account to recover that progress on another device. An installation with an existing account may refresh its sign-in and synchronize cosmetic access when the app opens, after the native age check allows those services. Firebase Authentication handles those guest identities and email/password accounts. Firebase receives sign-in credentials; our game API uses the resulting account identifier and authentication information rather than storing your password. Account identifiers and email, when available, can also be stored in online room and matchmaking records.
Local saves, settings, progression and cached account or cosmetic information are stored on your device. Web caches keep game assets and previously played music available offline. Online matches are stored by the service. The game's fictional money, credit and hospital events are not records of your real finances or health.
For existing approved gifts, the service stores a one-way hash of the approved email address until the verified account claims the grant. The claimed grant is linked to that account; account deletion requests removal of its linked gift record.
Online play, safety and service providers
Cloudflare Workers, Durable Objects and D1 run the API, matchmaking and stored games. Records include account identifiers, curated handles, chosen characters, room membership, moves, results, timestamps, fixed reactions, in-game phone journals and equipped cosmetics. Other players see the shared game presentation. There is no open public chat.
Blocks, reports and restrictions support safety and abuse handling. A report can contain text you enter, account identifiers, a match reference and timestamps. Support email includes the information you send us. Avoid unnecessary personal information in reports and support messages.
We do not sell personal data or share it for targeted advertising. The app does not display ads or operate an in-game behavioral analytics service. The providers described here receive information needed to operate their services and may maintain technical, operational or security records. That processing is not a claim that no information leaves the app.
We do not use browser Do Not Track signals to change the service because the game does not use cross-site tracking or targeted advertising.
Optional feedback
You can report a problem or send an idea without creating an account. We receive the type and message you choose to send, an optional reply email you enter, and technical context to investigate: app version and build, platform and operating system, screen size, render quality and performance, app settings, the current screen, and recent redacted errors. During a game, context can include the map and content versions, initial seed when known, revision, phase, active player, recent public events and online room/seat. If you are already signed in, the report can be linked to your account. We use this information for support, diagnosing failures, improving reliability and preventing abuse.
The feedback sheet includes a removable screenshot of the visible app by default, including the game board. Review the thumbnail before sending. We do not use this feature to access your photo library, camera or microphone. The optional reply email is not filled from your account. Avoid unnecessary personal information in your message or screenshot; guest reports can still identify you through content you choose to provide. Authentication secrets and other players' hidden game state are excluded from automatic context.
Offline reports are stored on your device and retried when a connection is available. Submitted reports and images are stored privately using Cloudflare and accessible to authorized support administrators. If owner email notification is enabled, a support mailbox receives a copy of the message and summary context with protected links. These reports are not public posts or advertising profiles.
Server feedback reports and their screenshots are retained for 180 days from creation, then deleted. Support notification emails are separate support-mail records retained for 24 months; removing a feedback report does not automatically remove its mailbox copy. Pending unsent reports remain on your device until delivered, expired or removed. Provider backup windows remain separate.
When you delete an account, we retain a one-way hashed account identifier and the deletion time to prevent outstanding sign-in tokens or concurrent requests from recreating feedback. This security record does not contain your report, reply email, screenshot or sign-in token. It falls under the approved three-year retention category for hashed deletion identifiers below.
Purchases
When you use purchases or restore ownership, Apple or Google handles store billing and RevenueCat helps validate purchases and restore ownership. The app checks availability and account eligibility before configuring RevenueCat for these flows. This processes account, product and transaction identifiers, ownership, timestamps, transfers and refunds. RevenueCat includes purchase analytics. Our app does not collect payment-card or bank-account fields. Availability depends on the platform and release.
Notifications and security
When you create an email account or request a password reset, Firebase Authentication handles the account and link generation. Our branded verification and password-reset routes can send those links through Cloudflare email delivery. If branded verification delivery is unavailable, the app can ask Firebase to send the verification email instead. We keep hashed account, recipient and IP-bucket values with timestamps and delivery status to limit abuse and prevent duplicate sends; these claims are eligible for cleanup after 48 hours. We do not store passwords or the email action links in these claims. Email providers may retain their own delivery records.
If you opt in to notifications, the app can register a device push token with the service. Firebase Cloud Messaging and Apple Push Notification service support delivery. Their SDKs can process installation identifiers, device metadata and connection information. We store your notification choice, your device's timezone offset and a one-way hash of an app-generated installation identifier. These support delivery timing and prevent duplicate daily reminders when a push token changes. Daily challenge notices use a 9 am–9 pm window in the last timezone offset your device reported; travel or daylight-saving changes are reflected when the app next refreshes that offset. You can decline or change notification permission in your device or browser settings. Permission and delivery availability are separate; the app shows when reminders are not yet available. Account deletion requests removal of the current device's messaging token and Firebase installation; other devices and provider backups may need separate cleanup.
Our service keeps operational logs to diagnose errors, deadlines and delivery failures. Logs can contain request and diagnostic metadata; newly collected API request logs redact URL query strings. Feedback, verification and reset rate-limit records use one-way hashed IP buckets rather than raw IP addresses; infrastructure providers may separately process connection IP addresses. We do not deliberately log passwords, sign-in tokens, raw age signals or payment credentials. Provider security and infrastructure logs follow provider retention rules.
The production app uses encrypted HTTPS/WSS connections and authenticated access for online operations. Keep your account credentials private. No service can promise absolute security.
Your choices and requests
Every user can request access, correction or deletion, regardless of their state. Use the in-app account-deletion option or email support. We verify an account request through its email address, or a confirmation code sent to that address; we do not ask for your password. We respond to these requests within 30 days. See Delete your account for the process and current limitations.
Retention and deletion
In-app deletion closes the online identity, removes account-linked game and feedback records, and requests Firebase authentication deletion. It requests RevenueCat customer deletion when that integration is configured; support handles provider cleanup that cannot be completed automatically. A failed step can be retried. Local saves, other players' retained match records, legitimate safety records and provider backups can remain as described below.
We use the following retention periods. Scheduled cleanup runs daily in bounded batches; outages or a failed dependent cleanup can delay completion until a retry.
- Server detailed finished-match history: 12 calendar months after the game ends. Lifetime Rep, levels, milestones, character progress and earned rewards stay with your profile until account deletion; expiry of a synced match does not reset them. Never-synced games older than 12 months remain on the original device and cannot be added to the account total.
- Feedback reports and screenshots: 180 days from creation.
- Safety reports: 24 months from creation. Account restrictions: 24 months from the last restriction change, for safety and abuse handling.
- Hashed account-deletion identifiers and opaque deletion markers: 3 years from deletion. Purchase-delivery replay records and hashed signed transaction-status witnesses: 3 years from receipt. These witnesses support ownership verification and prevent refunded transactions from being restored; they contain no raw account or order identifier or provider response. Hashed expired-game markers: 3 years from game-history expiry. These prevent delayed requests from recreating deleted data. Legacy deletion markers without a recorded date begin a conservative three-year period when next encountered.
- Notification delivery logs: 90 days from delivery. Queued notification records and per-device delivery results: 90 days from creation, with sending stopped at the notice's earlier expiry. A hashed installation identifier and daily-attempt date are retained for 90 days from the attempt to prevent duplicate daily notices, including after account deletion. These daily markers contain no account identifier or push token.
- Records we must keep for tax purposes: 7 years when purchases apply. Store providers keep their own transaction records under their policies.
- Purchase-restore request limits use a hashed account identifier and become eligible for cleanup after 1 day. Verification and password-reset request claims contain hashed identifiers and become eligible for cleanup after 48 hours; rate-limit counters expire by their window. These support abuse prevention and duplicate-send handling. Bounded daily cleanup may lag during outages or backlogs; account deletion also removes account-linked operational claims.
- Support mail, including feedback notification emails: 24 months.
- Provider backups: the providers' applicable rolling retention windows.