Privacy notice

ModOnda (formerly Diokle and DAEdalus) is run by Andrea Ferrarelli. Contact through the project's GitHub issues. [Company details: to be confirmed.]

Beta text, published 17 October 2026. A lawyer will review it. Items in brackets are still to be confirmed.

#What your browser keeps

Everything below stays on your device. Nothing here is sent to us.

• Local storage: your theme, your assistant model choice, your OpenRouter key if you enter one, the address and access token of a local engine if you connect one, display preferences, dashboard layouts, and the models you keep in MyModels.
• IndexedDB: libraries you install, and simulation runs with their result series. Up to 300 unpinned runs are kept, and older ones are dropped first.

Models and results can contain sensitive work, so on a shared device clear them with the browser's site-data controls. The Forget key button removes only the OpenRouter key.

#What is sent to third parties today

Assistant chats. Each message you send the assistant, and the source, documentation and tool output it reads, goes to OpenRouter and to the model provider you select. Those providers process it under their own terms. This is the only time the site sends your content off the device.

Simulations. Simulation runs on your device. We do not receive your models or results.

Hosting. The site is hosted on EzKeel. Its servers log standard request data, such as IP address and the pages requested.

No analytics on the site today. We do not set cookies or run analytics on the static site. [Confirm at launch.]

#Sign-in with GitHub, and planned options

Sign-in with GitHub is live on the hosted site during the beta. Sign-in with Google, usage analytics and payments are not live yet. Those are described below as planned, and this section will be confirmed or updated at launch.

• Sign-in with GitHub. When you sign in with GitHub, we ask GitHub for your public profile and your primary email address. The name and email are returned to your browser when you sign in. [Confirm where they are kept and for how long before launch.] We use them to identify your account and to contact you about the service. Legal basis: [to be confirmed]. Retention: [to be confirmed].
• Sign-in with Google (planned). If it launches, we will receive your name and email address from Google, used for the same purposes.
• Usage analytics. We plan to measure usage with a self-hosted, cookieless analytics tool on our own server. It will record page views and feature events, not your name or email.
• Payments. Paid credits are processed by Stripe. We do not store card details. Stripe processes them under its own terms.

#Your rights

Depending on where you live, you may have the right to access, correct, delete or export your personal data, and to object to or restrict its use. Contact us through the GitHub issues link above. You may also complain to your data protection authority.

#Service providers

#Changes

We will update this notice when our practices change, and post the new date.