Version dated 16 September 2026. This page sets out the process for closing a personal Cicora Account and deleting or de-identifying related data. It supplements the Privacy Policy, Data Controls, Refund Rules, and, for a user working in an Organisation, the Business Data rules.
Account deletion is a separate action with consequences for sign-in, history, files, external-service connections, and available features. It is not an automatic subscription cancellation, automatic refund, waiver of a lawful refund, or a way to avoid payment, security, or legal obligations.
1. What can be deleted
A user may request deletion of their personal Account and related Personal Data that RIZZ TRADE processes for ordinary Cicora operation. Subject to what applies, the request covers:
- the profile, sign-in methods, active sessions, and personal settings;
- personal history, projects, files, saved instructions, or memory where they belong to that Account and the feature supports deletion;
- personal connections to external services that Cicora can technically disconnect;
- personal public links where the user owns and can control them; and
- data to be deleted or de-identified in response to a lawful request under applicable law.
Deletion does not guarantee destruction of objects owned by an Organisation, another Workspace participant, a public-link recipient, an external service, or a Model Provider. For those objects, Cicora determines its role and available assistance but cannot dispose of data beyond its rights, agreement, and the law.
2. Steps before making a request
Before deleting an Account, the user is encouraged to:
1. save needed materials through an available export feature or separate rights request; 2. remove or transfer projects, files, public links, and connections that should not be lost; 3. check whether the Account belongs to an Organisation Workspace or whether the user is its only administrator; 4. cancel future renewals and automatic operations in the available interface or through support; and 5. submit a separate refund or transaction-correction request under the Refund Rules if needed.
Stopping future renewal and deleting an Account are different actions. Cancellation stops future charges through the applicable payment method but normally preserves access through an already paid period. Account deletion ends Account access after the request is processed, but does not replace the rules of an app store, acquirer, or other party that controls a particular purchase.
3. How to submit a request
Use the deletion function in the application or Account area where available, or email support@cicora.ai from the email associated with the Account, with the subject “Delete Cicora Account.” State:
- the Account email or another safe Account identifier;
- the requested action: delete the Account, delete a particular object, disconnect a connection, or provide status information;
- where the Account is connected to an Organisation, the Workspace name/identifier and your role if known; and
- a preferred way to receive confirmation.
Do not send a full card number, CVV, PIN, password, bank code, another person's document, or another secret to verify identity. If the user no longer has access to the Account email, they may write from another address and explain the situation. We will offer a proportionate, secure way to verify the right to the Account without turning deletion into collection of unnecessary data.
After receiving a request, Cicora confirms receipt where possible and verifies Account ownership, representative authority, Workspace effect, active transactions, and whether a limited-retention ground applies. If the request is ambiguous, we ask for clarification before an irreversible action. Deletion confirmed by the user and performed by Cicora can be irreversible where the corresponding data has already been deleted or de-identified.
4. Identity and representative verification
We verify identity only to the extent needed to protect against deletion of another person's Account or unlawful disclosure of data. The method depends on risk: an ordinary request may be confirmed from the associated Account, while a sensitive operation, corporate environment, or representative may require additional authority evidence. A representative provides a lawful basis to act for the user to the extent required by applicable law.
We may refuse or limit an action where we cannot reasonably verify authority, where execution would disclose another person's data, violate law, create a security risk, or affect an active dispute or mandatory hold. Where possible, we explain the reason and available review path. Verification does not require payment secrets, unnecessary biometric data, or information unrelated to the request.
5. What happens after confirmation
After confirmed deletion, Cicora ends ordinary Account access, closes active sessions, and begins deletion or de-identification of data from active systems under the applicable process. We also disconnect connections controlled by Cicora unless this would conflict with law, security, an unfinished obligation, or Organisation rights.
Depending on the features actually enabled, the following can be affected:
| Object | Ordinary consequence of deletion |
|---|---|
| Personal profile and sessions | sign-in and access to the personal Account end; active sessions close |
| History, projects, saved instructions, and personal files | deleted or de-identified to the extent controlled by Cicora, subject to backup and legal exceptions |
| External-service connections | Cicora ends future access under the retained permission where technically available; disconnection with the external provider may also be needed |
| Public links | links owned by the user stop further delivery through Cicora; copies made by recipients are not controlled by Cicora |
| Workspace | personal membership/access can end, while Organisation data, administrator rights, and the Organisation agreement are handled under separate rules |
| Orders and billing | history needed for lawful accounting, refund, dispute, fraud prevention, or defence of claims can be retained in a limited manner |
The retention criteria in the Privacy Policy apply to deletion: active data is deleted or de-identified after the request is processed, while isolated backup copies are cleared through their ordinary cycle and do not return to ordinary use. A Model Provider or connected service can have its own deletion process for data already sent to it; where needed, we direct the user to that recipient or provide reasonable assistance within our role.
6. What may be retained in a limited way
Even after Account deletion, RIZZ TRADE may retain the minimum data needed for:
- compliance with law, accounting, tax records, or an obligatory request;
- confirmation of payment, refund, correction, prevention of double recovery, or resolution of a payment dispute;
- investigation of a violation, system protection, fraud prevention, and security;
- establishment, exercise, or defence of legal claims; or
- performance of an Organisation agreement where the data relates to its Workspace and the user is not its sole determining party.
Such records are isolated from ordinary Account experience and are not used for new personalisation, marketing, training of an own general model, or restoring personal access without an independent lawful basis. Where law requires longer retention or prohibits disclosure of a particular action, Cicora complies to the necessary extent.
7. Workspaces and corporate Accounts
Deletion of a personal Account does not unexpectedly destroy Organisation data or remove an Organisation's only administrator from a Workspace. Where a user belongs to an Organisation, Cicora checks who controls the Workspace and which actions the participant may take. An Organisation may retain its materials, logs, and lawful records independently of deletion of a participant's personal profile where this is consistent with its agreement and law.
Where an Organisation determines the purposes of processing data about its users, a participant's request to delete corporate content can require participation by the administrator or Organisation as the controlling party. Cicora does not disregard the request: we distinguish data related to RIZZ TRADE's own purposes from data processed on the Organisation's instructions and route the request through the applicable channel. See Business Data.
8. Purchases, subscriptions, and refunds
Account deletion is not an automatic refund and does not remove mandatory rights to a lawful refund. A user seeking to dispute a payment, correct duplication, obtain a refund for non-performance, or use a mandatory consumer right should state that separately in a request under the Refund Rules. Unused access or ordinary cancellation alone does not create a new refund ground unless the Rules or applicable law provide one.
A purchase through an app store, card, wallet, or other payment channel can require separate management in that channel. Cicora does not manage cancellation or refund where that power belongs to the store or another payment participant. We do not use Account deletion as a basis to refuse a mandatory refund, correction of an error, or lawful consideration of a request.
9. Status, timing, and review
We consider a confirmed request within the period required by applicable law and report the result or a lawful reason why part of the data is retained. Technical deletion processing, backup clearing, and an external recipient's response can have different stages; this does not provide a basis for returning data to ordinary access after confirmed deletion.
If a user believes deletion, a limitation, or a refusal was handled incorrectly, the user may request review through support@cicora.ai and use other remedies available under law. Additional rights and periods for the EEA, United Kingdom, Switzerland, applicable U.S. states, Republic of Korea, and other territories are described in the Privacy Policy and applicable law.
Questions about the deletion process may be sent to support@cicora.ai and +998 90 051 48 40.