Your circuits stay yours.

Who is responsible

The public legal controller identity, address and monitored privacy contact have not yet been published. Simvolta is the product name, not a claim about a registered legal entity.

The local desktop app

The current Electro desktop build stores project files, personal components and recovery data on your computer. It has no telemetry, automatic update checks or cloud solver. Copy Diagnostics is an explicit action that copies a redacted report to your clipboard; the app does not upload it.

One Simvolta release notification

The release-notification form asks for your email address and an unchecked, affirmative consent choice. With your permission, we store the address, signup and consent times, source page, consent wording and version, optional expiry and withdrawal status in a private SQLite database on our DigitalOcean server. This is solely a request for a Simvolta desktop availability notification, not a general marketing newsletter.

Registration does not send a confirmation email or verify ownership of an address. Requests remain unverified. Repeated submissions do not renew consent or reactivate a withdrawn request. There is no promised release date. The new waitlist does not send addresses to Brevo or another email-delivery provider at signup.

A public contact channel for withdrawal and deletion requests has not yet been published. A keyed matching value may be retained to prevent an opted-out address from being re-added, for as long as this release-notification program operates. It is still treated as personal data.

Separate installer requests

The older Brevo integration is reserved for published installer requests and optional newsletter confirmation, if separately enabled. A download request sends your email address, request time, source page, purpose and privacy-notice version to Brevo, the email service provider. A successful request reveals a reviewed installer link on this page. It does not send an installer email or subscribe you to marketing.

Previously collected Brevo records, if any, remain separate. The local waitlist does not import, delete or subscribe those contacts to a new purpose. Installer requests and release notifications never require choosing the newsletter.

Optional product updates

If the separate installer/newsletter integration is enabled, its optional updates checkbox is off by default. Choosing it asks Brevo to send a confirmation email and records the request time, source and wording version. Only its double-opt-in confirmation flow adds the newsletter subscription. A request or a visit to the confirmation-return page is not proof of confirmed consent.

Product updates rely on your consent. You can withdraw it using the unsubscribe link in each newsletter. Download and one-time notification lists are kept separate from the confirmed newsletter audience. A later download request does not authorize resubscription.

Technical data and cookies

The website sets one essential cookie that stores your analytics choice for a year. Only if you choose “Allow analytics” does it load PostHog, hosted in the EU, to measure page views, social-link clicks, video requests and signup submission outcomes, without sending your email address or form contents to analytics; PostHog then sets its own first-party cookie and local-storage identifier. If you choose “Only essential”, the PostHog script is never downloaded. You can change or withdraw your choice at any time with “Cookie settings” in the footer. Simvolta’s analytics do not use advertising scripts or cross-site tracking, and the desktop app contains no website analytics. Fonts, screenshots, video posters and short build recordings are served locally. Hosting and reverse-proxy services may process IP addresses, request paths, timestamps and user-agent information to deliver and protect the site; their final logging policy must be set before public launch.

Submission protection uses short-lived signed form tokens and bounded server-memory records. When a trusted proxy supplies an IP, it is keyed-hashed for rate limiting; normalized email addresses are also keyed-hashed for limiting. These values are used for at most an hour and held only in bounded process memory. The SQLite waitlist stores no IP or user-agent data. Successful retry responses can remain in server memory for 30 minutes. The application does not log email payloads or provider error bodies.

Brevo handles the requested email and confirmation link. Account-level open/click tracking must be disabled before collection opens; no tracking permission is inferred from newsletter consent.

YouTube videos and social links

Narrated tutorials use YouTube’s privacy-enhanced player. No request to YouTube or Google is made for these players until you press Play. Loading a player connects your browser to Google, which receives technical information such as your IP address and the embedding site’s origin, and may use storage for playback. Privacy-enhanced mode limits personalization; it does not make playback anonymous. YouTube may show non-personalized advertising.

This playback choice is separate from optional PostHog analytics. “Close YouTube player” removes the player; it cannot undo data already sent. The written guides remain available without loading external media. Following a YouTube or Facebook link opens that service, where its own privacy policy applies. See YouTube’s embedding guidance and Google’s privacy policy.

Retention and service providers

Release-notification requests currently have no automatic expiry. Newsletter data is used until consent is withdrawn, with minimal suppression evidence retained to honor an opt-out. An operator runs the waitlist expiry cleanup and handles withdrawals. Private exports and backups must follow the same retention policy; historical backup copies are removed through the operator’s bounded rotation schedule. A restore requires replaying later withdrawal and deletion requests before collection resumes.

DigitalOcean hosts the waitlist; Cloudflare delivers and protects website traffic, including form requests. These providers can process personal data. No email-delivery provider receives the local waitlist at signup. If the separate older integration is enabled, Brevo processes its email data on behalf of the operator. Its account agreement, processing region, subprocessors and any international-transfer safeguards must be reviewed for the actual account before launch. No customer data is sold by this application.

Your choices and requests

You can browse without providing an email. Where applicable, you may request access, correction, deletion or portability, object to or restrict processing, withdraw consent, and complain to your data-protection authority. Use the published privacy/support contact once available. No form is provided here to collect a request without a monitored recipient.