Data Retention and Deletion Policy
Effective date: September 28, 2026
Last updated: October 16, 2026
The short version
- We keep personal information only as long as we need it for a stated purpose, and every category has a defined retention period. Nothing is kept indefinitely.
- Your answer to the age question (18 or older, or under 18), or your date of birth where a Summer app asks for it, is kept privately with your Account and used to determine your age band; a date of birth also moves you to the next band as you grow older. Access is restricted, and it is never used for advertising or profiling. It follows the Account-data retention period in Section 3. The age band sets minor-protective defaults and, under Section 8 of the Summer Games Terms of Service, decides whether you can buy Sparks (only Users who are 18 or the age of majority where they live, whichever is higher, can). Age-check imagery is deleted immediately after processing and never stored by Summer. Creators who join the Summer Creator Program verify their identity with Persona before their first payment; Persona destroys the biometric data within 24 hours, keeps the document images for the period in the schedule below for fraud review and re-verification, and Summer keeps only the result. Nobody under 18 is asked for an identity document.
- AI conversation logs are kept for 90 days, payment records and Sparks Ledger entries for 7 years (tax law), Creator identity and sanctions records for 5 years after the last Program Payment, and account data for the life of your Account plus 30 days. Creator tax forms and withholding records are kept for 7 years after the tax year, and, for Creators, so is the Player Country of each spend that funded your earnings, because it decides how much US tax, if any, we must withhold and report.
- You can request deletion at any time; parents can request it for their teens.
- Legal obligations (like preserving evidence of child exploitation for law enforcement) can override normal deletion timelines. We say exactly where below.
1. Purpose and scope
1.1. This Data Retention and Deletion Policy (this "Policy") is the written data retention policy of Summer Labs, Inc., a Delaware corporation ("Summer", "we", "us"), located at 2810 N Church St, STE 89812, Wilmington, DE 19802, United States. It states the purposes for which we collect personal information, our business need for retaining each category, and the timeframe in which we delete it. It is published to satisfy, among other things, the written-policy requirement of the amended Children's Online Privacy Protection Rule, 16 CFR 312.10, and the retention disclosure requirements of US state privacy laws.
1.2. This Policy applies to all personal information processed by Summer in connection with the Platform, the Services, the Engine, the Editor, Hosting Services, Summer Passport, Sparks (Purchased Sparks and Earned Sparks), Game Data, and the Summer Creator Program (the "Creator Program"). Capitalized terms are defined in the Summer Dictionary and, for Game Data, in the Summer Games Privacy Policy Section 1.6.
1.3. This Policy supplements the Summer Games Privacy Policy and the US State Privacy Addendum. Where a specific notice states a stricter (shorter) retention period for a data type (for example the Age Check and Biometric Data Notice or the AI Conversation and Recording Notice), the stricter period controls.
1.4. This Policy governs Summer's own retention. Creators who process personal data of their Players through their own integrations are independently responsible under the Creator Data Processing Addendum and the Developer Tooling and API Terms.
2. Retention principles
2.1. Purpose limitation. We retain personal information only as long as reasonably necessary to fulfill the specific, disclosed purpose for which it was collected, or as required by law.
2.2. No indefinite retention. We do not retain personal information indefinitely. Every category in the schedule in section 3 has either a fixed retention period or a defined, purpose-based trigger (such as Account closure) followed by a fixed period. The periods in section 3 are the fixed values Summer applies at launch, decided 2026-09-19, reviewed under section 9 and changed only as section 10 describes.
2.3. Children under 13. The Platform requires Users to be at least 13. We do not knowingly collect personal information from children under 13. The neutral age gate necessarily processes a date of birth before we know the person's age; if the date of birth indicates the person is under 13, the attempt is refused, the date of birth is deleted immediately, and only a short-lived hashed device or session marker is kept to prevent an immediate second attempt (see the under-13 marker row in section 3 and Section 3.6 of the Age Check and Biometric Data Notice), so that no other personal information of a child under 13 is retained. This design, and this published Policy, implement 16 CFR 312.10's requirements that children's personal information be retained only as long as reasonably necessary for the specific purpose collected, never indefinitely, and only under a written, published retention policy.
2.4. Deletion or de-identification. At the end of a retention period we either delete the data or irreversibly de-identify it (section 4). De-identified data is no longer personal information and may be retained in aggregate form.
2.5. Shortest workable period. Where more than one purpose applies to a record, the record is retained for the longest applicable period in the schedule, and access is restricted to the surviving purpose once the shorter purposes lapse.
3. Retention schedule
The following schedule states, for each category: what it is, why we keep it, and how long we keep it. Every category has a fixed period or a fixed trigger plus period; the values are the launch values decided 2026-09-19. A summary table appears in Section 8.3 of the Summer Games Privacy Policy; this schedule controls.
| Data category | Examples | Purpose (business need) | Retention period | At end of period |
|---|---|---|---|---|
| Age answer or date of birth (age gate input) | The answer to "Are you 18 or older?", with its source and time, or the birth date entered in a Summer app | Determine the User's age band (13 to 15, 16 to 17, or 18 and over) as the User grows older, and the turn-of-age date that moves the User between bands; the age band is in turn used to determine eligibility to purchase Sparks or make any other real-money transaction under Section 8 of the Summer Games Terms of Service | Kept privately for the Account-data retention period in this schedule; the date of birth is used to determine the age band as the User grows older | Deleted |
| Age-check imagery (Players) | Facial age estimation captures; government ID images if the ID fallback is used | Verify age band for the closed list of gated actions in the Age Check and Biometric Data Notice; Age Check is live at launch for those actions only and is never required to sign up or to use default chat | Deleted by the Age Assurance Vendor immediately after processing and in every case within 24 hours (biometric data) or 30 days (document images held for fraud review); Summer never stores the imagery; only the pass or fail result and age band are retained. See the Age Check and Biometric Data Notice | Deleted |
| Creator identity verification imagery and biometric data | Government identity document images, selfie or liveness capture, and face geometry collected by the Identity Verification Provider (currently Persona) before a Creator's first Program Payment; never collected from anyone under 18 | Verify the identity and age of a Creator before the first Program Payment (anti-fraud, sanctions, tax); support re-verification and fraud investigation | Biometric data (face geometry): destroyed by the Identity Verification Provider immediately after the comparison and in every case within 24 hours of capture, as Section 9.2 of the Age Check and Biometric Data Notice requires, unless a warrant, subpoena or legal hold requires longer, then permanently erased so that it cannot be recovered or reconstructed. Document images and selfie: retained by the Identity Verification Provider under Summer's instructions for 12 months to support re-verification and fraud investigation, then deleted. Summer never holds face geometry; Summer accesses a document image only on a logged manual review and does not copy it. Summer stores only the result, verified name, date of birth, address, document type and country, and the inquiry reference (see the next row) | Deleted |
| Age band and age assurance result | "13 to 15", "16 to 17" or "18 and over" flag; the turn-of-age date; date and method of the check | Apply minor-protective defaults; gate 18-and-over features; determine eligibility to purchase Sparks or make any other real-money transaction under Section 8 of the Summer Games Terms of Service (only Users who are 18 or the age of majority where they live, whichever is higher); demonstrate compliance | Life of the Account plus 30 days | Deleted |
| Account data | Username, email, profile, settings, friends list, Passport Items inventory | Operate the Account and the Services | Life of the Account plus 30 days | Deleted |
| Creator projects and content | Game and Mod project files, Virtual Content, published Games | Hosting, distribution, and the content portability commitment in the Summer Games Terms of Service | Life of the Account; after closure, retained for an export window of 90 days during which the Creator may export Godot-compatible copies | Deleted after the export window |
| Text chat and social messages | Direct messages, in-Game chat | Message delivery; safety review under the Summer Games Community Standards | 12 months from sending, or life of the Account plus 30 days, whichever is shorter | Deleted; safety-flagged excerpts move to moderation records |
| Voice chat | Live voice audio in multiplayer sessions | Real-time communication; automated safety scanning | Not recorded. Transient processing buffers are deleted within 48 hours; safety-flagged snippets move to moderation records. See the AI Conversation and Recording Notice | Deleted |
| AI conversation logs | Prompts, AI Tools inputs and outputs, AI NPC conversation transcripts, voice audio spoken to an AI Tool while a voice session is active | Operate AI features, abuse prevention, safety review, service debugging. Not used for foundation-model training absent explicit opt-in under the AI Features and Generated Content Terms | 90 days, then deleted or de-identified (raw voice audio spoken to an AI Tool is deleted within 30 days of capture, as Section 11.1 of the AI Conversation and Recording Notice states); safety-flagged excerpts move to moderation records | Deleted or de-identified |
| Telemetry and analytics | Gameplay events, Editor usage, feature metrics | Improve and debug the Services; capacity planning | 13 months, then aggregated and de-identified | De-identified aggregate retained |
| Server, access, and security logs | IP-level access logs, authentication events, crash dumps | Security, incident response, fraud and ban-evasion detection | 12 months | Deleted |
| Game session join and leave records | Which Game a User joined and left, the session start and end times, and the server or session identifier | Safety review and abuse investigation; responding to lawful requests under the Law Enforcement Guidelines (Section 3.2 of that page takes its value from this row); service debugging | 90 days | Deleted; safety-flagged sessions move to moderation records |
| Payment and transaction records | Sparks purchase history, invoices, billing country or Storefront country at purchase (Player Country, disclosed in the Sparks Ledger entries row), for an App Store Purchase the Apple transaction identifiers and purchase status Summer receives (Apple bills you under Apple's terms and issues the receipt; Summer licenses the Sparks), chargeback and dispute records including the evidence pack, refund and account-credit records under the Refund and Billing Policy | Tax, accounting, audit, chargeback defense, legal compliance; the US-Source Share apportionment for Creator tax withholding and reporting is carried on the Sparks Ledger entries row | 7 years after the transaction | Deleted |
| Sparks Ledger entries | Purchased Sparks and Earned Sparks ledger movements, maturation and eligibility states, Network Share allocations under the Network Share Schedule, platform-credit elections; Player Country recorded at the time of each spend (for an App Store Purchase, the Storefront country of the purchase; for a purchase on Summer's web checkout, the Stripe billing country, with IP-derived country as the web fallback) | Compute balances and Program Payments; financial records; dispute and chargeback reversal across every leg of a spend; determining the US-Source Share of Creator earnings for tax withholding and reporting (the Payment and transaction records row points here) | Entries with financial significance: 7 years after the entry. Balance state: life of the Account plus 30 days | Deleted |
| Game Data | Progress, saves, settings and Game Points a Game keeps about a Player inside that Game; Virtual Content entitlements; Passport Item origin records | Operate the Game for the Player; deliver entitlements on every device; show Passport Item origin | Life of the Game and the Account, whichever ends first, plus 30 days. Game Points are Game data, not a Summer balance, and are never a financial record | Deleted |
| Creator identity, sanctions and Payout Account records | Identity verification results and inquiry references; verified legal name, date of birth and address; declared country of residence; sanctions and restricted-party screening results (including cleared matches); Payout Account token, last digits, country, currency and verification status (the account details themselves are held by Stripe as Summer's service provider); re-verification history | Anti-fraud, sanctions compliance, eligibility under the Creator Program Terms, payment delivery, audit (country of tax residence and any treaty claim are held with the Creator tax forms row on its 7-year period, not here) | 5 years after the last Program Payment or the end of participation in the Creator Program, whichever is later | Deleted |
| Creator tax forms and information-return records | Tax Forms: Forms W-9, W-8BEN and W-8BEN-E including any treaty claim and taxpayer identification number (held encrypted and access-logged); the Withholding Determination for each Program Payment (US-Source Share, rate applied, backup-withholding flag); payment statements showing the gross amount at the Creator Rate, withholding and net paid; Forms 1099-MISC and 1042-S issued and Form 1042 filing data; IRS remittance records; all under the Creator Tax Addendum | Federal and state tax documentation, information reporting and withholding on Program Payments, which Summer treats as royalties for US federal income tax purposes (24 percent backup withholding where no valid Form W-9 is on file; 30 percent, or the treaty rate a valid Form W-8 claims, on the US-Source Share for non-US Creators); Summer is payer and withholding agent of record; disclosed to the IRS and, where required, state tax authorities as recipients | 7 years after the end of the relevant tax year | Deleted |
| Fraud and security signals | Hashed payment-card fingerprints, hashed device fingerprints, IP address and 3-D Secure result at purchase, buyer-to-creator linkage signals, dispute outcomes, card-fingerprint purchase blocks | Fraud prevention, self-dealing detection, chargeback defense, ban evasion; never used to lock an Account over a billing dispute | 12 months with the security logs; card-fingerprint purchase blocks after a lost fraud dispute persist for that fingerprint. Where IP-derived location is the fallback for Player Country, only the derived country code is carried into the Sparks Ledger entry for the tax purpose; the IP address itself is deleted on this row's 12-month schedule | Deleted (block-list entry retained) |
| Under-13 re-registration marker | Hashed email address and device marker retained when an Account is closed because its holder is under 13; the short-lived hashed device or session marker kept when an under-13 date of birth is entered at sign-up (Section 3.6 of the Age Check and Biometric Data Notice), which is deleted within 72 hours | Prevent immediate re-registration by the same child, and an immediate second sign-up attempt | 12 months for the hashed email address and device marker of a closed Account; 72 hours for the refused sign-up marker | Deleted |
| Moderation and enforcement records | Reports, review decisions, enforcement actions, appeal outcomes | Enforce the Summer Games Community Standards; handle appeals; identify repeat violators; DMCA repeat-infringer tracking under the DMCA and Intellectual Property Policy | 24 months after case closure. For terminated Accounts, a minimal ban record (hashed identifiers only) is retained for 24 months to prevent ban evasion | Deleted |
| CSAE evidence and NCMEC report data | Content and data preserved in connection with a CyberTipline report under the Child Safety and CSAE Policy | Federal reporting and preservation duty | 1 year from the date of the report, as required by 18 U.S.C. 2258A(h) as amended by the REPORT Act; longer if subject to a legal hold or a lawful preservation request | Deleted |
| Law enforcement preservation | Data preserved under 18 U.S.C. 2703(f) per the Law Enforcement Guidelines | Comply with lawful preservation requests | 90 days, extendable once by 90 days upon renewed request | Deleted unless legal process received |
| Support tickets | Emails and messages to support, related Account context | Resolve the issue; quality assurance; dispute records | 24 months after resolution | Deleted |
| Parent Account, consent and disclosure records | Parent acceptance of the Summer Games Terms of Service for a 13-to-17 User under the Parent Account Terms; consent receipts required by state minors laws; affirmative consent records (timestamp and notice version) for biometric capture, voice recording, AI point-of-use notices and clips under the Age Check and Biometric Data Notice and the AI Conversation and Recording Notice; unlinked parent-link email deleted within 24 hours | Demonstrate that required review and consent occurred | Life of the linked Accounts plus 24 months | Deleted |
| Marketing and communications data | Email subscription status, campaign engagement | Send communications you have not opted out of | Until opt-out, or after 24 months of inactivity; suppression-list entries (email address only) are retained as long as needed to keep honoring your opt-out | Deleted (except suppression entry) |
| Dispute and legal claim records | Arbitration filings, informal dispute records under the Summer Games Terms of Service, litigation files | Prosecute or defend legal claims | Resolution of the matter plus the applicable statute of limitations | Deleted |
| Backups | Encrypted system backups containing the categories above | Disaster recovery | Rolling backup cycle of 35 days; deleted data ages out of all backups within one full cycle | Overwritten in cycle |
4. How deletion works
4.1. Deletion means removal from production systems such that the data is not recoverable in the ordinary course of business, followed by aging out of backups within the 35-day backup cycle in section 3.
4.2. De-identification means irreversible transformation so the data can no longer reasonably be linked to a person or device. We publicly commit not to re-identify de-identified data except to test the effectiveness of our de-identification, and we bind recipients to the same commitment, as stated in the US State Privacy Addendum.
4.3. Backups. Data deleted from production remains in encrypted backups until it ages out of the rolling cycle of 35 days. Backups are not queried in the ordinary course of business and are restored only for disaster recovery; if a restore occurs, we re-apply deletions that post-date the backup.
4.4. Service providers. When we delete personal information, we instruct service providers holding copies to delete it as well, and our contracts require them to comply and to certify deletion on request.
5. Account closure
5.1. You may close your Account at any time in the Summer Games app on iPhone or Android (You > Account > Sign out and deletion > Delete account), on the web at summer.games/account/delete after you sign in, or from Settings > Privacy and data on summer.games. On closure: (a) the Account is deactivated immediately and hidden from other Users; (b) Account data is deleted after the post-closure period of 30 days (a window that allows you to reverse an accidental closure and allows us to complete in-flight transactions); we tell you this period when you close your Account and send a confirmation to the email address on your Account when deletion is complete; (c) Creators receive the export window of 90 days in section 3 to export Godot-compatible copies of their projects, per the content portability commitment in the Summer Games Terms of Service. A verified deletion request from the Creator ends the export window early; we tell the Creator before acting. Closure without a deletion request keeps the full window; (d) records subject to a longer statutory period in section 3 (for example payment records and, for Creators, Tax Forms and Withholding Determinations) are retained for that period only, with access restricted to the surviving purpose; and (e) any remaining Sparks license terminates as described in the Summer Games Terms of Service and the Refund and Billing Policy; your right to use Sparks is a limited, revocable license, Sparks are not property, and closure does not create any right to receive money for them, except that (i) Purchased Sparks bought on Summer's web checkout may be refunded under Section 4.9(a) of the Refund and Billing Policy inside the window that Section states; Sparks bought as an App Store Purchase may be refunded only by Apple, so request that refund from Apple before you close your Account; other unspent Purchased Sparks lapse on closure, and (ii) Eligible Earned Sparks of an enrolled Creator receive a final Program Payment under the Creator Program Terms; Earned Sparks are a separate instrument governed by the Creator Program Terms and not a license, as described there; Game Data, including Game Points, is deleted with the Account and has no value outside its Game.
5.2. If the Platform is wound down, we will provide advance notice and an export period so Creators can export their projects, as committed in the Summer Games Terms of Service. Retention periods in this Policy continue to apply during and after wind-down.
6. Deletion requests
6.1. Who can request. Any User may request deletion of their personal information. A parent or guardian with a linked Parent Account may request deletion on behalf of their 13-to-17 User under the Parent Account Terms. Authorized agents may submit requests as described in the US State Privacy Addendum.
6.2. How to request. Submit requests through the data request link in Settings > Privacy and data on summer.games, close your Account as described in section 5.1, or email support@summerengine.com with the subject line "Deletion Request".
6.3. Verification. We verify requests as described in the US State Privacy Addendum (Account login or confirmation through the email address on the Account, with additional verification proportionate to sensitivity).
6.4. Timing. We confirm receipt within 10 business days and complete verified requests within 45 days, extendable once by 45 days with notice to you.
6.5. Effect. A verified deletion request triggers deletion of all categories in section 3 except those subject to a legal retention obligation or an exception in section 7, and we will tell you which categories we retained and why. For a Creator, a verified deletion request also ends the export window in 5.1(c) early; we tell the Creator before acting. Deletion of your Account data does not delete content you contributed that is incorporated into other Users' Games or Mods where removal is technically infeasible or would destroy other Users' data (for example, a Mod another Creator built on your published Game under the Network Share Schedule framework); in those cases we disassociate the content from your identity instead.
6.6. No retaliation. Submitting a deletion request never results in loss of Services while the Account remains open, degraded quality, or different pricing. We do not lock or suspend Accounts because a payment is in dispute; billing disputes are handled under the Refund and Billing Policy.
7. Exceptions and legal holds
7.1. We may retain specific data beyond the periods in section 3, or decline to delete it on request, only where and only as long as one of the following applies: (a) Legal obligation. A statute or regulation requires retention (for example, tax records, including information-return and withholding records, 18 U.S.C. 2258A preservation, or securities and corporate records requirements). (b) Legal hold. The data is subject to a litigation hold, a government investigation, an arbitration under the Summer Games Terms of Service, or a reasonably anticipated legal claim. Legal holds are issued and released in writing by the Chief Executive Officer of Summer Labs, Inc. or counsel, are scoped to the specific data and custodians at issue, and are reviewed at least every 6 months. (c) Lawful preservation request. A preservation request under 18 U.S.C. 2703(f) or equivalent lawful process, handled per the Law Enforcement Guidelines. (d) Safety and security. The data is necessary to detect or prevent fraud, ban evasion, or threats to the physical safety of any person, retained in the minimal form described in section 3 (moderation and enforcement records). The hashed ban record of a terminated Account is retained under this exception as pseudonymized personal information for 24 months; it is not de-identified data under sections 2.4 and 4.2, and the deletion commitments of this Policy apply to it when that period ends. (e) Completing a transaction you requested, including delivering purchased Virtual Content, completing a Program Payment in progress under the Creator Program Terms, or resolving a refund.
7.2. Data retained under an exception is used only for the purpose of the exception, access-restricted, and deleted promptly when the exception lapses. Information returns filed with the IRS and state tax authorities are outside Summer's deletion control once filed.
7.3. Nothing in this Policy prevents us from complying with the REPORT Act, COPPA, state law, or valid legal process.
8. Teens and children
8.1. All retention periods in section 3 apply equally to Users aged 13 to 17. In addition: (a) minors' chat and social data is subject to the privacy-protective defaults described in the US State Privacy Addendum and the Parents' Guide to Summer Games; (b) a parent or guardian may review and request deletion of their teen's personal information through the Parent Account at any time; and (c) we do not retain any data of known minors for targeted advertising, because we serve no targeted advertising to known minors.
8.2. If we obtain actual knowledge that an Account holder is under 13, we immediately place the Account in a locked hold in which it cannot be used and its data is not processed except for retention and correction, allow a parent or legal guardian 30 days to correct a wrong determination as Section 15.2 of the Age Check and Biometric Data Notice describes, and, absent a correction, close the Account and delete its personal information promptly, except data we must preserve under section 7 (for example a CSAE report already made) and the under-13 re-registration marker in section 3.
9. Governance
9.1. This Policy is owned by the Chief Executive Officer of Summer Labs, Inc., reachable at support@summerengine.com. It is reviewed at least annually and whenever we launch a feature that collects a new category of personal information; no new category may launch without a retention period assigned in this schedule first.
9.2. Retention periods are enforced by automated deletion jobs where technically feasible, with quarterly audits of job execution. Manual deletion workflows are logged.
9.3. Personnel with access to personal information receive training on this Policy. Violations are handled under our internal security and disciplinary procedures.
10. Changes to this Policy
We will post updated versions with a new effective date and provide advance notice of material changes as described in the Summer Games Privacy Policy. A change that lengthens a retention period applies only to data collected after the change takes effect, unless a legal obligation requires otherwise.
11. Contact
Summer Labs, Inc. Attn: Privacy 2810 N Church St, STE 89812, Wilmington, DE 19802, United States support@summerengine.com