Effective date: September 16, 2026
1. Scope and controller
Variant Power operates OhmSpice and is responsible for the processing described in this policy. This policy covers the OhmSpice website, simulator, account, cloud storage, project sharing, support reporting, and related OhmSpice Beta services. It does not govern third-party websites or services that you choose to visit.
2. Information we collect
Account and identity information
When you create or use an account, we process your email address, display name, optional profile image, account identifier, authentication-provider information, verification status, and security timestamps. Google or GitHub handles credentials when you use that provider. OhmSpice receives the identity information needed to establish your account and session.
Projects and design content
We store cloud projects, revisions, schematics, Parts, scripts, simulation settings, imported textual model bundles, provenance, thumbnails, visibility and sharing settings, and related metadata that you choose to save. A cloud project may be Public or Private. Public projects and public shares may be opened by other people. Private projects are limited to authorized workspace members and signed-in recipients with active account-bound access. Private visibility does not make OhmSpice a regulated, zero-knowledge, or archival service; do not upload regulated or exceptionally sensitive information, and keep offline exports of important work.
Assistant chats and requests
When you use Assistant, we store your messages, visible Assistant replies, summaries of completed changes, and request results in a chat attached to the cloud project. Other project members cannot access your chats. A request may include your message, the chat history needed to respond to your message, and relevant context from the active project, script, or model. OhmSpice sends that material to OpenAI. OpenAI handles it under its terms and the settings OhmSpice uses for OpenAI.
Service and diagnostic information
We process IP address and ordinary request metadata at our hosting providers. OhmSpice may send sanitized application-error events containing the route, app/build version, coarse browser information, short diagnostic breadcrumbs, error text, and an account or project identifier when available. Automatic diagnostics are designed not to contain project bodies, schematics, netlists, component values, scripts, simulation vectors, typed form content, clipboard content, credentials, tokens, or raw imported vendor-model text.
If you submit a bug report, you may choose to include the current circuit or a screenshot. Both are off by default and are uploaded only after your explicit action. Share-by-email records include a one-way hash of the recipient address, the sender and project identifiers, delivery-service metadata, and timestamps. We do not store the recipient address in OhmSpice’s share-email delivery records.
3. How we use information
We use information to:
- authenticate accounts and provide profiles, cloud storage, sharing, exports, and account deletion;
- run, secure, debug, maintain, and improve OhmSpice;
- send verification, recovery, security, project-sharing, and essential service messages;
- enforce quotas, prevent abuse, investigate incidents, and protect users and infrastructure;
- respond to support, privacy, legal, and intellectual-property requests; and
- comply with law and preserve evidence of administrative actions and policy acceptance.
We do not sell personal information. We do not use personal information for targeted advertising, and OhmSpice does not include a behavioral advertising SDK.
4. Legal bases
Where applicable law requires a legal basis, we process information to perform the service contract, pursue legitimate interests in operating and securing the service, comply with legal obligations, and act on consent for optional circuit or screenshot attachments. You may withdraw optional consent before submitting a report by removing the attachment.
5. Service providers and disclosures
We use service providers to operate OhmSpice. These include Supabase for authentication, database, storage, and server functions; OpenAI for Assistant request processing; Cloudflare for website delivery and network protection; Sentry for sanitized application-error processing; Resend for transactional email; and Google or GitHub when you choose federated sign-in. Providers process information under their own terms and our configuration of their services.
We may disclose information when required by law, to protect rights or safety, to investigate abuse, or as part of a merger, financing, acquisition, reorganization, or sale of assets subject to appropriate safeguards. Public projects and content you intentionally share are disclosed according to the sharing action you take.
6. Browser storage and cookies
OhmSpice uses browser storage and strictly necessary session technologies to keep you signed in, preserve local projects and drafts, remember application state, and protect account flows. We do not use non-essential advertising cookies. No cookie-consent banner is shown while the service uses only these necessary technologies. If that posture changes, this policy and the consent experience will be updated before non-essential tracking is enabled.
7. Retention and deletion
- Active cloud projects, Parts, revisions, and account content remain until you delete them or delete the account.
- Assistant chats, messages, and related context remain until you delete the chat, the project is permanently deleted, or account deletion removes the associated account data. Deleting a chat from its chat list removes it immediately. Deleting a project first starts its 30-day recovery period; associated chat data is removed when the project is permanently deleted. Revoking Assistant access does not delete existing chats.
- Deleted projects and My Library Parts remain recoverable for 30 days, then are deleted with their retained revisions and sharing records.
- Sanitized automatic error events and share-email delivery records expire after 30 days.
- Bug reports without a circuit or screenshot expire after 90 days. Reports containing either attachment expire after 30 days.
- Account deletion removes owned product data and the authentication identity. Security, legal-consent, and administrative audit records may be retained without the user id or email where needed for integrity, compliance, or abuse prevention.
Hosting-provider backups and logs may persist for a limited additional period under the provider's backup and security practices. We may retain information longer when reasonably necessary for a legal claim, security investigation, or binding legal obligation.
8. Security
We use access controls, permissions for individual records, email verification, size limits on submitted data, rate limits, redaction, restricted administrative operations, and encrypted network transport to protect information. No service can guarantee absolute security. Keep offline exports of important work and email [email protected] if you suspect account compromise.
9. International processing
OhmSpice and its providers may process information in the United States and other countries. Those countries may have different data-protection laws from your location. Where required, we rely on appropriate contractual or legal transfer mechanisms.
10. Your choices and rights
Account settings let you update profile information, export cloud projects and My Library Parts, delete projects or Parts, revoke sharing, and delete your account. Assistant's chat list lets you delete a chat and its transcript. The current account export does not include Assistant chat transcripts or related Assistant context. Depending on your location, you may also have rights to access, correct, delete, restrict, object to, or receive a portable copy of personal information, and to appeal or complain to a regulator.
Email [email protected] to make a privacy request. We may need to verify your identity. We will not discriminate against you for exercising a privacy right.
11. Children
OhmSpice is intended for engineers, students, and other technical users and is not directed to children under 13. Do not create an account if you are under the minimum age required to consent to online services in your location without authorization from a parent, guardian, school, or other responsible organization.
12. Changes and contact
We may update this policy as the product and legal requirements change. We will update the effective date and provide reasonable notice of material changes. Email [email protected] with privacy questions or requests.