Close or delete your account
You can stop renewal without deleting your files, request permanent closure of your RonikCloud account, or request a refund. These are separate actions and one does not automatically perform the others.
How to request closure
- Sign in to RonikCloud.
- Open Settings > Account Security > Request account closure.
- Review the billing and data notice, reauthenticate, and submit the request.
The in-app action records an authenticated request authorizing permanent deletion. It does not immediately sign you out, end access, cancel billing, or delete data. Processing runs in stages and disables account access before erasing personal storage. A separate support email is not required to confirm an authenticated request. Cancel renewal separately if you want to stop a future charge while the request is pending.
We aim to acknowledge account requests within two Czech business days and target completion within 28 days. We respond within one month; any lawful extension is explained within that first month. Save the private receipt link to check progress and completion without signing in. If you cannot submit in-app, use the support-email link above from the address associated with the account. Never send a password, encryption key, full card number, or card security code.
Cancellation, deletion, and refunds
- Cancel renewal: stops a future renewal and normally keeps the account and paid access through the current period.
- Complete account closure: ends RonikCloud access when closure processing begins and permanently removes the account and personal stored files. It cancels linked Stripe billing without an automatic refund. Organization-owned workspace data may remain with that organization after membership is removed.
- Request refund: asks the billing provider to review a completed charge. Deleting an account does not automatically create or approve a refund.
Request a refund before deletion when possible so the account and charge can be verified more easily. Mandatory consumer rights remain unaffected.
A company owner cannot be closed until ownership is transferred or the workspace is closed. Support will explain the available next step if those controls are unavailable.
Payment details
RonikCloud never receives or stores your full card number or card security code. An auto-renewing subscription requires its payment provider to retain a reusable payment credential. If Stripe checkout is abandoned before confirmation, no RonikCloud subscription or charge is created. Stripe may still process the checkout session and payment input already entered under its privacy policy.
When RonikCloud completes closure of a RonikCloud account with Stripe billing, RonikCloud cancels the linked Stripe subscription and requests deletion of every verified linked Stripe customer profile and its reusable payment details. Stripe and RonikCloud may still retain transaction, invoice, tax, fraud-prevention, or accounting records where required.
The server-only closure-request queue uses a SHA-256 hash of the Firebase user ID as its document key. Its minimal record contains the operational Firebase user ID, status, privacy version, request or update timestamps, fixed support-notification delivery status and code, notification timestamps and attempt count, and resolution fields when handled. It contains no email copy, free-text reason, card detail, billing identifier, or file identifier. A pending request has no automatic expiry and remains until it is handled. After audited resolution, it is assigned an expiry 90 days after resolution; scheduled maintenance may remove it later.
A long-lived deletion suppression record containing only a SHA-256 hash of the Firebase user ID, deletion state, and deletion timestamps is assigned an expiry 400 days after successful deletion completes to stop delayed billing events from recreating a closed account. It contains no email, card detail, file identifier, or raw user ID.
To block writes made with an already-issued sign-in token, RonikCloud also keeps a minimal profile tombstone and server-only rule-enforcement block at Firebase-user-ID-addressed document paths. They contain only deletion state, privacy version, timestamps, and expiry. After deletion completes, those records are assigned a 48-hour expiry. If closure is incomplete and authentication remains, closing-state deletion and enforcement records remain until you retry or support safely resolves the deletion; removing them sooner could reopen account writes. Scheduled maintenance removes completed-deletion records after expiry, and a delayed maintenance run may complete removal after the expiry time.
Apple subscriptions
Deleting a RonikCloud account does not cancel a subscription billed by Apple and cannot remove payment details from an Apple Account. You may still request RonikCloud account closure, but the Apple subscription remains active until you cancel renewal separately.