This Privacy Policy explains how the Dr. Testo website and iOS app, operated by Mustafa Mıhcı, handle information. It covers data stored on your device, limited data processed by service providers, Apple Ads acquisition measurement, purchases, notifications, support communications, and your privacy controls.
Operator · Mustafa MıhcıAges 13+Local-first core
01
Scope and responsible operator
Dr. Testo is the public brand of the website and mobile product. The responsible legal operator is Mustafa Mıhcı. This policy applies to the Dr. Testo website, the iOS app, and the service providers used to operate them. Send privacy and support requests to support@drtesto.com.
02
Information stored on your device
The app stores the information you choose to enter in its local Core Data database. This can include date of birth, body-fat range, sleep, training, diet, stress, alcohol, energy, mood, physical capacity, motivation, libido, morning erections, protocol selections, supplement and environment records, check-ins, completion history, preferences, and achievements. The app also creates Starting, Base, Today, projection, milestone, and progress records from those inputs. The core experience does not require a Dr. Testo account or custom cloud database.
03
Sensitive inputs stay out of product analytics
Some assessment and check-in data may be health-related or sensitive. Dr. Testo does not send raw assessment answers, libido or morning-erection answers, exact modeled testosterone values, free-text health notes, or protocol history to product analytics. The current app does not request HealthKit, precise location, contacts, photos, camera, or microphone access.
04
Product analytics
When enabled, the configured US-residency Mixpanel project receives a pseudonymous installation identifier, app version, build, environment, limited device context, and approved product-use events such as an app open, screen, or funnel step. Automatic event collection and IP-based geolocation enrichment are disabled in the Dr. Testo integration. Analytics is used to understand product operation and improve flows, not for cross-app tracking or advertising profiles.
05
Apple Ads acquisition measurement
In App Store builds where provider services are enabled, Dr. Testo uses Apple’s AdServices attribution service to determine whether an installation is attributable to an Apple Ads campaign. The app sends an attribution token generated on the device to Apple, which may return attribution status and campaign, ad group, keyword, ad, claim-type, and placement identifiers. RevenueCat also receives the AdServices attribution token to connect Apple Ads acquisition with subscription outcomes. Mixpanel receives only the resolved attribution status and campaign metadata; Dr. Testo does not send the raw token or raw Apple response to Mixpanel. A successful first result may be cached on the device to avoid repeated lookup. This is used for acquisition and campaign-performance measurement, not to target ads using health inputs, build a cross-app advertising profile, or access the advertising identifier. Dr. Testo does not request App Tracking Transparency permission for this standard attribution flow.
06
Reliability and remote configuration
Firebase Crashlytics may process crash stacks, app state, app version, device model, operating-system details, Firebase installation identifiers, and limited typed diagnostic keys. Firebase Remote Config processes technical app and device information needed to fetch a validated, versioned configuration. Dr. Testo excludes raw profile answers and exact modeled values from Crashlytics keys. Remote configuration cannot retrieve the local profile or replace the calculation engine with executable code.
07
Purchases and notifications
Apple processes App Store payments and payment credentials; Dr. Testo does not receive your card details. When enabled, RevenueCat processes a pseudonymous app user identifier, product and entitlement status, App Store purchase history, and Apple Ads attribution needed to present, unlock, restore, and measure subscription outcomes. When remote notifications are enabled, OneSignal may process a push token, a pseudonymous installation identifier, notification permission state, delivery or interaction information, and technical app/device data. Local reminders can also be scheduled through Apple notification services.
08
Website, support, and hosting data
The website has no user account, newsletter, advertising pixel, session replay, or enabled product analytics. The Support page asks for a name, reply email, platform, subject, and message. Submitting the form opens a draft in your device's email app addressed to support@drtesto.com; the website itself does not receive or retain the message. If you send the email, your email provider and Dr. Testo's inbound mail-routing service process the message and reply address. Do not send passwords, payment-card details, laboratory reports, or unnecessary health information. Hosting, DNS, CDN, and security infrastructure may process request metadata such as IP address, browser headers, URL, timestamps, and security events.
09
Why information is processed
Information is processed only for defined purposes: to provide requested app and website functions, calculate and store the local product experience, manage purchases and entitlements, measure Apple Ads acquisition and campaign performance, deliver notifications you enable, maintain reliability and security, improve the product through minimized analytics, answer support or privacy requests, and meet legal obligations. Depending on location and function, the intended legal grounds are performance of the service, legitimate interests in security and product reliability, consent where required, and compliance with law. Non-essential processing will not be enabled where consent is required until the relevant choice is implemented.
10
Sharing, sale, advertising, and tracking
Dr. Testo does not sell your profile, share it for cross-context behavioural advertising, or use sensitive inputs to target ads or build a third-party advertising profile. Apple Ads attribution is limited to measuring whether an App Store acquisition came from an Apple Ads campaign and how that cohort uses or subscribes to the product. Limited providers receive only the information needed to supply analytics, attribution, reliability, configuration, purchases, notifications, hosting, or support. Provider access is governed by service agreements and their privacy terms. Data may also be disclosed where legally required or necessary to protect users, rights, and service security.
11
International processing
The Mixpanel project is configured for United States data residency. Apple, Google/Firebase, RevenueCat, OneSignal, and website infrastructure providers may process technical service data in the United States or other countries under their terms, contracts, and applicable data-protection requirements.
12
Retention
Local records remain on the device until you delete them with the app's controls, remove the app, or the operating system clears app storage. A successful Apple Ads attribution result may remain in app storage to avoid repeated lookup and is cleared when the app container is removed. Firebase states that Crashlytics keeps crash stack traces and associated identifiers for 90 days before removal begins. Other providers retain minimized service, purchase, notification, analytics, or attribution records according to their configured retention, service needs, contracts, fraud-prevention, accounting, and legal requirements. Support emails are retained only as long as reasonably needed to answer the request, protect the service, and meet applicable legal obligations.
13
Your controls and privacy rights
You can review and correct ongoing product information in the app and permanently remove Dr. Testo's local journey data with Erase All Local Data. Removing local data or the app does not cancel an App Store subscription and cannot itself erase records already processed by Apple or an outside provider. Depending on your location, you may have rights to access, correct, erase, restrict, object, withdraw consent, obtain portability, or complain to a supervisory authority. Provider-held pseudonymous records may require enough information to locate and verify the relevant installation.
14
Age eligibility
Dr. Testo is designed for people aged 13 or older. Date of birth is used on device to enforce eligibility. Because the current age model begins at 18, users aged 13–17 are calculated with the age-18 model surface until their chronological age enters the supported range. The product does not currently request a real name, postal address, contact list, or custom login.
15
Security, changes, and contact
Dr. Testo minimizes off-device data, uses platform storage and encrypted provider connections, separates provider SDKs from the calculation engine, and restricts analytics to approved fields. No system can be guaranteed completely secure. Material changes to data collection, providers, purposes, retention, or controls will be reflected in this policy, the in-app text, and store disclosures before or when the change takes effect. The legal operator is Mustafa Mıhcı. Send privacy and support requests to support@drtesto.com.