SealbookThe short version. Sealbook has no account or social profile. Your journal stays on your iPhone and, if you enable it, syncs through your own private iCloud database with end-to-end encrypted fields. We do not sell personal information or use advertising or cross-app tracking. Limited product analytics and purchase infrastructure are described below.
1. Your journal and evidence
This policy applies to the Sealbook iOS app and this website. Sealbook is a personal record-keeping tool, not a law firm or legal service. Entries, attachments, search terms, passcode, recovery code, child labels, and settings are stored locally on your device. We do not operate a user-content server and we do not make your journal visible to the other parent, another Sealbook user, or the public.
If you enable iCloud sync, journal content is stored in your own CloudKit private database with end-to-end encrypted fields. iCloud is governed by Apple and your Apple Account. When an entry is sealed, Sealbook creates a SHA-256 fingerprint and may send only that fingerprint—not readable entry text, attachments, names, or locations—to DigiCert’s RFC 3161 timestamp service. The returned timestamp token is stored with your record.
2. Device permissions
Sealbook requests access only in context, and you can decline or change permissions in iOS Settings.
- Location (When In Use): optional for exchange check-in; check-in works without it.
- Photos, camera and files: only when you choose an attachment.
- Microphone and Speech Recognition: only for your own voice notes.
- Notifications: optional reminders and exchange actions. Notifications never show entry text, names, or places.
- Face ID / Touch ID: optional device-side app unlocking.
3. Limited data we process
Sealbook uses a random app installation identifier for product analytics and purchase entitlements. It does not require your name, email, phone number, or an account. PostHog receives usage events, screen views, and limited diagnostics tied to this random identifier. It must not receive journal text, attachments, photos, files, names, locations, passcodes, recovery codes, or search terms. Session replay masks text inputs and images and excludes passcode and recovery-code screens.
You can turn off “Share anonymous usage” in Sealbook Settings. This stops PostHog analytics, masked replay, and diagnostic reporting for that installation. Apple processes payments. StoreKit and Superwall may process purchase status and the random app identifier so the app can present paywalls, unlock purchases, and restore eligible purchases. We never receive payment-card details.
4. Service providers and disclosures
We use Apple (StoreKit, iCloud/CloudKit, push notifications and optional device analytics), PostHog (product analytics and masked replay), Superwall (paywall and entitlement), and DigiCert (hash-only timestamping). We disclose data only as needed to operate these services, comply with law, or protect users and our rights. We do not sell personal information, run third-party ads, use an IDFA, or engage in cross-app tracking. This website has no advertising cookies or account system; normal hosting logs may process technical information to deliver and secure it.
5. Your choices and privacy rights
You can export your journal, remove content where the app permits, or use Delete All Data in Sealbook Settings. You can disable analytics in the app and manage permissions in iOS Settings. Depending on where you live, you may have rights to access, correct, delete, restrict, object to, or receive information about personal data we process. Email andrew@xboostapp.io with “Privacy Request” in the subject; we may need information to verify your request.
6. Retention and security
Local data remains on your device until you delete it or remove the app. iCloud-synced content remains in your private iCloud database until you delete it. Analytics and diagnostics are retained only as reasonably needed to operate, improve, and secure Sealbook. We use standard safeguards, including protected device storage, encrypted connections, SQLCipher local database encryption, and CloudKit security. No system is perfectly secure; protect your device passcode and recovery materials.
7. Contact and changes
Sealbook is published by Xboost. For privacy questions, email andrew@xboostapp.io. We may update this policy as Sealbook or applicable requirements change; the revised version will appear here with a new date.