Steelshort LLC · Dr. Dookie
Privacy Policy
Effective Date: November 19, 2026
Owner and Operator: Steelshort LLC
Brooks Taylor is the individual developer releasing Dr. Dookie on behalf of Steelshort LLC through his personal Apple Developer account until distribution moves to Steelshort LLC's organization account. Apple may display Brooks Taylor as the developer or seller during this transition. Steelshort LLC remains the owner and operator responsible for the processing described in this Notice.
Mailing Address: 2108 N St #17999, Sacramento, CA 95816, United States
Privacy Contact: privacy@docdookie.com
Version: 2026-11-19. This policy covers features when they are available and you use or enable them. Some online features remain in testing or are not yet available for public use. Publishing this policy does not enable a feature or give consent on your behalf. If an in-app privacy request is unavailable or fails, contact privacy@docdookie.com; you do not need to wait for an app update to make a request. The separate Consumer Health Data Privacy Policy is available at https://docdookie.com/health-privacy/.
On this page
- 1 Scope and interpretation
- 2 Categories of information
- 3 Sources of information
- 4 Purposes of processing
- 5 Local journal and AI functions
- 6 Friends Groups and map disclosures
- 7 Recipients and external services
- 8 Advertising and tracking
- 9 Retention and deletion
- 10 Access correction and privacy requests
- 11 Withdrawal and device choices
- 12 Security
- 13 Age eligibility
- 14 Processing locations and international access
- 15 Changes to this Notice
- 16 Contact
1 Scope and interpretation
1.1 Operator and Services. This Privacy Notice (the “Notice”) describes how Steelshort LLC (“Operator,” “we,” “us,” or “our”) processes Personal Information in connection with the Dr. Dookie mobile application and its associated application services, including journaling, companion, nutrition, artificial intelligence, garden, rewards, subscriptions, Friends, private Groups, optional maps, rights handling for past usage analytics and optional journal backup (collectively, the “Services”). Our contact information appears above and in Section 16.
1.2 Personal Information. “Personal Information” means information that identifies, relates to, describes, or can reasonably be associated with a person or device, including information treated as personal data, sensitive personal information, or consumer health data under applicable law. Installation identifiers and records linked to those identifiers are not treated as anonymous merely because the Services do not require a conventional username and password.
1.3 Notice is not blanket consent. This Notice provides information concerning processing. Acceptance of the Terms of Service, acknowledgment of this Notice, or continued use does not, by itself, constitute consent to optional AI processing, journal context, food-preference sharing, Apple Health access, camera access, location collection, social sharing, group participation or journal backup. The applicable affirmative choices and permissions are described below. A device permission does not authorize every use or disclosure of the permitted information. You can keep a manual journal without enabling those optional online functions.
1.4 Local and hosted processing. The application processes certain information on the user's device and transmits other information to our hosted service or to the recipients identified below. The fact that information is initially recorded on a device does not mean that it remains on that device when the user requests an online feature, sends it to a friend, or exports it.
1.5 Other services. This Notice does not govern the independent processing of information by Apple, a website opened from the Services, a communication application selected by the user, or another independent service. Nor does it govern a recipient's copies of information that the recipient saves outside the Services. These limitations do not displace our obligations concerning disclosures we make or processors acting on our behalf.
2 Categories of information
2.1 Profile and preferences. The application may process the user's name, selected goals and digestive-health concerns, eating style, food-allergy status and listed allergies, sensitivities and restrictions, optional gender and pronouns, optional cycle settings, notification preferences, display preferences, and companion or garden choices. These fields are not all mandatory. A Friends profile uses the user's profile name unless the user selects a separate Friends screen name.
2.2 Journal and health-related information. Depending on the functions used, entries may include dates and times; Good dookie, Bad dookie, or No dookie status; stool form, color, urgency and discomfort; belly pain, bloating and gas observations; food, ingredients, portions and nutrient estimates; water and alcohol entries; medication and supplement names; sleep, stress, activity, steps and movement near meals; weight; period flow and symptoms; tags; titles; notes; and attached photographs. The application also produces charts, averages, comparisons, cycle estimates, summaries and other derived information from recorded data. Such information may constitute consumer health data even when the user has not received a medical diagnosis.
2.3 Apple Health information. Where the user permits access and elects to import a record, the application reads the authorized sleep, exercise-minutes and step-count information, together with information needed to identify its source, date and import. The Services do not request write access to Apple Health in the described implementation.
2.4 AI inputs and outputs. If an AI function is selected and authorized, we process the submitted image, description, question, relevant conversation history, permitted journal summary or food-preference context, and resulting response. The precise inputs depend on the selected function, as described in Section 5.
2.5 Friends and Groups. We process social profile names and character selections; invitation/referral codes; requests, connections, blocks and audience choices; stories, messages and check-ins; selected photos, captions, stickers, statuses, streaks, trends and garden scenes; reactions, reports, and associated identifiers, timestamps, expiration and read activity. Private Groups additionally use group names, owners, membership and invitation records, group photos and messages, selected log-category/status stickers, selected map places, challenge enrollment, participation points and reward claims. A group member need not be an individually accepted friend. We do not access the device address book to populate these features.
2.6 Map information. If optional map collection is enabled, we process geographic coordinates, place names and addresses, the date and time of the corresponding new log, its Good/Bad/No dookie status, and identifiers needed to associate the event with the installation and map place. Map records may reveal sensitive information about a person's home, work, activities or health. We also process bathroom searches, saved places or visits, reviews and ratings, comments, replies, likes, reports and map-activity records when those functions are used.
2.7 Installation, rewards and transactions. Our service processes an installation-linked wallet identifier, an authentication credential in protected form, invitation code, time zone, registration time, Sprout and reward records, cosmetic ownership and selections, growth-related log identifiers, activity-completion identifiers and dates, referral information, and subscription or trial verification records. Subscription records may include Apple transaction identifiers, account association, purchase and expiration dates, entitlement and revocation status. Apple processes payment credentials; the described app purchase flow does not provide us with the user's full payment-card number.
2.8 Service, security and communications information. Network requests necessarily expose information such as an IP address to the receiving service. We also process request counts, usage-category and timing information, security or error information, and information the user supplies in support, privacy, legal or abuse-related communications. Certain registration-abuse controls use a dated hash derived from the request origin. A hash or installation link does not necessarily render a record nonpersonal.
2.9 Past optional usage analytics. Optional first-party usage analytics is disabled in Dr. Dookie 1.5.113 and later. These versions do not record or upload optional screen/action sequences, active screen time, onboarding navigation, subscription-button choices/outcomes, app/operating-system telemetry or setup answers. Earlier consented versions could send installation-linked events and selected age range, gender category, digestive concerns, app goals, eating style and app style. Those historical records can reveal health information and are not anonymous merely because their visitor label is pseudonymous. The service stopped accepting new optional analytics events on November 10, 2026. Past records remain subject to the retention and rights described below.
2.10 Journal backup identity and contents. Optional backup processes an app-specific Sign in with Apple account identifier, protected authorization tokens, consent records, connected installations, synchronization metadata, journal entries and attached photos, including saved Apple Health imports. The backup sign-in does not request your Apple name or email address. It does not merge your wallet or subscription accounts.
2.11 Subscription and creator attribution. When the RevenueCat integration is enabled, it receives the app account identifier and purchase/entitlement records to validate purchases, provide Premium access and subscription reporting. When the creator program is enabled, Insert Affiliate processes creator-code/link attribution identifiers and subscription events supplied through the configured RevenueCat connection for attribution, commissions and refund reconciliation. These records are linked to an app account or installation; they are not represented as anonymous. We do not send journal entries, Health imports, AI conversations, photos or precise map history through these integrations. Connection and SDK metadata must be included in the final provider inventory described in Section 7.5.
2.12 Website visits and contact links. The Doc Dookie website is delivered using OpenAI Sites and Cloudflare hosting and loads typefaces from Google Fonts. These services can receive IP address, requested URL, browser/device information and ordinary security or delivery logs. The website does not upload your app journal and contains no account login, health-data submission form, advertising pixel or site-analytics script added by us. Selecting a mail link opens your chosen mail application; the information you choose to send is handled by that application and our Google Workspace email service. Do not include recovery keys or unnecessary health information.
3 Sources of information
3.1 We obtain information from you; the application and device when a selected function operates; Apple Health following permission/import choices; Apple for purchases and optional backup authentication; RevenueCat and Insert Affiliate for the enabled subscription/creator functions; accepted friends and group members who communicate or interact with you; and persons contacting us concerning support, rights, safety or disputes. Derived records are generated from those inputs. Public food-reference information may originate from USDA FoodData Central or Open Food Facts; those reference records are distinct from your journal.
4 Purposes of processing
4.1 We process information, as applicable to the selected function, to record, display, edit and export your journal; calculate requested summaries and reports; supply authorized AI assistance; provide optional backup/sync; maintain a garden, rewards and subscriptions; deliver selected Friends/Group communications and participation features; maintain optional maps and their audiences; provide reminders and support; authenticate requests, reconcile purchases/referrals, prevent duplicate transactions and misuse, moderate shared content and protect the Services; handle rights requests; and comply with applicable obligations. Optional first-party usage analytics is retired; past records are retained only under the limits and rights described in this Notice. Enabled creator attribution supports commission administration. Those purposes do not authorize sharing health content with advertisers.
4.2 The Services do not use the described journal or Apple Health processing to deliver behavioral advertising. Optional information is not required merely because the corresponding field or feature is available. If information necessary for a selected function is withheld, that function may be unavailable; declining an optional AI, social or map function does not itself require the user to stop maintaining a manual journal.
4.3 We do not sell your health information to data brokers or use your journal, Health imports, health-related setup answers or other health information for targeted behavioral advertising. We do not use your health content to train general-purpose AI models. Private information is processed for the disclosed service purposes and the sharing choices you make, subject to applicable legal obligations. Any proposed new health-data category, purpose or recipient requires a separate assessment, updated disclosures and affirmative consent where required before that processing begins. A general service-improvement statement is not permission for undisclosed secondary use.
5 Local journal and AI functions
5.1 Local journal by default. Journal entries, profile information and attached journal photographs are stored in the app's local storage, with iOS file protection; the journal folder is excluded from device backup. We do not automatically upload the full journal when you begin using the app. If you enable the separate journal-backup feature, the selected backup processing in Sections 5.9–5.10 applies. Other online actions transmit only their disclosed inputs. Without a completed backup or a separate usable export, deleting the app or losing the device may remove the only copy of your journal.
5.2 Apple Health. Health access is optional and read-only. You review available records and choose what to save in a log. Marked Health imports are excluded from automatic AI journal context, social trend generation, automatic group log sharing/participation and reward/growth synchronization. Saved imports may be included in optional journal backup after its separate consent, or in a report/export you expressly choose to share. Health permissions are managed on each device. Disconnecting stops new reads; removing saved imports and revoking permissions in Apple's Health settings are separate controls. Information independently typed or attached to a communication remains part of that communication.
5.3 Photograph and food-description assistance. Selecting or attaching a journal photograph does not alone request cloud analysis. When the user authorizes AI analysis or food-description assistance, the selected meal or stool image, optional nutrition-label image where supported, and accompanying description are transmitted through our service to OpenAI. Food matching may involve a further AI request using the recognized food descriptions and candidate food-reference records. Resulting estimates may be saved in the journal. A social photo sent to a friend is not submitted to AI merely because it is shared through Friends.
5.4 AI conversation. After separate chat authorization, each question is transmitted through our service to OpenAI with recent conversation messages and the selected companion's identity, name and growth stage. The app saves a limited conversation locally. When you withdraw chat, journal-context or food-preference sharing in Privacy controls, the app stops active AI requests and clears the saved conversation; a failure remains visible for retry. Withdrawal cannot recall an already transmitted request or establish provider erasure. A message that you later choose to send may itself include sensitive information regardless of the optional structured-context settings.
5.5 Optional journal context. If journal-summary sharing is enabled, the AI conversation may also receive a summary of approximately the preceding thirty days of manually recorded information. This includes relevant dates, stool observations, self-reported ratings, nutrient and water totals, belly and wellness observations, entry titles and tags, medicine or supplement names, goals, concerns, eating style, and selected descriptive comparisons. The application excludes attached journal photos, the free-text notes field, and records marked as Apple Health imports from this automatic summary. Entry titles, tags and chat messages can nevertheless contain personal or sensitive text entered by the user; those fields are not represented as anonymous or free of identifying information.
5.6 Food-preference context. The separate “Use these details in buddy chat” choice governs transmission of the structured allergy, sensitivity, restriction and eating-style profile. When enabled, that context may be sent even if journal-summary sharing is disabled. Conversely, the selected eating style can be included within authorized journal-summary context. A user's own messages may also disclose allergies or preferences independently of either control.
5.7 Journal explanations and external sources. A separately authorized AI journal-explanation request transmits the summary identified in that request to OpenAI. AI conversation may use OpenAI's web-search capability with selected medical source domains. The service instructs the model to search general topics and exclude personal details; that instruction is not a guarantee that a generative model cannot make an error. Opening a cited external website causes a separate connection to that website.
5.8 AI retention limitation. Our gateway is designed not to write AI request bodies or journal contents to its application database or ordinary request logs. It requests that OpenAI not store the response as a retained API response. This does not establish that OpenAI or infrastructure providers retain no information: service, security, abuse-monitoring or legally required retention may still apply. The applicable provider retention arrangements and processing locations are described in OpenAI’s API data controls. Standard abuse-monitoring retention can include inputs and outputs for up to 30 days, with longer retention for applicable legal or safety exceptions and additional feature-specific temporary processing. We do not claim special zero-retention eligibility or U.S.-only processing. Clearing a local conversation or deleting a journal does not by itself delete information already processed by an external provider.
5.9 Optional journal backup and sync. Settings → Journal backup & sync offers backup without adding registration to onboarding. After separate affirmative consent and Sign in with Apple, you can upload and synchronize journal entries, attached photos and saved Apple Health imports to our hosted service. We retain an app-specific Apple account association and protected authorization tokens for authentication and recovery across devices. No Apple name or email scope is requested. Stored journal bodies, photos and tokens are encrypted with keys managed by our service. This is not end-to-end encryption or iCloud storage: authorized service operation with the necessary keys can decrypt the backup. Backup does not authorize AI processing, social publication or advertising. Host and locations: Hetzner Cloud, with the primary app server in Ashburn, Virginia, United States.
5.10 Backup choices and deletion. Signing in does not start the first upload; select Back up & sync now. Automatic sync while using the app is separately optional and starts off. Conflicting edits or deletions require your choice; offline changes need a later successful sync. A completed-sync indication identifies the last completed operation, not a guarantee that unsynced changes are protected. Signing out stops that device's syncing while preserving the server copy. Delete cloud journal removes the hosted journal/photos, disconnects its devices and revokes retained Apple grants; existing copies on devices remain. Full account export includes the connected backup, and full account deletion from an installation previously connected to it removes that backup even after sign-out. Required provider/revocation or backup-copy work remains pending until resolved. Profile/preferences, reminders, chat, Friends/Groups, garden, rewards and purchase-account recovery are separate from journal backup. Retention and restoration limits appear in Section 9.
5.11 Optional usage analytics is retired. There is no analytics opt-in in version 1.5.113 and later. Upgrading discards unsent optional events and pending requests to enable collection; pending deletion requests are preserved. Settings → Privacy & permissions → Past usage data, also available through Privacy controls, lets you export or delete past records without enabling collection or changing your journal, garden or membership. Offline deletion remains pending and retries when the app reopens. Earlier collection excluded exact age/date of birth, name, email, free-form profile text, pronouns, allergy details, journal/Health contents, photos, messages, precise location and payment credentials, but could include the digestive-health setup answers identified in Section 2.9. It was not session replay and did not record screens or keystrokes. Our host processes retained records and rights requests for us. Past events remain subject to the 30-day event-age limit; minimal consent state prevents delayed uploads after withdrawal. Necessary subscription verification and rewards accounting continue separately, including the provider processing disclosed in Section 7.5.
6 Friends Groups and map disclosures
6.1 Optional Friends profile. Enabling Friends creates a hosted social profile. Connections require an invitation and acceptance. The Services use connection and audience records to determine who may access the content described below. Disabling Friends is distinct from deleting the wallet or all information associated with the installation.
6.2 Stories and direct communications. The user may send selected content to a particular accepted friend or publish a story to accepted friends or the selected Close Friends list. These actions upload the selected content and associated metadata to our service. The in-app audience applies to that communication; sharing a status or a selected trend does not grant the recipient access to the user's entire journal. Where the user selects story sharing while saving a dookie log, saving can publish the selected status directly, without opening the editor. The journal photograph, notes and location are not automatically included in that status story.
6.3 Current audiences. Changes to the Close Friends list affect access to still-active Close Friends stories, including their shared photos. Adding a person can provide access to such existing stories; removing a person withdraws that access through the Services. A general story remains a general accepted-friends story unless removed. Garden sharing and map sharing have their own controls and are not restricted merely by selecting a Close Friends story audience.
6.4 Photos. Friends photo upload begins when the user selects Send or Share, rather than merely selecting a photo in the editor. The app and service resize and re-encode shared images to remove embedded camera metadata such as EXIF/GPS information. The image pixels, caption, stickers or visible surroundings may still disclose identity, location or health information. Shared photos are stored on our service and accessed through the applicable audience checks; they are not represented as end-to-end encrypted communications.
6.5 Garden. A separate garden-sharing choice permits accepted friends to visit the user's saved garden arrangement, including shared plants, characters, decorations, outfits and growth state. Selecting a garden image for a communication may require enabling that broader garden-sharing choice. Turning garden sharing off withdraws access through the Services; it does not retrieve screenshots or other copies already made by recipients.
6.6 Location collection. The optional poop map begins disabled. A separate map-history choice and device location permission are required before automatic collection. The app requests the location associated with a newly saved, current Good dookie, Bad dookie or No dookie log while the app is active. It does not use this feature for continuous or background location tracking. Edited or backdated entries and records identified as sample data or Health imports do not initiate present-location capture. Permission to the former single-location feature does not itself enable the retained-history feature.
6.7 Map records and grouping. Location is transmitted to our service with the corresponding place, date, status and log identifier. Nearby repeat visits may appear as one map marker showing the latest visit, although the underlying visit records are retained. Marker grouping is not deletion or anonymization. Apple location and mapping services may process coordinates to resolve a place or display/search a map.
6.8 Map recipients and discussion. The map remains private from other users until the user selects accepted friends as map recipients. Newly accepted friends are not automatically added. A selected recipient may view existing map history, associated reviews and discussion, subject to current access controls, and may comment, reply or like where permitted. A user also receives access to another person's map only when that person has selected the user. Removing a recipient, removing or blocking the friendship, or disabling sharing changes access through the Services; it does not retrieve copies outside the Services. Map comments, replies and likes may produce activity notifications within Friends.
6.9 Collection, visibility and deletion are separate. Turning off automatic logging or revoking location permission stops new automatic captures but leaves existing map records. Turning off map visibility prevents friends from viewing it but does not itself delete the history. Removing an owned map place removes that place's associated visits, review and discussion from the active service. Saved bathroom finds remain private; published bathroom reviews use the selected map audience. Other deletion limitations appear in Section 9.
6.10 Recipient conduct. A recipient can take screenshots, copy text or retain other copies. Expiration, audience changes and deletion cannot guarantee recall of those independent copies. Users should not include another person's sensitive information without appropriate authority. Reports and blocking are available for specified content and connections; submitting a report is not a promise of immediate removal for every recipient or immediate staff review.
6.11 Private Groups and existing history. Joining with an invitation makes you a member of that group; members are not limited to your individual Friends list. Current members can view permitted retained group messages/photos, member profiles, participation displays and shared map places, including content posted before they joined. Close Friends and individual map-recipient settings do not define the group audience. Group owners manage names, invitations, membership and certain content. Sharing a group invitation can enable another person to join; review membership before sharing sensitive information.
6.12 Group stickers photos and participation. Choosing Share to group while logging sends the previewed category sticker and profile identity after the log is saved; a poop sticker also includes Good, Bad or No dookie status. It does not send that log's notes, measurements, photo or location. A separately selected group photo or message uploads its own content. Optional monthly challenge enrollment lets eligible new current manual logs send a category and identifiers for participation points; members see applicable points and progress. These choices can reveal health-related activity even without detailed journal contents. A failed delivery may remain in the device's retry queue until retried, discarded or no longer eligible. Pausing participation stops new contributions for that enrollment but does not erase already recorded points.
6.13 Selected group map places. Sharing a saved place to a group is separate from individual friend-map sharing. It makes that selected place's permitted location/status information available to current group members, subject to access and block controls. A newly joined member can gain access to retained shared places. Unsharing the place, leaving the group or removing the underlying place changes access through the service; it cannot recall an independent recipient copy.
6.14 Leaving blocking and removal. Leaving or being removed withdraws group access and removes your group messages, photos and map shares from the active group. Rejoining does not restore those removed items. Membership, participation and reward records have the separate criteria in Section 9. Group messages do not inherit Friends stories' 24-hour or direct messages' 30-day expiration. Blocking restricts access to the affected person's content through the service; it does not delete that person's account for everyone. Reporting and authorized moderation can separately restrict or remove content.
6.15 Safety review and reports. Shared photos are published to the audience you select without routine staff preapproval. We do not use an automated objectionable-image classifier. A limited automatic filter blocks a small set of severe racial/ethnic slurs and common variants in social text; it does not screen private journal notes, understand every context or catch every harmful statement. General profanity, threats and other prohibited conduct remain subject to the content rules, reports and human enforcement. Reports create safety records and can hide the item for the reporting viewer; an authorized moderation decision can separately restrict content or an account. Authorized reviewers inspect relevant reported content, not an unrestricted private journal. Decision and appeal information is available through the safety controls or safety@docdookie.com. The report queue is checked morning and evening, with a target of triage within 24 hours; this is not an emergency service or a guarantee of immediate action. Section 9 describes moderation retention.
7 Recipients and external services
7.1 Service providers and limited access. Our infrastructure providers process hosted records, including optional backup and retained past analytics, to operate the requested services. OpenAI processes authorized AI inputs. RevenueCat processes enabled subscription functions; Insert Affiliate processes enabled creator attribution. The categories and purposes are summarized below. Authorized Steelshort LLC personnel may access information necessary for support, safety, security, rights handling and service operation, with access limited to those functions. Private shared or backed-up content is not promised to be inaccessible to the operator. Actual hosting provider/locations: Hetzner Cloud, with the primary app server in Ashburn, Virginia, United States. Mail/support/security providers: Google Workspace for Doc Dookie email; Google and its service providers may process messages in the United States and other countries where they operate. We do not promise U.S.-only handling of email.
7.2 Apple and food-reference services. Apple provides the device platform, Health permissions, App Store purchase and verification functions, and mapping/location services used by the application. Online packaged-food search sends the user's query directly to Open Food Facts; that service may also receive the network information associated with the request. Searches of our hosted USDA reference copy send the query to our service and do not, through that route, send the journal or photograph to USDA. A third party's collection is governed in part by its own notices and terms.
7.3 User-directed recipients. We disclose selected Friends content to its applicable audience. When the user exports a JSON file, creates a PDF report, prints, or uses the device sharing menu, the chosen recipient or application receives the selected information. These actions can include sensitive records and, where selected, Apple Health imports. We do not automatically transmit a report to a clinician.
7.4 Legal and organizational disclosures. Where law permits or requires, information may be disclosed in response to a valid legal obligation, to address a security incident or unlawful conduct, or in connection with a genuine business reorganization. Such a disclosure remains subject to applicable health-data restrictions and any consent, notice, contractual or purpose limitations. This provision is not authorization for a use or disclosure otherwise prohibited by law. The specific affiliates receiving consumer health data, if any, are none in the current app service.
7.5 Subscription and creator providers. When enabled, RevenueCat receives our app-account identifier, purchase/transaction and entitlement information and supported SDK metadata for verification, access management and subscription analytics. Our app does not supply it with your name, email, journal, Health records or precise map history. If you explicitly apply a creator code, Insert Affiliate can receive the code, an attribution identifier, account association, related subscription-event and transaction identifiers, product, purchase/renewal/refund timing, value and currency needed to attribute purchases and calculate commissions. Our event relay excludes purchases without a creator-code association and strips unrelated customer attributes. Commission reporting may be available to the relevant creator; it does not include your journal or health content. The app disables automatic deferred device matching and clipboard attribution. Shareable code pages can still record link visits and ordinary connection information for click analytics; using code-only attribution is not a claim that no data is collected. These providers retain necessary attribution, billing, security and legally required records under their applicable arrangements. Privacy/deletion requests can be made to us at privacy@docdookie.com; you are not required to negotiate directly with a provider. Production availability and consent controls still apply. See RevenueCat’s privacy policy and Insert Affiliate’s privacy policy.
7.6 Data and recipient summary. The table summarizes the preceding descriptions. It does not authorize a new purpose or audience. Retention and deletion are addressed in Section 9; separately authorized inputs can include sensitive health information.
| Data category | Purpose and choice | Recipients or location |
|---|---|---|
| Journal profile entries and photos | Local recordkeeping; specific online actions have separate choices | Device by default; selected export recipients; backup host if enabled |
| Saved Apple Health imports | Reviewed imports, reports and optional backup | Device; selected export recipients; backup host if separately enabled |
| AI submissions and outputs | Authorized analysis, conversation or explanation | Our gateway/host and OpenAI; saved output on device |
| Friends and Groups content | Chosen communication, group participation and moderation | Our host; selected friend audience or current group members; authorized safety staff |
| Map coordinates and activity | Opted-in history and separately selected sharing | Our host; Apple mapping services; selected friends or group members for shared places |
| Backup account and sync records | Authentication, restore, conflict handling and deletion | Apple for authentication; our backup service/host |
| Purchase and referral records | Premium, restore, rewards and fraud prevention | Apple, our host and enabled RevenueCat; referring users see disclosed referral progress |
| Creator attribution and purchase events | Enabled creator program and commission reconciliation | RevenueCat, Insert Affiliate and the relevant creator’s commission reporting; no journal content |
| Past optional analytics and setup categories | Retention, export and deletion of earlier consented records | Our separate analytics store/host and authorized personnel handling those records |
| Support reports and security/request records | Requested help, safety, rights and service protection | Authorized operator personnel and Google Workspace for email; Hetzner for hosted service/security records |
7.7 Corporate affiliates and creators differ. A paid creator is not necessarily a corporate affiliate. The specific corporate-affiliate list in Section 7.4 concerns entities within a corporate relationship; creator attribution and its permitted reporting recipients are addressed separately in Section 7.5. Neither relationship gives permission to receive your journal or other health content for advertising.
8 Advertising and tracking
8.1 We do not sell Personal Information to data brokers or use health information for targeted behavioral advertising. Optional first-party usage analytics has been disabled, separately from the necessary subscription and enabled creator-provider processing described above. The app does not access Apple’s advertising identifier. Creator attribution uses the explicit code flow described in Section 7.5; independent creator-link pages may collect visit and connection data. We do not authorize our providers to repurpose your health content for advertising, and we require providers processing information for us to protect it consistently with this policy and applicable requirements. Additional uses or tracking requiring a separate choice will not be authorized merely by accepting these Terms or this policy.
8.2 The app does not use browser “Do Not Track” signals to change processing because its described functions do not perform browser-based cross-service advertising tracking. The promotional website does not add advertising pixels or a site-analytics script. Its hosting and font services receive ordinary connection information needed to deliver the pages, as described in Section 2.12. Independent services you open may have their own processing; our code-only choice does not control every independent website.
9 Retention and deletion
9.1 Retention standard. We retain information for the feature you request and the category-specific purposes and removal triggers below. Display expiry, loss of access and erasure from every copy are distinct. Primary records, processors, recovery copies and minimized anti-abuse/deletion proof can have different completion steps. We do not use a general reference to security or business needs to justify keeping an unrestricted health history. Applicable deletion requirements take precedence over ordinary retention, subject only to a specific lawful exception.
9.2 Local data. Journal information remains on the device until the user deletes it or another device/application event removes it. The app saves a limited recent AI conversation locally, currently up to sixty messages, rather than an indefinite full transcript. Local deletion does not erase a copy previously exported, transmitted or retained by another service.
9.3 Friends expiration and maintenance. Friends stories are visible for 24 hours and direct messages/check-ins for 30 days unless removed earlier or access is withdrawn. Primary-store cleanup removes expired material through service cleanup and the configured maintenance process. Visibility expiry is not a promise of simultaneous erasure from every backup or provider. Unattached sharing-photo uploads and approved moderation copies have separate cleanup rules. Group messages have the different retention criteria in Section 9.8.
9.4 Map history. Map visits persist until the corresponding place is removed, map history is reset, or the applicable Friends deletion operation is performed. Merely stopping automatic collection or hiding the map does not delete history. Opaque identifiers and timestamps used to prevent a delayed retry from recreating a deleted record may remain after a place or comment is removed. They do not contain the removed location or comment text but may remain linked to the installation. Deleting an individual local journal entry does not automatically delete a map record or story previously uploaded from that entry. Use the map-place or social-content removal controls, or submit the applicable privacy request, to address those separate records.
9.5 Available reset controls. The “Delete journal, chat & garden” control requests a reset of the local journal and conversation, reminders and growing garden, and the user's owned map places and associated discussions through the service reset. It preserves the wallet, Sprouts and unlocked cosmetics. It also does not constitute deletion of the user's Friends profile, friendships, all direct messages, legacy standalone bathroom reviews, or every comment or like made on another person's map. An online service step is required for the hosted reset. The user should review the completion or error message rather than assume that closing the app completes a failed reset.
9.6 Friends deletion. Turning Friends off removes the profile, connections and applicable hosted social content, uploaded sharing photos, bathroom records and map participation. It also removes active Group memberships and the user's associated group content under the leaving rules in Section 6.14. It does not delete the separate wallet, purchase/reward history or journal backup. Blocking is an access restriction, not full account deletion.
9.7 Complete account deletion. Use Settings → Export or delete my account → Delete my account. The same route is available from Privacy controls. After confirmation, the service revokes the affected account credential and processes deletion of account/profile, authored social and group content/media, map records, relationships, optional analytics, exports and the connected journal backup, with removal of the app's local account data. The receipt separately reports primary-server, device, processor and backup work. Keep the app available to complete local removal and check the receipt; a pending stage is not a completed deletion. Provider or Apple-token revocation failures remain retryable. Other devices may retain previously downloaded local journal copies. Independent recipient copies cannot be recalled. Only specifically justified, minimized records described in this policy may remain. Account deletion does not cancel an Apple subscription; the screen provides billing guidance and subscription management. For help or other rights, contact privacy@docdookie.com.
9.8 Groups and participation. Group messages/photos and selected place shares remain until removed, the author leaves/is removed, or the applicable account is deleted; they do not have an automatic 30-day message expiry. Membership, season participation, earned-reward and anti-duplicate records can remain after leaving to preserve valid accounting and stop duplicate claims, under the category criteria below. Pausing contributions does not delete their earlier history.
9.9 Journal backup. The current hosted journal remains until cloud-journal deletion or deletion of a connected account, subject to valid item deletions during sync. Signing out alone does not delete it. Revision/deletion markers prevent stale devices from recreating removed entries. Abandoned upload material is subject to the implemented 24-hour cleanup rule. Required provider revocation and operational backup-copy work follow the disclosed deletion process; a restored database must not make deleted records available again.
9.10 Analytics, exports and limited proof. Past optional analytics events have a 30-day age limit. Version 1.5.113 and later discard all unsent optional events on upgrade; older versions used a seven-day unsent-queue age limit. Minimal consent state prevents delayed uploads after withdrawal. An available server export states its download expiry; temporary on-device export files older than 24 hours are removed when export cleanup next runs. Files you save elsewhere remain under your control. We keep pending processor-request and deletion records until the work is resolved, then retain only the confirmation information necessary to demonstrate handling or meet an applicable obligation. Minimal transaction/reward identifiers may remain to prevent duplicate claims; revoked credential hashes remain while the old credential could otherwise be reused. Those records are not a license to retain a full deleted account and are not represented as anonymous.
9.11 Retention summary. The table describes ordinary feature criteria. Where a function is not available, this table does not imply that collection has begun. Request assistance, the status of retained copies or a specific deletion at privacy@docdookie.com.
| Category | Ordinary retention or removal trigger | Additional condition |
|---|---|---|
| Local journal and saved conversation | User deletion/reset; conversation limited to recent messages | Exports and transmitted copies are separate |
| Journal backup and saved Health imports | Item sync deletion, cloud deletion or connected account deletion | Operational backups and revocation work require verified completion |
| Friends stories and direct content | 24-hour stories; 30-day direct content | Scheduled purge and media/backup handling apply |
| Group content and shared places | Content removal, author departure/removal or account deletion | Participation/reward records are separate |
| Map history and discussion | Owner/author/related-content removal or account deletion | Turning collection or sharing off alone does not delete history |
| Past optional usage analytics | Event age limit of 30 days | Separate minimal consent proof; version 1.5.113 and later discard unsent events on upgrade |
| Account reward and consent records | Active account, then applicable deletion | Approved financial/anti-abuse proof exceptions only |
| Export copies | Download expiry shown for an available server export; local temporary copies removed after 24 hours when cleanup runs | User-saved copies remain separate |
| Moderation records | Closed-report details: 30 days after the latest decision; minimized audit: 90 days; remaining preapproval holds: seven days | Open appeals and minimum active-enforcement records may remain while needed |
| Support and security records | While needed to resolve the request or incident, maintain necessary account security, establish handling or meet a specific legal obligation | Avoid unnecessary health information in email; privacy requests apply |
| Operational backups | Restricted recovery copies may remain after primary deletion; completion is handled separately as described below | No uniform automatic backup-erasure period is currently promised |
| Processor and deletion-request records | Until required work is completed, then minimized confirmation for necessary handling/accountability | Pending work is not marked complete by passage of time |
9.12 Backup copies and completion. Recovery snapshots can contain older information after a primary record is deleted. We restrict their use to recovery, security or a specific legal obligation and must apply outstanding deletion and withdrawal requests before restored information returns to service access. The current testing service does not have a uniform automatic erasure period for all operational backup copies. We handle those copies and outside-provider requests separately, keep unresolved work pending, and explain remaining work or a specific lawful exception when responding to a deletion request. Applicable legal deadlines still apply; a missing automatic schedule is not permission to ignore a request.
10 Access correction and privacy requests
10.1 In-app access and exports. Review/edit local entries and supported profile fields and use the available content, consent and audience controls. A local journal JSON export includes profile/entries but not photo files or all server records. Settings → Export or delete my account provides a separate portable account archive combining the local journal, photos, saved conversation, reminders, privacy records and available authored server records, including the connected journal backup and its photos. It omits authentication secrets and other people's private records; protected moderation material may require a proportionate assisted request. An incomplete, expired or failed export is not reported as ready. Past usage data also has its own export control. Protect the archive and review its contents before sharing.
10.2 Requests to Steelshort LLC. Subject to applicable law, you may request confirmation/access, correction, deletion, a portable copy, withdrawal of consent or information about recipients. Use the in-app account/privacy controls or email privacy@docdookie.com. State the requested action and enough information to locate the relevant account or interaction. Do not email an account recovery key, Apple token, full journal or identity document; any necessary additional verification must use a secure, proportionate process. We do not require a reason for exercising a right. An optional additional request website is not a condition of using these channels.
10.3 Verification and response. We may take reasonable steps to verify the requester and authority to act. Where law permits an authorized agent, we may request evidence of that authority. We will apply the response periods, permitted exceptions and appeal requirements applicable to the request, explain a refusal where required, and not unlawfully discriminate because a person exercises privacy rights. The inability to continue a function after its necessary processing is withdrawn is distinct from unlawful discrimination.
10.4 Appeals. A person entitled to appeal a privacy-request decision may use privacy@docdookie.com with the subject “Privacy Request Appeal,” identify the earlier request, and explain the disputed decision. The response will state the result and reasons and, where required, provide the appropriate regulator contact. This procedure does not restrict any right to complain directly to a regulator. Additional consumer-health rights appear in the separate Consumer Health Data Privacy Policy at Consumer Health Data Privacy Policy.
10.5 California. California residents can use the contact and in-app routes above to request access, correction, deletion, portability, applicable information about recipients, and any limitation or opt-out right provided by law, including through an authorized agent where applicable. Sections 2–4 identify our categories, sources and purposes; Sections 7–9 identify disclosures and retention. We do not sell information or share it for cross-context behavioral advertising. We do not discriminate for exercising an applicable privacy right. Statutory rights depend on the law’s scope and exceptions; this paragraph does not claim that every statutory regime applies to every record.
11 Withdrawal and device choices
11.1 Settings → Privacy controls provides AI and audience choices and access to Health, past usage data and account controls. Settings → Journal backup & sync controls backup; Group settings control membership, shared places and monthly participation. Withdrawing an AI choice stops new requests and clears conversation as described in Section 5.4. Disconnecting Health or location stops future authorized reads/captures but does not itself erase saved records. Backup sign-out retains the hosted backup; cloud deletion is separate. Past usage data provides export and deletion of earlier optional analytics records; it cannot enable new collection. Turning off sharing restricts service access but cannot retrieve recipient copies. You may separately request deletion of retained records.
11.2 Notification permissions are optional. Reminder schedules are maintained on the device in the described implementation. Medication or supplement notification text omits the name and dose unless the user elects to display them. A person with access to the device may nevertheless see information in the app, notifications, exports or screenshots.
12 Security
12.1 The Services employ technical measures such as protected local journal files, installation credentials, encrypted network connections to the production service, request authentication and audience checks. These measures do not guarantee that unauthorized access, disclosure, loss or alteration can never occur. The Services do not provide a promise of end-to-end encryption for Friends content or a guarantee that only its named recipients could ever access hosted content.
12.2 Report suspected security incidents or vulnerabilities to security@docdookie.com. Send privacy concerns and data-rights requests to privacy@docdookie.com, and general support or accessibility concerns to support@docdookie.com. Where an incident requires notification, Steelshort LLC must give the legally required notices through appropriate means. Failure to contact us does not waive notification duties or your rights.
13 Age eligibility
13.1 The Services are intended for persons aged eighteen (18) or older and are not offered for use by children or teenagers under eighteen. A person under eighteen should not create a profile, submit health information, use AI chat, or participate in Friends. A person who believes that a minor has provided information should contact privacy@docdookie.com so that the matter may be assessed and addressed under applicable law. An age acknowledgment does not eliminate obligations that arise from actual knowledge or the nature of the service's audience.
14 Processing locations and international access
14.1 The app’s initial audience is United States adults. The primary app service is hosted on Hetzner Cloud in Ashburn, Virginia. Google Workspace handles Doc Dookie email; OpenAI, Apple, RevenueCat, Insert Affiliate and the website providers described above may process information in the United States and other countries where they and their service providers operate. The app does not promise that every provider copy stays in the United States. Use from another jurisdiction does not waive mandatory rights. Any expanded availability or new processing remains subject to applicable notices, safeguards and consent requirements.
15 Changes to this Notice
15.1 We may revise this Notice to reflect changes in the Services, processing or applicable requirements. We will identify the revised effective date and provide notice of material changes through a prominent dated notice on the policy page and within the app before additional processing begins, or by direct contact where available and legally appropriate. Where a change requires affirmative consent, we will obtain that consent before the additional processing. Continued use alone will not be treated as retroactive permission to collect or disclose a new category of consumer health data or use it for a new purpose requiring consent.
16 Contact
16.1 Privacy inquiries, access/export/deletion requests and privacy appeals should be directed to Steelshort LLC, Attn: Privacy, 2108 N St #17999, Sacramento, CA 95816, United States, or privacy@docdookie.com.
16.2 Other contacts: support@docdookie.com for general help, billing and accessibility; safety@docdookie.com for content reports and moderation appeals; security@docdookie.com for security incidents and vulnerabilities; legal@docdookie.com for formal legal notices; and partners@docdookie.com for creator, affiliate and partnership inquiries. Please do not email recovery keys or unnecessary health information.