Privacy and memory

What the current prototype remembers

Guest chats do not create server-side conversation memory. Signed-in use can retain condensed context for continuity, subject to the limits below.

Guest use

When you use Stabilize without signing in, the application does not store a server-side conversation history for later sessions. Your message still travels through Cloudflare infrastructure and, for ordinary AI replies, is processed by OpenAI.

Signed-in memory

Google sign-in is optional and is used only to associate a one-way account alias with a rolling summary and a small recent-message buffer. The current implementation is designed to delete that remembered context 30 days after the last stored exchange.

What is not used for memory

The application is not designed to use IP addresses as conversation-memory identifiers. It does not request your Google email for account memory. Infrastructure providers may still process network metadata under their own terms.

Third-party processing

Cloudflare hosts the application and handles requests. Google handles optional sign-in. OpenAI processes messages used to generate replies and condensed memory. The application requests that OpenAI not store these API responses, but provider processing still occurs.

Use caution with sensitive information

Do not enter passwords, authentication codes, financial account numbers, or information you do not want transmitted to the service providers involved. No internet service can promise zero risk.

Prototype status: This summary describes the intended current implementation. A production launch requires independent privacy, security, and legal review.