LAFAYETTE DIGITAL PRODUCTS

Orchestrateur privacy

Policy updated on 30 October 2026. The section “LFDP guides: protected requests on OVH” describes the protocol planned from Orchestrateur 0.3.4, a closed-test candidate. Google Play indicates the availability of this version. Practices for earlier versions remain described below.

Publisher and contact

LAFAYETTE DIGITAL PRODUCTS. For privacy questions and your rights: contact@lafayettedigitalproducts.com.

On your device

Messages, answers, dates, settings, commands, model selection, rules, permissions, memories and logs are stored in the app’s private Android files. Imported or downloaded documents are kept separately from AI models as extracted text. A bounded conversation window and relevant document passages are supplied to the local model. These data are not automatically synchronized to the cloud. Protection depends on Android and device security; Orchestrateur does not claim application-level encryption.

Changing models or deleting data

Conversations can be separate, renamed and organised in groups or subgroups. Edit an earlier question to resume from that point, select messages for deletion or clear a conversation. A local recovery archive precedes deletions and restarting a branch; deleting a message does not remove its archived copy. In Settings → My data, export a ZIP backup or merge a restored backup. Archives contain personal data in plain text and conversation organisation, but exclude models, purchases and reviewer access. Changing or removing an AI preserves these data. Manage unwanted archives and external copies separately. Uninstalling the app or clearing its Android data removes private storage, but not exports saved elsewhere. Trial expiry does not erase data.

Downloads, links and local reading

Installing an AI downloads its model from Hugging Face and its infrastructure. An explicitly requested HTTPS document contacts the chosen provider, which receives the IP address and requested address, among other information, without chats attached. External links follow the visited services’ rules and may involve processing outside the European Union. Importing a file accessible on the phone, bundled manuals and reading saved texts work without an Internet search. From the version compatible with the new catalogue, LFDP summaries are requested from OVH rather than bundled in the installation file.

LFDP guides: protected requests on OVH

To request a guide, the app sends its resource identifier, language and a temporary technical proof to an LFDP relay. The OVH server checks that the command comes from an authorised LFDP app. This operation requests no personal document, chat, search query, purchase token or extra account. Existing import conditions are separate from this check.

The proof contains an ephemeral key, Android certificates, a challenge valid for 120 seconds and a signature bound to the guide and version. No IMEI, hardware serial number or persistent installation identifier is requested. Certificates may nevertheless contain technical numbers that could allow linking; absolute anonymity is not claimed. The key is deleted after use; leftovers from an interruption are cleaned up on the next request.

Android or the manufacturer may contact its own certificate provisioning service. The OVH server checks Android’s public revocation list without attaching your command. No Google Cloud project or Play Integrity is used for this distribution. System services follow rules separate from the app’s network code.

The web relay sees the phone’s IP address, derives a fingerprint for a one-minute window and sends it to the content service in a signed command; it does not forward the raw IP. The VPS also sees the relay’s technical address. The fingerprint’s counter stays in memory for 60 seconds; people sharing one IP may share this quota. A technical nonce prevents replay and remains in memory for at most 30 seconds. Challenges are automatically purged at their 120-second expiry; verification is bounded to 15 seconds and that expiry. Service code durably stores no certificate chain, command body, raw IP or installation identifier. General hosting logs follow their providers’ rules; no retention period for them is inferred here.

Received LFDP text stays in the local library. Older editions and exports already received are not remotely erased. A recognised downloaded corrected edition takes priority in local retrieval for the same resource and language; older copies stay readable and exportable. Personal content is retained. Unavailable verification may prevent a new download; it does not stop reading saved texts.

Local chat and app connections

Chat is processed on your phone even when connections are allowed. Public search requires a separate entry of 1–500 public characters, a preview and your confirmation; Wikipedia/Wikimedia returns at most three snippets. Documents, history and drafts are not added automatically. Private text you confirm will be sent; the service also receives your IP address and network metadata.

The indicator shows connectivity and permission, not a transmission or service availability. The switch blocks new app-managed connections and interrupts tracked operations; data already sent cannot be recalled. Android, Google Play, other apps, links and external exports follow their own rules.

Wikimedia privacy policy: https://foundation.wikimedia.org/wiki/Policy:Privacy_policy.

In the prepared version 0.3.3, this permission also covers verification requests to the LFDP service: blocking app connections prevents new requests and interrupts tracked ones. Local chat does not need this permission; access already covered by a valid offline certificate remains usable within its limits.

Trial, subscriptions and offline access

The full 15-day trial does not automatically become paid. Afterwards: €1.99/month or €14.99/year including tax in France, subject to Play offers; local price and period are confirmed before payment. Subscriptions renew automatically and can be cancelled in Google Play. Cancellation is not a refund request. No new lifetime purchase is offered; existing lifetime rights are retained.

Examined versions 0.3.2 and earlier

Trial dates, signed receipts and checks are stored locally, without transmission to an LFDP billing server. Receipts may contain product, date, state, acknowledgement, order and token; checks include monotonic time and reboot records.

For a subscription, a successful Play check of a signed, acknowledged purchase allows at most 24 hours offline, until the phone restarts. This window is not the paid expiry date; reading a receipt or encountering an error does not extend it. Afterwards, allow connections and use Restore with Internet access.

Version 0.3.3 — offline continuity

This section describes how version 0.3.3 works. Check the installed version and the dates and status of your access in the app. Google Play indicates version and distribution track availability.

To verify a period and receive a signed certificate, the app sends the Google purchase token, a random installation identifier and a random nonce over HTTPS to the LFDP verification service. No messages, documents or conversation history accompany this check. The service receives connection metadata including the IP address. To limit abuse, a salted IP hash is kept in memory for 60 seconds; the service logs neither raw IP addresses nor request bodies. Any hosting-provider technical logs follow its own rules. The service queries Google, keeps a minimal private register of tokens and installations needed to track access, and supplies a certificate with verified dates, plan and status.

Requests from version 0.3.3 pass through an LFDP web relay over HTTPS. The web host receives the phone’s connection IP and maintains its separate technical logs. The relay code logs no request body, token or IP and does not forward the phone’s IP to the verification service. That service sees the relay’s technical address and keeps its salted hash in memory for 60 seconds. The abuse prevention quota is shared by users of the same relay during the closed test.

The register keeps only data needed for verification: purchase token, installation identifier, token hash, order reference, plan, period, status, dates and certificate sequence. Its retention deadline is the last known possible end of access (paid expiry E, continuity B or Google grace, and a known Google terminal expiry) plus 60 days; data then become eligible for purging. Simply checking or opening the app does not postpone this deadline. A first terminal status without a trustworthy deadline, or whose retention has already expired, creates no new durable token or installation record. A non-personal global counter may remain to prevent certificate sequences from resetting. The register is private; general encryption of it is not claimed.

A valid certificate covers the entire paid period until its end E, including after a normal restart. When renewal was expected but cannot be verified, local continuity is limited to E + 90 days for yearly plans or E + 15 for monthly plans, without changing Google Play billing dates or charges. A known cancellation of renewal retains paid access until E but removes continuity after E. Confirmed revocation, payment hold or effective pause applies when reliably received; a disconnected phone does not receive an instant remote revocation. Google grace is separate from the LFDP bridge.

Before the first extended certificate, old local access retains its maximum 24-hour limit and is invalidated on restart: use Restore online before leaving.

Reading and export remain free; expiry does not delete data. Restoring purchases does not restore conversations. Publisher-supplied reviewer access remains separate and local, and is excluded from exports and reports.

Optional reporting

You choose a response, can keep only the relevant excerpt, select a reason and add a comment. Sending requires an explicit consent checkbox and then the Send button. These texts, an identifier, app version, language and Android API level are sent over HTTPS to LAFAYETTE DIGITAL PRODUCTS. No personal name or email is requested; your chosen content may nevertheless identify you. The rest of the conversation is not attached. A receipt reference is shown only after server confirmation.

Report retention

Reports are stored in a private area of the OVH hosting service, separate from public pages, accessible to the publisher and authorized people. A technical notification may contain the reference without the message text. Files become eligible for deletion after 365 days and are purged when the service next processes a request; the publisher may delete them earlier. The service uses an IP address fingerprint to prevent abuse for 24 hours, without saving the raw IP address in its request files. Expired fingerprints are purged on the next request. The hosting provider may separately retain technical logs under its rules.

Data deletion and your rights

For data held by the publisher, contact contact@lafayettedigitalproducts.com, preferably with the report reference. Request access, correction, deletion, restriction and, where applicable, objection, portability or withdrawal of consent for future processing. The publisher cannot read data remaining on your phone. Local deletion is available in Settings → My data; archives and external copies require separate handling. You may complain to the CNIL. Avoid attaching your entire history to a simple rights request.

Advertising

Orchestrateur displays no advertising. External services you choose to use apply their own privacy rules.

Purposes and legal bases