Effective 12 November 2026
About Witbound
You do not need a Witbound account to read or sync books. Witbound has no advertising and does not sell your personal data. Your library, reading statistics, settings and notes are stored locally. This policy covers Witbound on Apple platforms and Android; available features depend on the platform and app version.
Your books and audio
Imported books and audiobooks are stored on your device. Speech processing and word alignment run locally, with one exception: if you turn on Cloud sync (on Android, iPhone and iPad), the device sends a book’s audio to Witbound’s server for speech processing, as described under Cloud sync below. Matching the words to your ebook still happens on your device, and your ebook never leaves it. Witbound does not upload your book text or audio to its community-sync service. Android may download its speech model from Hugging Face before the first local sync; this downloads a model, not your books. Apple platforms may download speech or language resources through Apple's system services.
On Android, Read aloud speaks a book with a text-to-speech voice already installed on your phone. Witbound offers only voices that work offline, so the book’s text is spoken on your device and is not sent to Witbound or anyone else.
You can delete imported books in the app. Copies you exported, shared or backed up are separate. Your operating system's backup and device-transfer settings may also apply to local app data.
Your place on your own devices (iCloud)
On iPhone and iPad, Witbound keeps your place in each book in your own iCloud, using Apple’s iCloud key-value storage, so that your other devices signed in to the same Apple Account can offer to continue from it. This is on by default. Each book’s record holds a content fingerprint of the book’s text, which names the record; where you are in the audio and how long the narration is; the fingerprint of your chapter and how far through it and through the book you are; when your place last moved; the device’s name in Witbound (“Witbound on iPhone”, “Witbound on iPad” or the name you gave it for KOReader sync); and a random identifier made on that device. It contains no book text, titles or audio. Apple stores and syncs it with the rest of your iCloud data; Witbound has no access to it and never receives it. Another device’s place is only ever offered, never moved to on its own. Turning off “Sync my place across my devices” in Settings stops saving and reading places there and, if the device is signed in to iCloud at the time, removes Witbound’s places from your iCloud, including the ones your other devices saved. Each device has its own switch: a device where it is still on goes on saving its places there.
Community sync
Community sync is on by default. It connects to Witbound's service hosted on Cloudflare to find and contribute reusable timing maps. Requests contain hashed fingerprints derived from ebook and audio files and from ebook content. These fingerprints help match the same content, including compatible editions; they are not a Witbound account or device identifier.
Contributed maps contain word positions, word start and end times, counts, alignment flags and information about the app version and speech engine. They contain no book text, titles, authors, audio recordings, reading history, name or email address. Other readers with matching content can download these maps. Exact-file matches reuse validated timings directly. For content-based chapter matches, Witbound checks samples of the audio on the receiving device before using the shared timings.
The community service counts, per day, how many map lookups found a map; the totals hold no identifier, address or book.
Cloudflare necessarily handles ordinary connection information, such as your IP address and request headers, to deliver and protect the service. Cloudflare's own handling is described in its privacy policy.
Turn community sync off in Settings to stop new community lookups and contributions; a request already in progress may finish. On Android, a book that Cloud sync helped with still shares its finished map, as described under Cloud sync. This setting does not disable purchases, model downloads, Discover, optional server connections or sharing. Turning it off or deleting a local book does not remove maps already contributed to the shared library.
Cloud sync (Android)
Cloud sync is an optional Android feature that helps a long English audiobook sync in minutes instead of the hour or more a phone can take. It is off until you turn it on, either for your books in Settings › Cloud sync (“Long books only” or “All books”) or for one book with “Sync in the cloud”. Before anything is sent, Witbound shows a note saying what Cloud sync does, and nothing is sent unless you agree.
It works only:
- on Wi-Fi or another unmetered network, or on mobile data or a hotspot if you turn on “Use metered networks” in Settings › Cloud sync and say yes for that book, which shows how much audio it will send (never while roaming or with Data Saver on);
- for books in English;
- while Witbound’s server is taking work.
At any other time, including when the server is busy, unreachable or at its limit, your phone syncs the book on its own. If community sync is on and already has timings for your book, Witbound uses them, and Cloud sync sends only the parts still missing, if any.
What is sent. While a book syncs, your phone works through the audiobook from the start and sends its audio from the end. The audio goes to Witbound’s server in pieces of about five minutes, over an encrypted connection. A piece holds only the recorded sound, not the file’s tags, so it carries no title, author or cover (though the narrator may read the title aloud).
When a book starts, the app also sends:
- a random identifier it made for Cloud sync on your phone. It is not tied to an account, and it is separate from the identifiers described elsewhere in this policy;
- the audiobook’s length and audio format, and how many pieces there are;
- the fingerprint of the book’s files that community sync uses;
- Witbound’s version;
- a Google Play integrity token (see below).
Cloud sync never sends your ebook, its text, your library, your notes or highlights, or where you are in a book. Matching the words to your ebook happens on your phone, and your ebook never leaves it.
What the server does with it. Witbound’s server runs on Cloudflare. It turns each piece into words and their timings, using the same speech engine Witbound uses on Android phones. It sends them back to your phone and then discards the piece. The audio and the words exist only in the server’s memory while that piece is processed. They are never written to disk, logged or kept, and Witbound keeps no copy of them. Request logging is off.
Limits and misuse. To keep Cloud sync free and within its budget, the server keeps only:
- a keyed one-way hash of your phone’s Cloud sync identifier, with how much audio it sent this month and last. These are deleted 35 days after the phone last used Cloud sync;
- while a book is syncing, a record of that session (the same hash, the book’s length and format, and the number of pieces) for up to 3 hours, and a note of each piece in progress until it is finished;
- a one-way hash of each integrity token, for about 6 minutes, so that a token can’t be used twice;
- request counts for rate limits, for no more than a day. They are keyed by the hashed identifier, or by a keyed hash of your IP address made with a key that changes every day.
It does not store your IP address, the identifier itself, any audio or words, or the book’s title.
Each phone has a monthly safety limit, and the service has a monthly budget. When either is used up, your phone syncs on its own, and Witbound tells you until when in a notification and on the book’s card. Both are created on your phone.
To know whether to offer Cloud sync, the app asks the server from time to time whether it is taking work, even while Cloud sync is off. That request carries no identifier and nothing about you or your books.
Google Play Integrity. Before the server accepts a book, the app asks Google Play for an integrity token, and the server asks Google to read it. The answer says:
- whether the request comes from the genuine Witbound app from Google Play;
- whether the device passes Google’s integrity checks;
- how many integrity checks Witbound has asked for on that device in the last hour.
To make the token, Google Play services sends Google:
- details of the app (its package name, version and signing certificate);
- its Google Play licence status;
- device attestation data.
The token is tied to a one-way hash of your Cloud sync identifier and the book’s length, so Google sees neither. Witbound uses the answer only to accept or refuse the request. Google handles this data under its own terms: see how the Play Integrity API handles data and Google’s privacy policy.
The finished map. When a book that Cloud sync helped finishes syncing, and its timing map passes Witbound’s quality check, the app shares the map with community sync, as described above, so the next reader with the same edition can sync it almost instantly. This is part of what you agree to when you turn on Cloud sync, so it happens even if community sync is off.
- It sends the same map and fingerprints that community sync sends, and nothing more.
- A map is never shared before the whole book has synced.
- Maps already shared stay in the shared library.
Who handles it, and where. Cloudflare runs the server for Witbound as its processor, under Cloudflare’s data processing addendum. Like any website, it handles ordinary connection information such as your IP address and request headers, as described under Community sync. Your phone connects to a Cloudflare data centre near you. The speech engine runs in a Cloudflare data centre that Cloudflare chooses, which may be outside the UK, including in the United States. Cloudflare’s addendum protects those transfers with the UK’s approved safeguards.
Your choice. Witbound relies on your consent for Cloud sync. You give it on the note, and you can withdraw it at any time: set Settings › Cloud sync to Off, or choose “Sync on this phone instead” for a book.
- Uploads stop at once. A piece already sent is still processed, and its words are discarded.
- Withdrawing doesn’t undo syncs already finished, and it doesn’t remove maps already shared.
- The server holds only a one-way hash of a random identifier, so Witbound can’t tell which counts are yours, and can’t find or delete them on request. They are deleted automatically 35 days after the phone last used Cloud sync.
Cloud sync on iPhone and iPad
Cloud sync is optional. It helps a long English audiobook sync in minutes on an iPhone or iPad. It is off until you turn it on with the Cloud button at the top of your library or in Settings › Cloud sync, or choose “Sync in the cloud” for one book, and Witbound shows a note saying what it does before anything is sent. It works only on Wi-Fi (not on a personal hotspot or in Low Data Mode), only for books in English, and only while Witbound’s server is taking work; at any other time your iPhone or iPad syncs the book on its own. It is not available in the iPhone and iPad app on a Mac.
What is sent. While a book syncs, your device works through the audiobook from the start and sends its audio from the end, in pieces of about five minutes, over an encrypted connection. Each piece is re-encoded on your device from the recorded sound alone, so it carries no title, author, cover or other tags (though the narrator may read the title aloud). Cloud sync never sends your ebook, its text, your library, your notes or highlights, or where you are in a book.
When it starts a book, the app also sends:
- a random identifier made for Cloud sync on this device, not tied to an account or to any other identifier in this policy;
- an Apple App Attest key and signature, which let the server check that the request comes from the genuine Witbound app on a genuine Apple device;
- an Apple DeviceCheck token (see below);
- the App Store’s signed record of your copy of Witbound and, if you have Witbound Plus, the App Store’s signed record of that purchase;
- the audiobook’s length and audio format, the number of pieces, and Witbound’s version.
While Cloud sync is on, the app also asks the server from time to time how much Cloud sync you have left (when Settings opens, and while a book syncs). That request carries the first two items above; the first time, and after a purchase or restore, it carries the first four.
To know whether to offer Cloud sync, the app asks Witbound’s server from time to time whether it is taking work, even while Cloud sync is off. That request carries no identifier.
On iPhone and iPad, when a book’s cloud session ends, the app tells the server how it ended (finished, stopped, or the app was closed) and a few timing numbers about that sync: how long it ran at full speed, while the device was warm, paused, off Wi-Fi or in the background; how long preparing the pieces took; the upload speed; how many pieces were out at once; the warmest the device got; how many pieces were sent again; and whether it picked up again after a break. They say nothing about you, and nothing about the book beyond the length the app already sends. The server does not store them: it turns them into one line of a private report that Witbound’s developer reads in Discord, with no identifier, no title and nothing else about who or what the sync was for.
What the server does with it. Witbound’s server runs on Cloudflare. It turns each piece into words and their timings with a speech engine Witbound runs, sends them back to your device and discards the piece. The audio and the words exist only in the server’s memory while that piece is processed. They are never written to disk, logged or kept. Matching the words to your ebook happens on your device.
What the server keeps, and for how long. To keep Cloud sync free and within its budget, the server keeps only:
- a keyed one-way hash of your device’s Cloud sync identifier, with how much audio it sent this month and last;
- the public half of the App Attest key and a counter, so the same signature can’t be used twice;
- for your free first book, a keyed one-way hash of its length and how many hours it has used;
- if you have Plus, a keyed one-way hash of your purchase’s identifier and the hours used this month and last;
- while a book syncs, a record of that session for up to 3 hours, and one-time codes for 5 minutes;
- request counts for rate limits, for no more than a day, keyed by the hashed identifier or by a keyed hash of your IP address made with a key that changes every day.
All of these are deleted 35 days after your device last used Cloud sync. The server does not store your IP address, the identifiers themselves, your Apple Account, any audio or words, or the book’s title.
Your free first book and Apple DeviceCheck. Each iPhone or iPad gets one book synced in the cloud for free. So that reinstalling the app doesn’t start that over, the server asks Apple’s DeviceCheck service to remember one yes-or-no fact for your device: whether its free cloud book has been used. Apple keeps that fact, with the month it was set, for Witbound; Witbound can read it only when your device sends a fresh token, and it can’t tell which device or person it belongs to. If you leave your free book unfinished for more than 35 days, its remaining cloud hours lapse and your device finishes it.
Your allowance. Settings shows how much Cloud sync you have left. Witbound Plus includes up to 100 hours of cloud audio each month. When your hours or the service’s monthly budget run out, your device syncs on its own, and Witbound tells you until when.
Apple’s services. App Attest, DeviceCheck and the App Store’s signed records are Apple services that Apple runs under its own privacy policy.
The finished map. When a book that Cloud sync helped finishes syncing and its timing map passes Witbound’s quality check, the app shares the map with community sync, as described above, so the next reader with the same edition can sync it almost instantly. If community sync is off, nothing is shared. It sends the same map and fingerprints community sync sends, and nothing more, and never before the whole book has synced.
Who handles it, and where. Cloudflare runs the server for Witbound as its processor, under Cloudflare’s data processing addendum. Your device connects to a Cloudflare data centre near you; the speech engine runs in a Cloudflare data centre that Cloudflare chooses, which may be outside the UK, including in the United States. Cloudflare’s addendum protects those transfers with the UK’s approved safeguards.
Your choice. Witbound relies on your consent for Cloud sync. You can withdraw it at any time: turn Cloud sync off (the Cloud button at the top of your library, or Settings › Cloud sync), which also withdraws a yes you gave a single book, or choose “Sync on this iPhone instead” for a book. Uploads stop at once, and the app sends none of the identifiers above until you turn Cloud sync on again or choose “Sync in the cloud” for a book; a piece already sent is still processed and its words discarded. Withdrawing doesn’t undo syncs already finished or remove maps already shared. Because the server holds only one-way hashes of random identifiers, Witbound can’t tell which counts are yours or delete them on request; they are deleted automatically after 35 days.
Discover: your to-read list, synced books and free classics
On iPhone and iPad, your to-read list is stored on your device and is never sent to Witbound. When you add a book, its title and author are looked up in Open Library and Google Books to find it, as described below, and its cover is saved on your device. To tell you when a book on your list becomes quick to sync, Witbound downloads the public Synced list from time to time (in the background too, if you allow its notifications) and compares it with your list on your device. A list you shared with an earlier version is taken down from our server the first time the new version (1.9.1 on iPhone and iPad, 1.1.1 on Android) is online.
Some parts of Discover send a random installation identifier created on your device. On iPhone and iPad it is kept in the keychain, so it stays the same if you delete and reinstall Witbound. On Android it is kept in the app’s own storage and left out of backups, so reinstalling Witbound or moving to a new phone makes a new one. The service stores only a one-way hash of it, so it can count each installation once; it has no account, name or email address to attach it to.
Older versions of Witbound for Android (before 1.1.1) let you choose, in Discover, to share your to-read list with the community. Then Witbound sends the catalogue id, title and author of each book on your to-read list, and whether you want it illustrated (yes, no or either), to its service hosted on Cloudflare, together with the installation identifier. Other readers see how many people want a book, and how many of them want it illustrated, never who: this is the public Wanted list. Witbound for Mac and older versions of the iPhone, iPad and Android apps still show the Wanted list; the current iPhone, iPad and Android apps no longer do. While sharing is on, when a book on your to-read list that came from Open Library finishes syncing on your device, Witbound also tells the service which edition and narrator it synced (as named inside your files) and the id of its timing map, so other readers can find a matching copy. Nothing else about the book or your reading is sent. Turning sharing off withdraws your shared to-read list: the service removes your installation from each book on it and lowers that book’s count. The book entries themselves stay, with their titles, authors and remaining counts, as do the editions and narrators already reported. Do this before deleting the app: once the app is gone, Witbound can no longer tell which entries were yours.
When one of your own books finishes syncing and its timing map is on the community service, Witbound may show a card under it on your shelf offering to share it. To decide, it downloads the public Synced list to see whether the book is already there. Nothing about your book is sent unless you tap Share. Then, to name the book, Witbound searches the public Wanted and Synced lists for the book’s main title (these searches carry no installation identifier and are not stored) and, if neither list names it, looks up the book’s title and author in Open Library. It sends the service the Open Library id of the book (or, if there is no clear match or Open Library doesn’t answer, its title and author), the edition and narrator as named inside your files, and the random installation identifier described above, of which the service keeps only a one-way hash. The book can then appear on the public Synced list, so readers with the same files can sync it almost instantly; the list never shows who shared it. “Not now” and “Don’t ask again” send nothing, and “Offer to share books I sync” in Settings turns the card off. A shared book stays on the Synced list; to have one removed, contact us at the address below. Witbound for Mac makes the same offer under a book that finishes syncing on your Mac, with its own “Offer to share books I sync” switch, and a book synced there can also be shared later from its right-click menu, when Witbound can name its edition (“Show the community it’s synced…”). When you click Share on the Mac, it names the book the same way (the public lists, then Open Library, else its own title and author) and sends the same details in the same way, with a random installation identifier created on that Mac, of which the service keeps only a one-way hash. If that book’s timing map is not on the community service yet (for example because community sync is off), the right-click share sends that one map first, as its window says; community sync stays off. A book whose timing map the service turned away shows a “Share again” button, which sends that one map again, also when community sync is off. While Witbound for Mac holds a map the service turned away, it asks the service every few hours whether its rules for maps have changed, so that it can offer the map again; that request carries nothing about you. To show which of your books are already on the Synced list, Witbound for Mac also downloads that public list from time to time while it is open, including when community sync is off; these requests carry no installation identifier.
To add a book to your to-read list, you type its title (and, if you like, its author). When you tap Add, Witbound looks the book up in Open Library, a public catalogue run by the Internet Archive, and, if Open Library has no match or you ask to see another, in Google Books. Only the title and author you typed are sent, and only when you tap Add or ask for another match. The cover shown with a match is loaded from that catalogue. See the Internet Archive’s terms and privacy policy and Google’s privacy policy. If neither has the book, it is added exactly as you typed it.
Shared titles are checked before they appear in the public Wanted or Synced lists: by a word filter, by the subject labels the catalogue gives the book, and by an automated safety check for titles typed in by readers, titles from Google Books and Open Library books without subject labels. The automated check is Meta’s Llama Guard model, run by Cloudflare Workers AI; it is given only the title and author. Flagged titles wait for a person to review them. Edition and narrator names you share go through the word filter and the automated check.
When you search the Synced list, or the Wanted list in apps that still show it, the words you type are sent to Witbound’s service as you type, to filter the list. They carry no installation identifier and are not stored.
You can hide any book in Synced, or in Wanted where your app still shows it; hiding stays on your device. You can also report one, choosing a reason (sexual content, hateful, spam or something else). A report sends the service the book, the reason and your random installation identifier, and hides the book for you. The service keeps the one-way hash of the identifier with the reason, so each installation counts once. A book that several readers report is taken off the public lists until a person reviews it.
Book covers in Discover, and in the Community view of Witbound for Mac, are loaded from the public catalogues that hold them: covers.openlibrary.org (which can redirect to the Internet Archive’s archive.org servers), standardebooks.org, gutenberg.org, books.google.com and books.googleusercontent.com. That includes covers for books on your to-read list, requested by the catalogue’s id for the book. Like any website, these hosts receive ordinary connection information such as your IP address. A cover for a book on your to-read list is saved on your device after the first time, so it can show again without asking anyone.
A book’s short description in Discover is loaded from Open Library when you open it; only the book’s Open Library id (or its title and author when there is none) is sent.
The Synced list is information only. It names editions and narrations that Witbound can sync almost instantly if you already own them. Witbound does not provide, host or link to those books.
When you tap Get on a free classic, Witbound downloads the ebook from Project Gutenberg (gutenberg.org) and the LibriVox recording from the Internet Archive (archive.org), directly from those sites. Like any website, they receive ordinary connection information such as your IP address. Witbound hosts none of these files.
Clubs: reading together
Clubs let people read the same book on a shared schedule: friends join a club with its code or a link, and readers can also join a club its owner lists in Find a club (below). They are optional, and nothing is sent until you open Clubs and create a club profile. Clubs are part of Witbound for iPhone, iPad and Android.
Your club profile. When you create one, Witbound makes a random device key on your device and keeps it in the keychain. It is not synced through iCloud Keychain, and it moves to a new device only inside an encrypted backup. On Android, the key is protected by the phone’s Android Keystore and left out of backups, so it never leaves that phone and a new Android phone starts a new club profile. The key is sent in a request header with every Clubs request, never in a web address, to Witbound’s service hosted on Cloudflare, which stores only a one-way hash of it. It is separate from the Discover installation identifier described above. Your profile is the name you choose plus a random 4-digit tag, such as “Sam#4821”; there is no email address, phone number or password. You can also pick a picture for your profile from 24 engravings that come with the app. The service stores only which one you picked and shows it wherever your name appears in Clubs; there is no photo upload.
What you add. Club names, and the books an owner adds to a club’s roadmap or a member suggests, are stored by the service and shown to the club’s members. Books are chosen from Open Library: the words you type to find one are sent to Open Library from your device, as described above for Discover, and the service reads the book’s title, author and cover reference from Open Library. Witbound also sends the title and author Open Library gave for the book, which the service uses only when it can’t reach Open Library itself. A book Open Library has no match for, or doesn’t answer for, can be started by the club’s owner from their own copy instead: Witbound sends the service that copy’s title and author, after taking out the names of websites a file came from that it recognises; the service takes such names out again, and the club sees the book by the title that is left, with no cover. Your name, club names and book titles go through the same word filter and automated safety check described above (it is given only the name or the title and author) before anyone else sees them.
The club’s book. When a club’s owner starts a book, Witbound sends an outline of the owner’s copy: a content fingerprint of the book and of each chapter, each chapter’s word count and, where known, its listening time, and one-way fingerprints of a few short passages in each chapter, from which no text can be recovered. It contains no book text, titles or audio. For a book a club started before Witbound sent these passage fingerprints, the owner’s phone adds them to its outline when the owner next opens the club, if it still has the copy the outline was made from. Members’ progress is placed on that outline, so friends with different editions can read together: a member’s phone looks for those fingerprints in its own copy and adds to its progress (below) where its place falls on the outline, and whether that place was found by the text or only approximately. To match a club’s book to a book in your library, Witbound compares chapter fingerprints on your device.
Your progress. While you read a club’s current book, Witbound sends the service how far you have listened or read: the fingerprint of the chapter you have reached, how far through it you are, your overall percentage, whether you are listening now, your time zone’s offset from UTC (so a reading streak counts your own days) and when you reached that place, which the service uses only for progress that arrives late. It is sent at most every two minutes while you listen, and when you pause, close the book or leave the app. It contains no book text and no position within your audio files. The other members of the club see your name, the picture you picked (if any), your chapter in the owner’s edition, your percentage, your stage and status, when you last read, whether you are reading now, your streak, your badges and club moments such as “Sam cleared Stage 2”. They never see the fingerprints, your time zone, your device key or its hash, or your IP address.
Quotes. You can share a passage you highlighted in a club’s current book with that club, or turn on “Share my highlights with this club” to share each new highlight you make in that book. Witbound sends a pointer, not the passage: the content fingerprint of the chapter in your copy, the chapter’s word count, which of its words the passage covers, a short fingerprint of those words and how far through your copy it is. It never sends the words themselves, your note on the highlight or any audio. Each member’s app finds the passage in its own copy of the book and shows it from there, with that copy’s narration, only once that member has reached the passage’s chapter. The other members see your name and picture with the quote, when you shared it, and how many of each reaction it has, not who added them. Reactions are four fixed kinds; the service stores yours with your club profile. It also stores whether “Share my highlights with this club” is on, and a club moment says when you shared quotes.
Read or die. A club’s owner can set its schedule to Read or die. Then a member who hasn’t reached the end of a stage by its deadline can be removed from the club, but only if someone in the club reached the stage at a believable pace, as the terms explain. The service notes which version of Witbound each member uses, and since when, so that it never removes a member whose app doesn’t show this rule, or has shown it for less than a day before a deadline. For the pace, the service keeps, for each member of any club, when their first report on the club’s current book arrived, and which part of the book, if any, their place got through faster than listening to it from its start at double speed, plus 15 minutes, could have taken them since then. In a Read or die club it also keeps the stage, if any, at which the simpler rule (anyone reaching a stage in time puts out everyone behind) would have removed them, and when, so that the believable pace can only ever keep members in. These pace facts start again when the club starts another book. The service also notes how each member came into the club (with its code or link, from a Find a club listing without asking first, or by a request the owner accepted), which decides who the club passes to if a deadline removes its owner. None of this is shown to anyone. When a member leaves any club or is removed from it, the service keeps their seat for as long as the club is on the same book: when and how they first joined, how far they had read, the stages they had cleared, when they finished, their badges, when they left and came back, and the version and pace facts above (and, for an owner a deadline removed, who the club passed to). This is so that leaving and rejoining can’t skip a deadline once a club has started, and so that coming back gives a member their place. The service keeps a record of the removal, with the club’s name and the book’s title as they were then, so that the club’s code can’t bring the member back until the club starts its next book (the club’s owner can let them back in sooner), and so that the member’s app can tell them what happened. The record is deleted once the club has moved on to another book and the removal is 30 days old, or sooner if the club is deleted or you delete your club profile.
Reports and blocks. You can report a member or a club with a fixed reason (there is no free text). A report stores the reason, what was reported, the club you reported it from and your profile (so each reader counts once), and whether, when you made it, your profile was at least a week old and you had been in that club for at least a day. Only reports from readers who had both can hide anyone: a member or club that several such readers report can be hidden until a person reviews it. Blocking a reader stores the block on the service, so their content stays hidden from you, they are removed from the clubs you run and they cannot join a club you run. If a profile is removed for breaking the terms, the hash of its device key is kept so it cannot simply return.
Find a club. On Android, iPhone and iPad, a club’s owner can list the club in Find a club, in Clubs, so that readers they don’t know can find it and join, before or after it starts. Until the club’s last deadline has passed, and while it has a spot left, anyone with a club profile can see its listing, unless either of you has blocked the other: the club’s name; its book’s title, author and cover; when the club starts; its schedule (how many stages, how far into the book they go, when the last one falls and, where the owner’s copy has it, the listening time); how many readers it has and how many spots; whether the owner approves each reader; whether it is Read or die; when it was listed; and the owner’s Clubs name and picture. A listing says how many readers a club has and nothing else about them, but a reader who joins from it is a member of the club and sees what members see (above). So if you are in a club its owner lists, on any device, readers you don’t know can see your name, your picture and your progress there. Members whose app shows Find a club are told when their club is listed: a club moment says so, and the club’s screen says so while it is listed. The service stores the listing itself (which club and book, who listed it, the choices made and when) and builds what it shows from the club. To save work it keeps one copy of the whole list, which it shows for two minutes at most and builds again the next time someone opens Find a club after that, or after a change, so a change to the club shows within minutes. Your app asks for the listings only when you open Find a club, and opening it stores nothing about you. Which listings are for books on your shelf is worked out on your device, so the service never learns what is on your shelf.
If the owner approves each reader, asking to join sends a request. The service stores it with your club profile, when you asked, the app and version you asked from (so that, if you are accepted, your seat records your app as a join does) and a code standing for the club’s book, schedule, start and Read or die as the listing showed them (so that accepting can tell whether the club has changed since you asked), and the club’s owner sees your Clubs name and picture and when you asked. A waiting request is deleted when the owner accepts it, when you take it back, or when the owner takes the listing down or lets anyone join. A request still waiting when a Read or die club starts can’t be accepted any more: it is kept, and shown to you as ended, until you remove it or it is deleted with the listing. If the club has changed when the owner accepts, you don’t join: the request is kept, marked as changed, until you ask again (which makes it a new waiting request) or it is deleted as a waiting one is. A declined request is kept, so that you can’t ask the same club again while it is listed. A listing is deleted, with its requests, when its owner takes it down, within a day once the club moves on to another book or owner, about a week after the club’s last deadline, or with its club. A listing we took down stays while its club does, and so does one under review, unless its owner takes it down. Day counts of what each profile does in Find a club, used for its limits, are deleted after a week.
You can report a listing with a fixed reason (there is no free text). The service keeps which club, the reason, your club profile and when, so each reader counts once. You don’t see that listing until we have reviewed it, and we are told of each report at once, with only its reason. A listing reported by two readers, or by one whose club profile is a week old or more, can be hidden from everyone until we review it. Reports are about the club, not one listing: they stay when the club is listed again or moves on to another book, and a new listing of the club is hidden until we have reviewed them. A report is deleted with its club, or once it is 30 days old, we have reviewed it and the club’s listing has been deleted. If you delete your club profile, the reports you made on listings are kept for review without your profile, and a listing of yours under review, or one we took down, stays with its club, without its owner.
Nudges. If you allow notifications and leave club nudges on, Witbound checks your clubs from time to time in the background, using your device key, and shows reminders such as an upcoming stage deadline as notifications created on your device. Turn off “Club nudges” in Settings to stop them.
Keeping and deleting. Club moments are kept for 90 days. The rest of your Clubs data is kept until you leave a club or are removed from it (except the seat record described under Read or die, and Find a club’s listings, requests and reports, described above), the club is deleted or you delete your club profile. A quote is also deleted when you unshare it or the club’s owner removes it. Once a club finishes a book, that book’s quotes are no longer shown, and they are deleted when the book leaves the club’s history. Delete my club profile, in Settings, deletes from the service your profile, your memberships and progress, your suggestions, the quotes you shared and the reactions on them, your own reactions, the moments about you, any record of a Read or die removal, your blocks and the reports you made on members and clubs, your Find a club listings and your requests to join (reports you made on listings, and a listing of yours under review or taken down by us, are kept without your profile, as described above), and your Roadmap ideas, the votes and reports on them and your Roadmap blocks. A club you run passes to its longest-standing member (and any listing of it ends), or is deleted if you are its only member. Your device then forgets the device key. The service uses IP addresses only to limit how fast requests can be made, and does not store them; Cloudflare handles connection information as described above.
Deleting your club profile without the app. If you no longer have Witbound installed, email zarksided@gmail.com with your profile name and tag (for example “Sam#4821”) and the name of a club you were in, and ask for your club profile to be deleted. We delete it, with everything Delete my club profile deletes, within 30 days and reply to confirm.
Roadmap: votes and ideas
On iPhone and iPad, Discover’s Roadmap shows what we’re working on, and lets you vote on it and suggest ideas. Votes and reports are tied to the random installation identifier described under Discover, which our server keeps only as a one-way (hashed) value, so it can count one vote per install without knowing who you are. To limit abuse, the server briefly uses your IP address, in memory only, to limit how many votes and reports can be made, and never stores it. Posting an idea needs a Clubs profile: ideas you post appear publicly under your Clubs name (name#tag), with what you wrote. Before anyone sees an idea, an automatic filter checks it: a word list, then an AI safety model run by Cloudflare. If you report an idea, it can be hidden until we review it; a report stores only the reason you chose, with the hashed identifier. The people you block are kept with your Clubs profile. You can delete your own ideas at any time, and deleting your Clubs profile deletes your ideas, the votes and reports on them, and your blocks.
Update checks in Witbound for Mac
Once a day, when its window opens, Witbound for Mac asks GitHub (api.github.com) whether a newer version has been released. The request carries no identifier. Like any website, GitHub receives ordinary connection information such as your IP address; see GitHub’s privacy statement. If there is a newer version, Witbound shows a notice. Nothing is downloaded unless you click Download, which opens the release page in your browser. Turn off “Check for updates” in Settings, or at the foot of the window, to stop the check.
Optional library and progress services
If you connect Audiobookshelf, Calibre, BookOrbit, Grimmory or another compatible OPDS server, Witbound sends library requests and the necessary authentication information to the server you select. Files and artwork are downloaded from the addresses supplied by that service. Credentials are kept on your device; they are not sent to Witbound's community-sync service.
Plex sign-in connects to Plex and then your selected Plex server. Plex requests include a generated installation identifier used for that connection. If you enable KOReader progress sync, your chosen KOReader sync server receives the login information needed to authenticate you, book fingerprints, reading positions, a device label and an installation identifier. If that server is BookOrbit, Witbound also asks it which of its files a book is, sending the book’s title, author and fingerprint, the id of the BookOrbit file the book was downloaded as (if it was), the same device label and identifier, Witbound’s version and the device’s local time. If you turn on “Send highlights to BookOrbit”, Witbound first asks that server whether it holds each book you have highlights in, sending only the book’s fingerprints and the same device details, and then sends it your highlights in the books it holds: the highlighted text, your note, the chapter title, where the highlight is, its colour and when it was made or changed. Deleting a highlight in Witbound deletes it there too. They go only to the server you signed in to. These services have their own privacy practices. Use a trusted server and HTTPS where available.
Sharing and device transfers
Sharing is initiated by you. Progress cards, selected passages, notes or audio clips go to the destination you choose, such as a Discord webhook, an Obsidian folder or another app through the system share sheet. Your chosen app or folder may sync those files using its own services. A local device transfer sends the books or audio you select to the other device.
Android translation
Android's optional translation feature uses Google ML Kit. Language recognition and translation run on the device, with language models downloaded when needed. Google documents that its SDK collects installation identifiers, device and app information, performance and error information, feature events, input/output sizes and language settings for diagnostics and usage analytics. Translation also uses Firebase services for model configuration; Google documents country-level information derived from connection addresses for this service. This is separate from Witbound's local reading statistics and the community-sync setting. See Google's ML Kit data disclosure, Firebase's Remote Config disclosure and on-device translation documentation.
Purchases
Witbound Plus is sold through the App Store and Google Play. Apple or Google handles payment information. Witbound receives the purchase and entitlement information needed to unlock Plus, restore purchases and confirm a transaction. Witbound does not receive your card or bank details. The stores process purchase data under their own privacy policies. A Witbound subscription you already have can be managed or cancelled through Apple's or Google Play's subscription settings.
Support, retention and your choices
If you contact support, we receive your email address and whatever you include in your message. We use it to respond, investigate problems and keep necessary support records. Please send only information relevant to the issue. Clubs data is kept as described in the Clubs section above. Cloud sync keeps no audio or words; its usage counts are deleted 35 days after a phone last used it. On iPhone and iPad, one fact (whether a device has had its free cloud book) is kept by Apple’s DeviceCheck for Witbound. Other community data has no expiry date: shared timing maps, shared to-read entries, Synced entries, Roadmap ideas and votes, and reports are kept until they are removed. When a better timing map replaces one, the earlier version is kept beside it, never served, so a bad replacement can be undone. Local app data stays until you remove it or the app's storage is cleared. Third-party services and backups have their own retention rules.
Where data-protection law applies, you may have rights to access, correct, delete or restrict the use of your personal data, and to complain to your data-protection regulator. Contact us using the address below. We may need enough information to locate the relevant data; a shared content fingerprint does not identify a Witbound user account. To withdraw a to-read list you shared, update Witbound, which takes it down. To delete your Clubs data and your Roadmap ideas, use Delete my club profile in Settings, or, without the app, email us as described under Clubs. To take back a Roadmap vote, tap it again. To withdraw your consent to Cloud sync, set Settings › Cloud sync to Off.
Children
Witbound does not ask readers for their age or build advertising profiles. If you believe a child has sent personal information to support, contact us so we can review and remove it where appropriate.
Changes
We will update this page when features or data practices change, and show the effective date above.
Contact
Privacy questions and requests: zarksided@gmail.com
