Privacy Policy

Last updated: 4 October 2026

This policy explains what Siliqun Rotor collects, where it goes, and what you can ask us to do with it. Siliqun Rotor is operated by an individual trading as Siliqun Rotor. Questions go to owner@sqrplatform.com.

The short version

• If you run the engine on your own machine, your requests never reach us. You need no account.
• If you use the hosted platform, we keep what we need to run it for you, and nothing more.
• We never sell your data, and we never use it to train Siliqun Rotor's shared models or anyone else's.
• Card details go to Paddle, never to us.

Where your requests are decided

• In your browser or on your machine: the first tier of an exported agent runs locally (for example as a WebAssembly module in the browser). Those decisions stay where they run.
• On the hosted engine: when your project calls the hosted engine, the request is decided on a server we control. Your data there is kept to your workspace; another customer cannot read it.
• Your own model provider (optional): if you connect one, it receives only what your project's configuration sends it, under that provider's own privacy terms.

What we collect

• Account: your email address and sign-in details. You can sign in with email and password, or with Google or LinkedIn; if you choose one of those, it confirms your identity and email address to us. LinkedIn shares your name and email address with us.
• Workspace content: your projects, declarations, cues, flows, documents and settings, so the Studio and the hosted engine can use them.
• Usage: a count of hosted decisions per project, so we can apply your plan's limits. If you use your own model provider, we also record which provider and model answered and the token counts it reported, shown to you separately as third-party usage.
• History: runs, traces and feedback from hosted use, so you can read and correct them. Each plan states how long this history is available.
• Your model provider's key, if you add one: stored encrypted for that project only, never shown again, and never written to replies, traces or logs.
• Waiting list: your email address, and the name, organisation and intended use you give, when you request a place.
• Billing: for card plans, Paddle's subscription, customer and transaction identifiers, your plan and its status. For an invoice request, the billing email, company name and note you enter.

What we do not collect

• No card numbers. Paddle handles them.
• No advertising or analytics trackers on the Studio or the site.
• No model provider calls on our account. Your provider bills you, not us.

Browser storage

The Studio keeps your sign-in session, a few preferences (such as the theme and the last project you opened) and, if you enter one, the key for connecting to your engine in your browser's local storage. They stay on your device. The site's pages load fonts from Google Fonts.

Who else handles your data

We share nothing with anyone else unless the law requires it.

Ownership and training

You own your declarations, cues, flows and the bundles you export. They export with your bundle on every plan. What you teach your project improves your project only. Siliqun Rotor's own models are trained on public datasets and data we make ourselves, never on customer data.

Your choices

• Export: your bundles and cues export from the Studio at any time.
• Access, correction or deletion: email owner@sqrplatform.com and we will act on it. We answer within two working days.
• Remove your provider key: from the project's settings in the Studio, at any time.
• Close your account: by email. We delete your workspace content, except billing records the law requires us to keep.

Security

API keys are stored only as hashes, and your model provider's key is stored encrypted. Keys are never written to replies, traces or logs. No system is perfectly secure; if we learn of a breach that affects your data, we will tell you.

Changes

We will update the date at the top when this policy changes, and email your workspace's owners about any change that affects how your data is used.