# AI Conversation and Recording Notice

Effective date: September 28, 2026

Last updated: October 16, 2026

> **The short version**
>
> - When you talk or type to Summer's AI features (the creation copilot in the Editor today, AI characters in Games in the future), the conversation is recorded and processed. This page is the standing notice; you also get a short notice at the moment you first use each feature.
> - Voice recording never starts silently. You see a notice before the first use and an indicator whenever a microphone is live.
> - Conversations are used to run the feature, keep the Platform safe, and fix problems. A small sample may be reviewed by trained people. The AI providers that power our features are named in this Notice and may not train on your conversations. Conversations are never used for advertising, and never used to train foundation models unless you explicitly opt in.
> - If a session could pick up other people, everyone present is told in product before capture begins.
> - Do not want to be recorded? Do not use voice features. Text alternatives exist for everything, and you can delete your copilot history.

## 1. What this notice covers

1.1. This AI Conversation and Recording Notice (this "Notice") explains how Summer Labs, Inc. ("Summer", "we", "us"), a Delaware corporation with offices at 2810 N Church St, STE 89812, Wilmington, DE 19802, United States, records and processes text and voice conversations between Users and the AI Tools available on the Platform and in the Engine and Editor. Capitalized terms used but not defined here have the meanings given in the Summer Dictionary.
1.2. This Notice supplements the Summer Games Privacy Policy, the AI Features and Generated Content Terms, and the AI Acceptable Use Policy, and is part of the Additional Terms incorporated into the Summer Games Terms of Service. If this Notice conflicts with the Summer Games Privacy Policy with respect to AI conversation recordings, this Notice controls for that data.
1.3. This Notice does not cover person to person chat between Users. Person to person chat is described in the Summer Games Privacy Policy and governed by the Summer Games Community Standards. This Notice covers conversations where an AI system is a participant.

## 2. The AI features that record

2.1. Creation copilot. The Editor includes an AI creation copilot. When you use it, your Prompts (text you type, and voice input where you use a voice mode), the copilot's responses, and the project context the copilot needs to help you (for example, the scene you have open, file names, error output, and selections you point it at) are recorded and processed as described in this Notice.
2.2. AI NPCs. Games on the Platform may in the future include AI driven characters ("AI NPCs") that Players can talk to by text or voice. AI NPCs exist only as a Platform provided service: a Game cannot embed its own model, cannot send your conversation anywhere other than Summer's AI gateway, and cannot read your conversation except as Section 12.3 allows; every request to the gateway carries your age band so that the character follows the rules for your age under the Content Maturity Policy, and open ended AI conversation is not offered to any User the Platform treats as under 13. Realtime voice conversation with AI NPCs is reserved and, when offered, will require a confirmed age of 18 or over under the Age Check and Biometric Data Notice, your affirmative consent under Section 4, and the persistent indicator in Section 3.2(b). When AI NPC features launch, conversations with AI NPCs will be recorded and processed as described in this Notice, and this Notice will be updated with any feature specific details before launch.
2.3. Future AI Tools. Any new AI Tool that records conversations will present the point of use notice described in Section 3 before its first use, and will be covered by this Notice or by feature specific Additional Terms that we will identify at the point of use.
2.4. "Recorded" in this Notice means captured and stored, in the form of text logs, audio, and transcripts, as described in Section 6. It does not mean broadcast. Nothing in this Notice makes your private project content public; publication is governed by the Summer Games Terms of Service.

## 3. How you are told: standing notice plus point of use notice

3.1. This Notice is the standing disclosure. It is always available from the Platform's legal pages and from the settings surface of each AI Tool.
3.2. In addition, each AI Tool that records presents a just in time notice at the point of use: (a) before the first time you use the feature on an Account, a full screen or modal notice states that the conversation will be recorded and processed, links to this Notice, and requires an affirmative action to continue; and (b) for voice features, a persistent visual indicator is displayed whenever the microphone is live, and capture stops when you end the session or the indicator is dismissed by ending voice mode.
3.3. Voice capture never starts without a user action. There is no always on listening. The microphone is opened only when you start a voice session, and the operating system's own microphone indicator will also reflect this.

## 4. Your consent, including in states that require every party's consent

4.1. By starting or continuing a conversation with an AI Tool after receiving the point of use notice described in Section 3.2, you consent to the recording and processing of that conversation as described in this Notice. If you do not consent, do not use the feature; Section 9 describes the alternatives.
4.2. Some states, including California, require the consent of every party to the recording of certain communications. Summer designs its AI features so that every party has consented or been notified before capture begins: (a) you consent as described in Section 4.1; (b) Summer, which operates the AI Tool and is the other party to the conversation, consents; and (c) where a session can involve other Users, the disclosures in Section 5 are made to each of them before capture of their communications begins.
4.3. Consent under this Section is per feature, not per session: your affirmative action at the first use of a feature covers later sessions of that feature, and the persistent indicator in Section 3.2(b) is displayed in every voice session. If we materially change what a feature records, the point of use notice is shown again and fresh consent is required.
4.4. You may revoke your consent prospectively at any time by stopping use of the feature, by disabling it in settings, or as described in Section 9. Revoking consent does not affect processing that already occurred.

## 5. Sessions that involve other people

5.1. Some AI sessions are single user: you and the copilot, or you and an AI NPC in a single player context. Others can involve more than one person: for example, an AI NPC in a multiplayer Game that hears open voice chat near it, or a shared Editor session where two Creators talk to the copilot together.
5.2. Before any AI Tool captures the communications of a User in a multi user context, that User receives an in product disclosure: an entry notice when joining a Game, area, or session where an AI NPC or shared AI Tool captures voice or text, and an on screen indicator identifying the capturing feature while capture is possible. A User who does not want to be captured can decline at the entry notice, leave the area or session, or mute their microphone; declining or leaving excludes their voice from capture.
5.3. A User who remains in a disclosed session after the entry notice consents to the capture of what they say or type in that session, to the extent it is picked up by the disclosed feature. This is the same contextual consent structure used for the recording features our model documents describe.
5.4. AI NPCs do not capture voice outside their disclosed range or context, and Creators are prohibited from configuring them to do so by Section 12 and the AI Acceptable Use Policy.
5.5. For Users we know to be under 18, the defaults in Section 10 further limit multi user capture.

## 5A. Clips and screen recording (reserved)

5A.1. Status. Summer does not offer a clip, screenshot or screen recording feature at launch. This Section takes effect only if and when Summer offers one, and Summer will update this Notice and show the point of use notice in Section 3.2 before the feature is enabled.
5A.2. What everyone acknowledges. If the feature is offered, anything you say, type or input inside a Game where recording is enabled, together with your username, display name, avatar and in Game likeness, may be recorded by other Users and shared by them on and off the Platform. A visible indicator is shown in the Game whenever a clip that captures voice is being recorded. If you do not want your voice heard, recorded or shared by other Users, do not use voice features; text alternatives remain available.
5A.3. Licenses. The recording User receives a non exclusive license to reproduce, display and share the clip on and off the Platform, including on social media and content sharing channels, subject to the Summer Games Community Standards and the Fan Content Policy, and may not sublicense the clip beyond the distribution channels used to share it. Summer receives a non exclusive license to store, process, moderate and display the clip on the Platform in order to operate, moderate and secure the Services, and to use it to promote the Services on Summer's own channels, from which a Creator may opt a Game out under the Summer Games Terms of Service. Neither license is perpetual or irrevocable as against a Player who deletes the clip, and neither extends to training any model. Creators keep their intellectual property in the Game shown in a clip under the Summer Games Terms of Service.
5A.4. Processing and retention. When you create a clip, a copy is uploaded to Summer's servers for processing (transcoding, moderation and, if you choose, sharing). The Summer Games Privacy Policy applies to Personal Information in a clip, clips are Communications for the purposes of Section 5 of that Policy, and clips you do not publish are deleted on the schedule in the Data Retention and Deletion Policy.
5A.5. Community Standards apply. Any clip shared on the Platform is subject to the Summer Games Community Standards, and Summer may remove a clip and act on the Account that shared it if the clip poses a risk of harm, exposes another User's Personal Information, or violates those Standards.

## 6. What we collect

6.1. Depending on the feature, an AI conversation record can include: (a) your text Prompts and the AI's text responses; (b) voice audio you speak to the feature while the indicator is displayed; (c) transcripts generated from that audio; (d) the context the feature operates on, such as Editor project context (Section 2.1) or the in Game state an AI NPC needs to respond (location in the Game, the Player's display name, recent in Game events); (e) session metadata (timestamps, feature and model identifiers, device and client version, error states); and (f) your feedback on responses, such as ratings.
6.2. We do not collect voice audio when no voice session is active, and AI Tools do not read project content beyond what the feature discloses at the point of use.
6.3. AI conversation records are associated with your Account so that we can provide history features, enforce the AI Acceptable Use Policy, and honor your deletion rights.

## 7. How we use conversations

7.1. We use AI conversation records to: (a) provide and operate the feature, including maintaining conversation context and history; (b) enforce safety, including automated scanning of Prompts and outputs under the AI Acceptable Use Policy and the Summer Games Community Standards; (c) investigate abuse, fraud, and security incidents; (d) debug and improve the reliability of the feature, such as diagnosing why a response failed; (e) comply with law; and (f) with your separate opt in only, the training uses described in Section 8.
7.2. We do not use the content of your AI conversations for advertising, and we do not sell it.
7.3. Human review. A limited sample of AI conversation records may be reviewed by trained Summer personnel or vetted contractors under confidentiality obligations, for the purposes in Section 7.1(b) through (d): safety escalations, abuse investigations, and quality diagnosis. Reviewers work in access controlled tooling, and conversations of Users we know to be under 18 are reviewed under heightened controls described in the Child Safety and CSAE Policy. If you contact support about an AI feature, support personnel may review the specific conversations relevant to your report. Quality diagnosis sampling under Section 7.1(d) excludes conversations of Users we know to be under 18; safety, abuse and support review of those conversations continues under the heightened controls described above.
7.4. AI Model Providers and service providers. The AI Tools are powered in part by third party AI Model Providers, currently Anthropic, OpenAI, Google and the other model developers reached through the Vercel AI Gateway (including DeepSeek-family models), [fal.ai](https://fal.ai) and the media-generation models it hosts (including Meshy), and ElevenLabs, as published and updated at [summerengine.com/legal/subprocessors](https://summerengine.com/legal/subprocessors). We send a provider only the Prompt, the disclosed context and the conversation history needed for the response. Our contracts prohibit these providers from using your Prompts, context, outputs or any other Summer content to train or improve their models, restrict their use to providing the service to Summer, and require deletion after processing or retention of no more than 30 days (zero data retention where the provider offers it). Other service providers that host or process AI workloads for us act under contracts limiting them to processing on our instructions, as described in the Summer Games Privacy Policy.

## 8. No foundation model training without opt in

8.1. Your AI conversations, including copilot conversations that contain your private project content, are not used to train foundation models by default. The baseline license you grant Summer covers hosting, operating, moderating, and securing the Services, as stated in the Summer Games Terms of Service and the AI Features and Generated Content Terms; it does not cover foundation model training.
8.2. Summer operates an explicit opt in program for Creators who choose to contribute content, which may include copilot conversations, to model training. The program's scope, controls, and withdrawal terms are stated in the AI Features and Generated Content Terms. If you have not opted in, nothing in this Notice enrolls you.
8.3. Section 8.1 does not prevent the uses in Section 7.1(a) through (e), including evaluating and fixing model behavior on specific failures, which does not involve adding your conversations to a training corpus. Conversations that our safety systems flag, or that a User reports, may also be used to evaluate and improve Summer's own safety classifiers and filters, with Account identifiers minimized where the review purpose allows; that use is not foundation model training, is never shared with an AI Model Provider for that provider's training, and never extends to your private, unflagged content.

## 9. How to decline or limit recording

9.1. Voice. If you do not want your voice recorded, do not use voice features. Every AI Tool with a voice mode also works by text, and declining voice never removes text access.
9.2. AI NPC encounters. Entry notices under Section 5.2 always offer a path that avoids capture: decline, mute, or leave. Games that make an AI NPC conversation mandatory to progress must still honor the text alternative where the Player has declined voice.
9.3. Copilot. You can clear your copilot conversation history in the Editor, which deletes it on the schedule in Section 11. You can also start a session without project context sharing where the feature offers a restricted mode, as described at the point of use.
9.4. Deleting your Account deletes your AI conversation records on the schedule in the Data Retention and Deletion Policy, subject to the legal hold and safety exceptions stated there.
9.5. Declining recording features is never penalized. It does not affect your Account standing, your Sparks, your Earned Sparks, your eligibility for the Summer Creator Program, or the discoverability of your Games.

## 10. Users age 13 to 17

10.1. For Users we know to be 13 to 17: (a) realtime voice conversation with AI NPCs is not offered to Users under 18 at all (Section 2.2); where a Game's voice chat can be heard by an AI NPC, that voice chat is off by default for every 13 to 17 Account and can be turned on only after an Age Check and a linked parent's approval of a Consent Request under the Parent Account Terms Section 5.2(d), and the parent can turn it off again at any time; (b) chat and social defaults remain private and trusted connections only, as stated in the Summer Games Terms of Service, and AI features do not widen them; (c) the content of AI conversations is never used for advertising of any kind, consistent with the Platform wide rule against targeted advertising to known minors; and (d) human review occurs under the heightened controls in Section 7.3, and quality diagnosis sampling under Section 7.1(d) excludes their conversations.
10.2. A parent or guardian with a linked Parent Account can view which AI features are enabled on the minor's Account, turn off voice chat where a Game offers it (which also keeps the minor's voice out of any AI NPC's disclosed range), and request deletion of the minor's AI conversation records as described in the Parent Account Terms and the Summer Games Privacy Policy.
10.3. AI Tools are instructed and monitored to avoid content inappropriate for the User's age category under the Content Maturity Policy. This is a moderation measure, not a guarantee; the reporting channel in Section 14 applies.

## 11. Retention

11.1. Retention periods for AI conversation records are stated in the Data Retention and Deletion Policy. In summary, and subject to that policy's stated exceptions for legal holds, safety investigations, and CSAE preservation obligations under the Child Safety and CSAE Policy: (a) raw voice audio is retained only as long as needed to produce a transcript and verify its quality, and is deleted within 30 days of capture; (b) transcripts and text conversations are retained for the AI conversation log period stated in the Data Retention and Deletion Policy (currently 90 days from the conversation, a bracketed working default there) or until you delete them under Section 9.3, whichever is earlier, except that safety scanning extracts and enforcement records may be retained longer as stated in the Data Retention and Deletion Policy; and (c) session metadata is retained on the standard operational log schedule stated there.
11.2. Conversations quoted in an enforcement action (for example, in a moderation decision under the Summer Games Community Standards) are retained as part of the enforcement record for as long as that record is retained.

## 12. Creator obligations for AI NPCs

12.1. Creators who add AI NPCs or other conversation capable AI Tools to their Games must: (a) leave the platform provided entry notices, indicators, and consent surfaces intact and unobstructed; (b) not configure any AI Tool to capture voice or text outside its disclosed context or range; (c) not present an AI NPC as a human User, and not suppress, obscure or contradict the AI disclosure that the Platform renders at the start of every AI NPC interaction and, for Users we know to be under 18, repeats at least every three hours of continuous interaction; and (d) comply with the AI Acceptable Use Policy and the Developer Tooling and API Terms. AI NPCs must be identifiable as AI in their disclosed context.
12.2. Violations are enforced under the Summer Games Community Standards and the Summer Games Terms of Service, and can result in removal of the Game and Account action. Where removal of a Game containing purchased Virtual Content occurs, the credit provisions of the Refund and Billing Policy apply.
12.3. Creators do not receive raw voice audio of Players from platform AI NPC systems. What conversation derived signals, if any, a Game can access is stated in the Developer Tooling and API Terms, and is limited to what the entry notice for that Game disclosed.

## 13. Do not share sensitive information with AI Tools

13.1. AI Tools are not a channel for confidences. Do not tell an AI Tool passwords, payment card numbers, government identification numbers, health information, or other sensitive personal information, whether yours or anyone else's. Conversations are recorded, scanned for safety, and sampled for human review as this Notice describes, and information you volunteer enters those records.
13.2. If you inadvertently submit sensitive information, you can delete the conversation under Section 9.3, and you may contact us at the address in Section 16 to request expedited deletion.

## 14. Safety escalations

14.1. Automated scanning and human review under Section 7 can surface imminent threats of harm, child sexual abuse and exploitation material or conduct, and other emergencies. We handle these under the Child Safety and CSAE Policy and the Law Enforcement Guidelines, which describe when we preserve records, when we report to the National Center for Missing and Exploited Children, and when we contact law enforcement.
14.2. To report a harmful AI interaction, including an AI NPC behaving inappropriately, use the in product report control on the conversation, or the channel identified in the Summer Games Community Standards.

## 15. Changes to this notice

15.1. We will update this Notice before AI NPC recording features launch (Section 2.2), before any material expansion of what AI Tools record, and before any change to the training default in Section 8. Material changes are announced in product and by email, and Section 4.3 requires fresh point of use consent where what a feature records has materially changed. The current version always lives at the Platform's legal pages alongside the Summer Games Terms of Service.

## 16. Contact

16.1. Questions and requests under this Notice: [support@summerengine.com](mailto:support@summerengine.com), or by mail to Summer Labs, Inc., Attn: Legal, 2810 N Church St, STE 89812, Wilmington, DE 19802, United States.
