Body & Word Privacy Policy
Onyx Hawk LLC — Effective November 6, 2026
This policy covers the Body & Word mobile app and our optional Body & Word feedback board. For privacy questions or requests, email contactdev@onyxhawk.net. See our support page.
Information on your device
Body & Word stores alarms, reading progress, preferences, and other app settings on your device so its basic features can work without an account. Camera-based exercise checks process camera frames locally. The app does not save or upload camera images or videos as part of those checks. Optional skeleton troubleshooting exports are a separate, user-triggered action: if you export and share a file, the recipient receives the information in that file. Review it before sharing.
If you choose to use referral features, the app stores a bounded affiliate code locally. That code is not included in the usage events described below.
Optional usage sharing
If you enable usage sharing, the app sends limited usage events over HTTPS to our configured PostHog US service. We use them to understand feature use and investigate reliability problems, including onboarding failures.
The event payload is limited to an event UUID, a random per-installation identifier, the event name, a UTC timestamp, a test flag, and flags requesting that PostHog disable geographic enrichment and person-profile processing. Events cover app foreground activity; alarms saved, delivered, snoozed, or dismissed; mission and verse completion; and onboarding steps viewed, completed, or failing to save.
These payloads do not include repetition counts, workout details, Scripture text, names, personal setup answers, images, audio, advertising identifiers, or device profiles. The app does not send session replay through this integration. The installation identifier can connect events from the same installation; these events should not be considered completely anonymous. Network providers, including PostHog, necessarily receive connection information such as the IP address. We request no geographic enrichment.
You can disable usage sharing and clear local tracking in Profile > Privacy & referrals. Disabling sharing removes or rotates the local tracking identifier and clears pending local event records. It does not automatically erase events already delivered to PostHog. You may email us to request deletion of previously delivered information. Because we do not attach your name or email to these events, we may need information sufficient to locate the records and may not be able to identify them from your email address alone. Do not send passwords or private health information.
Cloud voice services, when available
Cloud voices depend on access availability. When you use those services, our server processes the requested Bible chapter, translation and voice, installation/device-key identifiers, access credentials, request status, and service-usage information needed to authorize downloads, produce or retrieve audio, and manage capacity and security. Generated Bible audio may be cached for reuse. This is generated narration, not a recording of your microphone. Network connections also expose connection metadata to the systems carrying them.
This policy does not mean that app accounts or paid subscriptions are available. They are not included in the current closed-test build. Optional feedback-board sign-in is a separate service.
Feedback board and support
Opening Feedback & ideas takes you to a separate browser-based Fider board. The app does not prefill personal identifiers, feedback text, or attachments. You choose what to submit.
Fider stores your sign-in email, display name, authentication records, settings, posts, comments, votes and related activity. Display names, posts and comments can be publicly visible, and voting activity may be visible through the board. Do not post passwords, private prayer requests, health details, or other sensitive information you do not want made public. Search-engine indexing is discouraged, but the board remains public.
The board is hosted on our server and uses Cloudflare for network delivery/security and Gmail SMTP to deliver sign-in and service emails. These providers process relevant connection and email information. Browser analytics are not enabled in Fider; an additional browser security policy blocks Cloudflare's injected analytics script. This does not prevent Cloudflare from processing requests as the network proxy or mean that infrastructure has no logs.
If you contact support by email or voluntarily share a troubleshooting export, we receive your email address, message and any information you choose to attach. We use this information to respond and troubleshoot.
Retention and deletion
Device data remains under the app's and operating system's local storage controls. Use available in-app controls or your device's app-data controls to remove it; clearing app data can remove alarms, settings and progress. Copies you export or share are outside those local controls.
We retain delivered usage information while needed for the purposes above, subject to provider retention controls. We have not established a verified fixed PostHog retention deadline and do not promise one here. Disabling collection is distinct from requesting deletion of previously delivered data.
Feedback-board records and cloud-service records are stored persistently for their functions, security and support. Generated audio and review files may remain cached for reuse. We have not set a universal automatic deletion deadline for these records. Warning/error and infrastructure logs may also be retained.
Deleting a Fider account clears or anonymizes its name, email and certain account-related records, but does not automatically remove authored posts or comments. Contact us separately if you want public contributions reviewed for removal. Our local feedback backups retain the latest 14 completed backup sets. This is not a guaranteed 14-day deletion deadline; removed information can remain in backups until those copies are replaced. Provider-controlled copies and logs follow the provider's applicable controls.
For access, correction or deletion requests, contact contactdev@onyxhawk.net. We will assess the request, whether we can identify the relevant records, and any applicable retention requirements. We may need to verify that the request concerns your information. We do not promise that uninstalling the app, disabling analytics, or deleting a feedback account removes all previously shared information.
Service providers and choices
PostHog processes optional usage events; our hosting systems process cloud-voice and feedback activity when used; Cloudflare processes feedback-board network traffic; and our email providers process support and board emails. Data can be processed outside your country, including in the United States. You can use basic app features without signing in, leave usage sharing disabled, and choose not to open or submit feedback. No marketing subscription is created by these choices in the current build.
Changes and contact
We may update this policy as the app or its services change. The effective date identifies this version. Material new collection or features will need corresponding disclosures and controls.
Onyx Hawk LLC
Privacy and support: contactdev@onyxhawk.net
## Launch-notification email signup
You can voluntarily request Body & Word launch notifications through our website. The form collects your email address and your affirmative consent to launch updates through an unchecked checkbox. Onyx Hawk LLC uses Loops to process the request and deliver launch notifications only. This does not create an app account, enroll you in unrelated marketing, or change your app analytics preference.
Loops double opt-in is enabled for new contacts. Where confirmation is needed, follow the provider's confirmation instructions. An accepted form request does not establish that every address received a confirmation email or that a previous unsubscribe was reversed. We do not override a contact's global subscribed status or remove provider suppression records through this form.
You can unsubscribe using the provider's email unsubscribe controls or contact contactdev@onyxhawk.net for removal requests. Loops retains contact, consent, confirmation and suppression information under its configured controls; we have not established a fixed deletion deadline. Suppression records may be retained to honor opt-out choices, and unconfirmed requests may remain pending until removed.
The signup service temporarily keeps keyed hashes for duplicate prevention and abuse limits, plus a consent timestamp, text version, source and provider result. It does not store your raw email address or IP address in this local signup database. These local records become eligible for cleanup after their short retention windows (up to 24 hours), with cleanup performed on subsequent requests. Network providers still receive connection metadata. The website does not send your signup email or consent to analytics.
Account and data deletion instructions
See our step-by-step deletion request page for feedback accounts, individual public contributions, and other data requests.
## Request removal of your information
See our data-deletion instructions for account, feedback and analytics requests.