Controller
THE BLUE HOUSE (SASU), 7 rue d'Arsonval, 75015 Paris, France, is the data controller. Privacy requests can be sent to support@ficelle.ai.
Data we process
- Website: limited technical logs such as IP address, user-agent, requested URL and timestamp, as provided by Netlify.
- Checkout: email address, plan, payment status, customer and subscription identifiers. Card data is handled directly by Stripe and is not stored by Ficelle.
- Licence service: licence key, machine fingerprint, activation identifier, plan and entitlement status.
-
Update checks: a count. Ficelle asks
install.ficelle.aionce a day whether a newer release exists. We record one number per calendar day and nothing else: no address, no identifier, no machine or licence details, nothing that could be linked back to you or joined to your purchase. The web server log line for that request, which would otherwise contain your IP address, is discarded rather than written. - Support: your email address and the content of messages you send us.
Why we count update checks, and how to opt out
Ficelle sends us no usage data, so we have no way of knowing whether the software people install is still in use a month later. The daily update check is the one request every install already makes, and counting it is the least we can ask to answer that question. It tells us how many installations are alive on a given day, and nothing about any of them.
Your machine still has to reach our server to ask, so your IP address is
visible to it for the duration of the request, as it is to any website you
open. We neither store it nor log it. If you would rather not ask us at all,
point the check elsewhere by setting
FICELLE_UPDATE_MANIFEST_URL to the GitHub releases API, which
is where Ficelle looked before, or to your own mirror. Nothing else in the
product changes.
Local product data
Ficelle runs locally. Prompts, API keys and model responses are not sent to THE BLUE HOUSE by the router. They go directly between your machine and the providers you configure. Each provider applies its own privacy policy. The router reports no usage to us: the only request it makes to our servers is the daily update check described above, plus licence activation if you are a Pro customer.
Purposes and legal bases
- Provide checkout, licence activation and support: performance of the contract.
- Prevent abuse and secure the service: legitimate interests.
- Keep invoices and mandatory records: legal obligations.
Processors and transfers
We use Stripe for payment, Render for the licence service, Netlify for the website and GitHub for source and release hosting. Some providers are based in the United States and rely on applicable transfer safeguards, including standard contractual clauses where required.
Retention
Licence and contract records are retained while access is active and for the period needed to handle disputes and legal obligations. Accounting records may be retained for ten years. Support messages are kept only as long as needed to resolve the request. Hosting logs follow each provider's retention settings.
Your rights
Subject to applicable law, you may request access, correction, deletion, restriction, portability or objection. You may also complain to the CNIL at cnil.fr.