# Law Enforcement Guidelines

Effective date: September 28, 2026

Last updated: October 16, 2026

> **The short version**
>
> - We disclose User data to law enforcement only in response to valid legal process: a subpoena for basic subscriber information, a court order for non-content records, and a search warrant for content.
> - In an emergency involving a good-faith belief of imminent death or serious physical injury, we can disclose voluntarily and fast; email us with EMERGENCY in the subject line.
> - We honor preservation requests for 90 days, renewable once for another 90 days.
> - We notify Users about legal demands for their data unless the law prohibits it or notice would create danger, including in child safety cases.
> - Non-US authorities must use the MLAT process or letters rogatory; we do not respond directly to non-US legal process.

## 1. Purpose and scope

1.1. These Law Enforcement Guidelines (these "Guidelines") explain how Summer Labs, Inc. ("Summer", "we", "us") responds to requests from law enforcement and other government agencies for information about Users of Summer Games, Summer Engine, and the other Services. Capitalized terms not defined here (including Account, User, Creator, Player, Game, Platform, Services, AI Tools, Generated Content, and Parent Account) have the meanings given in the Summer Dictionary.
1.2. These Guidelines are operational information for law enforcement. They are not legal advice, they do not create any enforceable rights for any person, and they do not waive any objection, immunity, or defense available to Summer. Summer may depart from these Guidelines where the law requires or permits.
1.3. Summer Labs, Inc. is a Delaware corporation headquartered in Wilmington, Delaware. Sparks are sold to Players by App Store Purchase in the Summer iOS app in every launch country from launch day, on the launch country list in Sections 3.7 and 3.9 of the Fee and Rates Schedule, as updated there (Japan, Brazil and Argentina included from launch day; Brazil and Argentina by App Store Purchase only), and on Summer's own web checkout in the United States at launch, with further web checkout countries added to that list as each is cleared. In Japan, Sparks are sold from launch day through App Store Purchase, and Summer monitors the total unused Purchased Sparks balance held by Players in Japan against the Payment Services Act registration threshold (JPY 10,000,000 outstanding at the 31 March and 30 September test dates) and completes the prepaid payment instrument notification, registration and security deposit before that threshold is reached; until then Summer is within the exemption, as the Regional Schedule for Japan states. Creators may be located anywhere. All requests should be directed to Summer Labs, Inc.; no affiliate of Summer holds User data for the Platform.
1.4. These Guidelines cover government and law enforcement requests only. Civil litigants and private parties should see Section 13.

## 2. Legal framework

2.1. Summer is a provider of electronic communication services and remote computing services to the public within the meaning of the Stored Communications Act, 18 U.S.C. §§ 2701 through 2713 (the "SCA"). The SCA restricts what Summer may disclose and prescribes the legal process each category of data requires.
2.2. Summer requires valid legal process issued by a court or authority with jurisdiction over Summer, properly served under Section 10, and specific enough to identify the Account and data sought under Section 5. Process issued outside California is addressed in Section 4.6 (criminal process) and Section 13.2 (civil process).
2.3. Summer reviews every request for facial validity, jurisdiction, and scope. Summer may seek to narrow or quash requests that are overbroad, unduly burdensome, or legally deficient, and interprets ambiguous requests narrowly.

## 3. What data exists and how long we keep it

Retention periods below are operating targets; the controlling schedule is the Data Retention and Deletion Policy, and data may be deleted earlier at a User's request or later where preserved under Section 7 or Section 8 or required by law. If data has already been deleted in the ordinary course, it cannot be produced.
3.1. **Basic subscriber information.** Username and display name; email address; phone number if provided; Account creation date and time and the IP address used at creation; Account status and age band; Parent Account linkage for Users aged 13 to 17; and the means and instrument of payment at the level Summer holds it (see Section 3.6). Retained for the life of the Account plus 30 days after Account deletion.
3.2. **Non-content records and logs.** Login and session IP address history with timestamps, retained 12 months; device and client identifiers, retained 12 months; friend and trusted-connection lists, retained for the life of the Account; Game session join and leave records, retained 90 days; and transactional metadata for Sparks purchases, spends, and Program Payments (dates, amounts, counterpart Account identifiers, the Player Country recorded at the time of each spend, and for each Program Payment the gross amount at the Creator Rate, any legally required withholding, and the net paid, but not message content), retained 7 years for financial and tax recordkeeping.
3.3. **Content.** Text chat messages, retained 12 months from sending or for the life of the Account plus 30 days, whichever is shorter; voice chat, which is not recorded (transient safety buffers are deleted within 48 hours and only safety-flagged snippets are retained as moderation records) as described in the AI Conversation and Recording Notice; AI conversation transcripts between a User and AI Tools or AI-driven characters, retained as described in the AI Conversation and Recording Notice; published Games, Mods, Virtual Content, avatars, profiles, and other uploaded content, retained while published and for 90 days after removal or deletion; private, unpublished Creator projects hosted by Summer, retained while the Account is active; and customer support communications, retained 24 months.
3.4. **Moderation and safety records.** Reports, enforcement actions, and related safety case records, retained 24 months after case closure, and longer for child safety matters preserved under Section 8. Enforcement actions are taken under the Summer Games Community Standards, Section 28.
3.5. **Age assurance data.** Data collected for age checks is minimized and deleted on the short schedule described in the Age Check and Biometric Data Notice; in most cases only the resulting age band is retained.
3.6. **Payment data.** Summer bills Sparks sold on its web checkout and in the desktop app (payments powered by Stripe), but payment card numbers and full payment credentials are held by Summer's payment processor (Stripe), not by Summer. Summer holds transaction records (amount, date, last four digits and card brand where provided by the processor, and processor transaction identifiers). Requests for full payment instrument data should be directed to the payment processor. Where Sparks are bought as an App Store Purchase in the Summer iOS app, Apple bills the Player under Apple's terms, holds the payment instrument, issues the receipt, collects tax where Apple collects it for the Player's Storefront and decides refunds; Summer licenses the Sparks. Summer holds the Apple transaction identifier and original transaction identifier, the product identifier, the Storefront country, the purchase date and status (including refund and revocation notices) and the Sparks delivered. Requests for payment instrument data or Apple Account billing details for those purchases should be directed to Apple. Where Sparks are bought through Google Play's billing system in the Summer Android app, Google bills the Player, holds the payment instrument, issues the receipt and handles refunds; Summer holds the Google Play purchase token and order identifier, the product identifier, the country, the purchase time and status (including refund and cancellation notices) and the Sparks delivered. Requests for payment instrument data or Google account billing details for those purchases should be directed to Google. Creator Payout Account details are collected through a form hosted by Summer's Payout Provider (Stripe Global Payouts) and stored by that provider as Summer's service provider; identity verification records for Creators are held by Summer's Identity Verification Provider (currently Persona) as Summer's service provider. Requests for those records should be directed to Summer, which will coordinate with the provider. Summer holds Program Payment amounts, dates, and provider transaction identifiers. Summer also holds, as its own tax records, the tax form each Creator provides before the first Program Payment (Form W-9 for US Creators; Form W-8BEN or W-8BEN-E for non-US Creators; each including the taxpayer identification number and any treaty claim), its withholding determinations, and the information returns it files (Forms 1099-MISC and 1042-S), retained 7 years after the end of the relevant tax year (the Data Retention and Deletion Policy schedule value, above the IRS floor of 3 years from the return due date, 4 years where backup withholding applies). Those forms are collected by Summer itself before the first Program Payment and stored by Summer, encrypted and access-logged, not through the Payout Provider's hosted form; if Stripe Global Payouts tax support is adopted, Stripe holds a copy as Summer's service provider and requests for those forms still route through Summer. Amounts withheld from a Program Payment are remitted to the Internal Revenue Service and are not held for the Creator. Summer holds nothing for any Creator; Program Payments are made from Summer's own revenue.
3.7. **What Summer does not have.** Summer does not collect precise geolocation from Accounts belonging to Minors and does not offer location sharing to Minors (see the Child Safety and CSAE Policy); does not hold government ID documents except transiently where the Age Check and Biometric Data Notice describes it; and does not hold Creator bank account numbers (see Section 3.6 for where Payout Account details are held).

## 4. Required legal process by data type

4.1. **Basic subscriber information: subpoena.** Summer discloses the basic subscriber information listed in 18 U.S.C. § 2703(c)(2) (name, address, records of session times and durations, length and types of service, subscriber identity, means and source of payment as held by Summer, and temporarily assigned network addresses) in response to a valid federal or state subpoena, including a grand jury, trial, or administrative subpoena. From a Creator tax form, a subpoena reaches only the fields 18 U.S.C. § 2703(c)(2) lists (name, address, and means and source of payment), never the taxpayer identification number; the form itself is a non-content record under Section 4.2.
4.2. **Non-content records: court order.** Summer discloses non-content records and other information pertaining to an Account beyond basic subscriber information (for example IP history beyond session records, friend and trusted-connection lists, Game session logs, transactional metadata, Creator tax forms, Withholding Determinations, information returns and the Player Country recorded at spend) in response to a court order issued under 18 U.S.C. § 2703(d) on a showing of specific and articulable facts, or a search warrant.
4.3. **Content: search warrant.** Summer discloses the content of communications and stored content (chat message content, AI conversation transcripts, non-public uploaded content and projects, and support message content) only in response to a search warrant issued on probable cause by a court of competent jurisdiction under 18 U.S.C. § 2703 or equivalent state authority. Summer requires a warrant for all content regardless of the age of the communication.
4.4. **Consent.** Summer may disclose Account information with the lawful, verified consent of the Account holder, or of a parent or legal guardian acting through a linked Parent Account for a User aged 13 to 17, to the extent 18 U.S.C. § 2702(b)(3) and (c)(2) permit.
4.5. **Public content.** Content that is public on the Platform (published Games, public profiles, public Game descriptions) may be viewed without legal process like any member of the public. Requests for records about public content (for example, who published it and when) follow Sections 4.1 through 4.3.
4.6. **Process issued outside California.** Summer accepts criminal legal process issued outside California without domestication when it is facially valid and served under Section 10: a search warrant issued by a State court of general criminal jurisdiction that the law of that State authorizes to issue search warrants (18 U.S.C. § 2711(3)(B)); a court order under 18 U.S.C. § 2703(d) issued by a court of competent jurisdiction; and a federal or State grand jury or trial subpoena, or an administrative subpoena authorized by a federal or State statute, for the basic subscriber information listed in 18 U.S.C. § 2703(c)(2). Civil process issued outside California is addressed in Section 13.2.

## 5. What a valid request must include

5.1. Every request should include: the issuing agency and the name, badge or identification number, and official contact details (government-domain email and phone) of the requesting officer; the legal authority for the request; the specific Account identifiers (username, User ID number, email address, or transaction identifier; a display name alone is often not unique); the specific categories of data sought; a bounded date range; and the requested response format and deadline. Process delivered by email must be an uneditable PDF of the complete document, including attachments; a link to download process is not valid service (see Section 10.2).
5.2. Summer cannot search by real-world name alone with any reliability, because Accounts are pseudonymous. Where only a real name is known, include corroborating identifiers (email, IP address, payment identifiers, or Game and timestamp details).
5.3. Overbroad requests (for example, "all data for all Users of a Game") will be returned for narrowing. Summer produces the data that the process validly compels, and no more.
5.4. Requests and process should be in English. Summer responds within 10 business days for routine requests; emergencies are handled under Section 6 and child safety matters are prioritized.

## 6. Emergency disclosure requests

6.1. Under 18 U.S.C. § 2702(b)(8) and (c)(4), Summer may voluntarily disclose information, including content, to a governmental entity when Summer believes in good faith that an emergency involving danger of death or serious physical injury to any person requires disclosure without delay of information relating to the emergency.
6.2. To submit an emergency disclosure request, email [support@summerengine.com](mailto:support@summerengine.com) with EMERGENCY in the subject line, from a government-domain email address, and include: the identity and contact details of the requesting officer; the nature of the emergency, including why it involves danger of death or serious physical injury and why it is imminent; the Account identifiers involved; the specific information sought and how it relates to the emergency; and a signed statement, on agency letterhead or an agency emergency disclosure form, attesting to the above.
6.3. Summer reviews emergency requests around the clock, may verify the request by callback to a published agency number, and decides each request in its own discretion. Voluntary emergency disclosure is a decision Summer makes; it is not compelled process, and Summer may ask that legal process follow.
6.4. Emergency requests involving harm to a Minor are handled with the highest priority, alongside Summer's own reporting duties under the Child Safety and CSAE Policy.

## 7. Preservation requests

7.1. Under 18 U.S.C. § 2703(f), Summer will preserve records and other evidence in its possession pending the issuance of legal process, for 90 days, renewable once for an additional 90 days upon a renewed request.
7.2. Preservation requests should be in writing, on agency letterhead or from a government-domain email, sent to [support@summerengine.com](mailto:support@summerengine.com), and must identify the Account (by username, User ID, or email) and the categories of data to preserve, with a date range where applicable.
7.3. Preservation is not disclosure. Preserved data is set aside in a snapshot as of the date the request is processed and is produced only upon valid legal process under Section 4. Summer does not notify the User of a preservation request. A preservation request does not obligate Summer to retain data generated after the snapshot; ongoing or prospective collection requires appropriate legal authority (for example, under the Wiretap Act or the Pen Register statute), which Summer evaluates separately.
7.4. If no legal process is received before the preservation period (including any renewal) expires, the preserved snapshot is deleted in the ordinary course.

## 8. NCMEC reports and child safety matters

8.1. Summer reports apparent child sexual abuse material and related apparent violations to the National Center for Missing and Exploited Children (NCMEC) CyberTipline as required by 18 U.S.C. § 2258A, as described in the Child Safety and CSAE Policy.
8.2. Law enforcement seeking the contents of a CyberTipline report should obtain it from NCMEC, which routes reports to the appropriate agency. Please reference the CyberTipline report number when contacting Summer about a reported matter.
8.3. Summer preserves the contents of each CyberTipline report and associated records for at least one year from the date of the report, consistent with 18 U.S.C. § 2258A(h) as amended by the REPORT Act. To extend preservation beyond that period, send a preservation request under Section 7 referencing the CyberTipline report number.
8.4. Disclosure of the underlying Account data connected to a CyberTipline report follows the process tiers in Section 4, except as 18 U.S.C. § 2258A itself permits disclosure to NCMEC and to law enforcement.
8.5. Summer does not notify Users of CyberTipline reports or of legal process in child safety matters, as described in Section 9.3.

## 9. User notice

9.1. Summer's policy is to notify a User before disclosing that User's information in response to legal process, and to give the User a reasonable period to seek relief from a court, unless an exception in Section 9.3 applies. Where the User is a Minor with a linked Parent Account, notice may also be given to the Parent Account.
9.2. Where notice was delayed under Section 9.3, Summer provides notice after the restriction expires or is lifted, unless an exception still applies at that time. In emergency disclosure cases under Section 6, Summer gives delayed notice after 90 days unless an exception in Section 9.3 still applies.
9.3. Summer does not provide notice, or delays it, when: a court order under 18 U.S.C. § 2705(b) or another law prohibits notice; the request is an emergency disclosure under Section 6 and notice would compound the danger; Summer believes in good faith that notice would create a risk of harm to any person, including in child sexual abuse and exploitation matters, or a risk of evidence destruction, witness intimidation, or flight; or the Account shows sustained abuse such that notice would be counterproductive to the safety of others.
9.4. Summer may seek to modify or challenge non-disclosure orders that are indefinite in duration or unsupported by individualized findings.

## 10. How to serve legal process

10.1. Serve legal process on Summer Labs, Inc. through its registered agent: The Corporation Trust Company, Corporation Trust Center, 1209 Orange Street, Wilmington, New Castle County, DE 19801, United States. Summer Labs, Inc. is a Delaware corporation with its principal place of business at 2810 N Church St, STE 89812, Wilmington, DE 19802, United States.
10.2. For efficiency, law enforcement may also deliver process and requests by email to [support@summerengine.com](mailto:support@summerengine.com) from a government-domain email address. Attach the complete process, including attachments, as an uneditable PDF; Summer does not download process through links, and a link to download process is not valid service. Acceptance of email delivery is a convenience only; it does not waive any objection to jurisdiction, venue, service, or validity, and Summer may require formal service.
10.3. Include with any process the information listed in Section 5.1. Summer responds to the contact details in the process; responses containing User data are delivered through secure channels.
10.4. Summer employees are not authorized to accept service in person at offices or events; use the registered agent or the email channel above.

## 11. Requests from outside the United States

11.1. Summer Labs, Inc. is the sole party holding User data, wherever the User is located; Sparks are sold to Players in the countries described in Section 1.3 (App Store Purchase in the Summer iOS app in every launch country from launch day; Summer's web checkout in the United States at launch), and Creators may be located anywhere. Summer does not respond directly to legal process issued by non-US courts or authorities.
11.2. Non-US authorities should proceed through a mutual legal assistance treaty (MLAT) request or letters rogatory directed to the United States Department of Justice, Office of International Affairs, resulting in US legal process served under Section 10.
11.3. Where an executive agreement under the CLOUD Act between the United States and the requesting country applies and the requesting authority is a designated authority under it, Summer will evaluate orders submitted under that agreement on the agreement's terms.
11.4. The emergency disclosure standard in Section 6 applies regardless of where the danger is located; non-US authorities facing an emergency involving danger of death or serious physical injury may contact [support@summerengine.com](mailto:support@summerengine.com) with EMERGENCY in the subject line.

## 12. Costs, testimony, and authentication

12.1. Summer may seek reimbursement of costs of producing information as permitted by 18 U.S.C. § 2706 and other applicable law, particularly for requests that are voluminous or require engineering work. Summer does not seek reimbursement for emergency disclosures under Section 6 or for child safety matters under Section 8. A schedule of reimbursement rates is available on request.
12.2. Records produced by Summer are business records. On request, Summer provides a certificate of authenticity consistent with Federal Rule of Evidence 902(11) and, for machine-generated records, Rule 902(13), so that a records custodian need not appear. Summer asks that agencies use certifications rather than testimony wherever the rules allow; requests for live testimony should be directed to [support@summerengine.com](mailto:support@summerengine.com) as early as possible. Subpoenas seeking witness testimony are not accepted by email; serve them personally or through the registered agent in Section 10.1. Summer resists subpoenas for testimony served with fewer than 14 days notice.
12.3. Summer personnel do not provide expert or interpretive testimony about User intent, slang, or in-Game behavior; produced records speak for themselves.

## 13. Civil requests and non-government parties

13.1. These Guidelines address government and law enforcement requests. The SCA generally prohibits Summer from disclosing the content of communications in response to civil subpoenas, and Summer objects to civil process that seeks content.
13.2. Civil litigants, criminal defense counsel, and other private parties should serve process through the registered agent in Section 10.1 and direct questions to [support@summerengine.com](mailto:support@summerengine.com). Defense counsel seeking data about their own client should consider proceeding with the client's verified consent under Section 4.4. A civil subpoena issued outside California must first be domesticated under the Interstate and International Depositions and Discovery Act, Cal. Code Civ. Proc. §§ 2029.100 to 2029.900, by submitting the foreign subpoena to the clerk of the superior court so that a California subpoena issues (§ 2029.300); Summer does not respond to an out-of-state civil subpoena that has not been domesticated.

## 14. Reservation of rights

14.1. Summer may update these Guidelines at any time without notice. The version posted at the time a request is received governs Summer's handling of it.
14.2. Nothing in these Guidelines commits Summer to disclose, or to refrain from disclosing, any particular information in any particular case, and nothing in them creates rights enforceable by any User, agency, or other person. Summer complies with valid legal obligations and otherwise acts in its discretion, including by challenging process it believes is invalid, overbroad, or unduly burdensome.

## 15. Contact summary

Law enforcement requests, preservation requests, emergencies: [support@summerengine.com](mailto:support@summerengine.com) (use EMERGENCY in the subject line for Section 6 requests, and "Law Enforcement Request" for other requests)
Registered agent for service of process: The Corporation Trust Company, Corporation Trust Center, 1209 Orange Street, Wilmington, New Castle County, DE 19801, United States
General legal: [support@summerengine.com](mailto:support@summerengine.com)
Principal place of business: Summer Labs, Inc., 2810 N Church St, STE 89812, Wilmington, DE 19802, United States
Child safety reporting for the public: see the Child Safety and CSAE Policy.
