Effective date: 9 June 2026 · Last updated: 24 October 2026
This Privacy Policy explains how HushBook ("HushBook", "we", "us", "our") handles information when you use (a) the HushBook mobile application (the "App"), (b) HushBook Desktop for Windows and macOS (the "Desktop App", described in Section 5), and (c) our website https://hushbook.app (the "Website").
We never receive your audio. HushBook has no accounts and no server of its own; your audiobooks, transcripts, quotes and listening data are created and stored only on your own devices. Your audio leaves your phone only if you choose to send a book to HushBook Desktop on your own computer, and then only over your local network.
Data controller. HushBook is operated by Rakesh Aditya. For any privacy question, request, or complaint, you can contact us at hello@hushbook.app.
1. Information stored
A. Information stored on your device. The App creates and stores the following only on your device:
- downloaded audiobooks and associated files;
- word-level transcripts generated by the HushBook Engine on-device;
- saved quotes;
- listening data such as progress, goals, streaks, badges, "neuron score", and accessibility profile.
We do not receive your audio. It leaves your phone only if you choose to send a book to HushBook Desktop on your own computer (see Section 5).
B. Crash & performance diagnostics. When the App crashes, encounters an error, or is running slowly, the App sends diagnostic data to help us identify and fix the issue. We use Firebase Crashlytics, a crash-reporting service provided by Google LLC ("Google"), for this purpose. Diagnostics may include:
- crash stack traces and error logs (technical traces showing where code failed), together with short technical notes describing what the App was doing immediately before the error;
- device and app information (device model, operating system version, available memory and storage, whether the device is rooted or jailbroken, App version, language/locale);
- stability and performance signals (for example, whether the operating system closed the App while it was working, or whether a transcription stalled);
- app state at the time of the error, limited to technical settings: whether HushBook Pro is active, the transcription engine and its stage, the audio file format, the number of chapters, an approximate length band for the book, which player view is open, and the selected accessibility profile;
- identifiers: an installation identifier and a Firebase installation identifier generated by Crashlytics, and the randomly generated, per-installation identifier that HushBook also uses with RevenueCat to manage purchases (described in Section 4). None of these is your device's advertising identifier or a hardware identifier.
Because the per-installation identifier is also used with RevenueCat, diagnostics can be linked to the purchase record for that installation. We use this link only to provide support and fix problems (for example, to investigate an error that affects a purchase), and never for advertising or tracking.
The App is designed so that diagnostics do not include book titles, author names, or file names, and file and folder locations are removed from reports before they are sent. Diagnostics do not include your audio, the content of your transcripts, your saved quotes or notes, or screenshots (except where such information is inadvertently included in an error message). As with any internet service, Google receives the IP address of the device sending a report as part of the network connection.
Diagnostic data is transmitted over an encrypted connection (encrypted in transit). Google acts as our data processor for diagnostics under the Firebase Data Processing and Security Terms, and may process this data in the United States and in other countries where Google or its agents maintain facilities. See Firebase's privacy information at firebase.google.com/support/privacy and Google's Privacy Policy at policies.google.com/privacy.
C. Information you provide when contacting us. If you contact us at hello@hushbook.app, we collect:
- your email address;
- the contents of your message and any attachments you choose to send;
- any information you include to help resolve your issue (for example, device details).
D. Website information. Our Website uses Google Analytics, provided by Google, to understand in aggregate how visitors use the site (for example, which pages are viewed, how visitors arrive, the type of device and browser, and an approximate location derived from the IP address). Google Analytics uses cookies or similar browser storage to do this. We use this information only to improve the Website and do not use it to show you advertising. You can block or delete these cookies in your browser settings, or install Google's Analytics opt-out browser add-on. In addition, our hosting provider/CDN may automatically process basic server logs (e.g., IP address, user-agent, timestamp, and requested URL) for security, abuse prevention, and reliable delivery of the site.
E. App permissions. The App requests only the permissions needed for its features: access to audio files you choose to import (to play and transcribe your own files on your device); camera or photo access (only when you set a profile picture, create a shareable quote image, or scan the pairing code shown by HushBook Desktop); local network access (only to find and connect to HushBook Desktop on your computer); and notifications (to show playback and download/transcription progress). The App does not request microphone or location access.
2. How we use information
We use information only for the purposes below:
- to operate the App on your device (on-device data is used by the App locally);
- to maintain and improve reliability (crash and performance diagnostics);
- to respond to you (support emails and troubleshooting);
- to protect the Website and App (security, fraud/abuse prevention, and ensuring availability).
We do not sell personal data, and we do not use it for targeted advertising.
3. Legal basis / lawful use
Where the Digital Personal Data Protection Act, 2023 (the "DPDP Act") applies, we process personal data:
- for purposes for which you have consented (for example, when diagnostics are enabled by your device/App settings, or when you email us); and/or
- for legitimate uses permitted under applicable law (such as responding to requests, maintaining security, and preventing fraud), as applicable.
Where the EU/UK General Data Protection Regulation ("GDPR") applies, our legal bases under Article 6 are:
- Crash & performance diagnostics and server logs — our legitimate interests (Article 6(1)(f)) in app reliability, security, and abuse prevention. We have weighed these interests against your rights, and you may object at any time;
- Website analytics — our legitimate interests (Article 6(1)(f)) in understanding how the Website is used, or your consent where applicable law requires it;
- Responding to your support emails — taking steps at your request and our legitimate interests in providing support (Article 6(1)(b)/(f));
- Any future paid in-app purchases or subscriptions — performance of a contract with you (Article 6(1)(b)).
4. Sharing and third parties
We may share limited information with the following categories of service providers solely to run and support HushBook:
- Crash/performance provider: Google, through Firebase Crashlytics, acting as our processor for diagnostics (described above).
- Website analytics: Google, through Google Analytics, for Website usage statistics (described in Section 1(D)).
- Platform providers: Apple App Store (including the Mac App Store) and Google Play. When you make a paid purchase, they act as independent controllers and process payment and purchase-related information under their own policies (Apple, Google). We do not receive your full payment-card details.
- Subscription management: RevenueCat processes purchase/receipt data and an anonymous app-user identifier on our behalf to manage your entitlements when you make a paid purchase and, if you pair HushBook Desktop, to confirm your HushBook Pro status on your computer (see Section 5.4) (RevenueCat privacy).
- Model hosting: speech-recognition models are downloaded to your device from Hugging Face (huggingface.co) when you set up on-device transcription. That host receives standard request information (such as your IP address and the model file requested) under its own policy, and receives no HushBook account or app content.
We only engage service providers that are contractually bound to protect this data to a standard equivalent to this policy and to use it solely to provide their service to us. Some providers may process data outside your country, including outside the EEA/UK; where that happens we rely on appropriate safeguards (such as the provider's standard contractual clauses or equivalent transfer mechanism).
4.1 Public-domain catalogue (LibriVox & Internet Archive). If you choose to browse, search, view details, stream, or download titles from the App's public-domain catalogue, the App must connect to third-party services such as LibriVox and the Internet Archive (archive.org) to fetch search results, metadata, and files. These services act as independent controllers of any information they receive. When the App makes these requests, those third parties will receive certain information as part of standard internet communications, and they will process it under their own privacy policies and terms. HushBook does not control how those third parties use or retain that information.
What can be shared with archive.org:
- IP address;
- User-Agent header;
- search query text;
- applied filters;
- sort preference;
- pagination/page number;
- book identifier (sourceId).
What is not shared:
- no user account, email, or device ID;
- no authentication tokens;
- no app-internal analytics back to archive.org.
Requests to third-party providers are subject to their own terms and privacy policies, and we do not control how those third parties process data. HushBook does not add advertising identifiers or create a HushBook-side profile for these requests. However, because these requests go directly to third-party services, those services may be able to associate requests using network and device information (such as IP address and user-agent) in accordance with their own policies.
5. HushBook Desktop (Windows and macOS)
This section applies to the Desktop App. Unless this section states otherwise, the rest of this Privacy Policy applies to the Desktop App in the same way as it applies to the App. The Desktop App has no accounts and does not connect to any HushBook server. It can be used without a phone, and it never sends your audio, transcripts, or library to us.
5.1 Information stored on your computer. The Desktop App creates and stores the following only on your computer:
- audiobooks and ebooks you add, including books you send from your phone;
- transcripts and synced read-along text generated on your computer, and the speech-recognition models used to create them;
- listening and reading data, and your settings;
- technical logs and crash files used to diagnose problems, which may contain file names or book titles;
- if you pair a phone: the phone's name and identifier, the security keys used for the connection, and the RevenueCat app-user identifier described in Section 5.4. Security keys and pairing details are kept in your operating system's protected storage (Windows data protection or the macOS Keychain).
5.2 Connecting your phone. You may choose to pair the App on your phone with the Desktop App, either by scanning a code shown on your computer or by confirming matching numbers on both screens. Once paired:
- your phone and computer communicate directly over your local network (for example, your home Wi-Fi) using an encrypted connection tied to the paired devices. The Desktop App refuses connections that do not come from your local network, and no data passes through a HushBook server;
- the Desktop App announces itself on your local network using your computer's name so that your phone can find it. Other devices on the same network may be able to see that name;
- the devices exchange the details needed to operate the connection, such as device names, platform, app version, and supported file formats;
- when you choose to transcribe a book on your computer, the App sends the audio files, the cover image, and book details (such as title, author, chapter list, and duration) to the Desktop App. The App asks before sending a book, unless you have chosen to send new books to your computer automatically. The Desktop App keeps a copy of the book in its library on your computer and returns the finished transcript to your phone.
You can end the connection at any time by choosing to forget the computer in the App or to forget the phone in the Desktop App.
5.3 Connections to third parties. As with the App, the Desktop App connects to third-party services only to provide features you use. It downloads speech-recognition models from Hugging Face when transcription needs them (and checks whether that host can be reached), and it fetches catalogue search results, metadata, cover images, and audio from LibriVox and the Internet Archive when you browse or download titles, including when it resumes a download you started earlier. Section 4 describes what these services receive.
5.4 HushBook Pro on your computer. HushBook Pro in the Desktop App can come from the purchase on your paired phone. To make this possible, the App shares its RevenueCat app-user identifier (a random identifier, not your name or email address) with the Desktop App during pairing, and records a random identifier of the paired computer with RevenueCat. The Desktop App sends that app-user identifier to RevenueCat to check whether HushBook Pro is active and stores the result on your computer. On macOS, you may also buy HushBook Pro in the Desktop App through the Mac App Store; Apple processes the payment and RevenueCat manages the entitlement, as described in Section 4.
5.5 Diagnostics. On Windows, the Desktop App does not send crash reports, analytics, or usage data; its logs and crash files stay on your computer unless you choose to send them to us, for example with a support email. On macOS, the Desktop App sends crash and performance diagnostics to Firebase Crashlytics on the same terms as the App, as described in Section 1(B).
5.6 Permissions on your computer. The Desktop App uses only the operating-system permissions its features need: access to the files and folders you choose (on macOS, the Desktop App runs in Apple's App Sandbox and can reach only the locations you select); local network access, to find and connect to your paired phone (on Windows, you may be asked to allow HushBook through the firewall); and notifications, to report transcription and transfer progress (on macOS, the system asks for your permission first). The Desktop App does not use your microphone, camera, or location. It does not start automatically when you sign in to your computer and does not keep running after you quit it; while it is open, it may remain available from the system tray (Windows) or the menu bar (macOS) after you close its window.
5.7 Deleting Desktop App data. You can delete individual books within the Desktop App. Forgetting the paired phone removes the phone's details, its RevenueCat app-user identifier, and the stored HushBook Pro status from your computer. To remove all Desktop App data:
- Windows: uninstall the Desktop App and, if any data remains, delete the folder
%APPDATA%\com.hushbook\hushbook; - macOS: delete the Desktop App and its data folder at
~/Library/Containers/com.hushbook.hushbook.6U2CKDN54G. Pairing details kept in the macOS Keychain are not removed when the app is deleted; you can remove them with the Keychain Access app.
Data on your phone and on your computer is stored separately: deleting data on one device does not delete it from the other.
6. Data retention
- On-device App data: stored on your device until you delete it within the App or uninstall the App.
- Desktop App data: stored on your computer until you delete it as described in Section 5.7.
- Crash/performance diagnostics: Firebase Crashlytics retains crash reports and their associated identifiers for 90 days, after which they are automatically deleted.
- Website analytics: retained in Google Analytics for no longer than 14 months, after which it is automatically deleted.
- Support emails: retained for up to 24 months after your request is resolved, unless a longer period is required to maintain reasonable support records or by law.
7. Your choices and rights
Depending on applicable law, you may have rights such as:
- access to personal data we hold about you;
- correction of inaccurate personal data;
- erasure of personal data;
- restriction of processing;
- data portability;
- objection to processing based on our legitimate interests;
- withdrawal of consent at any time, without affecting processing already carried out before withdrawal;
- grievance redressal.
To exercise any of these, email us at hello@hushbook.app; we aim to respond within a reasonable time and in line with applicable law. If you are in the EU or UK, you also have the right to lodge a complaint with your local data protection supervisory authority (in the UK, the Information Commissioner's Office (ICO)).
8. How to delete your information
- App data: delete individual books, transcripts and quotes inside the App (where available), reset in-App data (if provided), or uninstall the App to remove locally stored data.
- Desktop App data: follow the steps in Section 5.7.
- Diagnostics: uninstalling the App stops future diagnostics from being sent. To request deletion of diagnostic data already received, email hello@hushbook.app; we will action verified requests within a reasonable period.
- No account: HushBook has no user accounts, so there is no account to delete; removing the App and the Desktop App and requesting deletion of diagnostics (above) clears the data associated with you.
9. Security & data breaches
We use reasonable technical and organizational measures, including encryption in transit, to protect the limited personal data we process. No method of transmission or storage is completely secure; however, if a breach affecting your personal data occurs, we will notify you and the relevant authorities where required by applicable law (including the DPDP Act and, where it applies, the GDPR).
10. Children
The App is not directed to children and is not intended for those below the applicable age of digital consent in their jurisdiction. We do not knowingly collect personal data from children without verifiable parental or guardian consent, and our diagnostics are not used to profile or target children. If you are a parent or guardian and believe a child has provided personal data to us, please contact hello@hushbook.app and we will delete it.
11. Changes to this policy
We may update this Privacy Policy from time to time. We will update the "Last updated" date above. Material changes may be communicated through the Website or App release notes where appropriate.
12. Grievance / Contact
For questions, requests, or complaints, contact us by email at hello@hushbook.app.
Response timeline: we aim to acknowledge and respond within a reasonable time and in line with applicable law.
We process personal data only occasionally and on a small scale, and have concluded that we are not required to appoint an EU/UK Article 27 representative or a Data Protection Officer. If this changes, we will update this policy with the relevant details.