This notice explains what personal data sparkle.space handles, why, who else sees it, how long we keep it, and what you can ask us to do.
Last updated .
Who is responsible
sparkle.space is operated by Eycarus AS, Norway, organisation number 989664174MVA. For privacy questions or requests, write to [email protected].
We play two roles:
For your account, sign-in, security and billing, we decide how the data is used. We are the controller.
For what a workspace puts into sparkle.space
(ideas, notes, documents, sources and what we collect for them), the organisation that owns the workspace decides. We process that content on its behalf. If a workspace holds personal data about you, ask that organisation first; we will help them answer. We offer organisations a data processing agreement on request.
What we collect
Your account
Your email address, which is how you sign in and how we reach you.
Your password, stored only as a one-way hash. If you use a passkey, its public key, a device name you choose and usage counters. If you sign in with Google, GitHub or your organisation's own sign-in, the identifier and email that service sends us.
The workspaces you belong to and your role in each.
When you accept the Customer terms for a workspace, we record which version you accepted and when.
Security records
For each sign-in session: your IP address, your browser's user agent and when the session started and ends. Sessions last up to 30 days.
For failed sign-in attempts: the email typed, the IP address and the user agent.
What your workspace puts in
Ideas, notes, evaluations, Vault entries, Blueprints, scratchpad items, pitch decks, and the images and files your team uploads.
Sources your workspace registers, and what our collector gathers from them. This can include public posts and their authors' public names and handles, for example from X.
People outside a workspace
If someone invites you, your email address and who invited you.
If someone shares a pitch deck with you: your email and any note they add. When you open the deck, we record your IP address, your user agent and which sections you viewed, and show those views to the workspace that shared it. If you accept an NDA to view it, your email, IP address, user agent and the NDA text you accepted.
Payments
Payments run through Stripe. Stripe's checkout page collects the payer's email and card details; we never see the card. We keep the Stripe customer and subscription identifiers so we can show the workspace's plan.
Agents and integrations
If your workspace connects an AI agent, we store a hash of its key (never the key itself), its name, and who created or revoked it.
If your workspace sends events to its own systems, we store the endpoint address and a log of each delivery.
We use no third-party analytics, advertising or tracking tools, and we do not sell personal data. The only viewing analytics are the pitch-deck views described above.
Why we use it
Purpose
Legal basis
Run your account and the workspaces you belong to
Our agreement with your organisation, and with you as its user
Our legitimate interest in protecting accounts and the service
Send the emails the product needs: invitations, verification, password resets, security notices, notifications you turned on
Our agreement; legitimate interest for security notices
Record which version of the Customer terms you accepted
Our agreement, and our legitimate interest in being able to show it
Take payment and keep billing records
Our agreement; legal obligations for accounting records
Process workspace content
On behalf of the workspace's organisation
Who else handles it
We use these services to run sparkle.space. Each receives only what its job needs.
Service
What it does
Where
Stripe Payments Europe, Ltd.
Takes payments and runs the customer portal
Ireland; Stripe may transfer data to Stripe in the United States
Amazon Web Services (SES)
Sends our email
Ireland (eu-west-1)
Scaleway SAS (France)
Turns text into embeddings for search and for suggesting related content: Vault entries and their titles, search queries (typed in the Vault or sent by a connected agent), and the text of an idea in the Forge (its title, description, vision and refinement notes). Scaleway keeps none of this text, except that a request which fails with an error or looks like abuse may be kept for up to two weeks so the fault can be investigated. Scaleway does not use the text to train or improve models, and does not share it with the model's makers.
Europe: currently Paris, France. Scaleway notifies us if it moves this to another European location.
X Corp.
Supplies the public posts your workspace follows; post avatars load from X's image servers
United States
Cloudflare, Inc.
Carries all traffic between your browser and our servers
United States and Cloudflare's global network
Backblaze, Inc.
Stores encrypted offsite backup copies
EU Central: Amsterdam, the Netherlands
Our hosting and backups
sparkle.space runs on servers we operate in Norway; encrypted backup copies are also kept on our own storage in Norway
Norway
If you sign in with Google, GitHub or your organisation's own identity provider, that sign-in is between you and that provider.
When data goes to the United States (Stripe, X and Cloudflare), the transfer relies on the EU–US Data Privacy Framework, with the EU Standard Contractual Clauses as a fallback. Scaleway, Backblaze (EU Central) and our own servers are in Europe, so they need no transfer safeguard.
How long we keep it
Data
How long
Your account
While it exists. Erasure is described below.
Customer terms acceptances
While your account exists
Session records
The session lasts up to 30 days; the record is kept while the account exists
Failed sign-in records
For an address with no account: the IP address and user agent are erased after 30 days, and the typed email is removed from the records we use; that email stays in the history (next row). For an existing account: kept while the account exists.
The product's history
Permanent. It is append-only and holds email addresses in plain text (see "Your rights"). Other personal details in it are encrypted and become unreadable when the person is erased or the 30-day period above ends.
Rate-limit counters
24 hours
Pitch shares
While the workspace exists. A share's expiry ends access to the deck; it does not delete the record.
Workspace content
While the workspace exists, including after it is archived
X posts
Until X or the author withdraws them; we check again at 7, 14, 21 and 28 days and delete withdrawn posts
Backups
Up to about 30 days for database backups; longer for backups of uploaded files (up to about 7 weeks) and if a backup run stalls
Server logs
Up to 30 days. They can include IP addresses.
Billing records
As long as Norwegian accounting law requires
Your rights
You can ask us to:
tell you what personal data we hold about you and give you a copy;
correct it;
erase it;
restrict or object to how we use it.
Write to [email protected]. We answer within one month. For workspace content, we work with the organisation that owns the workspace.
What erasing your account does.
We revoke your sessions and agent keys, delete your password hash, and remove your email, IP addresses and device details from the records we use. Some of these details are encrypted with a key unique to you, and erasure destroys that key, so the encrypted copies can no longer be read. Some things remain:
sparkle.space keeps a permanent, append-only history of what happened in the product. Email addresses in that history are stored in plain text: yours as an account holder, and any address used for an invitation, a pitch share, an NDA or a failed sign-in. Erasing your account does not remove them from the history. Account history is not shown anywhere in the product, and only our operators can read it. Other screens do show email addresses to members of the same workspace: current members, open invitations, Vault approvers and pitch-share recipients. Erasing an account blanks those, except in pitch-share records.
A random identifier for your account, and the record that it belonged to a workspace, with no name or email attached.
Content you wrote in a workspace belongs to that workspace and stays there.
Backups that hold your data are destroyed within about 30 days, longer for uploaded files and if a backup run stalls. If we ever restore one, we apply your erasure again before the service is back in use.
You can also complain to Datatilsynet, the Norwegian Data Protection Authority.
Cookies and browser storage
sparkle.space uses one cookie and two browser-storage entries. All are first-party, and none tracks you.
Name
Type
Why
_sparklespace_key
Cookie, ends when you close the browser
Keeps you signed in and protects forms
phx:theme
Browser storage
Remembers light or dark mode
sds:nav-collapsed
Browser storage
Remembers whether the sidebar is collapsed
Because these are needed for the product to work or only remember your own settings, we do not ask for cookie consent.
Changes
When we change this notice in a way that matters, we update the date at the top and email workspace owners.