Private, local-only tool

Keep what matters in your own words.

Draft a private continuity note before an app changes or disappears. The four-part starter works without JavaScript; the optional local generator can expand it.

Service-change and shutdown plan

What happens when an AI companion service changes or shuts down?

There is no universal outcome. Access to conversations, media, account controls, and paid features depends on what the provider still makes available. A product can remain online while its model or features change; a closure may include a short export window, or access may already be gone.

A note you write can preserve only your own summary. It cannot preserve or transfer the provider’s model, hidden memory, chat history, media, purchases, subscription, account state, settings, or product behavior.

Access still works

The product or model changed.

  • Read the provider’s current notice and check the settings that still exist.
  • Describe what changed in observable terms; do not assume the change is temporary, permanent, or universal.
  • Request any documented export and write your own continuity note before trialing another service or deleting anything.

A wind-down date is active

Treat the official date as a deadline.

  • Request the documented export now and save only material you are allowed and comfortable to keep.
  • Record the billing channel and renewal date; cancel renewal separately if that is your decision, then verify it.
  • Keep deletion last, after exports, receipts, refund questions, and your continuity note are settled.

Access is already unavailable

Separate recovery hopes from actions you can verify.

  • Check the provider’s official status, help, and announcement channels, then keep any receipts or confirmations you already have.
  • Use the actual web, Apple, Google, or other billing channel to inspect and stop renewal when appropriate.
  • Do not give a password or full export to an unofficial recovery service. No third-party checklist can recover provider-only state.

When access remains, use the reversible order: official notice and controls → documented export → your own summary → billing channel → cancellation verification → deletion last.

Why this checklist separates service access, models, and exports

Three first-party examples show why one outcome should not be assumed:

  1. New Computer’s Dot wind-down notice gave users a limited operating period and a settings-based data-request instruction.
  2. OpenAI’s model-retirement notice says existing conversations and projects defaulted to replacement models.
  3. OpenAI’s exported-conversation transfer limits distinguish reference access from a full account migration.

Sources checked 2026-07-17. These examples illustrate different service outcomes; they do not predict another provider’s future or prove that an export is complete, portable, or successfully delivered.

Works without JavaScript

Start a private continuity note.

Select and copy these four prompts into a note you control. Summarize only what helps you continue a conversation; this page does not save what you write.

1 · Relationship role

Define what this connection is.

What role, tone, and expectations matter most in this relationship?

Describe the relationship in your own words rather than relying on a provider’s label.

2 · Durable preferences

Keep the patterns that matter.

What communication style, recurring routines, likes, dislikes, or shared context should remain consistent?

Prefer a short summary over a pasted transcript or a list of every past interaction.

3 · Boundaries and non-transferable details

Say what should not carry forward.

What should a new service not assume, recreate, or receive?

Leave out real names, contact details, passwords, payment details, health information, and anything you do not want copied elsewhere.

4 · Restart note

Write the first message.

Who is this companion to you, what context matters now, and what should it ask before filling important gaps?

Treat this as an introduction to a new conversation—not proof that the old experience can be restored.

This is a continuity note—not a transfer. It is not a provider export, product-data backup, migration or transfer method, compatibility guarantee, or claim about any product. It cannot move a model, hidden memory, chat history, media, purchases, account data, or proprietary settings.

Keep the note only where you trust the privacy protections. Separately check the documented account controls; a documented route does not show what an export contains or prove that it succeeds.

Closing an account? Preserve only what you need, then follow the safer sequence for exporting, canceling, requesting a refund, and deleting. Those are separate actions. If you are leaving Replika, use the preservation-first Replika alternatives guide before making the irreversible decision.

Quick start

Start with four essentials

Every field is optional. Start with these four and add detail only where it would help you describe the context in your own words.

Use summaries, not full chat logs. Avoid real names, addresses, passwords, financial details, health information, or anything you would not want copied into another service.

Quick-start details
Add communication style, backstory, memories, routines, and a restart message (optional)

Your local result

Companion continuity brief

This local summary records the relationship context you choose so you can refer to it when starting a new conversation. It does not transfer or recreate the original product.

Privacy boundary

Nothing is sent to us or saved by this page. Copying places the brief on your device clipboard; downloading creates a local file. Clipboard sync, backups, and downloaded-file protection are controlled by your device.

Add the details you want to preserve. Your continuity brief will appear here.

What this note cannot transfer

It cannot export a provider’s model, hidden memory, media, account history, purchases, or proprietary character settings. Check the provider’s export and deletion documentation separately.