MESELEO
FRStart the trial

Legal information

Privacy

Last updated: 11 October 2026

Responsible person and contact

Houcine Messad, Paris, France, runs the MESELEO project. Data questions and requests: simavionicsfr@gmail.com.

Data and purposes

  • Forms transmit the contact details and information you enter to answer your request and prepare a possible project: pre-contractual steps or legitimate interest depending on the request. Required fields are marked on the form.
  • Accounts, organizations, members, missions, campaigns and results provide the requested service. API keys are stored as digests; their secret is displayed only at creation.
  • Sensitive actions, usage counters and technical logs support security, diagnosis and quota enforcement: service operation and legitimate security interests.
  • When payment is enabled, Stripe handles hosted payment. MESELEO retains customer/subscription identifiers, statuses and billing events needed to follow the contract; MESELEO forms do not request card entry.

Retention and deletion

Accounts and work data are retained to provide the service and organization permissions. Send deletion or access requests to the contact above; deleting one member’s account does not necessarily delete shared organization data. Any statutory retention must be distinguished from ordinary use.

The audit-retention mechanism targets 365 days; its execution depends on service availability and requires monitoring. It does not guarantee deletion at an exact instant. Provider log settings, backups and billing archives still need to be confirmed in the processing register before commercial opening. No uniform maximum log-retention period is guaranteed here.

Cookies and browser storage

Applications use session and organization-context cookies. Language preferences also use localStorage and persist until changed or cleared. Authentication cookies are configured without persistent expiry; session restoration also depends on the browser. The website code includes no advertising or third-party audience analytics tool. Hosted provider journeys, including Stripe, also have their own notices. Absence of a banner is not certification of every tracker in the live journey.

Recipients and transfers

Netlify hosts the website, applications and forms; Render hosts the API; Supabase provides database and authentication; Stripe handles payments when enabled. GitHub hosts source code and development automation. Data flows, hosting regions, downstream providers and possible access from outside the EU must be documented for each service. No international-transfer mechanism or certification is presumed to cover every provider.

Your rights

Depending on the processing and applicable legal basis, you may request access, correction, deletion, restriction, objection or portability using the contact above. You may also contact the CNIL. This notice describes the known scope; it does not replace verification of processing agreements and configurations before commercial opening.