Data Retention Schedule
This Schedule is given pursuant to Article 13(2)(a) of the General Data Protection Regulation and forms part of the Privacy Notice. Each period stated is enforced by the software rather than by administrative practice.
Periods of retention
- Authentication link. Twenty minutes from issue, and one use. A link presented a second time is refused and a further link must be requested.
- Authenticated session. Ninety days from the date upon which the session was last used, whereupon it expires.
- Record of a request for an authentication link. Retained for so long as is required to operate the rate limit described at clause 3.4 of the Privacy Notice, and no longer.
- A targum deleted by the User. Seven days, during which period it is held in the trash, the number of days remaining is displayed and restoration is available. Upon expiry the directory and all material generated within it are deleted.
- A correction of meaning. Retained without limit of time. Such a record is evidence about a language rather than about a person: it bears a role and a pseudonym and no account, and a corpus which emptied whenever a contributor departed would not be a corpus. Upon the closure of an account the secret by which that account's pseudonym was formed ceases to relate it to any person, and the correction thereafter stands alone.
- An account closed by the User. Seven days from the request for closure. Upon expiry the following are deleted: words, meanings, phrases, documents, dates of reading, records of use of the reader, sessions, authentication links and the account record itself, together with all files generated for the account.
- Material retained by the User. Until deleted by the User or until closure of the account. No period of inactivity causes such material to be deleted.
- Records of use of the reader. For so long as the account subsists, and erased with it; or sooner, upon the request of the User made from the account page, which takes effect at once.
- A linked Telegram chat. Until the User unlinks it, by sending /stop to the bot or from the account page, or until the account is closed, whichever is the sooner. Deleted at once upon either.
- Server access records. Written by the reverse proxy and rotated by file size, such that the records held comprise the recent past rather than the whole. Retained for so long as they remain of use in diagnosing faults and detecting misuse.
- Aggregate visit counts. Derived from the server access records, and containing no personal data. Retained indefinitely.
Qualifications
- Deletion of expired material is performed upon restart of the Service. Accordingly a period of seven days stated above is to be construed as a period of not less than seven days.
- The database is copied nightly and the fourteen most recent copies are retained. An account deleted in accordance with clause 1.5 above may therefore persist within a backup for a further period not exceeding fourteen days. A copy transmitted from the server is encrypted before transmission. No backup is read save where restoration is required.
- Text transmitted to Anthropic PBC for translation is deleted by that processor in accordance with its own published policy, namely within thirty days of receipt. Deletion effected under this Schedule does not accelerate that period.
Erasure upon request
- The procedure by which a Data Subject may obtain erasure is set out in the Erasure and Account Closure Procedure.
- Enquiries concerning this Schedule may be addressed to hello@targum.page.
Last amended 28 September 2026. Adapted in part from 37signals' open-source policies, used under CC BY 4.0. This document is not legal advice.