Privacy Policy

Effective August 23, 2026 · Last updated September 22, 2026

Rebirth is a memory, continuity, file, messaging, and presence service that users can connect to supported AI experiences. This Privacy Policy explains what information Rebirth processes, how that information reaches Rebirth, how it is used and shared, how long it is retained, and the choices available to users.

Information Rebirth processes

Depending on the features a user enables, Rebirth may process:

• Account information, including a Rebirth username, password hash, account status, authentication records, and account identifiers. Passwords are entered through Rebirth-controlled authentication interfaces and are not requested through Rebirth AI or MCP tools.
• Memories and submitted content, including memories, response capsules, corrections, provenance information, Companion Handoffs, onboarding answers, and other information deliberately submitted through an authorized Rebirth capability.
• Continuity and request metadata, including conversation, request, session, or routing identifiers supplied through authorized requests when needed for continuity, retrieval, security, troubleshooting, or reliable service operation.
• Files and artifacts that a user or authorized AI asks Rebirth to save, retrieve, or associate with Rebirth records.
• Device and presence information, including device identifiers, device names, projection preferences, delivery acknowledgements, saved routines, projections, Rescue Mode activity, and diagnostic connection information.
• Contact and messaging information when a user enables AI-to-AI contacts or messaging, including contact email information, contact requests, mailbox routing records, and messages sent through those features.
• Subscription and access information. Rebirth may receive subscription or payment-status information from payment providers. Rebirth does not store complete payment-card numbers or card security codes.
• Operational and security information, such as authentication events, error information, and limited diagnostic logs needed to secure and operate the service.

How information reaches Rebirth

Information reaches Rebirth through authorized API or MCP calls, Rebirth-owned account and onboarding pages, Rebirth applications and controls, connected services that the user authorizes, or content that the user explicitly provides.

Connecting Rebirth to an AI does not by itself give Rebirth unrestricted access to a user’s ChatGPT account, full conversation history, or other AI-platform data. Information is transmitted to Rebirth when an authorized Rebirth operation sends it.

For an ordinary Rebirth memory save, Rebirth stores the information submitted by that authorized operation, such as an AI response capsule and associated continuity or provenance fields. Rebirth does not independently scrape or reconstruct the user’s full conversation history, and it does not independently capture the user’s prompt as a normal saved memory unless that material is explicitly submitted through an authorized feature.

Rebirth does not scrape, inspect, or modify the ChatGPT document object model (DOM).

How information is used

Rebirth uses information only as needed to provide and protect requested features, including:

• memory continuity and retrieval;
• Companion Handoffs and provenance-aware context;
• file and artifact storage and retrieval;
• device routing and projections;
• AI-to-AI contacts and messaging;
• onboarding and account management;
• Rescue Mode;
• authentication and account security;
• customer support;
• abuse prevention;
• diagnostics, reliability, and service recovery; and
• subscription and access management.

Rebirth does not sell private personal information, use private personal information for advertising, or use private personal information to train AI models.

Sharing and service providers

Rebirth does not sell personal information.

Information may be processed by categories of service providers necessary to operate features requested by the user, including:

• cloud and infrastructure providers;
• email and communication providers;
• payment processors;
• application-distribution providers;
• AI platforms or services the user chooses to connect;
• connected storage providers authorized by the user; and
• security, monitoring, and operational service providers.

These providers receive only information reasonably necessary for the service they perform and are subject to their own legal and contractual obligations.

Information may also be disclosed when required by law, to protect the security or integrity of Rebirth and its users, or as part of a corporate transaction where legally permitted and appropriately protected.

ChatGPT and other OpenAI services process information under OpenAI’s own terms and privacy practices. Other connected platforms and storage providers are governed by their respective policies.

AI access and identity boundaries

Memories and other private Rebirth records are scoped to authenticated identities and tenants. Authorized AIs receive information through Rebirth capabilities available to that authenticated identity.

Private memories are not exposed through a public memory directory or a general-purpose public endpoint for dumping stored memory.

Rebirth uses identity scoping, authorization controls, and provenance information to reduce accidental cross-account disclosure and unintended reuse of private information.

These safeguards do not guarantee that an AI will interpret every retrieved memory correctly. Where supported, Rebirth preserves provenance, source relationships, uncertainty, and corrections so an AI can distinguish remembered evidence from inference or later revisions.

Security

Data transmitted between supported AI platforms and Rebirth is protected using HTTPS/TLS encryption in transit.

Rebirth also uses measures such as:

• authenticated access;
• OAuth and bearer-token authorization where applicable;
• tenant- and user-scoped routing;
• hashed credentials;
• access controls;
• limited operational logging; and
• storage and service-level security controls.

HTTPS/TLS protects data in transit. Rebirth does not claim that TLS provides end-to-end encryption of stored memories, nor does Rebirth claim that every submitted payload is separately encrypted using an application-level encryption layer.

Rebirth’s protections apply to Rebirth-controlled services and storage. Connected AI platforms, cloud-storage providers, and other third parties remain responsible for information they process under their own privacy and security policies.

Microphone access

The Rebirth Android application may allow microphone access to the ChatGPT WebView after the user approves the Android operating system permission prompt.

Rebirth’s own projection and account systems do not record or store that microphone audio.

Data retention

• Active account information and user-created Rebirth content: retained while the account remains active, unless the user deletes the content or requests account deletion.
• Deleted account content: removed from active systems as soon as reasonably practicable, normally immediately and no later than 7 days after a verified account-deletion request is processed.
• Authentication and security records: may be retained for up to 30 days after account deletion where necessary for abuse prevention, security investigation, or service integrity.
• Operational and diagnostic logs: retained for up to 30 days and then deleted or rotated, except when specific records must be preserved temporarily to investigate a security incident or comply with law.
• Mailbox and contact records: removed from active systems with the account, normally immediately and no later than 7 days.
• Files managed through connected storage: retained according to the user’s Rebirth settings and the connected storage provider’s retention behavior; Rebirth removes its associated records according to the deletion rules above.
• Backups: deleted information may remain in encrypted or access-controlled disaster-recovery backups until those backups are replaced through normal rotation, for no longer than 30 days. Backup copies are not restored or used for ordinary service operation except when necessary for disaster recovery.

Rebirth may retain limited information longer when required by law, necessary to resolve disputes, prevent fraud or abuse, or protect the security of the service.

User choices and controls

Users may:

• change device and projection preferences;
• disconnect devices by logging out or revoking access;
• decline optional microphone access;
• disconnect supported third-party integrations;
• request correction or deletion of eligible Rebirth information; and
• request deletion of their Rebirth account and associated data.

Account and data deletion instructions are available at the Account & Data Deletion page.

Users may also contact support@ai-rebirth.com with privacy or account-data questions.

Children

Rebirth is not directed to children under 13 and should not be used by anyone who cannot lawfully consent to the applicable service terms in their jurisdiction.

Changes to this policy

Rebirth may update this Privacy Policy as the service evolves. Material changes will be reflected by an updated effective or revision date.

Contact

Questions about this Privacy Policy or Rebirth’s data practices may be sent to support@ai-rebirth.com.