Dr. DookieBack to home

Steelshort LLC · Dr. Dookie

Consumer Health Data Privacy Policy

Effective Date: November 19, 2026

Version: 2026-11-19. Feature descriptions apply when the feature is available and you choose it. Some online functions remain in testing. Privacy requests can be sent to privacy@docdookie.com even when an in-app route is unavailable.

This Consumer Health Data Privacy Policy describes the consumer health data processed by Steelshort LLC (“we,” “us,” or “our”) in connection with Dr. Dookie. It addresses the categories, sources, purposes, disclosures and rights applicable to that data. Privacy and consumer-health-data requests: privacy@docdookie.com; 2108 N St #17999, Sacramento, CA 95816, United States. Report security incidents or vulnerabilities to security@docdookie.com; general help and accessibility questions go to support@docdookie.com. The general Privacy Notice is available separately at Privacy Policy. Consumer Health Data Privacy Policy: https://docdookie.com/health-privacy/.

On this page
  1. 1 Categories purposes and processing
  2. 2 Sources
  3. 3 Disclosed categories and recipients
  4. 4 Choices and rights
  5. 5 Material changes

1 Categories purposes and processing

1.1 Recorded information. The application processes information the user elects to record concerning bowel movements and stool observations; digestive pain, bloating and gas; food, nutrient estimates and water; medication, supplements and alcohol; sleep, stress, activity and weight; menstrual periods and cycle settings; and related dates, titles, tags, notes and photographs. It also processes selected health goals, concerns, eating style, allergies, sensitivities and restrictions. Optional gender or pronoun information may be associated with those records. These data are used to maintain the user's journal and produce requested displays, calculations, summaries and reports.

1.2 Health imports and derived information. With your permission and reviewed import choice, the app processes Apple Health sleep, exercise-minutes and step-count records and derives requested summaries. Saved imports remain local by default, but are included when you separately enable journal backup or expressly share a report/export. Marked imports are excluded from automatic AI context, social trends, automatic group log sharing/participation and reward synchronization. Device permission is not consent to every subsequent disclosure.

1.3 AI information. When separately authorized, we process selected photos, descriptions, questions, recent conversation, companion information and permitted journal or food-preference context to provide AI assistance through OpenAI. The journal context may include entry titles/tags, goals, concerns, eating style and dated observations, although the automatic context excludes the notes field, journal photos and marked Apple Health imports. Information that a user independently types into a message remains part of that message.

1.4 Social and location information. We process voluntarily shared health statuses, selected trends, captions, photos and messages to provide Friends communications. Following separate map-history authorization and location permission, we process coordinates, place/address, date, status and related identifiers from eligible newly saved current logs to maintain an optional map. The map retains visits even when nearby visits are displayed as one marker. We process associated reviews, comments, replies, likes and activity records to support the selected friends' discussion.

1.5 Associated identifiers. Installation, account, invitation, transaction, interaction and security identifiers may be linked to the preceding information. They support authentication, selected access, delivery, rewards, limits, duplicate prevention, security and rights handling. An installation-linked record is not treated as anonymous solely because it lacks a legal name. The full journal is not uploaded merely to credit growth; that route uses opaque saved-log identifiers and service receipt times.

1.6 Optional journal backup. After a separate Settings consent and Sign in with Apple, you can synchronize journal entries/photos, including saved Health imports, to our hosted service and recover them on another device using the same Apple account. We process the Apple account association, protected authorization tokens, connected installations and sync/deletion records for that purpose. Our service manages the encryption keys; this is not end-to-end encryption or iCloud. Signing in alone does not upload the journal. Manual first sync and separately optional automatic sync follow your choices. Backup does not authorize AI, social or advertising use.

1.7 Past optional analytics. Dr. Dookie 1.5.113 and later do not send digestive concerns, age-range/gender categories or other setup answers for optional analytics, and have no analytics opt-in. The service stopped accepting new optional analytics events on November 10, 2026. Earlier separately authorized collection could include installation-linked screen/actions, active time, app/device versions, subscription choices/outcomes and selected age range, gender category, digestive concerns, goals, eating style and app style. Health-related answers and app-use patterns can reveal health information; those records are not anonymous merely because their visitor label is pseudonymous. Earlier collection excluded journal/Health contents, photos, messages, precise location, names, exact birth dates, free-form profile text, pronouns, allergy details and payment credentials. Retained records remain subject to the published retention, export and deletion rights.

1.8 Groups and subscriptions. Selected group stickers reveal log category and, for poop stickers, Good/Bad/No status; separately selected messages/photos and map places reveal their selected contents to the group. Monthly participation can send a category for points after enrollment. These features do not share the full journal. Subscription/referral and creator-attribution records may reveal use of a health-related app even without journal content. They are used for access, rewards, purchase verification and the enabled commission program, subject to the recipient limits below.

2 Sources

2.1 Sources are you; your device and selected permissions; reviewed Apple Health imports; accepted friends and group members; Apple purchase verification and optional backup authentication; RevenueCat and Insert Affiliate for enabled subscription/attribution processing; and support/rights communications. We derive records from these inputs. We do not obtain your full journal from an employer, insurer or clinician through the described service.

3 Disclosed categories and recipients

3.1 Authorized AI inputs in Section 1.3 are sent through our gateway to OpenAI. Our hosting/storage providers process online feature records, optional backup contents and retained past analytics. Apple processes selected authentication, purchase and mapping functions. Host names/locations and other processors: Hetzner Cloud hosts the primary app service in Ashburn, Virginia, United States; Google Workspace handles email communications. OpenAI, Apple, RevenueCat and Insert Affiliate handle the feature-specific records described here and in the general Privacy Policy. Their support, security and service processing may occur in the United States and other countries where they operate. Queries you choose to send to an external service can contain health information. Authorized Steelshort LLC personnel may access necessary records for operation, support, safety, security and rights handling; hosted information is not promised to be inaccessible to the operator.

3.2 Selected Friends stories/messages go to their chosen accepted-friend or Close Friends audience. Individual map sharing goes to selected friends. Private Group messages/photos, category/status stickers, permitted participation displays and selected shared places go to current members, who need not be your individual friends and may see retained content from before joining. Audience changes can grant access to existing applicable content. Current access controls, blocking and removal apply through the service; recipients may preserve independent copies.

3.3 A report/export goes to the person or service you select. RevenueCat receives account and subscription information for enabled purchase/access functions; the enabled creator program sends attribution and subscription-event data to Insert Affiliate, through explicit code association and a minimized attributed-purchase feed. Creator commission reporting and link-visit information are described in Section 7.5 of the general Privacy Policy. Journal/Health content, AI conversation, photos and precise map history are not sent through those integrations. Corporate affiliates receiving consumer health data, if any: none in the current app service. Corporate affiliates and commissioned creators are different recipient categories. Legally required disclosures remain subject to applicable health-data restrictions.

3.4 We do not sell consumer health data to data brokers, use it for targeted behavioral advertising or use health content to train general-purpose AI models. Past consent to optional product analytics does not authorize those uses. The reviewed app disables the creator SDK's automatic deferred matching and clipboard modes, but external link/provider practices require their separate assessment. External code pages can record visits and ordinary connection information for click analytics. The app’s code-only settings do not promise that independent sites collect no information; we do not authorize cross-service advertising use of health content. No blanket statement that all app-related data is anonymous or untracked replaces that assessment.

4 Choices and rights

4.1 AI, Health imports, map collection/sharing, Groups and backup have their described choices. Optional usage analytics has been retired. Consent to collect and consent to share are distinct where required, and Terms acceptance alone does not supply either. Use Settings → Privacy controls, Privacy & permissions → Past usage data or Journal backup & sync, the Group controls, or privacy@docdookie.com to change choices or request help. Turning off map collection/visibility leaves existing map records. Backup sign-out leaves the hosted copy; Delete cloud journal removes it for connected devices but not downloaded local copies. Full account deletion also covers a previously connected backup after sign-out.

4.2 Where applicable law provides the right, you may request confirmation/access, information identifying applicable recipients, withdrawal/cessation and deletion of consumer health data. Use Settings → Export or delete my account or email privacy@docdookie.com. We use proportionate authentication and do not ask you to email recovery keys or full health records. Applicable response, downstream-notification and deletion periods govern. An account-deletion receipt distinguishes primary records, device data, processors and backup copies; no unresolved required stage is represented as complete. Only a specific lawful retention basis can justify retained records. Sections 9.1–9.12 of our general Privacy Policy describe category criteria, moderation periods, provider work and restricted recovery copies, including the absence of a uniform automatic backup-erasure period in the current testing service.

4.3 A denied request may be appealed through privacy@docdookie.com with the subject “Consumer Health Data Appeal.” Identify the original request and the disputed decision. We will provide the applicable written determination and regulator information. Consumers may also contact the Washington Attorney General or Nevada Attorney General, as applicable. We will not unlawfully discriminate for exercising these rights.

4.4 Review and correct local journal/profile records in the app; request review of other retained records at privacy@docdookie.com. The local JSON export excludes photos and complete server records. The separate account export combines local journal/photos/conversation with available authored server data and the connected backup. It omits secrets and other people's private records. Removing a local log does not by itself remove an independently shared post or map place; use those controls or account deletion. During backup sync, item deletions propagate through the connected journal. Past optional analytics can also be exported or deleted through Past usage data; upgrading to 1.5.113 or later discards unsent optional events and preserves pending deletion requests.

4.5 Retention and copies. Local entries remain until removed. Hosted backup remains until item, cloud or connected-account deletion. Friends stories expire from view after 24 hours and direct content after 30 days, followed by cleanup; Group content follows content-removal/member-departure/account-deletion triggers instead. Past optional analytics events have a 30-day limit with scheduled cleanup; consent proof is separate. Closed moderation-report details normally expire after 30 days from the latest decision, minimized moderation audit after 90 days and existing preapproval holds after seven days, with open appeals and minimum active enforcement preserved. Minimized transaction/anti-reuse proof, processor records and recovery copies follow the purposes and limits described in the general Privacy Policy; no fixed provider-erasure period is promised. Independent recipient/export copies may remain outside our control. Restoring our operational backups must not restore deleted or withdrawn data to service access.

5 Material changes

5.1 Material changes will be identified through a prominent dated notice on this page and within the app before additional processing begins, or by direct contact where available and legally appropriate and a revised effective date. Additional health-data categories, purposes or disclosures requiring consent will not commence merely because a revised policy has been posted. The required affirmative choice will be obtained before the relevant processing.