Nelby
Nelby app privacy
Local profile data, Apple and RevenueCat purchases, notifications, retention and your data rights.
Scope and controller
Updated 10 September 2026. This policy describes Nelby 1.2.0, build 17, in preparation, with Firebase Analytics and the Meta SDK removed. It applies to that configuration when you install this version; it does not retrospectively describe older Éclo versions or builds 15 and 16.
Yann Lephay, sole proprietor, is the controller for processing performed for Nelby: 53 avenue Charles de Gaulle, 57530 Courcelles-Chaussy, France. For privacy questions and requests, email info@yann-lephay.com.
Your profile and reading records stay on your device
The questionnaire uses your answers and preferences to create a profile and select content. The profile may include a local identifier, an optional name, scores, traits and questionnaire progress. Favourites, message history and preferences help you return to readings and inform content selection.
The app stores this information locally. Some profile information uses the iOS Keychain; other data and preferences use the app’s local storage. This is not a personal journal account hosted by Nelby.
The message library is bundled with the app and selection takes place on the device. This version does not send your answers, profile or name to OpenAI or a cloud text-generation service. It does not send that information to RevenueCat as customer attributes.
Notifications, widgets and sharing you choose
Reading reminders are local notifications configured through iOS permissions. Widgets use information shared locally between the app and its extension to display content. You can change notification permissions in iOS settings and remove a widget.
Text shown in a widget or notification may be visible to someone looking at your screen. Check previews and lock-screen display settings to match your preference. If you use a sharing action, the selected content goes to the app or recipient you choose; their rules then apply.
Apple and RevenueCat handle purchases
Apple manages the App Store account and payment. Nelby does not receive your payment card number. Apple processes information for its services under its own policy, including purchases, purchase history and refunds.
RevenueCat helps load offers, validate purchases, recognise Premium and restore an existing entitlement. Data includes a technical user identifier created by its SDK, products and transactions, purchase or subscription dates and status, and associated access rights. The SDK may communicate with RevenueCat before you buy, to load offers or check access.
RevenueCat calls its generated identifier “anonymous”, but it can connect an entitlement with its transactions; this does not promise irreversible anonymity. Restoration can associate identifiers with purchase history. An identifier used by an older version may also have been shared with that version’s measurement tools.
RevenueCat also receives technical request information: platform and operating-system version, app and SDK version, language or storefront settings and connection information, including the IP address needed for communication. Its tools may display a country inferred from that connection; this is not GPS access requested by Nelby.
Purchase information also supports RevenueCat’s commercial reporting. Removing Firebase Analytics and Meta therefore does not mean that no purchase analytics exist. This version’s configuration does not send RevenueCat your name, email address, detailed questionnaire answers or personal profile.
Apple: App Store and privacy →
If you contact support
If you email info@yann-lephay.com, we receive your email address, message and any attachments you choose to send. We use them to handle your request and, where needed, investigate an access problem. The publisher and email service providers participate in this processing.
Start with the issue, app version and displayed message. Do not send an Apple password, verification code, payment details or personal questionnaire answers. If more information is needed to identify a purchase or a rights request, we will ask only for relevant details.
Purposes and legal bases
Local information needed for your profile, selection and favourites provides the features you use. Offer, purchase and entitlement checks provide the service and fulfil the relevant purchase. Necessary processing relies on performance of the contract or steps you request before a purchase.
Where not required for the contract, security, abuse prevention, general enquiries and purchase-level commercial reporting rely on the publisher’s legitimate interest in operating and maintaining the service. You may object to legitimate-interest processing under the applicable legal conditions. Records required by law are processed on that legal basis.
Optional features you enable, including notifications, follow your choices and device permissions; you can disable them. This policy is not blanket consent to advertising processing. Automated reading selection does not make legal or similarly significant decisions about you.
Recipients and international transfers
Local profile data is not sent to a Nelby server to select messages. The technical and purchase data described above is processed by Apple, RevenueCat and their necessary providers according to their respective roles. The publisher can consult available purchase and entitlement information in its management tools for support and commercial reporting.
RevenueCat, Inc. is based in the United States, and technical and purchase data may be processed outside the European Economic Area. Its processing agreement provides Standard Contractual Clauses for transfers subject to that mechanism. Apple describes its processing and safeguards in its privacy documents. You can ask us about safeguards applicable to processing performed for Nelby.
These documents are not presented as proof that all data is hosted in the European Union or that no transfer can occur.
Retention: three different situations
On your device, the profile, favourites and history remain while retained in the storage used by the app. The profile deletion or reset feature clears the local data covered by that action. Uninstalling is not proof of complete erasure: iOS Keychain and any device backups also follow their own rules.
Some purchase information must remain available to recognise Premium, restore purchases, manage older subscriptions, prevent fraud or meet legal obligations. Retention therefore does not automatically end when you delete a profile. Apple and RevenueCat apply requirements connected to their services and the relevant obligations.
Support correspondence is kept while handling the request and relevant follow-up, then only as needed for legal obligations or a dispute. There is no single period that applies to all these records; you may ask which criteria apply to your situation. We do not promise automatic complete erasure on a fixed date.
Older Éclo versions and builds 15 and 16
Older versions could include Firebase Analytics and the Meta SDK for usage events, technical information and purchase events. Builds 15 and 16 included them. Removing these SDKs from the new build ends their use by this new configuration; it does not automatically erase information already received by providers.
If your request concerns that period, include the version or approximate dates if you can. We will examine the records we can identify and the applicable provider procedures, without asking for passwords or promising deletion of information that must legally be retained.
Your rights and how to use them
Under the applicable GDPR conditions, you may request access, correction, erasure, restriction or portability of relevant personal data, or object to certain processing. Available rights depend on the processing and its legal basis. Requests about Apple’s own account processing may also be made to Apple.
Email info@yann-lephay.com with your request. Proportionate information may be needed to verify that the data concerns you; we do not routinely require identity documents. Information held only on your device may not be accessible remotely to the publisher.
We respond within the statutory period, normally one month from the request. If a legally permitted extension is needed, we inform you and explain why. You may complain to the CNIL or another competent supervisory authority if you believe your rights have not been respected.
Policy updates
This page covers the configuration identified at the top. Changes to providers or processing lead to an appropriate update and, where required, further notice or a choice. The website privacy notice is separate from this app policy.