A companion.
With boundaries.

Newbie pilot privacy notice

Newbie runs on a shared cloud host. Adding the app to a server activates access automatically, with separate memory, settings, and allowances for that server. Players need no API keys or separate hosting account and do not need to keep an operator's PC awake. Adding the app does not start voice listening: someone must join a voice channel and use /newbie join. This is a free pilot with customer billing disabled. Voice reliability across microphones and longer sessions is still being tested, and no availability or performance guarantee is made. Account-specific provider privacy settings have not been verified; see the provider section below.

Voice channel audio

When someone runs /newbie join, Newbie receives participants’ audio from that voice channel. The cloud service sends live channel audio over its private hosting network to a separate, temporary listening worker for that active server. This worker runs wake-name recognition in memory, has no Discord or AI-provider keys or access to saved notes, and is removed after the session. Each player does not need a local detector. Questions addressed to Newbie go to OpenAI for transcription, reasoning, and a spoken reply. Newbie does not save audio recordings or keep a background conversation diary. Replies are audible to everyone in the channel; answers are not private.

The GPT-Live hybrid backend keeps the same wake and permission controls. Addressed captures up to three seconds go directly to Live for a reply; longer captures first go to OpenAI transcription, and verified question text primes Live. This cutoff is a measured compatibility rule for captured audio bursts, not an OpenAI limit or a promise of faster replies. Research and actions still use Newbie's managed agent and host permission checks. The hosted pilot uses this backend; actual Discord acceptance remains tracked in the operator rollout record.

Live sessions explicitly use store:false. Newbie does not enable Live's saved recording or fork features, and does not keep a Live connection open for the whole party call. This does not promise zero retention by OpenAI; its processing and abuse-monitoring policies still apply.

Tell all participants how this works before joining. Do not invite Newbie into a channel without their knowledge. Members in Newbie’s active channel can use /newbie quiet to stop a reply or /newbie leave to end listening without Manage Server permission. A server manager can also disable Newbie. Wake recognition can make mistakes; avoid discussing sensitive information while she is present.

“Hey Newbie” and “Newbie” are supported. The Ask Newbie button or /newbie wake arms that participant for one question within fifteen seconds. /newbie followup enabled:true explicitly opts that person into an eight-second window after Newbie finishes playing a completed answer to them. Their next sentence in that window can go to OpenAI without another wake phrase. Other speakers are not armed. Follow-ups are off by default, last only for that voice session, and are revoked on leave. /newbie followup enabled:false turns them off. Quiet, reset, and interruption clear pending windows.

Questions, screenshots, and generated media

Recent addressed questions and answers provide temporary context. After leaving, the host can keep up to three bounded channel snapshots per server in RAM for up to one hour. Context can return only in the same server and channel. Reset, forgetting, restart, expiry, or data deletion clears this RAM context. Relevant permitted context and enabled saved notes can be sent to OpenAI to answer an addressed request. SDK tracing and local session-content logging are disabled.

Ordinary follow-up questions use recent conversation automatically; you do not need to enable automatic saved notes or ask her to remember each question. An interrupted question and completed generated speech may remain as clearly marked context, without claiming unfinished playback or tool work succeeded. Local recognition can supply a marked temporary approximation, but cannot authorize automatic long-term memory. The legacy Realtime backend may retain an input-only connection for up to 1.5 seconds to correct its latest approximation; this cannot invoke tools or save notes.

Cloud conversation history

Cloud conversation history is on by default for each person while the server allows saved memory. The default applies to new requests you address to Newbie. Earlier conversations are not added to the archive. Use /newbie history enabled:false to turn it off for this server and /newbie history enabled:true to turn it back on. On the managed Agents backend, OpenAI stores addressed text, Newbie's answers, and associated tool exchanges so your conversation can resume after Newbie leaves, updates, or restarts. A separate remote session is used for each server, voice channel, and speaker. Another participant does not inherit your remote session or its personal tool results. Replies are still spoken aloud to the channel.

On the Live backend, that same choice permits a separate text-only OpenAI Conversations archive of completed addressed questions and spoken answers. This archive does not store audio and does not replace or overwrite existing native managed history. Its ownership, fixed seven-day deadline and reset/opt-out/deletion controls are the same. Local storage holds only routing, expiry and append/deletion receipts; cloud dialogue is not copied into the host database. With history off, ordinary Live dialogue uses bounded RAM without creating this persistent archive. Delegated requests and screenshots retain the managed processing rules below. Cloud history and exports are bounded; reaching a save limit can prevent a completed reply from being stored.

Newbie permits reuse for a fixed seven days from each session's creation. New questions do not extend that deadline. Expiry immediately blocks further reuse and queues deletion at OpenAI. Provider deletion can take longer if the provider or host is unavailable. Reset clears all participants' remote conversations in the active channel. Saved notes and history preferences remain, so a later addressed question can start a new session. Forgetting a note also invalidates conversation sessions that could contain recalled copies.

/newbie history enabled:false stops persistent history for you and immediately blocks reuse of your sessions in every channel of this server. Their IDs remain in a deletion queue until remote deletion is acknowledged. The queue contains routing identifiers and retry state, not conversation text. Deletion is retried after failures and across host restarts. If tracking capacity is exhausted, Newbie refuses new managed sessions rather than creating untracked history.

These controls invalidate both native managed history and the Live text archive together. OpenAI's Conversation deletion does not erase its items, so Live archive cleanup deletes individual items before deleting their container. An uncertain or late text write remains tracked until it can be reconciled and erased; it is not automatically repeated or reported as deleted without confirmation. Provider outages can delay this work after reuse has already been blocked.

With history off, successful managed voice requests may reuse a temporary remote session only for the same speaker, server, channel, and current host process during the call. Reuse expires after five idle minutes; leaving or a host restart ends it. These temporary sessions can contain recent addressed text and tool exchanges. Their reuse ends when you leave the call or Newbie restarts. Expiry, leave, failure, cancellation, reset, or opt-out blocks reuse and queues deletion. Manually uploaded screenshots use separate disposable sessions, queued for deletion after that turn even when cloud history is enabled. A remote creation whose result is uncertain is retained as a content-free reconciliation ticket until it can be found and deleted; a missing search result does not prove deletion. Provider deletion can take longer during outages. This is request processing, not a promise of zero provider retention.

Use /newbie history to inspect your choice and /newbie history export:true for a private, bounded JSON export of your available question and reply text in this server. The export excludes other members' sessions, internal tool records, audio, and credentials; a size-limited export may omit older text. /newbie export-data remains the separate export for owned saved notes. You can manage your history choice and request exports while Newbie is disconnected or disabled, without Manage Server permission.

Automatic saved notes, cloud conversation history, and wake-free follow-up mode have separate controls. Turning the server's Allow saved memory setting off pauses cloud history and queues existing sessions for deletion, including tool results that could contain recalled notes. Personal choices remain in effect when a manager turns the server setting back on. Provider abuse-monitoring logs, backups, and any posted Discord copies have their own retention and are not erased by a managed-session deletion request.

Manual screenshots attached with /newbie look are uploaded through Discord and sent to OpenAI for analysis. The bot does not write screenshot bytes to disk. On the managed backend they use separate disposable sessions, queued for remote deletion after the turn. Newbie does not watch Discord Go Live streams or continuously capture your screen. Choose screenshots carefully and obtain permission before sharing someone else’s information.

Web-search queries go to Exa. Requests to generate images go to OpenAI, and song requests go to ElevenLabs. Generated files are temporarily written on the host for delivery to the originating channel, then removed when the job finishes, fails, or is cancelled. Startup and hourly sweeps remove crash remnants once older than one hour. Discord attachments and provider processing follow their own policies. Deleting Newbie data does not remove copies already posted to Discord or held by a provider.

You can also ask for a song by starting a message with a direct @Newbie mention in the active voice channel's chat, while you are in that voice channel. The host checks that direct command, current membership, server access rules and allowances, then sends its song brief to ElevenLabs. This generation route does not send the message to OpenAI or add it to saved notes or cloud conversation history. Other channels, direct messages, bots, webhooks and ordinary unaddressed chat are ignored by this feature. The brief stays in RAM while its creation job runs. After a confirmed MP3 post, the song library retains the creation brief as described below; failed or cancelled jobs discard it. Discord keeps the original message and resulting MP3 under its own policies. Requests are bounded and rate-limited; duplicate delivery of the same message cannot start another song.

Finished songs start playing aloud to everyone in the original voice channel as soon as generation and fresh permission checks complete, while the requester is still present and authorized. The host streams the existing MP3 through a local decoder without another generation request, while the file uploads to chat. Ordinary party chatter and unused follow-up windows do not delay playback; music can take over an older Newbie reply, and a newer ready song replaces older music. Wake Newbie or use /newbie quiet to stop music; cancellation, reset, leaving, requester departure, and data deletion stop affected playback. A failed attachment upload does not stop music. The posted Discord MP3 remains a separate copy.

On an explicit spoken replay request, Newbie reuses an already-published song rather than generating another one. One MP3 can remain in RAM for at most one hour from creation or an explicit older-song retrieval; replay and reads do not extend that deadline. Leaving, reset, restart or relevant personal/server deletion clears this copy. Playback is limited to the current authorized voice channel and fresh permission checks.

After a successful MP3 post, the host saves a song-library record: its title (when present), original creation brief, duration, creation time, creator/server/channel IDs and exact Discord message/attachment references. It saves no audio or lyrics in this database. Records expire after a fixed 30 days, with at most 256 per server and 4,096 across the host; activity does not renew them. The library survives restarts and conversation resets and is separate from saved game notes and cloud conversation history. Those memory switches do not disable the library. Metadata is used only to locate a requested song, not inserted into ordinary conversation context. Any authorized current participant can search published titles; original briefs are searchable only by their creator or a current server manager. Your private data export includes your song records, and personal/server data deletion removes the corresponding records. Forgetting a personal note also clears your retained song briefs; forgetting a shared note clears server briefs conservatively while preserving attachment references.

When an older named song has no catalog match, an explicit replay request can inspect Newbie's own MP3 posts in the same channel from the last 30 days, bounded to 500 message metadata records and eight songs. It checks embedded titles first and may send generated MP3 audio to OpenAI transcription to find a unique lyric match. These lyrics remain transient and are not saved in the library, history or logs. A bounded lookup can fail to identify a song; it does not choose an arbitrary latest track when a name is missing or ambiguous. Generic latest-song fallback without a catalog record remains limited to 25 recent messages and a one-hour post age. All history access needs Read Message History permission. No general chat text is read or sent for these lookups. No new ElevenLabs generation or song-second debit occurs, although legacy transcription can incur OpenAI usage. Original prompts cannot be recovered for songs made before the library existed. A legacy post may not identify its human creator, so any personal deletion clears and stops that unattributed replay copy. Posted Discord files remain separate copies under Discord's retention; a later explicit request can retrieve them again unless removed from Discord.

Saved game notes

Saved memory is enabled by default for this pilot. Explicit requests to remember can save brief personal or shared server notes. Automatic game notes are on by default for each person while the server allows saved memory. Useful gaming preferences, roles, games, definite goals, plans, and progress may be saved from your own addressed requests with evidence from your current words. Use /newbie memory automatic:false to stop future automatic saves in this server and /newbie memory automatic:true to turn them back on. Background chatter, source quotes, full transcripts, guesses, sensitive details, and requests not to remember are excluded. Automatic party notes require a clear group goal, plan, or progress statement.

Each note belongs to a Discord user in a particular server. Personal notes are associated with their author; shared notes can help the party. Relevant notes may inform a spoken answer everyone in the channel hears. Do not ask Newbie to remember passwords, payment details, or another person’s private information.

/newbie memory privately lists your personal notes and all shared notes in this server, including shared notes written by other members. /newbie memory automatic:false stops future automatic saves and clears temporary context; it keeps existing notes and leaves explicit remember and recall available. /newbie forget removes an owned note and clears recent context. Server managers can also remove shared notes.

The host uses the OpenAI Agents SDK and a self-hosted Mem0 adapter. Canonical notes and ownership remain in the service database. Approved facts and short recall topics go to OpenAI’s embedding API; the separate server search index stores embeddings and references rather than another copy of note text. Relevant recalled notes may go to OpenAI for an answer. No hosted Mem0 account is used; Mem0 history and telemetry are disabled. Forgetting removes the live note and its search entry. If the optional index is unavailable, saved-note recall falls back to keyword matching.

A server manager can turn Allow saved memory off with /newbie settings. Off stops new saves and model recall of saved notes. Existing notes remain until deleted; owners can still inspect, export, and delete them. Temporary recent conversation remains separate from saved memory.

/newbie export-data returns a JSON file in a private Discord reply. It includes your automatic-memory choice, owned personal/shared notes, and owned song-library records including creation briefs for this server. Other owners’ notes and song briefs, credentials, audio, conversation transcripts, and provider records are excluded; use the separate history export for available cloud conversation text. /newbie delete-data scope:personal confirm:true removes your owned notes and song-library records, turns off automatic notes and cloud history for you in this server, invalidates your remote sessions, queues their deletion, cancels your pending creations, and clears recent RAM context. The host keeps the two off choices to honor them. Other members' remote histories remain unless shared notes you authored were removed: those shared facts may have appeared in any member's tool results, so the server's remote conversation sessions are rotated and remaining song briefs cleared too. Other members' saved notes and history choices remain. These personal controls do not require Manage Server permission and work when Newbie or saved memory is disabled.

Server managers can use /newbie delete-data scope:server confirm:true to remove saved notes, song-library records, memory/history choices, and settings, invalidate all server remote sessions, queue their deletion, and disconnect Newbie. The deletion queue survives removal of those settings. Content-free quota and usage totals remain as described below. Posted Discord messages and attachments remain separate copies.

Settings, usage, and backups

Server managers use /newbie setup and /newbie settings to review the voice notice and control enabled status, allowed channels, allowed roles, and saved memory. Web sign-in is not configured for this pilot. The prepared sign-in feature requests Discord identity and server lists without email; it keeps OAuth tokens server-side in sessions lasting at most two hours or until restart. Those account controls are currently unavailable on the website.

The host stores server settings, bounded song-library metadata and original briefs, explicit and automatic notes, per-person memory/history choices, remote-session routing and expiry metadata, deletion/reconciliation tickets, and content-free aggregate usage and allowance totals. Cloud conversation text is not copied into the host database. Accounting excludes question text and audio. It is retained for the current and two previous UTC calendar months, including after saved data deletion, to operate the pilot and prevent allowance resets. A content-free worker ledger stores random allocation references, machine identifiers, status and expiry times to recover from interrupted provisioning. It contains no audio, transcripts, player identifiers or worker authorization tokens. Diagnostic logs contain timings and outcomes rather than conversation text. Conversation-context checks record message counts, transcript-source labels, and interruption/correction/reset status without identity fields; other operational events can contain server identifiers or short speaker tags. Hosting providers may keep platform logs under their own policies.

Hosting volume snapshots are configured for five days. A one-off encrypted backup is also kept on the operator’s Windows PC until the operator removes it. These backups can contain earlier notes, song-library metadata and briefs, memory/history choices, session routing metadata, settings, and accounting. Forgetting or deleting data removes live canonical/index data but does not retroactively erase existing backups, provider records, or Discord copies. Any restore must be reviewed against later deletion requests before saved notes or remote session references become available again.

Website availability check

The homepage makes one request to Newbie’s cloud host to check whether shared voice capacity is available. It sends no Discord account or server ID, message, microphone data or cookies. The host receives ordinary connection metadata and uses a short-lived IP-based rate limit. The response contains only an availability label, without party names, server identifiers or occupancy counts. Hosting providers may retain platform logs under their own policies.

Provider retention and AI training

Newbie’s no-recording rule does not mean its providers retain nothing. Account-specific zero-retention or training opt-out arrangements have not been verified for this pilot. Do not treat it as a confidential channel.

OpenAI API data is not used for model training by default unless the customer opts in. Default abuse-monitoring logs may retain customer content for up to 30 days, subject to exceptions. Approved zero-retention controls are account-specific; this pilot makes no such promise. See https://developers.openai.com/api/docs/guides/your-data.

Exa directs customers seeking zero data retention to its Enterprise offering. This pilot does not promise zero retention for search queries. See https://exa.ai/docs/reference/security.

ElevenLabs retains data by default. Its listed zero-retention products do not include Music. Inputs may be used to improve models depending on account settings. This pilot does not promise music zero retention or a training opt-out. See https://elevenlabs.io/docs/eleven-api/resources/zero-retention-mode.mdx and https://help.elevenlabs.io/hc/en-us/articles/29952728805393-Is-my-data-used-to-improve-ElevenLabs-AI-models.

Discord hosts the voice connection, commands, messages, and attachments under its own policies and controls. See https://discord.com/privacy.

Privacy requests

Saved notes persist until deletion. Removing the bot stops new interactions but keeps saved notes and settings until explicitly deleted; use deletion controls first if you want them removed. Removing and reinstalling Newbie does not reset allowances. Provider and Discord copies must be managed through those services separately. For access, deletion, backup, or other privacy questions, contact the pilot operator using the contact below.