Privacy Policy

Plain-language overview. Midgame uses account, device, activity, subscription, notification, and sports-preference information to operate and improve the Service. We do not exchange personal information for money or use it for cross-context behavioral advertising. Optional website analytics remain off until you choose to allow them. This overview is not a substitute for the complete policy below.

This Privacy Policy explains how Midgame, Inc. (“Midgame,” “we,” “us,” or “our”) collects, uses, discloses, and retains personal information when you use the Midgame iOS or Android app, mid.game, or a related service that links to this policy (collectively, the “Service”). It also describes privacy choices and rights that may be available to you.

This policy is a notice of our practices; it is not a contract requiring you to surrender a privacy right. The Terms of Service govern use of the Service. If a feature provides a more specific privacy notice when information is collected, that notice also applies.

Midgame provides odds, sports data, analytics, and alerts for entertainment purposes only. That description does not reduce our obligations concerning your personal information, and accepting the Terms is not blanket consent to optional tracking or marketing.

#1. Scope and who is responsible

Midgame, Inc. is the business or controller responsible for personal information covered by this policy, except where another notice identifies a different responsible party.

This policy covers information handled by the Midgame app and website, including registered and guest accounts, support and contact communications, referrals, subscriptions, alerts, and website analytics. It does not govern an independent website, sportsbook, app store, authentication service, or other third party that processes information for its own purposes under its privacy notice.

The Service is operated from the United States. If you use it from another country, Section 12 explains international processing and transfer considerations.

#2. Information we collect

The information we collect depends on the features you use, the permissions you grant, your device, and whether you have an account or subscription. “Personal information” means information that identifies, relates to, describes, is reasonably capable of being associated with, or could reasonably be linked to a person or household, as defined by applicable law.

#Account and identity information

We may collect:

• name, display name, username, avatar, email address, phone number, and account identifiers;
• information supplied through Sign in with Apple, such as an Apple account subject identifier, relay or other email address, and name if Apple makes it available;
• phone number and verification status when phone authentication is used;
• guest-account and session identifiers; and
• authentication, recovery, session, and security records, and records of terms acceptance, such as the version and acceptance time where collected.

Midgame receives verification results from authentication providers. Do not send us a password or verification code except through the specific authentication interface that requests it.

#Age, state, and location information

We collect your date of birth and selected state or region to apply age requirements, configure the experience, support legal compliance, and help prevent misuse. Date of birth and location can be treated as sensitive personal information under some laws.

On supported iOS and Android versions, opening a country-code, state or region, or time-zone control may ask you to share your approximate location through the operating system. This is a one-time foreground request, not continuous or background tracking. Android requests coarse location only; iOS requests reduced accuracy by default. We use the result to suggest a country, region, or time zone. You can decline or later revoke permission in device settings. Country and state remain manually selectable. This feature does not determine whether any activity outside Midgame is lawful.

Like most internet services, our systems receive an IP address when a device connects. We may derive approximate country, region, city, coordinates, and time zone from that IP address for security, administration, service operation, and region-aware communications. If device-location permission is declined or a device result is unavailable, the app can use this connection-based location as a default. Denying device permission does not stop ordinary IP processing. IP-based location can be inaccurate, especially when using a VPN, and is separate from optional device-location permission. An unavailable lookup is not proof of your location.

The account-linked approximate-location snapshot can include country, region, city, time zone, the source of the result, permission outcome, and observation time. Device-derived coordinates are rounded for a transient time-zone lookup, not saved in that snapshot; it does not accept a street address. The request IP and separately inferred IP-location fields may also be saved to your user record. Authorized administrators can view these records for support, security, and account administration. A detected area remains distinct from your chosen home state and display time zone.

Android setup and returning-session refresh can automatically save a valid connection-derived time zone when needed, without a separate confirmation prompt; an existing valid selection is preserved. iOS time-zone changes remain subject to confirmation. Device-permission behavior depends on app version and prior permission choices.

#Preferences and feature configuration

We may collect sports and team selections, followed teams, alert rules, tracked or muted games, notification choices, Live Activity choices, language, time zone, quiet hours, responsible-use settings, cooling-off state, alert caps, and self-exclusion settings. We do not assign a player type or use one to determine an alert audience. Older software or historical records may contain retired preference fields that no longer control alert delivery. Responsible-use settings support your requested restrictions; they are not a clinical diagnosis. These choices can reveal interests and create inferences about how you use the Service.

#Activity and interaction information

Our first-party systems record how the Service is used. Depending on the feature, this may include:

• session identifiers, screen views, taps, feature interactions, funnels, and timestamps;
• game, trend, alert, or prediction identifiers viewed or acted on;
• tracked games, opened alerts, notification interactions, and the duration or sequence of an interaction;
• referral, invite, attribution, and conversion events;
• when you choose to open an independent third-party destination from Midgame; and
• app version, operating-system version, device model, locale, time zone, screen characteristics, referral parameters, and similar context.

This app activity may be associated with an account or guest identifier and is therefore not necessarily anonymous. We may create aggregate or deidentified statistics, but we treat information as personal unless it has been transformed so it cannot reasonably be linked back to a person.

#Device, diagnostics, and network information

We may collect device model, operating system and app version, language, time zone, network information, IP address, event times, crash reports, stack traces, app-hang information, performance traces, and technical view-hierarchy or similar diagnostic context. Diagnostic context is used to understand a malfunction and may incidentally reflect what the app displayed when the problem occurred.

Apps store credentials using the credential-storage mechanisms implemented for their platform, including the iOS Keychain. The apps may also cache account, game, alert, trend, rule, subscription, preference, and queued activity data locally so features can load and function. Local data is subject to your device’s security and may persist until the app, cache, or device data is cleared.

#Notifications and Live Activities

For notification registration and delivery, we may process Apple Push Notification service tokens on iOS, Firebase Cloud Messaging tokens on Android, installation identifiers, push-to-start and per-activity tokens for supported iOS features, device and app version, permission status, Live Activity support status, and records of sending, delivery feedback where available, opening, actions, and related conversions. Registration and permission behavior differ by platform; a technical token may exist even when display permission is disabled. Tokens route messages to a device; they are not the content of a text message or phone call.

Notification previews, widgets, and Live Activities may display game interests or alert content on a lock screen visible to others. Use device settings to control previews and visibility. Turning off notifications does not necessarily remove registration, security, or historical delivery records.

#Subscription and transaction information

When you start, purchase, restore, or manage a paid feature through the Apple App Store or, where offered, Google Play, we may receive product and entitlement information, subscription tier, purchase tokens or transaction identifiers, storefront or currency context, trial status, purchase and renewal dates, auto-renewal or cancellation state, billing-issue state, and related receipts or verification results from the store and our subscription infrastructure providers. Providers can receive an account or app-user identifier to associate an entitlement with your account.

The store and its payment providers process payment credentials for app-store purchases. Midgame does not receive your complete payment-card number from those purchases. Stores and subscription providers may retain their own transaction records under their policies and legal obligations.

#Communications, support, reports, and feedback

We collect information you submit through contact, support, waitlist, reporting, feedback, and account-deletion flows. This may include your name, email, phone number, message category, message body, feedback, report details, deletion reason, and related records. Messages may contain information you choose to include. Please do not include payment-card details, passwords, verification codes, health information, or other unnecessary sensitive information.

Phone sign-in uses the number you supply and a verification provider to send requested authentication messages. We use authentication message and verification records for account access, security, and abuse prevention. Providing a phone number for sign-in does not enroll you in promotional texts. We do not give authentication phone numbers or messaging-consent records to third parties for their independent marketing. Delivery and verification providers may process them to perform those services.

#Referrals and fraud-prevention information

If you use a referral or invite feature, we may collect the referral code and relationship, platform, operating-system version, screen size, locale, time zone, user agent, IP address or a hashed form of it, device or token-derived fingerprints, invite status, join time, and reward qualification. An inviter may see limited status information about an invitee, such as a first name or username and whether the invite qualified, but not the invitee’s phone number or email through that feature.

#Website cookies and similar technologies

The website uses local storage and may use cookies or similar technologies to remember consent choices, maintain essential functions, protect forms, measure performance, and understand traffic. Optional analytics are disabled by default and enabled only after an affirmative choice through our consent interface. Necessary hosting, security, and form-processing requests still occur when optional analytics are declined.

When analytics is enabled, website events may include page URL and path, page title, referrer, campaign parameters, browser or device information, and interaction events. We configure advertising-storage signals as denied and do not use the Service to deliver third-party targeted ads. Section 9 explains browser controls and Global Privacy Control.

#3. Where information comes from

We obtain personal information:

• directly from you, including information entered during onboarding, support, referrals, settings, rules, and deletion flows;
• automatically from your device and use, including app activity, IP-derived location, diagnostics, permissions, tokens, cookies, and local-storage choices;
• from platform and service providers, such as Apple, Google, authentication and verification providers, subscription infrastructure, analytics, diagnostics, and email providers;
• from another user, such as when someone sends an invite or identifies a referral relationship; and
• by generating inferences, such as sports preferences, likely region from IP, feature interests, and fraud or security signals.

Sports data providers supply game and market information displayed in the Service. We do not treat public game statistics as your personal information merely because you view them, although the record of what you viewed may be personal information.

#4. Why we use information

We use personal information to:

• create, authenticate, maintain, and secure registered and guest accounts;
• verify age information and configure region-relevant features;
• provide games, trends, alerts, rules, follows, notifications, Live Activities, referrals, and responsible-use controls;
• manage subscription access, verify entitlements, restore purchases, and address billing-support issues;
• personalize sports, team, alert, and notification experiences;
• send verification, security, service, support, policy, and other transactional communications;
• respond to inquiries, reports, deletion requests, rights requests, and feedback;
• monitor performance, debug crashes and app hangs, analyze feature use, and improve the Service;
• measure referral eligibility and prevent duplicate, automated, fraudulent, abusive, or unauthorized activity;
• enforce our Terms, protect users and systems, and investigate security incidents;
• comply with law, court orders, valid legal process, and recordkeeping obligations;
• establish, exercise, or defend legal claims; and
• create aggregate or deidentified insights that do not reasonably identify a person.

We do not use a date of birth, device location, authentication credential, or responsible-use setting to infer sensitive characteristics for advertising. We do not make eligibility decisions for independent wagering operators.

#5. Legal bases for processing

If European Economic Area, United Kingdom, or similar law requires a legal basis, our bases depend on the context:

• Contract: processing needed to provide the Service you request, authenticate an account, deliver selected features, or manage subscription access.
• Legitimate interests: operating and improving the Service, understanding use, maintaining security, preventing fraud, supporting users, and protecting legal rights, balanced against your interests and rights.
• Consent: optional device location, notifications where the operating system requests permission, optional website analytics, and other processing where we specifically ask for consent. You may withdraw consent prospectively.
• Legal obligation: processing needed to comply with law, valid process, tax, accounting, consumer-protection, or regulatory requirements.
• Vital interests or public task: only in the limited circumstances where the applicable law recognizes and requires that basis.

If we ask for information needed to perform a contract or comply with law and you do not provide it, the applicable feature may be unavailable.

#6. How we disclose information

We disclose personal information only as described below, as otherwise explained at collection, or with your direction.

#Vendors that process information for us

We use providers to perform defined functions. Depending on the Service configuration, these may include:

• Apple for Sign in with Apple, StoreKit and App Store purchases, APNs, Live Activities, and iOS platform services;
• Google / Firebase for Android notification delivery, installation and referral services, and Google Play purchases where offered;
• Twilio for phone-number verification;
• RevenueCat and CashSDK, as configured for your app and account, for subscription offerings, purchase verification, entitlement checks, restoration, and subscription-lifecycle infrastructure, including parallel verification during provider transitions;
• Sentry for production crash, app-hang, error, and performance diagnostics;
• Resend for transactional, verification, support, and website-form email delivery;
• Google Analytics and Segment for website analytics only after optional analytics consent, subject to the configuration described in this policy; and
• hosting, database, content-delivery, monitoring, security, customer-support, and infrastructure providers that help us operate the Service.

These providers receive information appropriate to their function and process it under their agreements with us. Some also process information for their own purposes as independent businesses, particularly Apple and services you choose to visit; their notices govern that independent processing. Vendor names and functions can change as the Service evolves, and we will update this policy when a change is material.

#At your direction or when you leave Midgame

When you choose to open an independent third-party service, the destination may receive ordinary connection and request information directly from your device, and any referral or destination parameters included in the link. Midgame may record that the action occurred. The third party’s terms and privacy policy apply after you leave Midgame.

#Legal, safety, and rights protection

We may disclose information if we reasonably believe disclosure is necessary to comply with a law, subpoena, court order, or other valid legal process; respond to a government request; enforce agreements; investigate fraud, security, or illegal activity; protect the rights, property, or safety of Midgame, users, or others; or establish, exercise, or defend legal claims. We assess requests and may object or narrow them where appropriate and lawful.

#Corporate transactions

Information may be disclosed in connection with due diligence, financing, reorganization, merger, acquisition, sale of assets, bankruptcy, or a similar transaction. A recipient may use it only as permitted by this policy unless it provides notice and any choice required by law.

#Professional advisers and business administration

We may disclose information to lawyers, auditors, insurers, accountants, banks, and professional advisers when reasonably necessary for their work and subject to appropriate duties of confidentiality.

#Aggregate and deidentified information

We may disclose statistics or information that has been aggregated or deidentified so it cannot reasonably be linked to you. We do not attempt to reidentify information that applicable law requires us to maintain as deidentified, and we require the same where legally required of recipients.

#7. Sale, sharing, advertising, and profiling

Midgame does not exchange personal information for money. As of this policy’s effective date, we do not display third-party advertising in the Service and do not use personal information for cross-context behavioral advertising or targeted advertising based on activity across unrelated businesses.

Some U.S. state laws define “sale” or “sharing” broadly enough that disclosures to an analytics provider may qualify even when no money changes hands. This can concern website identifiers, device and network information, and browsing or interaction events disclosed to the analytics providers identified in Section 6. Optional website analytics remain off until you opt in, and you may reject or revoke them through Your Privacy Choices in the website footer without creating an account. We also treat a recognized Global Privacy Control signal as an opt-out for that browser. We do not knowingly sell or share the personal information of anyone under 18. A future change to advertising or data-sale practices requires the applicable notice and choices; this policy does not authorize it in advance.

Automated rules generate sports analytics and alerts and help apply age, account-security, subscription, and responsible-use restrictions within Midgame. They do not decide your eligibility with an independent wagering operator or assess your financial suitability to wager. If an automated restriction appears incorrect, contact support@mid.game; applicable rights to object, contest a decision, or request human review can also be exercised through Section 10.

#8. Retention and account deletion

We retain personal information only for as long as reasonably necessary for the purposes described in this policy, including providing the Service, maintaining security and integrity, resolving disputes, enforcing agreements, meeting accounting or legal requirements, and establishing or defending claims. Retention depends on the type of information, sensitivity, operational need, account status, legal requirements, and risk of harm from unauthorized use or disclosure.

In general:

• account and preference records are retained while an account is active and as reasonably necessary after deactivation;
• session, device, security, and fraud records are retained for security and integrity needs;
• subscription and transaction records may be retained for entitlement verification, accounting, disputes, fraud prevention, and legal compliance;
• analytics, diagnostics, alert, notification, and interaction records are retained for product, reliability, security, and recordkeeping needs;
• support, rights-request, report, and legal records are retained long enough to respond, document the response, prevent abuse, and meet legal obligations; and
• local app caches and browser storage remain on your device until the app, browser, or stored data is cleared, subject to operating-system behavior.

#Deactivation and permanent deletion are different

Deactivation disables the account, revokes active sessions, and removes registered push devices while retaining personal records, including profile, preferences, activity, and any voluntary deactivation feedback. In app versions offering a separate deactivation choice, signing in can restore the account without the previous 30-day cutoff. Deactivation is not erasure and does not clear responsible-play restrictions. Older versions may label a reversible deactivation flow as “delete”; use the web request below when you want permanent deletion.

Permanent deletion removes identifying profile and contact fields, sign-in associations, stored location and IP information, preferences, follows and tracked games, personal activity, analytics, feedback, reports, referral relationships, account-linked subscription mappings, sessions, and notification-device records from the active account database. It also removes contact snapshots and feedback previously stored with an in-app deactivation request. Optional feedback is not required to request erasure. An erased account cannot be restored. After its login identifiers are released, a new signup can use the same phone number or email without restoring the old profile or activity.

#Limited retention after permanent deletion

• Responsible-play enforcement: protected, keyed fingerprints of account identifiers may be retained to enforce an active cooling-off period or self-exclusion if you register again. These fingerprints are not raw contact fields, but remain protected, linkable information. Finite restrictions expire when the restriction ends; permanent self-exclusion has no expiry. Neither deactivation nor a new signup clears an active restriction.
• Shared delivered-alert history: an inaccessible account record with identifying profile fields removed and delivery receipts may remain to preserve shared sports-results history. Direct contact details and personal interaction fields are removed. We do not treat an identifier as anonymous while it can still be linked through a pending cleanup record.
• Provider-cleanup records: a restricted work record holds the account and provider identifiers necessary to complete associated service-provider deletion while it is pending. Once cleanup is verified, provider identifiers are removed and a minimal completion record is retained for 30 days before scheduled removal. This is not a 30-day promise for provider deletion or backup erasure.
• Necessary legal exceptions: if particular information must be retained for a legitimate security, fraud-prevention, or legal reason, we explain the affected information, purpose, and applicable retention period when processing the request. This does not authorize indefinite retention of all personal records after permanent deletion.

Deletion requests cover associated personal data processed by our service providers as well as our active database. Acceptance of a request or completion of active-account erasure does not mean provider cleanup has finished. Deletion from active systems and expiration of backups can occur on different schedules; applicable backup limitations and retention periods must be explained when the request is processed. Independent app stores may retain transaction records under their own policies and legal obligations. Contact us for the status of your request rather than assuming all copies disappeared when you signed out.

#How to request deletion

Visit Midgame Account Deletion for instructions that work without installing the app or signing in, or email delete@mid.game or privacy@mid.game. Include the phone number or email associated with the account, but no password, verification code, or payment-card details. We explain any ownership verification needed and any retention exception. Where the app offers separate choices, select Delete permanently, not Deactivate. You do not need to wait through a recovery period or cancel a subscription before submitting a deletion request. Applicable request-response periods are described in Section 10.

Deleting or deactivating a Midgame account does not cancel an app-store subscription. Cancel through the store that processed the purchase before its displayed renewal time to stop future renewal charges. See the Subscription Terms.

#9. Your controls and choices

Depending on your device and features, you can:

• update available profile, sports, team, alert, quiet-hour, and responsible-use settings in the app;
• grant or deny available device permissions in iOS or Android settings, including notifications, supported approximate-location permissions, and iOS Live Activity permissions;
• turn categories of app notifications on or off where those controls are available;
• request permanent account deletion through the website instructions or supported in-app account controls, separately from deactivation;
• reject optional website analytics in the consent banner or later through Your Privacy Choices in the footer; and
• clear website cookies or local storage through browser controls.

If you receive promotional email, use its unsubscribe link or contact support@mid.game to opt out. Essential authentication, security, purchase, support, and legally required notices may still be sent. Marketing consent, where required, is separate from agreeing to the Terms or requesting a sign-in code.

The website stores a consent record in browser local storage. If Global Privacy Control (GPC) is enabled, our website treats it as an opt-out of optional categories for that browser. A browser-level choice does not delete an app account or submit an access, correction, or deletion request. Email privacy@mid.game for those requests.

Browsers may send Do Not Track signals that do not have a uniform legal or technical standard. We do not respond to generic Do Not Track signals as a separate control, but we honor GPC where required and provide the choices described above.

Midgame’s mobile first-party product analytics do not currently have a user-facing analytics toggle. Device settings that limit advertising do not necessarily disable operational, security, entitlement, first-party analytics, or diagnostics data that are not advertising. You may exercise applicable legal rights as described in Section 10.

#10. Privacy rights and requests

Depending on where you live and subject to exceptions, you may have the right to:

• know whether we process personal information and access or receive a copy of it;
• know the categories, sources, purposes, and recipients of personal information;
• correct inaccurate personal information;
• delete personal information;
• receive certain information in a portable format;
• object to or restrict certain processing;
• withdraw consent without affecting prior lawful processing;
• opt out of sale, sharing, targeted advertising, or certain profiling;
• limit certain uses or disclosures of sensitive personal information;
• appeal our decision on a request; and
• receive equal service and not be discriminated against for exercising a privacy right.

To submit a request, email privacy@mid.game with the subject “Privacy Request” or use an in-app method where available. Account deletion can also be initiated in app settings. Describe the right you want to exercise and the account information needed to locate your records, but do not send a password, verification code, government identification, or full payment-card number unless we specifically request an appropriate verification method.

We will verify requests to a degree appropriate to the sensitivity of the information and risk of harm. Verification may require confirming control of an account, email address, or phone number. If we cannot verify a request, we may deny it or limit the information provided. We may also deny or retain information where an exception applies and will explain the basis where required.

Browser opt-outs through Your Privacy Choices or GPC do not require identity verification or a new account. We use information supplied to verify a rights request only for verification, security, and documenting or fulfilling that request, not to enroll you in marketing.

An authorized agent may submit a request where law permits. We may require proof of the agent’s authority and may ask you to verify your identity or confirm the request directly. We respond within the period required by applicable law and may take a permitted extension with notice. If we deny an appealable request, you may appeal by replying with the subject “Privacy Appeal.”

For a covered California request to know, correct, or delete, the ordinary response period is 45 calendar days, with a permitted extension and notice where applicable. For a request governed by the GDPR or UK GDPR, the ordinary period is one month, subject to the applicable extension rules. Other requests, including opt-outs and appeals, may have different deadlines; we apply the deadline the law requires. You may complain to the relevant state attorney general, privacy regulator, or data-protection authority without first completing our internal process.

We do not charge for ordinary requests, but may charge or decline as permitted for requests that are manifestly unfounded, excessive, repetitive, fraudulent, or not legally required. We will not retaliate or unlawfully discriminate because you exercised a right.

#11. U.S. state privacy disclosures

This section supplements the rest of the policy for residents of states with comprehensive privacy laws, including California, where the law applies to Midgame and the person or information at issue.

In the preceding 12 months, we may have collected the following statutory categories described in Section 2:

• identifiers, such as name, username, account IDs, email, phone, IP address, device and push tokens, and referral identifiers;
• customer-record information, such as contact and account information;
• protected classification information, such as age or date of birth;
• commercial information, such as subscription product, transaction, entitlement, trial, renewal, and cancellation status;
• internet or electronic-network activity, such as screen views, taps, sessions, referral activity, destination opens, interactions, and website usage;
• geolocation information, including selected state, optional approximate device location used for country, region, or time-zone suggestions, permission and source records, and location inferred from IP;
• audio, electronic, or similar information, limited to electronic messages, screenshots, attachments, or similar content you voluntarily send to support or reporting channels;
• inferences, such as sports, team, feature, alert, and product preferences; and
• sensitive personal information, which may include account authentication information, date of birth, and location data as defined by the applicable law.

We collect these categories from the sources in Section 3 for the purposes in Section 4. We may disclose them for business purposes to the recipient categories in Section 6, including platform, authentication, subscription, diagnostics, analytics, communications, hosting, security, infrastructure, professional-adviser, legal, and corporate-transaction recipients as appropriate. We do not collect every statutory category and do not knowingly collect characteristics such as race, religion, union membership, genetic data, or health diagnoses through the core Service.

We do not exchange personal information for money. Our position on analytics disclosures that a law may define as sale or sharing is described in Section 7, along with the opt-out method. We do not use or disclose sensitive personal information to infer characteristics or for purposes that require a separate right to limit under California law. If that changes, we will provide the required notice and control.

California residents may have rights to know, access, correct, delete, and receive information about categories, sources, purposes, and recipients; to opt out of sale or sharing; to limit certain sensitive-information uses; and to be free from unlawful discrimination. California residents may use an authorized agent as described above. California’s “Shine the Light” law may permit residents to request information about certain disclosures for another company’s direct marketing; we do not disclose personal information to third parties for their own direct marketing as contemplated by that law.

Other U.S. state residents may have similar rights, including opt-out and appeal rights. Submit requests through Section 10. We will apply the law associated with your verified residence and the Service as required.

#12. International users and transfers

Midgame is based in the United States, and we and our providers may process information in the United States and other countries where we or they operate. Those countries may have privacy laws different from those where you live.

Where required for a restricted transfer, we rely on an approved legal mechanism, such as an adequacy decision, standard contractual clauses, a provider’s valid certification framework, or another lawful safeguard. You may contact us for information about the mechanism applicable to your information, subject to confidentiality and legal limits.

Residents of the European Economic Area or United Kingdom may have the rights described in Section 10 and may lodge a complaint with the data-protection authority where they live, work, or believe a violation occurred. We encourage you to contact us first so we can try to address the concern. Nothing in this policy limits the right to contact an authority.

#13. Security

We use administrative, technical, and organizational measures designed to protect personal information, taking account of the nature of the information and reasonably foreseeable risks. Measures include access controls, authentication and session protections, transport security, protected storage for certain device credentials and push tokens, monitoring, and vendor controls where appropriate.

No method of transmission, storage, or processing is completely secure. We cannot guarantee that unauthorized parties will never defeat safeguards or that information will never be lost, altered, accessed, or disclosed. You are responsible for securing your device, account recovery channels, and verification codes and for promptly reporting suspected unauthorized access.

If a security incident affects personal information, we will investigate and provide notice to affected people or authorities where required by law.

#14. Children and younger users

The Service is not directed to children or anyone under 18, and we do not knowingly permit a person under 18 to create or use an account. If you are under 18, do not use the Service or send us personal information.

If we learn that we collected personal information from a person under 18 in violation of this policy, we will take appropriate steps to restrict the account and delete or otherwise handle the information as required by law. A parent or guardian who believes a minor provided information may contact privacy@mid.game.

Independent wagering services may impose a higher minimum age, commonly 21 in parts of the United States. Midgame eligibility does not establish eligibility to use those services.

#15. Third-party links and services

The Service may link to Apple, Google, independent wagering operators, social platforms, help resources, or other services. Their privacy practices are outside Midgame’s control. Once you interact with an independent service, it may collect information directly from your device under its notice. Review that notice before providing information or completing a transaction.

Apple and Google control their respective store payment, refund, subscription-management, and certain platform information. Midgame’s policy does not replace their privacy notices or the notice of another independent service.

#16. Changes to this policy

We may update this policy when the Service, law, vendors, or our practices change. We will post the updated version, revise the “Last revised” date, and provide additional notice when required. If a change materially affects processing based on consent, we will request new consent where law requires it.

Prior versions may be requested by contacting us. We encourage you to review this policy periodically, but posting alone will not substitute for a notice or choice that applicable law requires.

#17. Contact Midgame

Questions, complaints, privacy requests, or appeals may be sent to:

Midgame, Inc.
3857 Birch Street, #3396
Newport Beach, CA 92660
United States

• Privacy: privacy@mid.game
• Account deletion: delete@mid.game
• Support: support@mid.game

Please use “Privacy Request” or “Privacy Appeal” in the subject when applicable. Do not include passwords, verification codes, complete payment-card numbers, or unnecessary sensitive information.