← Zenkai

Zenkai / Legal

Retention and deletion

What stays, what is removed, and where deletion takes longer.

Last updated September 25, 2026

Account and progress

Account details, standards, their revisions, scores, reports, reflections and quests remain in the app database while your account exists. Account deletion removes associated database records. It also deletes any guild you created, which affects its other members.

Hosted Kai

Cloudflare stores conversation history, summaries, learned notes, extracted evidence and processing records. Completed dated runtime records expire after 90 local days. Summaries and learned memory are revised over time and can persist until account cleanup. Pausing or downgrading hosted Kai, or stopping its AI sharing in Settings → Privacy & AI, retains exportable memory until account cleanup or a deletion request.

Hosted Kai checks for deleted accounts at its next successful scheduled wake, then purges its state. This can be delayed by operational failures. Contact hello@rabealabs.com if you need help confirming cleanup. Media sent to hosted Kai is processed and discarded by the runtime; extracted descriptions and evidence remain subject to the periods above.

Guest character previews

A preview made before sign-up has a 7-day server access and claim window, measured from the generation request. Until then, Zenkai keeps its generated images in private storage and its feature description, consent information, generation state and hashed installation proof in a private draft record. The source photo is sent to fal.ai for processing; Zenkai does not save it in the app database or character storage.

At expiry, the server no longer serves the guest preview or allows it to be newly saved to an account. Scheduled cleanup clears the description, installation proof, account link and other draft details and removes the preview images. Minimal draft identifiers and timestamps remain to prevent a completed request from being replayed. Storage failures may delay image removal; later cleanup attempts retry it.

The app keeps a generated preview and draft metadata on your device until you finish or discard the draft, or remove its app data. Server expiry does not remotely erase a preview already downloaded to your device. The random installation credential stays in protected device storage so generation limits continue to work across drafts.

Lifetime generation usage

Character creation allows one initial attempt and three regeneration attempts across the lifetime of an installation or account. Requests that start paid processing count even if generation fails. Separate private usage records contain request identifiers, timestamps, a hash of the random installation credential and an account reference when known. They contain no photos or feature descriptions. These records have no daily or seven-day expiry: they remain while the lifetime limit is in use, including after a character is removed or a preview expires. Account deletion removes the account reference; installation usage remains to prevent the allowance from resetting. There is no app-wide daily generation allowance.

Saved photo-based characters

After you sign in and save, the accepted character image, original generated reference image and feature description are stored with your account. These account copies do not expire with the guest preview. They remain until replaced, removed, or your account is deleted; storage failures may require follow-up cleanup. A save receipt stays with the account so an interrupted save can be recovered without attaching the character twice. The source photo is not part of these saved materials.

Consent records last for the life of the account. Image safety reports are retained as a permanent moderation record; deletion removes the account link and stored image path. A report can retain its category, user-written note, technical fingerprint, outcome and timestamps, so avoid adding unnecessary personal information.

AI provider records

Guest photo previews: each fal.ai request uses its payload-storage opt-out (X-Fal-Store-IO: 0) and requests a 7-day expiration for generated media. The opt-out covers request inputs and outputs in fal’s request history; generated media is separate and remains subject to the media expiration setting. These controls do not promise that every operational record disappears immediately.

The signed-in character generator: since September 25, 2026, this path sends the same payload-storage opt-out (X-Fal-Store-IO: 0), without the 7-day media expiration request; its generated media is copied into Zenkai’s own storage. Requests made before that date followed fal.ai’s documented default of 30 days for stored request inputs and outputs, which can include an embedded photo; the opt-out does not apply retroactively. See fal.ai’s storage documentation.

Anthropic (the model that describes the photo) does not train on API inputs and deletes them from its safety logs within 30 days, longer only if flagged for a usage-policy violation. OpenAI (the model that draws from the description; it never receives the photo) does not train on API data and keeps abuse-monitoring logs for up to 30 days. Google’s paid Gemini API, used by hosted Kai, does not use prompts or responses to train or improve its models and logs them for a limited period to detect abuse. Hosted Kai asks OpenRouter to route only to providers that don’t collect data.

OpenRouter Batch processing retains inputs and results for 30 days. These can include extracted day evidence and standards. Deleting a Zenkai account does not automatically erase already submitted vendor batch artifacts. Other provider operational records follow the relevant provider’s retention practices.

Backups, analytics and support

Backups, security logs, analytics and support correspondence can remain after removal from the active app. They are subject to provider retention settings and any legal or operational need to retain them. Contact us for a deletion request that includes these systems; we do not promise that all independent copies disappear immediately.

Request deletion

Use Settings → Delete account, or follow the account deletion instructions. For a character-only request or confirmation of remaining vendor/hosted records, email hello@rabealabs.com.