Account, credits, and troubleshooting
Deletion, retention periods, and recovery
Seven-day recovery applies only to eligible recycled content. Collection removal, material deletion, and permanent clearing differ.
Open featureView recycled sessionsOn this page
Deletion is not hiding or collapsing
Collapse, filters, and layout changes affect display. Deletion affects formal content and availability; do not use it to adjust reading density.
Check names, counts, and relationships in confirmation and back up important files. Favorites are not recovery or independent backup; storage effects are explained separately.
Retention and restoration by operation
| Operation | Rule | Entry/scope |
|---|---|---|
| Delete canvas node/formal card | Currently seven days to recover; clearing/expiry ends recovery. | Restore batches from Cards/Canvas Trash. |
| Delete one output | Image and related downstream enter that window. | Upstream and siblings stay. |
| Delete session | Currently seven days. | Settings → Storage session recovery. |
| Remove inspiration | Immediately irreversible; history visible seven days. | Recollect from accessible eligible source as a new record. |
| Remove favorite | Only the relation is removed. | Re-favorite if source remains accessible. |
| Delete personal material | No promised canvas/session recovery window. | Other valid image references stay. |
| Delete custom folder | Organization only. | Materials remain in All; inspirations become Uncategorized. |
| Permanently clear Trash | No user restoration. | Not a second undo operation. |
| Clear removed inspiration | History is no longer viewable or restorable. | Later active recollections are unaffected. |
Session and canvas recovery
Why canvas deletion includes downstream
Connections express dependency. Deleting selected nodes/records can include related downstream, not merely remove a visual rectangle.
For reference → generation → output → outpaint, deleting the reference may affect the whole later path. Deleting an output affects its branch, not siblings or upstream.
Deleting the last output can leave its operation and Regenerate available; no image does not mean the whole record disappeared.
Queued/running tasks block related deletion. Wait for final status; deletion is not generation cancellation.
Notes anchored to deleted nodes become independent. Restoring nodes does not automatically re-anchor them.
Restore canvas/session, not canceled collections
These steps apply to eligible recycled batches and sessions. Recently removed inspiration has no restoration; source restoration does not revive removed collection.
An active collection not removed remains independent after source deletion. Restoring the source may restore location, not move canceled inspiration back.
- Find the correct batch/session and inspect name, scope, and remaining time.
- Check current storage, not the plan at deletion time.
- Confirm. Required parent batches may also need recovery; unrelated downstream is not all restored.
- Wait for success and inspect the workspace. A failure is not restoration; resolve capacity/dependency errors.
Before clearing or expiry
- Confirmed clearing is asynchronous with queued/running/success/failure states. Leaving does not cancel it.
- The confirmed target set excludes items recycled later; inspect completion.
- Cleared or expired content has no user recovery. Do not wait until the last day.
- The 1,500 canvas-node limit includes uncleared Trash nodes. Ordinary deletion does not free node slots; bytes and node counts differ.
- Recycled content itself does not count as member active storage. Check other valid references if usage stays; waiting seven days or immediate clearing is not mandatory.
Guests and deleted accounts are not archives
Standard guest lifetime is 180 days from creation without visit renewal. Register a new account to inherit important guest work; existing-account sign-in does not merge it.
Sign-out is not deletion. Account deletion is irreversible; re-registering the contact creates a new account, not old-workspace access.
Share links, favorites, and sidebar entries cannot extend a deleted source's recovery window.
Disconnect cloud storage and revoke access
- Open Settings → External connections, select Disconnect for the provider, and check the result. BANANAI removes stored credentials, connection details, and pending authorization state, and attempts remote revocation where supported.
- Disconnecting does not delete imported personal materials or files already backed up to the provider. Remove those copies separately in Personal materials or your cloud storage.
- You can also revoke BANANAI on the security or connected-app page of Google, Dropbox, Microsoft, or Baidu. BANANAI may not learn about provider-side revocation until the next request, so disconnect locally too.
Delete your entire account
Account content enters an inaccessible retention period of up to six months before physical removal, except transaction or security records that must be retained by law. This retention is not a user undo or recovery window. See the Privacy Policy for data-handling rules.
- Download or back up important originals, text, and creation records, and verify the files. Account deletion is not sign-out and has no seven-day canvas/session recovery entry.
- Open Settings → Account, choose Delete account, read the confirmation, and complete the confirmation required by the interface.
- Successful deletion signs you out immediately and removes access to the old account, its authentication identities, and cloud credentials. Registering the same contact again creates a new account, not access to the old workspace.
Request deletion when you cannot sign in
Contact support@bananai.com.cn from the email address bound to your account and specify account deletion or the particular data. Account ownership must be verified to prevent unauthorized deletion; sending an email does not complete deletion immediately.
Provide only information needed to handle the request. Do not send passwords, SMS/email codes, full payment-card details, or publish private creation content.
