Pre-release legal draft · Last updated 31 August 2026
Privacy Policy
This policy explains the current data practices of the Dr. Testo website and pre-release iOS app operated by Mustafa Mıhcı. It covers the product and configured service boundaries; the remaining contact and jurisdiction details will be completed before public release.
Operator · Mustafa MıhcıAdults 18+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 covers the website, the current iOS app, and the services used to deliver them. Android is planned but not yet released. support@drtesto.com is the designated public support address, but mailbox operation is not yet launch-verified. The postal address, dedicated privacy contact, effective date, and any applicable regional representative details remain release fields.
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 or age, body-fat range, sleep, training, diet, energy balance, 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
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.
06
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, and App Store purchase history needed to present, unlock, and restore subscriptions. 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.
07
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. Until direct delivery is configured, submitting the form opens an email draft addressed to support@drtesto.com; the website does not receive the message. When server delivery is enabled, those fields will pass through the named production email provider to that support mailbox, and this policy will be updated before activation. Do not send passwords, payment-card details, laboratory reports, or unnecessary health information. Hosting, DNS, CDN, and security infrastructure may also process request metadata such as IP address, browser headers, URL, timestamps, and security events.
08
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, 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.
09
Sharing, sale, advertising, and tracking
Dr. Testo does not sell your profile, share it for cross-context behavioural advertising, or use sensitive inputs to build a third-party advertising profile. Limited providers receive only the information needed to supply analytics, 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.
10
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. Before release, the operator will document the applicable transfer mechanism and safeguards for users whose law requires them, including contractual safeguards where appropriate.
11
Retention
Local records remain on the device until you delete them, use the app's deletion controls, remove the app, or the operating system clears app storage. Firebase states that Crashlytics keeps crash stack traces and associated identifiers for 90 days before removal begins. Other providers retain minimized service, purchase, notification, or analytics records according to configured retention, contractual, fraud-prevention, accounting, and legal requirements. Final production retention settings and any account-independent deletion workflow will be confirmed before release.
12
Your controls and privacy rights
You can review and correct assessment or ongoing product information in the app and permanently remove Dr. Testo's local journey data with Delete 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.
13
Adults only
Dr. Testo is designed for adults aged 18 or older. Date of birth is used on device to enforce eligibility and support the age-specific product model. The product does not currently request a real name, postal address, contact list, or custom login. If Dr. Testo learns that information was collected from an underage user contrary to this rule, it will take reasonable steps to remove it.
14
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. The legal operator is Mustafa Mıhcı; the final postal address, privacy contact, effective date, and jurisdiction details will be added before launch.
