Delete your handyREADER account and data

Removing data and the account

Request server-data erasure or account closure at privacy@silkidea.com, quoting the account code from (i) › Credit balance › Credit history. We verify authority proportionately and explain how pending jobs and credits are handled. Deletion is not conditional on using the balance or waiving claims. Evidence needed for a legal obligation or specific claim is separated and its retention reason explained.

Uninstalling alone does not delete the server account, transaction history or all Keychain, iCloud, Block Store or Google-backup records. Manage local books, synchronised copies and backups on your devices and in the relevant Apple or Google account; we assist with erasure of app records. For Android a request also covers purchase links, credit-code use and the notification identifier. Erasure from the active database is not immediate erasure from every backup or provider system; requests also address these copies, Firebase and any restoration. While the identifier remains on a device or in a backup, the app may register it again as a new empty account after server erasure, typically at the next launch or connection to our server; this may also affect version 4.10 on both platforms. We therefore address local and backed-up identifiers when handling a request, rather than only deleting a server record. The precise process depends on the app version and may require your cooperation; uninstalling alone does not guarantee removal of the identifier.

Requests can be fulfilled manually after verification; we do not rely only on automatic rotation. Erasure covers linked records in active systems and unnecessary data in operational records. Ordinary logs are retained only as needed to diagnose and protect the service, according to the duration of a particular fault or security risk. We review necessity and erase or irreversibly anonymise records when it ends; a specific incident or legal claim may justify separate retention of the necessary records.

Backups and completion of erasure

We use daily Hetzner server backups in seven rotating slots for recovery. With regular daily operation, the cycle therefore covers approximately seven days. This is a server backup, not a separate retention period for accounts, operational logs or other providers’ data; their retention follows the purposes and rules described above.

A backup is a snapshot of the whole server. It may also contain chapter text queued or currently being processed, translation context, results awaiting download and persisted abuse-prevention counters. The periods above apply to the live system; after removal from it, data may remain in an earlier backup until that slot is overwritten, approximately a further seven days with regular daily operation. Manual copies and other providers’ backups follow the rules below.

Erasure also covers manual technical and migration copies. We retain these only as needed to verify recovery or complete a migration, then remove them unless a specific legal reason requires separate retention. Hetzner’s seven slots do not automatically remove these copies.

If an individual record cannot safely be separated from an immutable backup, we restrict further use and access, establish the earliest deletion date for that copy and reapply the relevant erasures before normal use after restoration. Technical difficulty alone is not a reason to refuse a request or retain data indefinitely. We explain the scope, timing and any statutory exception when handling the request.