Until dedicated department inboxes are introduced, contact us about privacy, data access, deletion, school requests, or complaints at dev@kapadia.biz.

For the current beta, de:volt acts as the service operator for direct users. For de:volt Learn used by a school or institution, the school may be the primary decision-maker for student accounts and class data, and de:volt processes that data to provide the education service.

• Account data: email address, user ID, display name, avatar, timezone, authentication provider details, and profile preferences.
• Simulator data: project names, circuit components, wiring, labels, settings, revisions, exports, and cloud-save metadata.
• AI data: prompts, selected action, compact circuit snapshots, conversation history, generated replies, edit plans, validation results, token usage, and request-cost metadata.
• Learn data: schools, classes, memberships, roles, join codes, teacher invites, lessons, teacher-authored module content, assignments, submissions, scores, objective progress, live classroom session status, and student/teacher display information.
• Billing data: Stripe customer IDs, subscription IDs, price IDs, subscription status, cancellation timestamps, billing events, and limited invoice/payment metadata. Stripe collects and handles card details and billing addresses directly.
• Education enquiry data: institution name, contact name, work email, estimated seats, and message content submitted through the education pilot form.
• Analytics and telemetry: Vercel Analytics events, opt-in product telemetry stored in Supabase, AI and billing operational logs, error reports, device/browser metadata, IP-derived region data, URLs, referrers, and timestamps.
• Support and communications: messages you send us, email metadata, and records needed to respond.

We collect information when you create or access an account, use magic links or Google OAuth, save projects, use the AI assistant, join a class, submit assignments, manage billing, send an education enquiry, contact us, or browse the sites. Some technical data is collected automatically through cookies, local storage, analytics, logs, and error-monitoring tools.

• to authenticate users and maintain secure sessions;
• to provide simulator, cloud-save, project revision, Learn, classroom, assignment, AI, and billing features;
• to enforce plans, quotas, subscriptions, fraud controls, and acceptable-use rules;
• to provide support, respond to enquiries, send service messages, and manage education pilots;
• to debug, secure, monitor, and improve the service;
• to satisfy legal, tax, accounting, consumer, security, and dispute obligations; and
• to analyse aggregate product usage where permitted and, for de:volt's own product telemetry, where you have opted in.

de:volt uses cookies, local storage, and similar technologies for authentication, cross-subdomain sign-in, preferences, onboarding state, analytics, security, and billing redirects. See the Cookie Notice for details.

The simulator has a separate opt-in setting for de:volt product telemetry stored in Supabase. Vercel Analytics may still collect privacy-preserving site analytics for marketing, simulator, and Learn pages. Error monitoring may collect diagnostic information needed to investigate failures.

The AI assistant currently uses OpenRouter and a configured third-party model provider. AI requests send your prompt and a compact circuit snapshot that may include component kinds, IDs, pin nets, parameters, labels, and live simulation readings. Requests do not intentionally include payment card data or account passwords.

Do not submit confidential, export-controlled, regulated, student sensitive, or other sensitive information to the AI assistant unless you have authority and accept third-party AI processing.

de:volt Learn is intended to support classroom instruction. Student data may be visible to authorised teachers, school owners, and the student as needed for class membership, live classroom operation, assignments, marking, and progress tracking.

We do not sell student personal information. We do not use student personal information for targeted advertising. Where a school uses de:volt with children, the school is responsible for obtaining any parent, guardian, or school-official authorisation required by law and for sending de:volt any lawful access, correction, export, or deletion requests that the school wants us to action.

We disclose information only as needed to operate, support, secure, or legally protect de:volt. Current categories of recipients include:

• Supabase for authentication, database, row-level security, and account/project storage;
• Vercel for hosting and analytics;
• Stripe for checkout, billing, tax, invoices, payment processing, and the customer portal;
• OpenRouter and configured AI model providers for AI requests;
• Sentry for error monitoring and diagnostics;
• Resend and email systems for education pilot enquiries and service communications;
• Google where you choose Google OAuth sign-in;
• teachers, school owners, classmates, or invited users where Learn or sharing features require it;
• professional advisers, legal authorities, regulators, or dispute counterparties where required or reasonably necessary; and
• a successor organisation if de:volt is involved in a merger, acquisition, financing, restructuring, or sale of assets.

A current provider summary is available in the Subprocessors Notice.

de:volt is built and hosted with cloud providers that may process data in Australia, the United States, Europe, and other locations where our providers operate. By using de:volt, you understand that your information may be processed outside your country, subject to applicable transfer safeguards where required.

We keep information for as long as needed to provide the service, maintain backups, comply with law, resolve disputes, enforce terms, prevent abuse, and support billing or accounting records.

Account deletion removes the account and associated user-owned cloud data where the database is configured to cascade deletion. Some records may remain where required for security, tax, billing, legal compliance, backup integrity, or dispute handling. AI conversations that you clear in the product may be hidden from the panel but may remain in backend records unless your account or the relevant project is deleted.

Depending on your location, you may have rights to access, correct, delete, export, restrict, or object to certain processing of your personal information. You may also have rights to complain to a privacy regulator. California residents may have rights to know, delete, correct, and opt out of sale or sharing. de:volt does not sell personal information and does not share it for cross-context behavioural advertising as those terms are commonly used in California privacy law.

You can update profile preferences in settings, disable de:volt product telemetry in telemetry settings, manage billing in Stripe's portal, and request access, correction, export, or deletion by contacting dev@kapadia.biz.

We use technical and organisational safeguards including authentication, row-level security, service-role separation, validation, provider controls, and monitoring. No internet service is perfectly secure, so you should avoid storing unnecessary sensitive data in projects, prompts, lesson content, or support messages.

If you have a privacy concern, contact us first at dev@kapadia.biz so we can investigate. If you are not satisfied, you may have the right to complain to the relevant privacy regulator, such as the Office of the Australian Information Commissioner in Australia or a local data protection authority in your region.