Skip to content
dismoi

Last updated: 16 October 2026

Privacy policy

What we do with personal data, in the two situations where we come across it: when you visit this site or hold a dismoi account, and when a visitor to your site uses the Trame, Gouvernail or Pilote widget you installed there.

In short

  • This site sets no cookies and does no audience measurement.
  • Our servers are in France, at QUIDDEM SAS, on OVHcloud infrastructure. Our providers are named below; Stripe, for payment collection, and Google, for the applications' fonts, may process data outside the European Union.
  • We do not sell, rent or transfer any data, and we build no advertising profile from it.
  • For what your visitors submit or show through a widget, we do not act on our own behalf but on yours: you remain responsible for it, we are your processor.

Two roles, not to be confused

The GDPR distinguishes the controller, who decides why and how data is processed, from the processor, who processes it on instruction. The suite puts us sometimes in one role, sometimes in the other.

CoderKaine as controller

When you visit this site, write to us, create an account, manage an organisation and when we invoice you, we decide on that processing: we are its controller.

CoderKaine as processor

When a visitor to your site submits feedback through Trame, shares their page with you through Gouvernail or gives an instruction to Pilote, you decided to install the widget, on which pages and for what. We only carry, store where intended and present that data to you, and we never use it for our own purposes. Your obligations are set out on the GDPR page.

What we process, and why

You visit this site

No account, no form other than the widget, no cookie, no measurement tool. Like any web server, ours writes technical logs (IP address, requested page, browser), which our platform collects. The two preferences the page remembers, theme and language, stay in your browser: the cookies page lists them by name.

You write to us

Through this site's widget or by email, we process what you send us (email address, message content) solely to answer you. Legal basis: our legitimate interest in handling a request you initiated.

You hold a dismoi account

One account opens all three products and the account area. We process your email address, your name if you provide it, your password, the organisation you belong to and your role, the invitations you send, the products enabled, authentication tokens and, if you turn it on, the secret of your second factor. If you choose to sign in with Google or Apple, we receive the identity that provider passes to us. Purpose: providing the service and securing access. Legal basis: performance of the contract, that is the terms of use.

You subscribe to a paid plan

We process your organisation's billing details, its subscriptions, the usage measured by each product and the history of its invoices and payments. We never see or keep your card number: it is entered in a field hosted by Stripe and does not pass through our servers. Invoices are issued by Pennylane. Legal bases: performance of the contract, and our legal obligation to keep accounting records.

Trame: your visitors' feedback

The widget sends the content of the feedback, the visitor's email address if they provide it and, depending on the kind of feedback, a technical context. In a conversation it also sends the messages exchanged and a pseudonymous visitor identifier, issued by our servers and kept in the browser, so the thread can be found again from one visit to the next. When the visitor leaves their address, it goes into the project's contact directory, with their name if given and the dates of their first and last visit.

Always attached: the page address, the browser, the operating system, the window size and the declared language.

Attached to a problem, an improvement and a conversation: console messages, errors that occurred, observed network requests and, if the visitor produces them, an annotated screenshot, a video or a voice note.

None of this for a rating or a contact request: these two kinds carry no technical context.

Masking before sending. Passwords, tokens, authorisation headers, cookies and email addresses found in the captured context are replaced by markers on the visitor's device, before anything leaves for our servers. You can turn off network capture with data-capture-requests="false" and restrict the kinds offered with data-types. Opening the widget sends nothing: sending follows submission of the form.

Gouvernail: the shared page

Nothing is sent until the visitor has entered the six-digit code your agent gives them, opened the link carrying that code, or opened the invitation received in a Trame conversation, and then accepted sharing in the window that names the agent. They can decline.

Once sharing is accepted, the widget copies the page live to the agent (structure, text, movements and clicks), along with the page address, parameters included; the fragment (#…) and any credentials placed in the address are removed.

Never shown to the agent: field input (replaced by asterisks, except under data-ck-unmask, and never for a password or card field, even when marked), the text of editable areas, areas marked data-ck-block, embedded videos, sounds and frames, hidden fields, and the Gouvernail and Trame widgets themselves.

What is kept. The last copy of the page is deleted when the session ends. Relayed event batches remain in a fixed-size buffer (128 MB), overwritten as it fills, with no guaranteed duration. The session history (dates, agent, site origin, end reason, with no page content) is not purged. The code and access tokens are only stored as a hash.

Pilote: instructions and the page

When a user of your application gives Pilote an instruction, the widget sends that instruction and a description of the page to our service, which relays it to the language model hosted by OVHcloud in France. This description may include the content of the form fields visible on the page.

The request content is never logged and Pilote keeps no conversation. We keep your API keys, the allowed origins and a count of tokens consumed per day and per month, used for the quota and the invoice.

Retention periods

Message sent through this site's widget or by email
As long as it takes to handle the request.
Account
For the life of the account. You can delete it yourself, after confirming with a code received by email.
Trame feedback and conversations
90 days without activity by default, adjustable per project; at most 7 days on the Discovery plan. The period runs from when the feedback was submitted or, for a conversation, from its last message; email replies and internal notes do not extend it.
Trame contact directory
Address, name, first and last visit of visitors who left their address: no automatic purge.
Gouvernail page copy
Deleted when the session ends.
Gouvernail event batches
Kept in a fixed-size buffer (128 MB), overwritten as it fills, with no guaranteed duration.
Gouvernail session history
Dates, agent, site origin and end reason, with no page content: no automatic purge.
Pilote instructions
Not kept; only token counts are.
Invoices and accounting records
10 years, under the legal retention obligation.

Who else has access

No data is sold, rented, transferred or exchanged. It is only shared with our sub-processors, each for the part needed for its task:

QUIDDEM SAS
Hosting of the site, the three products and the account area, in France.
OVHcloud
Sub-processor of QUIDDEM SAS: compute servers, databases, files attached to feedback and Pilote's language model, in France.
Mailjet
Sending of transactional emails: verification codes, invitations, product notifications, billing notices.
Stripe
Collection of card payments.
Pennylane
Issuing and keeping invoices.

Outside the European Union. Stripe, for payment collection, and Google, for the fonts loaded by the applications, may process data outside the European Union.

One caveat, which we prefer to state: the Trame, Gouvernail and Pilote applications and the account area currently load their font from Google Fonts, which sends your browser's IP address to Google. This site does not: its fonts are served from our own servers.

Security

  • Widget key public by design but bound to a domain: outside the declared domain it is useless.
  • Secrets masked on the visitor's device, before sending, in Trame as in Gouvernail.
  • Second authentication factor by time-based code (TOTP).
  • Data partitioned by organisation: billing rights are reserved for the owner and administrator roles.

Your rights

Under the GDPR and the amended French Data Protection Act of 6 January 1978, you have the right of access, rectification, erasure, restriction, objection and portability, as well as the right to withdraw your consent where processing relies on it.

For the processing we are responsible for, your account, your billing or a message you sent us, exercise these rights by writing to contact@coderkaine.com. We answer within one month.

If you are a visitor to a site that installed one of the suite's widgets, contact that site's publisher first: they are the controller. If you cannot identify them, write to us and we will pass it on.

Finally, you may lodge a complaint with the CNIL, the French data protection authority, 3 place de Fontenoy, TSA 80715, 75334 Paris Cedex 07, France, www.cnil.fr.

The Trame widget on this site

This site runs its own product: the launcher at the bottom right is a real Trame widget. It observes this page as it would observe yours, in the tab's memory. Nothing is sent before you have filled in and submitted the form, with one exception: if you have already opened a conversation from this browser, the widget asks on load whether you have unread messages, then receives replies while the thread is displayed.

Changes

This policy evolves with the products. Each version is published on this page, with its date of update.