Privacy Policy
“Birth Plan” app — Birth Plan – Hospital Bag List
Version 1.0 · effective 25 August 2026 · app identifier: fr.becune.birthplan
1. In short
This app helps you prepare a birth plan and a hospital bag list. What you write in it is intimate. So the app was built so that we never have access to it.
| What you enter | Where it goes |
|---|---|
| Your birth plan answers, due date, intended place of birth, the name of your maternity unit, your ticked list items | Your phone only. Nothing is uploaded: no server, no account. The developer never sees any of it. |
| Anonymous usage statistics | Only if you say yes. Six funnel events, with no answers and no personal data. You can decline, and change your mind at any time. |
| The one-time in-app purchase | Handled by Apple (the seller) and by RevenueCat (our purchase-management tool). We receive neither your name nor your payment details. |
| The PDF you export | Built on your phone. It only goes where you send it. |
This summary is here for clarity. The sections below are the binding text.
2. Who is responsible for your data
The controller, within the meaning of Article 4(7) of Regulation (EU) 2016/679 (“GDPR”), is:
- Louis-Frédéric Fortier, sole trader publishing under their own name
- Address: CDV 260133, 350 chemin du Pré Neuf, France
- Telephone: +33 7 58 45 89 65
- Email: loufi.officiel@gmail.com
The developer is not required to appoint a data protection officer under Article 37 GDPR: the activity involves neither large-scale systematic monitoring nor large-scale processing of special-category data, since the app’s data never leaves the device. Any question about this policy should be sent to the address above.
becune-technologies.com, the site hosting this document, is hosted by Vercel Inc., 440 N Barranca Ave #4133, Covina, CA 91723, United States (https://vercel.com).
3. The principle: no account, no server
The app works offline. There is no sign-up, no authentication, no synchronisation and no server operated by the developer. The questionnaire, your answers, your priorities, your profile and the state of your lists are saved in a local database (SQLite) held in the app’s private storage on your device.
Two consequences, stated plainly:
- We cannot read your answers, retrieve them, or restore them if you lose your device.
- That local file sits in the app’s “Documents” folder and is therefore, unless you change your settings, included in your device backup (iCloud backup or an encrypted local backup). That backup is performed by Apple under its own terms and privacy policy, which the developer has no visibility into. You can turn it off for this app in your device’s iCloud settings.
Deleting the app removes this data from the device. A copy may remain in your backups until you delete those too.
4. The data involved, one item at a time
4.1 Your birth plan and profile (local)
This covers your answers to the birth plan questions, the free text you write, the questions you flag “to discuss with my medical team”, your three priorities, your due date, the intended place of birth, the name of the maternity unit, the expected length of stay, the season, and the items you tick in the bag lists.
Some of this is data concerning health within the meaning of Article 9 GDPR. It stays exclusively on your device, under your sole control. It is never transmitted to, accessed by, or analysed by the developer or any third party. The app does not interpret it and draws no recommendation from it.
4.2 Anonymous usage statistics (optional)
After onboarding, the app asks you a question, once. Until you answer “I accept”, collection is disabled at system level: the Firebase flags are set to off at build time (FIREBASE_ANALYTICS_COLLECTION_ENABLED = false), Google consent mode is initialised as denied, and the app does not even emit the events internally. Nothing is buffered for later sending.
If you accept, the app sends Google Analytics for Firebase six funnel events, and nothing else:
| Event | What it means | Parameters sent |
|---|---|---|
onboarding_completed | Onboarding was finished | none |
theme_completed | A questionnaire theme was worked through | the theme identifier (for example labor) — never an answer |
paywall_viewed | The purchase screen was shown | none |
purchase_completed | A purchase succeeded | none |
pdf_exported | A PDF was exported | none |
checklist_progress | Progress in a bag list | the list identifier and the number of ticked items — never which ones |
The app’s internal analytics interface deliberately makes any other event impossible to send: there is no generic logging function. Automatic screen tracking (screen_view) is switched off.
Alongside these events, the Firebase SDK attaches technical information it generates itself: an app instance identifier (specific to the installation, not tied to your identity), the device model, the operating system version, the app version, the language, the country inferred from the IP address, and aggregate usage data such as session counts. The IP address is used to infer the country and is not retained by Google Analytics for Firebase.
No advertising identifier is used (no IDFA on iOS, no Android advertising ID). The app shows no advertising, performs no tracking across other companies’ apps or websites, and therefore never shows Apple’s “Allow tracking” prompt (App Tracking Transparency).
A note on wording. The app, like this page, speaks of “anonymous” statistics. Strictly under the GDPR this data is pseudonymous: it rests on an installation identifier that carries neither your name nor your address, but that technically distinguishes one installation from another. It is tied to no identity, and neither the developer nor Google has any means of locating you within it. The word “anonymous” is used in the app because it faithfully describes what this means for you; this document uses the legally exact term.
You can change your mind at any time in the “Your details” screen. Withdrawing consent immediately stops collection and resets the device’s analytics identifiers.
4.3 The one-time purchase
Unlocking PDF export and all three lists is a one-time purchase, not a subscription. The purchase is made from Apple, which is the seller: Apple takes the payment and applies its own terms and privacy policy. The developer receives neither your name, nor your address, nor your payment method, nor your Apple Account.
The app uses RevenueCat to verify that the purchase took place and to restore it across your devices. For that purpose RevenueCat processes an anonymous user identifier it generates, the vendor identifier for the device (IDFV, shared only across this developer’s apps), the purchase receipt issued by Apple, the product identifier, the store country, and technical information about the device and app version. This data does not let the developer identify you by name.
The outcome — “unlocked” or “not unlocked” — is cached on the device so the app keeps working offline.
4.4 Bag reminders
If you save a due date and grant the system permission, the app schedules two local notifications, four and two weeks before the due date. They are scheduled and fired by your device: there are no push notifications, no device token, no delivery server, and your due date is not sent to anyone. Declining the permission stops nothing else from working.
4.5 PDF export
The PDF is composed on your device from the local data. It is not uploaded anywhere. When you export it, the system share sheet opens and you alone choose the recipient (print, messaging app, storage app, and so on). From that point the document is governed by the terms of the service you chose.
4.6 Messages you send to support
If you write to loufi.officiel@gmail.com, the developer processes your email address and the content of your message in order to reply. There is no need to include health information in a support request.
5. Purposes and legal bases
| Processing | Purpose | Legal basis (GDPR) |
|---|---|---|
| Local storage of the birth plan, profile and lists | Delivering the core functionality of the app | Performance of the contract — Art. 6(1)(b). For health-related information, your explicit consent — Art. 9(2)(a) — given by choosing to enter it, and withdrawn by deleting the answer or the app. This data never leaves your device. |
| Anonymous usage statistics | Understanding which screens are used, to improve the app | Your consent — Art. 6(1)(a) — freely given, specific, prior and revocable |
| Purchase verification and restoration | Unlocking paid features and supporting “Restore purchases” | Performance of the contract — Art. 6(1)(b) |
| Bag reminders | Alerting you four and two weeks before the due date | Your consent, given through the system permission — Art. 6(1)(a) |
| Replying to your messages | Support and complaint handling | Performance of the contract and the legitimate interest in answering users — Art. 6(1)(b) and 6(1)(f) |
There is no automated decision-making producing legal effects and no profiling within the meaning of Article 22 GDPR. The app does not advise you: it organises what you wrote.
6. Trackers and device identifiers
Article 82 of French Act No. 78-17 of 6 January 1978 (implementing Article 5(3) of the ePrivacy Directive) requires consent for writing to or reading from a terminal any information that is not strictly necessary for the service requested.
- Analytics identifiers (Firebase). They are written and read only after your explicit acceptance, and are reset if you withdraw consent. That is precisely what the one-time sheet shown after onboarding is for.
- The local database and the purchase cache. They are strictly necessary for the service you asked for (keeping your birth plan, knowing that you paid) and are therefore exempt from consent.
- No advertising cookies, no third-party advertising measurement, no advertising identifier.
becune-technologies.com, the site you are reading this on, sets no analytics or advertising cookies.
7. Recipients and processors
The developer does not sell, rent or trade any data. The only third parties involved are the following, each in the role stated:
| Third party | Role | Data involved | Policy |
|---|---|---|---|
| Google Ireland Limited / Google LLC (Google Analytics for Firebase) | Processor acting for the developer | The six funnel events and the technical information described in 4.2 — only if you consented | firebase.google.com/support/privacy |
| RevenueCat, Inc. | Processor acting for the developer | Anonymous identifier, IDFV, purchase receipt, product, country, technical data | revenuecat.com/privacy |
| Apple Inc. / Apple Distribution International Ltd. | Independent controller (seller of the app, distributor, provider of iCloud backup) | Account, payment and download data, backups | apple.com/legal/privacy |
Data may also be disclosed where the law requires it (court order, legal obligation). Given the architecture of the app, no such order could reach the content of your birth plan: the developer does not hold it.
8. Transfers outside the European Union
The data described in 4.1 (your birth plan) is not transferred anywhere: it does not leave your device.
Usage statistics and purchase data may be processed in the United States by Google LLC and RevenueCat, Inc. Those transfers are governed by the European Commission’s standard contractual clauses (Implementing Decision (EU) 2021/914), supplemented, where the provider is certified under it, by the EU–U.S. Data Privacy Framework, which benefits from the Commission’s adequacy decision of 10 July 2023. A copy of the applicable safeguards can be requested at the address in section 15.
9. Retention periods
| Data | Period |
|---|---|
| Birth plan, profile, lists (local) | Until you delete them or uninstall the app. The developer holds no copy and therefore cannot delete them on your behalf. |
| Usage statistics | At event level, for the retention period configured in Google Analytics for Firebase, then retained by Google in aggregate form. Withdrawing consent resets the analytics identifiers. |
| Purchase data (RevenueCat) | For as long as the app is operated, so that purchase restoration remains possible, then in line with the accounting obligations applicable to the seller. |
| Support emails | 3 years from the last exchange |
10. Your rights
You have the rights of access, rectification, erasure, restriction, objection and portability set out in Articles 15 to 22 GDPR, the right to withdraw consent at any time (Article 7(3)), and, under French law, the right to give directions on what happens to your data after your death (Article 85 of the French Data Protection Act).
In this app, concretely:
- Access, rectification, erasure and portability of your birth plan. You exercise these directly, without going through the developer: the app is the interface to that data. You can edit or delete any answer, export the whole document as a PDF, and remove everything by uninstalling the app.
- Withdrawing consent to statistics. “Your details” screen, effective immediately.
- Statistics already sent. They are pseudonymised and tied to no identity: the developer cannot locate you within them. Article 11(2) GDPR applies — the developer is not obliged to keep additional information for the sole purpose of identifying you. Withdrawing consent, which resets the identifiers, is the effective way to stop collection.
- Purchase data. Send your request to the developer, who will pass it on to RevenueCat; data held by Apple is a matter for Apple.
Requests can be sent to loufi.officiel@gmail.com. A reply is provided within one month, extendable by two months where the request is complex, in accordance with Article 12(3) GDPR.
If you believe your rights are not being respected, you may lodge a complaint with the French supervisory authority, the Commission nationale de l’informatique et des libertés (CNIL) — 3 place de Fontenoy, TSA 80715, 75334 Paris Cedex 07, France — www.cnil.fr — or with the supervisory authority of your country of residence.
11. Security
The strongest safeguard this app offers is architectural: there is no central database to breach. Your answers are stored nowhere but with you.
- Local data lives in the app’s private storage (the iOS sandbox), inaccessible to other apps and protected by system encryption when your device is locked with a passcode.
- The few network exchanges (consented statistics, purchase verification) use encrypted HTTPS/TLS connections.
- We recommend protecting your device with a passcode, fingerprint or face recognition: that is the most effective protection for your birth plan.
No system is infallible; the developer implements technical and organisational measures appropriate under Article 32 GDPR and proportionate to a server-less architecture.
12. Health data and hosting
The developer hosts no health data on behalf of third parties. The French “health data hosting” certification requirement under Article L. 1111-8 of the Public Health Code therefore does not apply: the health-related information you enter stays on your device, under your sole control, and is never placed on any information system operated by the developer or by a provider acting on the developer’s behalf.
If you choose to send your PDF to a healthcare professional or facility, that document falls outside the scope of this policy and is governed by the rules applying to the recipient.
13. Age of users
The app is intended for adults preparing for a birth. It is not directed at children and is not designed to knowingly collect data relating to children under the age of fifteen, the age at which a minor may consent alone to the processing of their data for information society services under French law (Article 7-1 of the French Data Protection Act). In other Member States that age may be between 13 and 16.
14. Changes to this policy
This policy may be updated, in particular as the app evolves. The version in force is the one published at this address, with its date. Where a change is substantive — a new category of data or a new recipient, for instance — you are informed in the app before it takes effect, and fresh consent is collected where required.
Version 1.0, effective 2026-08-25.
15. Contact us
For any question about this policy, to exercise your rights, or to report a problem:
- Email: loufi.officiel@gmail.com
- Post: Louis-Frédéric Fortier, CDV 260133, 350 chemin du Pré Neuf, France
See also the app’s terms of use.