Codex Books is a personal library cataloguing application. References to "we", "us", or "our" in this policy refer to the developer(s) of Codex Books, operating under the Shinro name. If you have any questions about this policy, please contact us using the details at the bottom of this page.
We do not collect or receive your library content. Codex Books does not use your library data to track or profile you.
Your library data — titles, authors, ISBNs, cover images, notes — lives on your own devices. On iPhone and iPad it also syncs through your personal iCloud account; on Android a copy is placed in your own Google account by Android Auto Backup. Both copies are held under your account rather than ours: we never see your library, access it, or store it on our own servers.
Camera access is used solely to scan barcodes or photograph covers. All image processing happens on-device and nothing is sent to us.
When the app crashes or encounters an error, Firebase Crashlytics may automatically collect limited technical diagnostic data. This may include crash stack traces, exception details, relevant application state, the date and time of the crash, the app version, device model, operating system version, device state, a Crashlytics installation UUID, and a Firebase installation ID. These pseudonymous identifiers help distinguish affected app installations and may be considered personal data under some privacy laws. Crash reporting is enabled by default, so that a crash during startup is still captured, and it can be switched off in the app under Settings; the choice persists across restarts and app updates.
Your library data is yours alone. On Apple devices it is synced between them by Apple's iCloud infrastructure; on Android it is backed up to your own Google account by Android Auto Backup. Neither copy passes through us.
We use crash-reporting data only to identify, diagnose, and fix technical problems, monitor app stability, and improve the reliability and security of Codex Books. We do not use this data for advertising, marketing, or profiling.
If you contact us for support, any information you share in that exchange is used solely to respond to you.
Codex Books uses iCloud to sync your library across your Apple devices. This is enabled by default. Your data is stored in your personal iCloud account — not on our servers — and is subject to Apple's Privacy Policy.
You can disable iCloud sync at any time in your device's Settings under your Apple ID → iCloud → Codex Books.
On Android there is no live sync between devices. The library database is included in Android Auto Backup, which the system copies to your own Google account and restores when you reinstall the app. The backup is run by the device, not by us, and you can turn it off in Settings under Google → Backup. What Google does with that copy is subject to Google's Privacy Policy.
Codex Books looks book data up in three catalogues, tried in order: the Google Books API, then Open Library (operated by the Internet Archive), then isbnsearch.org for new and self-published titles the first two do not carry. A lookup carries only the ISBN, or the words you typed when you search by title or author — no personal information. Please refer to Google's Privacy Policy for details on how Google handles such requests, and to the Internet Archive's and isbnsearch.org's own policies for theirs.
When you choose to translate a non-English book title or description, Codex Books uses the MyMemory Translation API. Only the text being translated is sent — no personal information. See MyMemory's Privacy Policy for details.
Codex Books uses Firebase Crashlytics, a service provided by Google, for crash and error reporting. It is on by default and can be switched off in the app under Settings. Diagnostic data is transmitted to and processed by Google on our behalf. For more information, see Privacy and Security in Firebase and Google's Privacy Policy.
We do not integrate advertising or behavioral analytics SDKs. Firebase Crashlytics is used only for crash and error reporting.
Crash reporting is used to understand the circumstances in which Codex Books fails so that we can correct defects and improve app stability. Crash reports are associated with pseudonymous installation identifiers rather than your name or email address. We do not intentionally include your library content, photographs, notes, contact details, or other directly identifying information in crash reports.
Firebase states that Crashlytics retains crash stack traces and associated identifiers, including Crashlytics installation UUIDs and Firebase installation IDs, for 90 days before beginning the process of removing them from its live and backup systems.
Firebase Crashlytics operates on Google's global infrastructure, so diagnostic data may be processed in countries outside the country where you live. Google applies the safeguards described in its Firebase Data Processing and Security Terms.
Where data-protection law requires a legal basis, we process this limited diagnostic data on the basis of our legitimate interest in maintaining a stable, secure, and reliable application.
Your library data lives on your device, and in your own iCloud or Google account, which you can manage directly through Apple's or Google's settings at any time. Deleting the app removes the local copy.
Depending on where you live, you may have rights regarding personal data processed through crash reporting, including the right to request access, correction, deletion, restriction, or objection, and the right to lodge a complaint with your local data-protection authority. Because crash reports are normally associated only with pseudonymous installation identifiers, we may not be able to identify a particular report as yours without additional information.
If you contacted us for support and want any correspondence removed, reach out at the address below.
We may update this Privacy Policy from time to time. When we do, we will revise the "Last updated" date at the top of this page and, where appropriate, notify you within the app. Continued use of Codex Books after changes constitutes acceptance of the updated policy.
If you have any questions or concerns regarding this Privacy Policy, you can reach us at:
Email: contact@shin.ro