Privacy policy
Last updated
The short version
The Hypercolor engine runs on your computer and works without an account. It sends us nothing unless you sign in to Hypercolor+. When you do, we keep what the service needs to work: your account, the installations you sign in on, the settings you sync, and records of Remote sessions and billing. We don't sell your data and we don't use it for advertising.
Hyperbliss Technologies runs Hypercolor+ and this website. Questions go to support@hypercolor.lighting.
What stays on your computer
Your devices, effects, media, layouts and everything the engine renders stay on your computer. Signing in doesn't upload them. Remote connects your browser to your installation directly whenever the network allows it, and Remote traffic is encrypted end to end between the two, so we can't read it even when it passes through a relay.
Two other services see your computer whether or not you have an account: the engine checks GitHub for new Hypercolor releases, and the Hypercolor app loads its fonts from Bunny Fonts. Both see your IP address, and GitHub also sees the Hypercolor version you run. Neither sends anything to us.
What we collect and why
- Your account. Email address, name and profile picture. If you sign in with Google, GitHub or Discord, we receive those from that provider, along with your account id there and the sign-in tokens it issues, which we store encrypted. A password is stored only as a one-way hash. A passkey is stored as its public key, its credential id and details about the authenticator. Each sign-in session records the IP address and browser it came from, so you can see and end your sessions and so we can protect your account.
- Your installations. For each installation you sign in on: the name it reports, its operating system, processor type and Hypercolor version, the public half of its identity key, and whether it is online and when it was last seen. This is how your account lists your installations and how Remote finds them.
- Settings you sync. Preferences, favorites, and your devices' names, slots, makers and models, so your installations stay in step. The service can also hold scenes, layouts, profiles and your list of installed effects; Hypercolor doesn't send those yet. When two installations change the same thing, both versions are kept so you can choose.
- Remote. When a session started and ended, which installation it reached, how much data it used, and short-lived credentials for Cloudflare's relays. Never the contents of the session.
- Effect covers. Preview images of effects you installed yourself, kept for your account so Remote can show them. Covers of the effects that ship with Hypercolor come from our servers and are the same for everyone.
- Billing. Your plan, your subscription's status, the identifiers Stripe gives your customer record and subscription, and the notices Stripe sends us about them, which can include your name, email and billing address. Stripe handles your card; we never see card numbers.
- Early access requests. What you entered in the form: your email address, the hardware you use, the lighting apps you used before, your notes and where you heard about Hypercolor. We also keep the IP address and browser it came from, to keep the queue free of abuse.
- Security records. Sign-ins, installation approvals and changes to your account, with the IP address involved, so we can investigate misuse and answer your questions about your account.
- Email. We only send email about your account: address verification and password resets, early access invitations, security notices, changes to your plan, and the confirmation when you delete your account.
Website analytics
The home page, early access, downloads and release notes can measure visits with Google Analytics, and only after you choose Allow. Until then nothing loads and nothing is stored. If you allow it, Google receives the pages you view and the links you click there, with a random identifier kept in your browser. It never receives your account, and there are no analytics in your account pages, the portal or Remote. You can change your answer here at any time.
Who processes data for us
- Cloudflare hosts this website and the Hypercolor+ service, carries Remote signaling and its relays, stores files, and keeps request logs.
- Neon hosts our database, in the United States (AWS, Oregon).
- Stripe takes payments and manages subscriptions.
- Google Workspace delivers our email.
- Google provides Analytics, only with your consent, and Google sign-in if you use it.
- GitHub and Discord provide sign-in if you use them. GitHub also hosts Hypercolor's releases, which the engine checks for updates.
- Bunny Fonts serves the fonts the Hypercolor app uses.
Each of them processes data under its own terms and only for the job we use it for. Because our database and several of these services are in the United States, your data is processed there.
Cookies and browser storage
Cookies on this site:
- A sign-in cookie keeps you signed in. It is required for your account to work.
- Short-lived cookies carry a sign-in with Google, GitHub or Discord, an early access invitation while you create your account, and access to the status page after you delete your account.
- A theme cookie remembers whether you chose the light or dark look.
Browser storage:
- On this website: your answer about analytics, and if you allowed analytics, its random identifier.
- In the portal: your progress through setting up an installation.
- In the Hypercolor app: an unfinished sign-in, so it can resume, and your display preferences, filters and layout.
- In Remote: the identity of each installation you chose to trust, a cache of effect covers, and what Remote needs to reload a session.
None of these are used for advertising.
How long we keep it
Your account data stays until you delete your account. Sign-in sessions end after 90 days without use. The history of sync changes is cleared after 30 days once every installation has caught up with it, and versions that conflicted stay until your account is deleted. Remote and security records are kept while they are needed to run and protect the service. Cloudflare and Stripe keep their own records for the periods their terms set out.
Deleting your account
You can delete your account from Account in the portal. Deletion removes your account, your installations, your synced settings, your effect covers and your Remote records, cancels your subscription with Stripe, and signs out every installation. Some records stay, to show the deletion happened, to finish cancelling with Stripe, and to answer questions about it later:
- A deletion record: your email address, your account id, the time and IP address of the request, and a summary of what was removed.
- The Stripe customer, subscription and checkout identifiers needed to finish cancelling.
- Security records and Stripe's notices about your account, with your IP address and contact details removed.
Stripe keeps payment records as the law requires.
Your rights
You can ask us for a copy of your data, to correct it, or to delete it, by writing to support@hypercolor.lighting. If the GDPR or UK GDPR applies to you, we rely on our contract with you to run your account and Hypercolor+, on our legitimate interest to keep the service secure, and on your consent for analytics. You can withdraw consent at any time and complain to your data protection authority.
Children
Hypercolor+ is not meant for children under 13, and we don't knowingly collect their data.
Voice assistants
Hypercolor+ doesn't work with Alexa, Google Home or other assistants yet. When it does, this policy will say what they receive before you can turn them on.
Changes
When this policy changes, the date at the top changes too. If a change affects how we use data you already gave us, we'll tell you by email first. The terms of service cover your use of Hypercolor+.