Alongkind companion app · Updated 15 October 2026

Chat privacy and storage

Chat history is saved in your browser. Sending a message also uses Alongkind’s server and OpenAI to generate a reply. This is not an entirely device-only conversation.

What happens when you press Send

The app sends the current conversation, including its attached images, and the active companion’s settings to Alongkind’s server, hosted using Cloudflare. The server forwards the companion’s name, tone and purpose, up to 12 recent messages and the latest message’s attached photo to OpenAI for a reply. Earlier images in the conversation are not forwarded to OpenAI by this route. Your new message may therefore cause earlier messages to be sent again as context.

Choosing a photo makes a local preview. Chat processing starts when you press Send. Consider everyone pictured before sharing a photograph. Avoid sending passwords, financial details or other information you do not want processed remotely.

What stays in this browser

Sent messages, replies and attached chat photos are saved in browser storage, including a sent message when a reply fails. Companion settings saved with “Remember on this device” also stay in this browser. Browser storage is not encrypted by the app. Someone with access to this browser profile may be able to read it; use care on shared devices.

The creator’s companion-saving and growth choices are separate from chat processing and chat-history storage. Turning those choices off does not make chat device-only or prevent the conversation history from being saved when you send messages.

Retention and removing a conversation

“Start again” replaces the active conversation history in this browser. Removing a saved companion removes its associated local conversation. These actions do not request deletion from OpenAI, Cloudflare, service logs or provider backups.

Alongkind has not established a verified provider-wide deletion deadline or a no-retention guarantee for this chat service. Local storage is not a backup: clearing browser data or changing browser profiles can make saved companions and chats unavailable.

Encrypted file backups and Google sign-in

Encrypted companion file backups contain settings, not chat messages or photographs. They require Google sign-in and a passphrase. Firebase Authentication and reCAPTCHA Enterprise provide account and application checks. The passphrase is used in the browser and is not saved by the backup flow; keep it safely because it cannot be recovered.

Cloud account backups are not available in this release. A downloaded encrypted file must be kept by you and imported with the same account and passphrase. Downloading a settings backup does not preserve conversation history.

Separate services and child-use limits

Deep Drive is a separate memory beta with its own privacy and access notice. Saving a chat photo does not transfer it to Deep Drive or Legacy. The username and synthetic guardian receipt trials do not prove safeguards across this companion chat.

Life-stage categories are catalogue filters, not age verification or parent PIN locks. Young Explorer and child-focused designs are previews, not approved for unsupervised child use.

Questions about your information

Contact bendyson@alongkind.com for access, correction or deletion questions. Do not email passwords, sign-in tokens or private photographs to explain a problem.