Privacy notice

Last updated: 4 October 2026

This notice explains how personal information is handled when you visit the Bloctric website, use its browser or desktop application, use online code generation, manage an account or subscription, or contact us. Bloctric is operated from Scotland. Its operator is responsible for the personal information described here as a data controller. Contact [email protected] about privacy or your information rights.

You can use Free features without an account. Accounts connect subscriptions, licensed devices, and authorised downloads. Cloud subscriptions and hosted project storage remain planned services.

What stays on your device

The browser application saves projects and recordings in your browser storage. This can include model contents, project names, version numbers, timestamps, and recorded signals. Preferences such as your chosen theme and saved application settings also stay in browser storage. The application caches software and compiled assets to support performance and offline use.

Browser simulations run on your device. Local storage is not a cloud backup. Data may remain until you delete it, the application replaces it, or your browser or device clears it. Clearing Bloctric site data can remove saved work, settings, and cached assets. Export anything you need to retain first.

Accounts, payments, and licensed devices

We use Clerk to manage accounts, sign-ins, and browser sessions. Clerk processes your sign-in information, including your email address and authentication details. Bloctric uses your account identifier to connect your subscriptions and licensed devices.

Paddle handles checkout, payments, invoices, and subscription billing. We receive payment and subscription notifications and retain the identifiers, statuses, plan details, and paid-access dates needed to provide your subscription. Bloctric’s account database does not store full payment-card details.

When you activate a desktop installation, we record its name, a generated device identifier, and activation and licence-refresh information. The desktop app stores its licence and renewal credential in your operating system’s credential store. Browser sign-ins do not create licensed-device records.

What online code generation receives

When a feature uses server code generation, the application sends the model information and dependencies needed for that operation to our code-generation service. Depending on the feature, this can include model structure, block names and parameters, configuration, workspace information, Raw C source, and required C or header files.

This can happen when preparing compiled simulations, checking Raw C, preparing CPU What-if operations, or exporting generated code. It is not limited to clicking an export button. The application does not include saved recordings or unrelated non-C files in these generation uploads.

The generation application processes the request and returns the result. It does not maintain a server-side library of uploaded models. Hosting and security systems also process technical request information as explained below; local execution does not mean that visiting the service creates no technical records.

Avoid putting unnecessary personal data or sensitive information in model names, source code, or files sent online. We use submitted content to provide the requested operation, not to advertise to you or train AI models. If your organisation needs us to process other people’s personal data in model contents on its behalf, contact us first so that suitable data-processing arrangements can be agreed.

Other information we receive

Our hosting and security provider, Cloudflare, processes information about connections to the website and online services. This can include IP addresses, request times and URLs, browser and device information, response status, errors, and security signals. The code-generation service uses IP addresses to apply request limits and protect availability.

If you email us, we receive your email address, the contents of your message, and any name, attachments, or other information you choose to supply. Our email provider processes that correspondence to deliver and store it. Only send information needed for your enquiry. Do not send passwords, full payment-card details, or unnecessary sensitive records.

We receive information directly from your device and messages, account information from Clerk, payment and subscription notifications from Paddle, and technical information from our hosting and security providers. If you authorise a third-party assistant, browser extension, or other tool to access Bloctric, that provider may receive information under its own privacy arrangements.

Why we use information and our lawful bases

• Providing requested features, accounts, and subscriptions: we process information needed to perform our agreement with you or take steps you request before entering an agreement. This includes sign-in, subscription access, device activation, and authorised downloads. For people using the service on behalf of an organisation, we rely on our legitimate interest in providing the service to that organisation where appropriate.
• Security, abuse prevention, and fault diagnosis: we rely on our legitimate interests in keeping the service available, protecting users, and resolving technical problems. This includes proportionate rate limits and technical diagnostics.
• Answering enquiries: we rely on steps requested before entering a contract, performance of a contract, or our legitimate interest in responding to other correspondence, according to the enquiry.
• Legal obligations: we process information where necessary to comply with a specific applicable legal duty, such as responding to a valid exercise of data protection rights.
• Handling disputes: we rely on our legitimate interest in establishing, exercising, or defending legal claims, subject to applicable safeguards.

We consider whether our legitimate interests are outweighed by your rights and interests. Information necessary to connect to the service or provide a requested operation is required for that function to work. You can choose not to send a support message or use an online feature, but we may then be unable to answer or complete that request.

We do not treat use of the website or acceptance of the Terms of service as consent to optional processing. If we introduce a purpose that requires consent, we will ask separately and explain how to withdraw it.

Cookies and similar storage

Bloctric uses browser storage for saved work, application settings, your theme preference, and offline or compiled assets. These technologies include local storage, IndexedDB, and browser caches, as well as any security cookies used by our hosting provider. They can store information without using traditional cookies.

Clerk uses cookies and related storage to manage sign-in and sessions. Paddle’s checkout uses storage to provide checkout and payment functions. An authorised desktop download sets a download cookie that expires after 10 minutes. Cloudflare may use security cookies to protect the service. The providers’ notices linked below describe their processing.

We use storage needed for functions you request and explain any other permitted use. Where consent is legally required, optional storage or access will not be enabled until you give it. We will explain the purpose and available controls before introducing additional tracking.

You can change your theme in the website or application and remove stored data through your browser’s site-data controls. Blocking storage can prevent saving projects, signing in, completing checkout, downloading a release, or using some offline features. Your browser’s settings may also let you control cookies separately. These controls do not delete your account, cancel a subscription, or erase information held by Bloctric or its providers.

Who receives information

We use Cloudflare to host and protect the website, provide online code generation, store account and subscription records, and deliver desktop downloads. We use Clerk for authentication and Paddle for checkout and billing. An email service provider handles correspondence. Providers receive information needed for their functions and are subject to appropriate contractual and security arrangements where they act on our behalf.

Paddle acts as the seller and merchant of record and handles purchase information under its own privacy notice. Clerk processes account and authentication information on our behalf under its data-processing agreement; its privacy notice explains its own processing. Cloudflare may also process certain information for its own security and service purposes, as described in its privacy policy.

We may share relevant information with professional advisers for a specific legal or business need, or with authorities where required by law. If the business is transferred, personal information may be transferred where lawful and necessary, with appropriate confidentiality safeguards and notice of any change of controller. We do not sell personal information.

International processing

Cloudflare, Clerk, and Paddle operate internationally, so information may be processed outside the UK, including in the United States. Processing locations depend on the provider and service.

Where we make a restricted international transfer, we must have a permitted basis for it, such as applicable UK adequacy regulations or approved contractual safeguards. Cloudflare’s and Clerk’s customer data-processing terms include provisions for UK transfers, including the UK Addendum to the standard contractual clauses where applicable. Paddle describes its international processing and safeguards in its privacy notice. You can contact us for information about the safeguards relevant to your data and how to obtain a copy, subject to necessary redactions.

How long information is kept

• Data on your device: saved projects, recordings, settings, and caches remain according to your actions, application storage management, and browser retention or eviction rules.
• Code-generation content: the generation application processes it for the requested operation and does not save it as a hosted project. Separate technical records are covered below.
• Account and billing records: we keep information needed to provide your account and paid access, reconcile payments, handle refunds and disputes, and meet applicable legal obligations. Retention depends on whether the account or subscription remains active, whether a payment or dispute remains unresolved, and any applicable legal retention duty. Account deletion does not automatically erase these records.
• Temporary authorisation records: desktop sign-in approvals expire after five minutes, and download permissions expire after 10 minutes. Expired records are removed during service maintenance. Revoked device records become eligible for removal after 90 days; expiry or revocation does not mean the stored record is removed immediately.
• Technical and security records: retention is limited to what is needed to operate the service, identify faults, and investigate or prevent abuse. Relevant records may be kept longer where a specific security incident, dispute, or legal requirement needs them. The criteria are the nature and age of the incident, whether an investigation remains open, and any applicable legal retention duty.
• Support correspondence: we keep it while dealing with your request and afterwards only where needed for related support, an unresolved dispute, or legal claims. We consider the subject of the request, whether it remains relevant, and applicable legal time limits, and remove information that is no longer needed.

Deleting your Bloctric account disables access through that account and revokes its licensed devices. It does not automatically cancel a Paddle subscription or erase payment records. Cancel renewal through Account → Plan and billing → Manage billing before deleting your account, or contact [email protected] if you can no longer sign in. A device that is offline may retain paid features until its saved licence expires.

We limit access to information that still needs to be kept. A request for erasure will be assessed against these purposes and any legal obligation to retain information. Deletion of local browser data does not automatically send us an erasure request. Clerk and Paddle also retain information according to their own roles and policies.

Your rights

Subject to the conditions and exceptions in data protection law, you can ask to access your personal information, correct inaccurate information, erase information, restrict its use, or receive qualifying information in a portable format. If we rely on consent, you may withdraw it at any time without affecting the lawfulness of earlier processing.

You have the right to object to processing based on legitimate interests because of your particular circumstances. We must then stop that processing unless we can demonstrate overriding legitimate grounds or need it for legal claims. You have an unconditional right to object to use of your personal information for direct marketing.

Email [email protected] to exercise a right. We may ask for proportionate information to confirm your identity. We normally respond within one month, subject to lawful extensions or pauses; we will explain any applicable delay. Requests are normally free of charge.

We do not use your information to make solely automated decisions with legal or similarly significant effects on you. Technical request limits help protect the service; contact us if you believe a limit has been applied incorrectly.

Privacy complaints

You can raise a privacy complaint by emailing [email protected]. We will acknowledge it within 30 days, investigate appropriately, keep you informed as needed, and communicate the outcome without undue delay.

You also have the right to complain to the Information Commissioner’s Office or call 0303 123 1113. You do not have to give up that right to contact us first.

Changes to this notice

We will date updated notices and explain material changes through the website or another suitable channel before starting a materially different use of your information. Where new consent is required, changing this notice will not replace obtaining that consent.