Kolo

Delete your Kolo account or selected data

Effective 7 October 2026

Delete your account in the app

Sign in, open Profile, choose Delete account, read the warning, and confirm your identity again when asked. If deletion fails, follow the retry instructions; a failed request does not confirm that deletion finished. Signing out or uninstalling Kolo does not delete your server account.

Kolo uses a shared Rolutec sign-in account. Deleting it removes that identity and can affect access and linked data in other Rolutec apps using the same account. This is not a Kolo-only profile reset.

Request account deletion without the app

Email support@rolutec.com from the address associated with your account. State that you want to delete the account used for Kolo. Do not send a password, authentication token, or precise location. Support may request reasonable identity verification and will explain the shared-account consequences before processing the request.

Delete selected data without deleting your account

You can remove your own event attachments and event reviews while keeping your account:

If you cannot use these controls, email support@rolutec.com from your account address. State that you want to keep your account and identify the attachment or review you want removed. Do not send another copy of sensitive content, a password, a token, or a precise location. Support may request reasonable identity verification. These controls do not offer independent deletion of every type of account data.

What account deletion removes and what can remain

Successful deletion removes the sign-in identity and its dependent Kolo rider profile, current location, broadcasts, ordinary events, participation, reviews, blocks, notification registrations and related account records. Required external-file cleanup is attempted before account deletion completes. A cleanup failure can require a retry; already completed external deletions cannot be rolled back.

Direct messages have a separate rule. The text of messages you sent is removed and a removal record can remain while the other participant still has an account. Messages the other participant wrote are retained under the message retention schedule. The current conversation list does not display a thread whose other account has been deleted; preservation does not promise continued access through that list. When both participants have deleted their accounts, the remaining message records are deleted.

Safety reports are an exception. Reports you filed remain after deletion, but their account link to you is removed. Open reports are not deleted on a timer. Resolved or dismissed reports and their handling history are deleted 24 months after resolution or dismissal. This does not promise that text somebody put in a report is anonymous; see the privacy policy for the safety-record practices.

Administrator-curated places and their change records follow their separate retention schedule, with deleted-account references cleared. They are not ordinary rider attachments. Copies previously exported to another app or held by another person are outside Kolo’s deletion controls.

The app clears its account-bound local cache and protected route recovery on the device where deletion is requested. This is not a remote wipe of every device. Backups do not change immediately: daily backups are retained for 6 days and monthly backups for 89 days, so a deleted record can remain in a backup for up to 89 days.

See the Kolo privacy policy for the wider retention schedule and contact details.