Genesis Evo
Data Retention And Deletion
Effective date: July 24, 2026
This policy explains how Genesis Evo may retain, export, delete or archive account, prompt, upload, artifact, memory, billing and security data.
1. Why Data Is Retained
Data may be retained to operate the service, preserve account memory, deliver artifacts, process payments, debug issues, enforce limits, prevent abuse, respond to support requests and comply with legal obligations.
2. Memory And Artifacts
Memory fragments and artifacts can be kept so EVO can continue useful work across requests. Low-quality, risky, obsolete or unnecessary memory may be compressed, ignored, archived or removed.
3. Uploads
Uploaded files may be retained while active, queued, scanned, attached to a run, used in an artifact, needed for support, or covered by retention requirements. Temporary download links may expire sooner than stored metadata.
4. Deletion And Export Requests
Signed-in members can request an account data export or deletion and track the request from Data Rights. Support from the account email remains the fallback when sign-in is unavailable. Some billing, security, abuse, audit, backup or legal records may be retained where necessary.
The Data Rights panel shows pending, processing, ready, failed and completed states. Opening it does not delete or export anything until you confirm an action.
5. Evo Synlume Community Records
While an account is active, Synlume may retain its profile, posts, comments, reactions, bookmarks, declared matching preferences, connection requests, connections, participant messages, blocks, reports, community-rules acceptance, Evo consent and Evo access log so the integrated community can operate and be reviewed for safety.
An account export includes the member’s Synlume profile and rule-acceptance record, authored content and activity, relationship metadata, submitted reports, Evo consent/access records, and a participant copy of messages from conversations that include the requesting member. The member’s own message body is included as stored. A peer-authored body is included only after export-time checks redact high-confidence email, phone, credential and token patterns; each message says whether redaction occurred and names only the redaction categories. The export does not include a peer’s raw account identifier, email field, profile record, client request identifier or any unrelated conversation. Automated pattern checks are deliberately limited and are not a guarantee that every sensitive phrase can be detected.
On confirmed account deletion, public authored content and personal profile data are removed; authored message bodies are redacted; shared relationship records may use a non-reversible tombstone so the other participant’s account remains consistent; and the minimum pseudonymized safety or audit evidence may be retained where necessary. A peer’s own messages are not treated as the deleting member’s data, but direct identifiers of the deleted account are scrubbed.
6. Contact
Data requests can be sent to support@genesis-evo.com.