Privacy notice
Who we are
The service is operated by 9000 AB, Sweden, which is the data controller for the personal data below. Questions and requests go to support@hyperspool.com.
What we hold
- Your account. Email address, display name, and the identifier your sign-in provider gives us: our own identity service today, and an external provider such as GitHub if and when that sign-in is offered. Sign-in sessions and any personal access tokens you mint.
- What your org produces. Workflow definitions, runs, their logs and artifacts, events, schedules, and the members of the org. Logs contain whatever your jobs print, so they may contain personal data you put there.
- Secrets and credentials you store for your workflows. They are encrypted at rest, the console and support tooling never show them, and they are opened only to hand them to your own jobs. The people who operate the service could technically reach them and do not.
- Billing. Your plan and usage. When you pay by card, payment details are held by our payments provider, which sells the subscription as merchant of record; we never see a card number.
- Technical. Request logs at our edge with IP address, path and user agent, and server logs with user and org identifiers.
- What you tell us. Feedback sent from the console or the CLI, with your email, the org and project you were in, and the page you were on. Invite requests sent from this site, with the name, email address, company and description you typed.
Why
To run the service you signed up for (performance of a contract), to keep it secure and abuse-free and to bill for it (our legitimate interests, and legal obligations for accounting), and to answer you when you write to us. We do not sell or share personal data for advertising, and there is no third-party analytics on the console.
Where, and who else
The service and the data it holds, backups included, are hosted in the European Union. The console and this site serve their fonts, scripts and styles themselves, so opening a page loads nothing from a third party.
Other companies process personal data for us, each for its own part:
- infrastructure and backup providers in the EU, which run the service and hold its data;
- a transactional email service in the EU, which delivers invitations, sign-in and account mail;
- a DNS provider in the EU, which answers lookups of our hostnames;
- a mail provider in Switzerland, which stores mail sent to our support, security and abuse addresses;
- a payments provider acting as merchant of record, which takes card payment for self-serve plans and handles sales tax;
- a model provider in the EU, which runs the model behind the copilot for orgs that use it.
Our payments provider and the card processor behind it are based in the United States, so when you pay for a self-serve plan by card, your payment details are transferred there. That is the only transfer outside the EU, the EEA and countries with an EU adequacy decision, such as Switzerland. Customers on invoiced plans are not processed by either. The subprocessors page names each company, what it does for us and where. We announce a new one there and by email before it starts.
When you connect a forge such as GitHub or another account, or a workflow calls a service with your own credentials, a model provider included, that service receives what you authorise or what the workflow sends it, under your own agreement with it.
For how long
- Runs, logs and artifacts: the retention window of your org's plan, shown on its usage page; older ones are pruned automatically.
- Edge request logs: thirty days.
- Account data and memberships: until you delete your account or leave the org.
- Backups: a rolling thirty days, after which deleted data is gone from them too.
- Billing records: as long as accounting law requires.
Your rights
You can have your personal data corrected, object to processing based
on our legitimate interests, and take it with you. Most of this you do
yourself in the console: Settings, Account downloads what we hold about
you and deletes your account. Under Settings, Data an org's admins
export the org and its owner deletes it, or with
spool org export and spool org delete. Deleting an org removes its runs, logs,
artifacts, secrets and members. Deleting your account removes your
sign-in, memberships, access tokens, the accounts you connected, your
chat links, your copilot conversations and what you wrote in an invite
request; runs
you started belong to their org and stay until its retention window
ends. For anything else, ask support and we answer within a month. You
may also complain to the Swedish Authority for Privacy Protection (IMY)
or the supervisory authority where you live.
Cookies
The console sets a session cookie, plus two short-lived ones that exist only while a sign-in or an account connection is in flight; the sign-in service sets its own session cookie. There are no tracking cookies.
Changes
When this notice changes materially we tell you by email before it applies. The date at the top says when it last did.