On-device by default
Anonymous profiles, events, analyses, and reviews stay in this browser.
Privacy / Plain Language / v1.0
Privacy Notice
First, a clear map of where your data goes. Relationship journals stay in your browser by default. Voice, Agent, and analytics services connect only after a deliberate action or opt-in.
Updated Aug 13, 2026 · Beta
Processed when sent
Signing in or opening the site does not automatically upload voice or Agent content.
Separated by account
Vector knowledge is scoped to one account. The Agent cannot search another user’s profiles.
Your controls remain
Export or clear local data, withdraw AI consent, and change analytics preferences.
00 / Scope
What this covers
This notice applies to the GAME Signal Lab beta at rsdgame.online, including its website, account features, speech recognition, relationship-reflection Agent, and opt-in usage analytics. The product is intended only for adults aged 18 or over.
We design for specific purposes, minimum necessary data, transparency, and user control. Relationship notes may contain information about someone else. Use aliases and do not enter names, account handles, addresses, precise locations, identity documents, or unnecessary full chat logs.
01 / Data Map
How data moves
Local relationship journal
Anonymous profiles, events, structured analyses, reviews, and preferences live in browser storage. Their full text stays on this device unless you deliberately use a connected feature.
Account and access
The server processes a username, password verifier, session, membership state, AI allowance, consent state, and limited security-audit metadata.
Agent and story conversations
Only text you actively send enters a model request. Messages and model responses are archived in encrypted form; minimum anonymous profile fields enter your account-isolated vector store.
Speech recognition
After recording ends, audio goes temporarily to local self-hosted FunASR only, with no cloud fallback. The site does not attach audio files to your relationship journal. A transcript returns to the composer for your review before sending.
02 / Details
Processing details
| Local data | Alias-based profiles, interaction events, your interpretations and feelings, analyses, reviews, and settings. It remains until you clear browser data, clear local data in the app, or remove the site’s storage. |
|---|---|
| Account data | Username, password verifier, login sessions, membership and grants, the included 50-call AI counter, consent records, and service audits. Used for authentication, security, access control, and troubleshooting. |
| AI content | Messages you intentionally send, model replies, and minimum anonymous profile fields you agree to sync. Message archives use AES-256-GCM encryption. Authorized support access is recorded in audit logs. |
| Opt-in analytics | Google Analytics 4 loads only after you allow it. It processes pages, locale, feature-completion events, session statistics, approximate location, and browser/device information, and may use the first-party `_ga` cookie to distinguish browsers. It does not receive journal text, profile content, recordings, AI messages, usernames, or GAME user IDs. Google Signals and advertising personalization are disabled. |
| Technical logs | To prevent abuse, keep sessions working, and diagnose failures, the service may process request time, status, request identifier, and necessary security metadata. Application audit tables do not store local journal text, system prompts, IP addresses, or browser identifiers. |
Important: if you voluntarily include identifying details in text or audio, those details may enter a speech-recognition or Agent request that you initiate. Use aliases and the smallest amount of context that works.
03 / Providers
Service providers
DeepSeek
Generates story follow-up questions, organizes profiles, and supports relationship reflection. It receives only text you explicitly send and the minimum context needed for that request. The provider processes API requests under its developer-service terms and data rules. See the official DeepSeek privacy policy.
Local FunASR
Local self-hosted FunASR is the only speech-recognition route. Failures return an error and never send audio to a cloud provider. Audio is used to complete that transcription and is not saved as a relationship-journal attachment.
Google Analytics 4
Helps us understand acquisition and feature completion. Its script does not load before you opt in, and you can change that choice from Privacy & Data. See Google’s Analytics data safeguards.
04 / Security
Isolation and security
- Passwords are not stored as plaintext; sessions use secure cookies and same-origin request protection.
- DeepSeek API keys are encrypted on the server and never embedded in client code.
- Every vector query is scoped by user so one account cannot retrieve another account’s profiles.
- Explicit conversation archives are encrypted; administrator access and permission changes are audited.
- No system is perfectly secure. Avoid entering sensitive information on shared devices, public browsers, or networks you do not control.
05 / Your Choices
Your choices and rights
Manage local data
From Privacy & Data in the app, you can export a JSON backup, import a backup, or clear all local records in the current browser.
Withdraw external-AI consent
After withdrawal, new Agent requests are blocked and your account-isolated knowledge base is cleared. Your local journal in this browser is unchanged.
Manage analytics
You can decline or reopen Google Analytics preferences. Declining does not affect journaling, profiles, or core Agent features.
Make a data request
During the beta, request access, correction, or deletion of account-side data through the official channel that delivered your testing invitation. To avoid deleting the wrong account, we may first verify account control.
06 / Retention
Retention and updates
You control local retention, and that data remains until you clear it. Account, allowance, encrypted conversation, and necessary audit records are retained while the beta account exists and as needed to operate, secure, and troubleshoot the service. Withdrawing AI consent immediately stops new AI processing and clears the isolated knowledge base. External providers retain logs under their respective developer-service terms.
If data categories, purposes, providers, or user choices materially change, we will update the version and date and request fresh consent where needed. Continuing to use ordinary on-device journaling does not automatically mean you accept new external-AI processing.