This is a courtesy translation. My Quiet Haven is published from France, and the French version of these documents is the one that is legally binding. Where the two differ, the French text prevails.
Privacy policy
My Quiet Haven
Last updated: 27 September 2026
In one sentence
My Quiet Haven works without an account, without a profile and without advertising trackers. What you write during an exercise is stored nowhere, not even on your phone. The only data that leaves your device is technical, and serves to display the content, to manage any subscription and to fix crashes.
This page says precisely which data, who receives it, and why.
1. Who is responsible for your data
Sima Création Web — Marie Schaer, sole proprietorship
8 rue du 11 Novembre 1918, 68180 Horbourg-Wihr, France
SIRET: 911 861 383 00014
Contact: contact@simacreationweb.fr
There is no data protection officer: the business meets none of the thresholds that would require one to be appointed. Your requests are handled directly by the publisher, at the address above.
2. What the app does not do
We want to write this before anything else, because it is the heart of the product:
- no account is requested, or created;
- no health data is collected: no mood, no symptom, no diagnosis, no self-report;
- no profile is built, and no recommendation is personalised on the basis of your behavior;
- no advertising, no advertising tracker, no audience measurement or behavioral analytics tool;
- no selling or commercial sharing of data, under any circumstances;
- no access to your contacts, photos, microphone, camera, location or notifications.
Because no tracker is used for advertising or measurement purposes, iOS does not display the tracking request (App Tracking Transparency): there is nothing to track.
One exception deserves to be named here rather than discovered further down: when the app crashes, a technical report is sent so the defect can be fixed. It contains no identity, no IP address and no exercise content, and serves no audience measurement. Section 5.4 details exactly what it holds.
3. What you write during exercises
Some tools invite you to put a thought, a situation or an answer into words.
These texts are never saved. They exist only in the app's working memory, for the length of the exercise, and disappear as soon as you leave it. They are written neither to the device's storage, nor to a server, nor to a backup. This choice is a constraint we accept: it makes it impossible to resume an interrupted exercise, and that is the price of the guarantee.
4. What stays on your device
These items are stored locally, in the app's private space. They are never transmitted, neither to us nor to anyone else.
| Data | Why |
|---|---|
| Your favorites (references to public content) | Finding a tool or an article again |
| Your appearance preference (light, dark, system) | Respecting your choice |
| The "introduction already seen" flag | Not showing it to you again |
| A copy of the content you have viewed | Allowing offline reading |
| The "this device has already had Premium access" flag | Restoring your access on launch — see 5.2 |
This data is erased when you uninstall the app. It may also be included in a backup of your phone (iCloud, Google), depending on your device settings — that backup belongs to you and we have no access to it.
5. What leaves your device
5.1 Displaying content — Supabase
To display the current library, the app queries our content host. As with any connection to a server, it receives your IP address and technical request information (date, device type, app version), which it keeps in its service logs.
- Purpose: serving the content and keeping the service secure.
- Legal basis: legitimate interest (art. 6.1.f GDPR) — operating and protecting a service you have chosen to use.
- Processor: Supabase, on infrastructure located in the European Union. No transfer outside the EU for this processing.
- Retention: technical logs kept briefly by the host, then deleted.
- Direction of travel: read-only. The app never sends any data back to that server.
If the server is unreachable, the app falls back on its built-in library: it remains fully usable offline.
5.2 Subscription management — RevenueCat
The management of Premium subscriptions relies on RevenueCat. Its software component is not started when the app opens. It starts only in two cases:
- you open the Premium screen, or you request a purchase restore;
- this device has already obtained Premium access — a simple boolean kept locally records this, so that a subscriber recovers access on launch.
As long as neither of these two cases arises, nothing is transmitted to RevenueCat: someone who never opens the Premium screen is never announced to that service.
When the component does start, the following are transmitted:
- an anonymous identifier generated by RevenueCat, which contains no name, no address and no email;
- a technical device identifier supplied by the system (IDFV on iOS, equivalent identifier on Android);
- the country, the platform and the version of the app;
- the subscription status and the history of the transactions attached to it.
We receive no payment details and no identity.
- Purpose: opening, maintaining and restoring access to Premium content.
- Legal basis: performance of the contract (art. 6.1.b GDPR) for subscribers. For everyone else, the processing only occurs following an explicit action on your part — opening the Premium screen or requesting a restore — and rests on our legitimate interest (art. 6.1.f) in presenting the offer to you and in verifying an existing purchase.
- Processor: RevenueCat, Inc., a company established in the United States.
- Transfer outside the European Union: governed by the European Commission's standard contractual clauses and, where applicable, by RevenueCat's certification under the EU–U.S. Data Privacy Framework.
- Retention: for the duration of the subscription relationship, then according to RevenueCat's retention policy.
5.3 Payment — Apple and Google
Payment is handled entirely by Apple or by Google, depending on the download platform. These companies act as independent data controllers: they collect your payment details under their own policies, over which we have no influence and to which we have no access.
5.4 Crash diagnostics — Sentry
When the app runs into an error it cannot handle, a technical report is sent to Sentry. It serves to fix the defect, and nothing else.
This component is inactive during development and only switches on in the versions published to the stores. As long as no error occurs, only session information is sent: the app opened, it closed without incident.
A report contains:
- the device model, the system version and the app version;
- the language and region configured on the device;
- the stack trace of the error, that is, the place in the code where it occurred;
- the names of the screens visited before the incident, in their generic form: `exercice/[slug]`, not the exercise actually opened.
The following are never sent:
- your IP address: it is explicitly cleared before sending. Without that precaution, Sentry's servers would infer it from the incoming request;
- no screenshot, no view hierarchy;
- nothing you write during an exercise, since that text is stored nowhere.
- Purpose: detecting and fixing defects in the app.
- Legal basis: legitimate interest (art. 6.1.f GDPR) in providing an app that works. No data is collected for statistical, advertising or commercial purposes.
- Processor: Functional Software, Inc., trading as Sentry, a company established in the United States.
- Data location: Sentry's European region, in Frankfurt, Germany. Reports do not leave the European Union for storage.
- Transfer outside the European Union: as the publisher is a US company, access from the United States remains possible; it is governed by the European Commission's standard contractual clauses, set out in Sentry's data processing agreement.
- Retention: under Sentry's retention policy.
6. Summary of recipients
| Recipient | Role | Data | Location |
|---|---|---|---|
| Supabase | Processor | IP address, request metadata | European Union |
| RevenueCat, Inc. | Processor | Anonymous identifier, device identifier, country, subscription status | United States (standard clauses) |
| Functional Software, Inc. (Sentry) | Processor | Device model, versions, stack trace, names of screens visited | Germany (US publisher, standard clauses) |
| Apple, Google | Independent controllers | Payment, invoicing | Under their own policies |
No other recipient. No data broker, no advertising network, no social network.
7. Your rights
The GDPR grants you rights of access, rectification, erasure, restriction, objection and portability over your personal data.
In practice, we hold no file in your name: with no account and no identity, we have no way of linking a technical data point to a person. So we cannot, on our own, find "your" data — and that is precisely the intended effect.
You retain these remedies:
- Erase local data — uninstall the app, or clear its storage from the system settings. Everything disappears.
- Subscription — manage, pause or cancel it from your App Store or Google Play account settings. For the erasure of data held by RevenueCat, write to us: we will pass the request on to our processor.
- Write to us — contact@simacreationweb.fr. We reply within one month.
- Complaint — you may lodge a complaint with the CNIL, 3 place de Fontenoy, TSA 80715, 75334 Paris Cedex 07, France, or www.cnil.fr. If you live in another European Union country, you may also contact your own national supervisory authority.
8. Minors
The app is intended for an adult audience. It is not aimed at anyone under 15 and knowingly collects no data concerning them. The content deals with mental health: support from an adult is recommended for teenagers.
9. Security
All network communications are encrypted (HTTPS/TLS). The content host access key embedded in the app is a public, read-only key, restricted by access rules at table level: it permits no writing and no access to any other data.
Since no system is infallible, the best protection remains the one we chose by design: holding no data that would need protecting.
10. Changes
This policy may change, in particular if the way the app works changes. The version in force is the one published at this address and reproduced in the app. Any substantial modification will be flagged in the release notes.
For any question about this policy: contact@simacreationweb.fr