Privacy Policy

1. Who we are

Alexandre Grisey is the developer of 74: Male Fertility (the “App”) and is the data controller for the personal data described in this policy, unless a service is identified as acting under its own terms.

2. Scope and the difference between local and remote data

This policy applies to the App, its subscription and analytics integrations, the optional AI question feature, and support requests sent through the App. It does not replace the privacy terms of Apple, Google, or any third-party website you choose to open.

Most sensitive App content is local. The App does not require a 74 account or upload your full profile to our servers. The profile, daily logs, cycles, semen analyses, partner details, photos, and uploaded documents described below are normally stored in the App's private storage on your device.

Some features require network processing. RevenueCat checks purchases; Mobiqo provides limited product analytics; and, only after separate notice and consent, an AI question is sent to our Firebase endpoint and OpenAI. Those flows are described in detail below.

3. Information we handle

3.1 Profile and onboarding information

Depending on what you enter, the App stores a locally generated user identifier, language and measurement preferences, first name, profile photo, birth year, height, weight, fertility goals and timeline, semen-test history, selected risk factors, lifestyle answers, health-connection choice, onboarding progress, and notification choices.

3.2 Daily, health, and fertility tracking

You may record weight, diet and processed-food estimates, supplements, coffee, alcohol, water, emotional state, sleep, smoking, exercise, intercourse count, heat or chemical exposure, medication use, notes, and events such as fever, illness, medication changes, surgery, or a semen analysis. The App uses some of these entries to create lifestyle scores, focus areas, projections, and an approximate 74-day timeline.

3.3 Apple Health and Health Connect data

If you choose to connect a health platform, the App requests read-only access to selected categories: birth year on Apple Health, height, weight, steps, exercise duration, sleep, and dietary water. On Android, the App reads workout sessions only to derive exercise duration because Health Connect has no standalone exercise-time record. The precise categories available depend on your device and the permissions you grant.

The App retains connection and synchronization metadata, the latest height and weight suggestions, and up to 30 daily summaries. It does not intentionally duplicate raw health samples or raw workout records, write information back to Apple Health or Health Connect, or send imported health-platform data to RevenueCat, Mobiqo, AI, advertising systems, or our remote database.

3.4 Semen analyses and documents

You may manually enter analysis dates, laboratory names, abstinence periods, semen-analysis measurements, units, reference context, notes, and related records. You may also save PDF, JPEG, or PNG documents and photos in the App's private local file area. The App does not automatically extract or interpret the contents of those files and does not send them to the AI feature.

3.5 Partner information

You may store a partner's first name, local photo, cycle dates, expected peak-fertility dates, estimated or manually entered planning windows, irregular-cycle information, and reminder preferences. This information remains local unless you deliberately use the system share sheet to send a selected window to a recipient you choose.

3.6 AI questions

If you accept the separate first-use AI notice and submit a question, the text of that question is sent to our Firebase Cloud Function and then to OpenAI for moderation and generation of a response. The request does not automatically include your App profile, imported health data, partner information, semen analyses, attachments, or previous questions.

The question and answer are saved in local App history until you delete them. Our backend is designed not to log or retain question or answer content. It derives a rotating pseudonymous rate-limit identifier from network information and stores only that identifier, counters, and an expiry timestamp for approximately two days. Firebase temporarily processes an IP address to deliver the request. OpenAI may retain prompt and response content in abuse-monitoring logs for up to 30 days under its default API controls, unless shorter or zero-retention controls apply to the deployed project. OpenAI states that API data is not used to train its models unless the API customer expressly opts in; we do not opt in for this feature.

Please do not put names, contact details, exact addresses, or other identifying information in an AI question. AI responses may be inaccurate and are not medical advice.

3.7 Subscription and purchase information

Apple or Google processes your payment credentials. We do not receive your full payment-card details. RevenueCat processes a pseudonymous App user identifier, store receipt or purchase token, product and transaction information, subscription and entitlement status, last-seen information, and technical details needed to validate and restore access.

3.8 Analytics and technical information

Mobiqo receives pseudonymous session and device information such as platform, operating-system version, device model, app version, country-level location derived without precise GPS access, and limited App events. Current events relate to the paywall and purchase flow, including paywall view, purchase attempt, selected plan, success, or failure. Mobiqo may synchronize the RevenueCat identifier and associated subscription information, including product, status, transaction, renewal, cancellation, refund, currency, and revenue information.

Mobiqo analytics must not include your raw health values, daily-log answers, partner dates, analysis values, document names or contents, or AI question text.

3.9 Support information

If you contact support through the App, we process the email address and message you provide and may attach a local App/device identifier, RevenueCat identifier, operating system, OS and App versions, device model, and platform information so that we can investigate your request. Your email provider also processes an email if you contact us using it.

4. Device features and permissions

The App may ask for the following permissions only in connection with the stated feature:

• Camera: to take a profile, partner, or document photo when you choose that action.
• Photos and files: to select and locally store a profile photo or PDF/JPEG/PNG document.
• Apple Health or Health Connect: to read only the health categories you authorize. Health integration is optional and manual entry remains available.
• Notifications: to schedule discreet reminders locally on your device. You can disable individual reminders in the App and revoke notification access in system settings.
• Network access: to validate subscriptions, send limited analytics, answer an AI question you submit, open legal/support pages, and send support requests.
• System share sheet: to export or share content with an app or person you select. Once shared, that recipient's privacy practices apply.

You can deny or revoke optional permissions in iOS or Android settings. Pausing health synchronization in the App stops new reads by 74 but does not itself revoke the operating-system permission; use the Apple Health, Health Connect, or system permission settings to revoke access.

5. How and why we use information

Withdrawing consent does not affect processing that was lawful before withdrawal. When processing is necessary to perform a feature you request, that feature may no longer work after you withdraw or revoke the relevant permission.

6. Service providers and platforms

• Apple App Store and Google Play: payment, billing, refunds, subscription management, distribution, and platform services. Their privacy terms apply to their direct relationship with you.
• RevenueCat: subscription validation, entitlement status, purchase restoration, and subscription analytics. RevenueCat acts as our processor for end-user information. See its privacy policy.
• Mobiqo: mobile product and subscription analytics, including the limited data described above. See its privacy policy.
• Google Cloud / Firebase: hosts the AI and support endpoints, temporarily processes network information for HTTP requests, and stores short-lived pseudonymous AI rate-limit records. See Firebase privacy and security information.
• OpenAI: moderates and generates answers to questions submitted through the optional AI feature. See the API data-controls documentation.

These providers may use their own sub-processors. We may replace a provider with one offering a comparable function; material changes will be reflected in this policy.

7. Retention, export, and deletion

• Local App data: kept until you delete an item, use “Delete all data,” uninstall the App, or your device/operating system removes it. Uninstall behavior and backups are controlled partly by your operating system.
• Health summaries: at most 30 local-day summaries, plus the latest height and weight suggestions and connection metadata, until replaced, disconnected/deleted, or all App data is deleted.
• AI history: kept locally until you clear AI history or all App data. Remote provider retention is described in section 3.6.
• Mobiqo analytics: generally retained for up to two years under Mobiqo's published policy, unless earlier deletion or longer legal retention applies.
• Subscription records: retained by the stores and RevenueCat as needed to administer purchases, resolve disputes, prevent fraud, and meet legal/accounting duties.
• Support correspondence: normally retained for up to three years after the request is resolved, and longer only where needed for a legal claim or obligation.

The App's PDF export includes a limited local subset: the last 30 days of daily scores, the current cycle, and structured semen analyses. It excludes document contents and is not a complete copy of every technical record held by service providers.

“Delete all data” clears App storage, local files managed by the App, local notification schedules, session access, and local AI history on that device. It does not cancel an Apple or Google subscription, delete data already shared by you, erase an older device backup, or automatically erase records the stores must retain. To request deletion of remote records linked to your App identifiers, contact us at the address below.

8. When information may be shared

We do not sell personal information or health data. The App does not display third-party ads or use your information for cross-app targeted advertising, and imported health-platform data is not used for advertising. We disclose information only:

• to the providers listed in section 6 for the stated purposes;
• when you deliberately export or share information;
• to professional advisers or authorities where reasonably necessary to comply with law, protect rights and safety, investigate fraud or security issues, or establish or defend legal claims; or
• as part of a business reorganization, transfer, or sale, subject to appropriate confidentiality and notice where required.

The App does not automatically share a partner's information. You are responsible for having an appropriate basis to enter and share information about another person.

9. International data transfers

Local information stays on your device, subject to your platform backup settings. Remote providers may process information outside France or the European Economic Area. In particular, RevenueCat stores end-user service data in the United States, the current Firebase AI endpoint is hosted in the United States, and OpenAI processing may occur outside the EEA depending on project configuration.

Where data-protection law requires it, transfers rely on an adequacy decision, standard contractual clauses, or another recognized safeguard. You may contact us for more information about safeguards applicable to your data.

10. Security, device access, and backups

We use safeguards appropriate to the nature of the App, including app-private file locations, limited permissions, data minimization, and encrypted HTTPS/TLS transport for remote requests. No storage or transmission method is completely secure.

The App does not currently include a biometric lock of its own. Anyone who can unlock your device may be able to open the App. Use a device passcode, keep the operating system current, and take care when exporting or sharing sensitive records.

Depending on your device and settings, App data may be included in Apple, Google, manufacturer, or device backups. Those backups are controlled by the relevant platform and may outlive deletion from the active App installation. Review your device backup settings if you do not want the platform to retain a backup copy.

11. Your rights and choices

Depending on where you live, you may have rights to access, correct, delete, restrict, or obtain a portable copy of personal data; object to processing based on legitimate interests; withdraw consent; and complain to a supervisory authority. You also have the right not to be subject to a decision with legal or similarly significant effects based solely on automated processing. 74's lifestyle scores, projections, and analytics are not used to make such decisions.

You can edit or delete many local records directly in the App, clear AI history, export the available PDF subset, pause health synchronization, revoke permissions in system settings, and use “Delete all data.” For remote-data rights, email pro@alexandre-grisey.fr. We may need reasonable information to locate your pseudonymous record and verify the request.

If you are in France and believe your data-protection rights have not been respected after contacting us, you may lodge a complaint with the Commission Nationale de l'Informatique et des Libertés (CNIL). You may instead contact the supervisory authority where you live or work.

12. Children

The App is intended for adults aged 18 and over and is not directed to children. We do not knowingly seek personal data from anyone under 18. If you believe a minor has submitted information to a remote feature, contact us so we can assess and delete it where appropriate.

13. Changes to this policy

We may update this policy when the App, its providers, or legal requirements change. The latest version will be posted at this address with a revised effective date. We will provide additional in-App notice or request new consent before a material change where required by law.

14. Contact

For privacy questions or requests: