Privacy Policy

Last updated: October 02, 2026

HookBook does not require a HookBook account. The app database is saved on your devices and, when database sync is enabled, in your private iCloud account. The developer does not receive or host a copy of your journal database, including its entries.

This policy explains how Prism32 LLC, the developer of HookBook, handles information in the app, on this website, and when you contact support.

Your app database

The HookBook database contains activities, partners, notes, medication records, and screening history. It is stored on your devices and can sync through your private iCloud account. It is not hosted on the developer’s servers.

This storage arrangement does not prevent selected information from those records being submitted separately to analytics. The categories below explain what is sent.

iCloud sync, photos, backups, and recovery

Database sync uses your private iCloud account when enabled. Photos and partner avatars can be saved in the app’s iCloud file container whenever it is available, independently of the database-sync setting. Turning off database sync does not necessarily keep those files out of iCloud.

The developer does not have access to the journal database stored on your devices or in your private iCloud account and cannot restore lost or deleted entries on your behalf. HookBook includes a free backup feature for exporting your database. Keep backups somewhere secure so they are available if you need to restore your records.

User-created backups also reside in iCloud Drive. A backup, export, or screenshot can contain sensitive information; keep copies somewhere you trust and consider their contents before sharing them.

Apple’s services are covered by Apple’s privacy information.

Analytics and information derived from your records

Database storage and analytics collection are separate. HookBook sends usage information to Firebase Analytics. The app also uses AppsFlyer for attribution and RevenueCat for purchase processing. These services process information outside your private iCloud database.

Firebase Analytics helps improve HookBook by collecting app usage, technical data, and selected in-app activity and settings information. Explicit analytics events do not submit complete activity entries, note bodies, partner contact details, photo files, precise locations, individual dose records, screening results, or Apple IDs. This does not mean journal data is entirely excluded from collection.

Firebase also collects usage and technical information and uses an app-instance identifier to associate events with an installation. Device-identifier collection depends on the SDK’s configuration and identifier availability. No HookBook account is required, but collection should not be understood as fully anonymous.

Google describes its Analytics data collection, collection controls, and privacy policy.

AppsFlyer attribution

AppsFlyer starts when HookBook launches and is used for attribution, such as understanding how installs relate to marketing. Its SDK can process attribution and technical information and identifiers, depending on its configuration and available signals.

The app passes the AppsFlyer identifier to RevenueCat. This allows an attribution identifier to be associated with purchase processing even without a HookBook account.

See the AppsFlyer services privacy policy for its data-processing practices.

RevenueCat and purchases

RevenueCat processes in-app purchases and subscription information to support HookBook Plus. It receives purchase information and the AppsFlyer identifier supplied by the app. Purchase processing is separate from storage of your app database.

RevenueCat explains its privacy practices and App Store data disclosures.

This website

This website has no analytics scripts, advertising trackers, email collection forms, or tracking cookies. Its images, fonts, and scripts are served locally by the website’s host. The app services described above are not installed in this website.

The hosting provider may process IP addresses, requested URLs, and other technical request information to deliver and secure the site. External links take you to services with their own privacy practices.

When you contact support

Emailing support shares your email address and whatever you choose to include with the developer. That information is used to respond and help resolve your request. Do not include intimate photos, partner details, or medical records unless necessary and after agreeing on a suitable way to share them.

Your information and privacy requests

You control what you record and what you choose to export or share. Manage journal content in the app and iCloud storage through Apple’s settings. Photos, backups, and copies you export or share may need to be removed separately.

Deleting local or iCloud records does not necessarily delete analytics, attribution, purchase information, or support correspondence. For questions about retention, deletion, access, or other privacy requests, use the contact address below. The absence of a HookBook account does not mean these services process no information.

Protecting your records

HookBook supports Face ID and Touch ID protection on compatible devices. Protect access to your device and Apple account, and take care with exported backups. App locks protect access to the app; they do not prevent the analytics and attribution processing described above or protect a copy shared outside the app.

Changes to this policy

Policy updates will be posted here with an updated date. Changes to HookBook’s data-handling practices will be explained in this policy.

Contact

For privacy questions, contact Prism32 LLC, the developer of HookBook, at info@hookbook.app.