Privacy.
This page says what happens to your data when you visit sealcord.com, when you leave your email address to hear when Sealcord opens, and when you sign in to the Sealcord Console: as a developer, as someone invited to a team, or to see licences you bought. It also says what happens when an organization pays for its Sealcord plan.
On this page 18 parts
- Who is responsible
- Visiting the website
- The launch list
- Where the list is kept
- How long the list is kept
- The Sealcord Console
- Developer accounts
- Paying for a plan
- Invitations
- Seeing your licences
- Sign-in limits
- Where the counters are kept
- Cookies
- Where Console data is kept
- How long Console data is kept
- If you write to us
- Your rights
- Your right to object
Who is responsible
Sealcord, reachable at hello@sealcord.com. See also the legal notice.
One exception: for the licences a software maker issues through Sealcord, and the machines they are used on, that maker is responsible, and Sealcord keeps the data for them (below).
Visiting the website
The website, and Sealcord’s API that receives the form, are delivered by bunny.net (BunnyWay d.o.o., Ljubljana, Slovenia), a content delivery network that processes data for Sealcord as its processor. Sealcord’s API runs on bunny.net servers in Germany; the counters described below are kept by Upstash (below). To answer your browser, bunny.net processes your network (IP) address, the page you ask for, the page you came from, your browser’s user agent, the time, and technical details of the connection, such as your country and network. bunny.net keeps these request logs for 3 days. Sealcord has turned on bunny.net’s log anonymisation for the website’s and the API’s logs.
Legal basis: Article 6(1)(f) GDPR. Our legitimate interest is delivering the website securely.
The website sets no cookies and runs no analytics or third-party scripts; its fonts come from sealcord.com itself. While you use the form, your browser keeps the address you typed for that tab only, so the form can show it again if it was not accepted. It stays in your browser and goes when you close the tab.
Sealcord’s emails show one image, the Sealcord logo, which your email app loads from sealcord.com. It is the same file for everyone and carries nothing that identifies you or the email. If your email app loads it, bunny.net processes and keeps the same details as for a visit, as above. Sealcord does not use them to tell whether or when you opened an email. Your email app may load images through its own servers, or let you turn them off; the emails work without them.
Legal basis: Article 6(1)(f) GDPR. Our legitimate interest is showing who an email is from.
The launch list
What: only the email address you type into the form.
Why: to send you an email when Sealcord opens, and news about the launch. Nothing else. The address is not sold, and nobody receives it except the service providers named on this page.
Legal basis: your consent (Article 6(1)(a) GDPR), which you give by sending the form. You join the list when you send the form; there is no separate confirmation email.
You do not have to give your address, and nothing else depends on it. Without it, we cannot tell you when Sealcord opens.
With your address, the list keeps a record of your consent: that you joined through the form on sealcord.com, when, and which version of the form’s wording and of this page you saw. Legal basis: Article 6(1)(c) GDPR, as Sealcord must be able to show that you agreed (Article 7(1) GDPR).
To stop the form being abused, Sealcord’s API counts sign-ups from your network address for 15 minutes, and from your email address for a day. Those counters hold your network address and a one-way code made from your email address, never the address itself, and they expire on their own. Like every request to the API, sending the form is also counted for one minute, under a code computed from your network address. Legal basis: Article 6(1)(f) GDPR. Our legitimate interest is keeping the list free of bulk and fake sign-ups.
Where the list is kept
With Resend (Plus Five Five, Inc., United States), the email service Sealcord uses. It keeps the list and sends the emails for Sealcord, as its processor under a data processing agreement. Resend stores the data in the United States and uses service providers of its own (resend.com/legal/subprocessors). Sealcord’s own servers keep no copy of your address.
Resend takes part in the EU–U.S. Data Privacy Framework (an adequacy decision under Article 45 GDPR), and our agreement with Resend includes the European Commission’s Standard Contractual Clauses (Article 46(2)(c) GDPR). To get a copy of the clauses, write to hello@sealcord.com.
How long the list is kept
Your address stays on the list until you unsubscribe or ask for it to be deleted, and at the latest until 12 months after Sealcord opens, when the whole list is deleted. If Sealcord does not open, the list is deleted when that is decided. The record of your consent goes with your address.
If you unsubscribe, your address stays on the list marked as unsubscribed, only so that no more emails go to it (Article 6(1)(f) GDPR), until you ask for it to be deleted or the list is deleted. Resend keeps a record of each email sent to you for 30 days.
The Sealcord Console
The Console, console.sealcord.com, is where developers manage the software they license with Sealcord, and where people who bought such software see their licences. Like the website, it is delivered by bunny.net, and it runs on bunny.net servers in Germany, next to Sealcord’s API and the MCP server that AI assistants connect to (mcp.sealcord.com). bunny.net processes the same details of each request as for the website (above) and keeps its request logs for 3 days. Sealcord has turned on bunny.net’s log anonymisation for the Console’s logs too. Legal basis: Article 6(1)(f) GDPR. Our legitimate interest is delivering the Console securely.
The logs Sealcord’s own servers write name people, organizations and licences by internal ids, and email addresses only by a one-way code; never by email address or network address. bunny.net keeps them for up to 5 days.
Developer accounts
What Sealcord keeps about you when you have a developer account:
- your email address, and a name only if Sealcord entered one when it created your account;
- the organizations you belong to, and your role in each;
- your passkeys: each one’s public key (which cannot sign in as you), the name you gave it, and the kind of device or password manager that holds it;
- if you link a GitHub account, its numeric GitHub id. When you link it and each time you sign in with it, GitHub sends Sealcord your public GitHub profile and your account’s email addresses; Sealcord uses them to check that the primary one is verified, and keeps only the numeric id, never the addresses, the profile or GitHub’s tokens;
- your sessions: when and how you signed in, when you last used the Console, and the network address and browser (user agent) you signed in from. Settings lists them, so you can spot one you do not know and sign it out;
- a record of what you did (the audit trail): sign-ins and sign-outs, passkeys and GitHub accounts added or removed, and changes to your organization, its members, products, licences, keys and integrations, each with your account’s id and the time, never your address. For a licence, the record also holds what the change concerned: a machine’s name, operating system and app version, a reason you gave, or your reference for the sale;
- AI assistants you allow to act for you: which assistant, for which organization and with which permissions, and its tokens, kept only as one-way codes;
- while a sign-up waits for you to confirm it: your address, the name and short name (slug) you chose for the organization and, if you answered it, how you heard about Sealcord (one answer from a list), for the 10 minutes the emailed link works; that answer then stays in the organization’s audit trail;
- each sign-in link or code Sealcord prepares: the link or code only as a one-way code, with the email address it was asked for, for the 10 minutes it works (below).
- which notification emails you chose for each organization, and each one queued for you: which organization and notification it is, the counts or ids it reports, and when it was sent, kept for 30 days after that. Never your address: it is read when the email goes.
Why: to give you your account and the service you signed up for, and to email you about it: sign-in links, a notice when a GitHub account is linked, for an organization’s owners its plan usage (below), and the notifications you leave on: alerts when a payment from Polar could not become a licence or a product cannot sign licences (on by default for owners and admins), and a weekly summary of the organization’s licence counts (off until you turn it on). Legal basis: Article 6(1)(b) GDPR. The network address and browser of each session, the audit trail and the sign-in limits (below) protect your account and your organization against misuse, and let us trace it. Legal basis: Article 6(1)(f) GDPR; that is our legitimate interest, and yours.
You need an email address to have an account. Passkeys, GitHub and AI assistants are your choice. The other members of your organization see your email address and role, and its audit trail. Your sign-ins, sign-outs and switches show in it only when they were made in that organization: never those in your other organizations, nor those as someone seeing their licences. Passkeys and GitHub accounts you add or remove show in the audit trail of each organization you belong to.
What you put into Sealcord, such as licences with your customers’ email addresses and the machines they activate, is your data about your customers: you are responsible for it, and Sealcord processes it for you.
Paying for a plan
An organization’s owners can choose a paid Sealcord plan for it in the Console. The plans are sold by Polar (Polar Software, Inc., United States) as merchant of record: you buy the plan from Polar, under Polar’s buyer terms, and Polar charges you, collects any tax and sends your receipts and invoices. The checkout, and the customer portal where you change or cancel the plan, update your payment method and see your invoices, are Polar’s pages.
What you enter there, such as your name, email address, billing address, tax number and payment details, you give to Polar, which uses it under its ownprivacy policy. Polar’s documents do not describe its role the same way: its privacy policy calls Polar the controller of the personal data processed in connection with its services (and, in another place, a processor of what it processes to provide them); the data processing addendum in Polar’s terms with Sealcord says Polar processes personal data as Sealcord’s processor; and thoseterms themselves say that, under U.S. state privacy laws, Polar and Sealcord each act independently for what each collects, not as processor for the other. Card payments are processed for Polar by Stripe (Stripe, Inc., United States, and Stripe Payments Europe, Ltd, Ireland), which collects your card details; Polar keeps the card’s type and last four digits, never its full number. Polar uses service providers of its own (polar.sh/legal/sub-processors). About what Polar holds, you can write to Polar at privacy@polar.sh, or to us.
What Sealcord sends Polar: to open a checkout, the plan chosen and the organization’s id, which is how Polar tells which organization it bills, and the Console’s address to come back to; to open the customer portal, the organization’s id; to cancel the plan when the organization is deleted, Polar’s id for its subscription. Never your name or email address. On monthly Business only, when the organization has more than 25,000 active licences, Sealcord’s API also reports to Polar, once a day, the organization’s id, the day, the highest number of active licences counted and the thousands above the limit, so Polar can bill the overage.
What Polar sends back: a message each time the plan’s subscription changes. It holds the customer’s details as Polar has them, such as the name, email address and billing address; Sealcord reads only the ids, the plan, the state and the dates in it, and stores none of the rest. For the organization, Sealcord keeps:
- its plan and billing interval;
- the subscription’s state (active, payment overdue or ended), when it started, when the paid period ends and whether the plan ends then, and Polar’s ids for the customer and the subscription;
- the last checkout opened: its plan, interval, Polar’s link and expiry, until it is paid or replaced;
- a record of each message from Polar: its id, type and time, what Sealcord did with it, the subscription and the organization, never the message itself;
- its active licences counted once a day, the plan’s limit, since when it has been over that limit, and which usage email each count called for and when it was sent;
- in its audit trail, which only its owners see, each change of plan, interval or state, and of whether the plan ends with the paid period, with Polar’s id for the subscription and Polar as its author.
The usage emails go to every owner of the organization, on any plan with a limit, Free included: when its active licences reach 80% of the limit, when they reach it, and when new licences pause. Each names the organization, the plan and the count, and goes out through Resend (below).
In the Console, the organization’s owners see its plan, the subscription’s state, when the paid period ends, its usage and its limits; every member sees the plan, its active-licence limit and usage, and whether new licences are paused. The audit trail’s entries about the plan (above), with Polar’s id for the subscription in them, are shown only to the owners, through Sealcord’s API; the Console’s screens leave them out. Polar’s other ids are not shown anywhere. How long all this is kept:below.
Legal basis: Article 6(1)(b) GDPR, to give the organization the plan it pays for and bill it as agreed. Where the organization is a company rather than you, Article 6(1)(f) GDPR: our legitimate interest, and the company’s, is giving it the plan it pays for. Paying is your choice: an organization can stay on Free, which needs no payment.
Polar Software, Inc. is in the United States and is not on the list of companies taking part in the EU–U.S. Data Privacy Framework. Its data processing addendum with Sealcord includes the European Commission’s Standard Contractual Clauses (Article 46(2)(c) GDPR), and its privacy policy says it transfers personal data out of the EEA only to a country with an adequacy decision or under safeguards such as those Clauses.
Invitations
If a member of an organization invites you to it, Sealcord keeps the address they typed, the role they chose, the organization, who invited you and whether the invitation is pending, accepted or revoked, and emails you the invitation through Resend. Sealcord got your address from that member. Every member of the organization sees the pending invitation, with your address. To stop the invitations being used to flood an inbox, Sealcord’s API counts them per invited address, under a one-way code, for a day.
Legal basis: Article 6(1)(f) GDPR. Our legitimate interest, and the organization’s, is letting its members invite the people they work with. The invitation works for 7 days. If you accept it, you have a developer account as described above. If you do not know who sent it, ignore it: nothing else happens.
Seeing your licences
If you bought software that is licensed with Sealcord, you can sign in to the Console with a code emailed to you, to see your licences and free the machines they are used on.
The software maker who sold you the licence is responsible for your licence data: they decide what it holds and why, and Sealcord keeps it for them, as their processor. Their privacy notice says more; write to them with questions about it. For each licence, Sealcord keeps your email address, the product, when the licence was issued and when it expires, how many seats or machines it allows, its state (with the reason, if it was revoked or expired), the maker’s own reference for the sale, if any, and the payment provider’s ids for the customer, checkout, order or subscription, if it came from a purchase. For each machine it is activated on: an identifier the app makes for the machine, the name, operating system and app version the app reports, and when it was activated, last checked and freed. Sealcord does not store the network address a machine checks in from; like every request to the API, a check is counted for one minute under a code computed from it. Sealcord also keeps a record of each change to the licence and of each machine activated, with the machine’s name, operating system and app version. For five minutes after a licence is checked, Upstash also keeps a copy of its state (below). The maker sees all of this in their Console.
If the maker has their own server told about changes (outgoing webhooks), Sealcord also keeps, for each change to the licence or a machine it is activated on, a copy of that licence data as it stood (never the key), with the machine’s details for a machine’s change, and a record of each delivery to the maker’s server: whether it arrived, and the answer’s status code. What reaches the maker’s server is theirs, under their privacy notice.
When you ask the maker to erase your data, they can have Sealcord anonymise your licence: your email address, their reference, the payment provider’s customer and checkout ids, the reason and every machine’s identifier, name, operating system and app version are removed from the licence, from its record and from the copies kept for the maker’s server, for good. What stays is the licence’s id, product, dates and limit, the counts, and the payment provider’s order or subscription id, so that a repeated or renewed purchase does not issue it again. The licence stops working and cannot be used again; the key you hold still contains your address, as every key does, but Sealcord can no longer make or show it.
For signing in, Sealcord itself is responsible. It keeps your account (your email address), your sessions (when you signed in and last used the Console, and the network address and browser you signed in from), a record of each sign-in, and the sign-in limits. Legal basis: Article 6(1)(f) GDPR. Our legitimate interest, and the software makers’, is letting you see and manage your licences, securely.
Sign-in limits
To stop guessing, and to stop sign-in emails being used to flood an inbox, Sealcord’s API counts requests for sign-in links, codes and sign-ups, code checks and wrong codes: per network address, kept in clear, and per email address, kept only as a one-way code made from the address. Like every request to the API, each is also counted for one minute under a code computed from your network address. The counters expire on their own, after a minute to a day. Too many wrong codes for your email address lock code sign-in for it for up to a day: from one network address, for that network address; from anywhere, for everyone, whoever entered them.
Each sign-in link or code Sealcord prepares is stored as a one-way code, together with the email address it was asked for, even when that address has no account and no email is sent. The record is deleted when the link or code is used, and otherwise, usually, within a day after its 10 minutes.
Legal basis: Article 6(1)(f) GDPR. Our legitimate interest, and yours, is keeping accounts safe and inboxes free of unwanted sign-in emails.
Where the counters are kept
Sealcord’s API keeps the counters described on this page, for the launch list, for signing in and for invitations, with Upstash (Upstash, Inc., United States), a database service Sealcord uses as its processor under Upstash’s data processing addendum. The counters are kept in Upstash’s Frankfurt (Germany) region, on Amazon Web Services servers; they hold only what is described on this page: network addresses, in clear or as a code, and one-way codes made from email addresses. Upstash also keeps, for five minutes, a copy of a licence’s state (its id, product, state, expiry and limit), so apps’ checks are fast. Each counter is deleted when it expires, after a day at the most, each copy after five minutes, and Sealcord keeps no backup of them. Upstash uses service providers of its own (upstash.com/static/trust/subprocessors.pdf).
Upstash, Inc. is a company in the United States and may access the data from there. It takes part in the EU–U.S. Data Privacy Framework (an adequacy decision under Article 45 GDPR), and its data processing addendum includes the European Commission’s Standard Contractual Clauses (Article 46(2)(c) GDPR) for any transfer the Framework does not cover. To get a copy of the clauses, write to hello@sealcord.com.
Cookies
The website sets no cookies. The Console sets only the cookies it needs to sign you in, to remember the product you chose, and to confirm a workspace you deleted. Each is sent only to console.sealcord.com, over HTTPS, and the page’s scripts cannot read it:
__Host-sealcord.session_tokenkeeps you signed in. It works as long as your session: at most 12 hours for developers (an hour without use), at most 30 days for people seeing their licences (a week without use). Your browser keeps it for up to 30 days, or until you sign out.__Host-sealcord.better-auth-passkey, for 5 minutes while you sign in with a passkey or add one.__Host-sealcord.state, for 5 minutes while you sign in with GitHub or link it.__Host-sealcord.product, set only when you choose a product in the Console’s sidebar: it holds that product’s id and your workspace’s, so the Console shows that product’s data. Your browser keeps it for a year.__Host-sealcord.workspace-deleted, for a minute after you delete a workspace: it holds the date until which you can ask for it back, so the next page can tell you.
They are strictly necessary for the sign-in, the choice and the deletion you ask for, so they need no consent (section 25(2) no. 2 of the German TDDDG, which implements Article 5(3) of the ePrivacy Directive), and there is no cookie banner. Neither the website nor the Console runs analytics, advertising or third-party scripts.
Where Console data is kept
Your account, your sessions, the audit trail, licence data and an organization’s plan and billing records are kept in a Postgres database run by Supabase Pte. Ltd. (Singapore), as Sealcord’s processor under the data processing addendum that forms part of its terms. The database and its backups are in Amazon Web Services’ Frankfurt (Germany) region. Supabase uses service providers of its own (supabase.com/legal/customer-resources/subprocessor-list) and its affiliate Supabase, Inc. (United States), and its staff and those companies may access the data from Singapore, the United States and other countries outside the EU for support, security and operations. These transfers rely on the European Commission’s Standard Contractual Clauses (Article 46(2)(c) GDPR), which its data processing addendum includes. To get a copy of the clauses, write to hello@sealcord.com.
The Console’s emails (sign-in links and codes, invitations, account notices and plan usage emails) go out through Resend (above), which keeps a record of each email for 30 days. bunny.net delivers the Console and runs it and the API in Germany; the counters, and a five-minute copy of a licence’s state, are kept with Upstash as described above.
When the API or one of its background jobs fails, Sealcord gets a report of the error through Sentry (Functional Software, Inc., United States), an error-tracking service it uses as its processor under Sentry’s data processing addendum. A report holds what the API writes to its own log about the failure: what failed, where in the code, and the ids of the records concerned (an account, an organization, a licence); never an email address, a network address, a licence key, a password or what a request contained. Sentry stores the reports in Frankfurt (Germany) and keeps them for up to 90 days. Functional Software, Inc. may access them from the United States; it takes part in the EU–U.S. Data Privacy Framework (an adequacy decision under Article 45 GDPR), and its data processing addendum includes the European Commission’s Standard Contractual Clauses for transfers the framework does not cover. Legal basis: Article 6(1)(f) GDPR. Our legitimate interest is finding and fixing faults in the service.
If you choose to sign in with GitHub, you deal with GitHub directly, under its ownprivacy statement: GitHub does not work for Sealcord. Sealcord sends it only what the sign-in needs, and asks it for your email addresses (the permission it asks for) and your public profile; it keeps only your GitHub account’s numeric id.
How long Console data is kept
A clean-up that runs once a day deletes each kind of record below when its period has passed: usually within a day after, and a few days after if it falls behind.
- Your account, as long as it exists. You cannot delete it in the Console yet: write to hello@sealcord.com and we delete it, with your sessions, passkeys, linked GitHub account, memberships, invitations and pending sign-in codes and links, or correct its email address. We cannot delete the account of an organization’s only owner until it has another owner. Your membership of an organization ends when you are removed from it, or when the organization is erased after its deletion (below). An account that belongs to no organization is deleted 12 months after its last sign-in, or 24 months after it when a licence was sent to its email address; its sessions, passkeys and linked GitHub account go with it.
- Passkeys and a linked GitHub account, until you remove them in Settings or your account is deleted.
- A session’s record, with its network address and browser, until you sign out or, as a developer, sign it out in Settings (or, for a session GitHub signed in, you unlink GitHub), and otherwise about 30 days after it expired.
- Error reports in Sentry (above), for up to 90 days.
- Sign-in links and codes, with the email address each was asked for, and sign-ups waiting for confirmation: they work for 10 minutes, and are deleted when used, and otherwise, usually, within a day after that.
- Invitations: they work for 7 days. The record is deleted about 30 days after it expired, was accepted or was revoked.
- The audit trail: sign-ins, sign-outs and switches between roles and organizations for 12 months; the rest as long as the organization exists, until it is erased after its deletion (below). Entries about an account in no organization (passkeys or GitHub added or removed after it left, its deletion) are kept as long as Sealcord runs. The audit trail holds ids and times, not addresses, and, for licences, machine names, operating systems and app versions (until 90 days after the machine is freed), reasons and the maker’s references (until the licence is anonymised), and, for the plan, each change of it with Polar’s id for the subscription (above). When an account is deleted, the entries keep only its id.
- An organization’s plan and billing records (above): Polar’s ids, the subscription’s state and dates, the daily counts and the record of Polar’s messages, as long as the organization exists. When a paid plan ends, the organization goes back to Free and the records stay. Deleting the organization cancels its paid plan at Polar at once. Polar keeps what it holds as its privacy policy says: while the account is open, and longer where the law, such as accounting or tax law, requires it; or, under its data processing addendum with Sealcord, for as long as Sealcord uses Polar and three years after, or longer where the law requires it.
- An organization, and everything it holds, until 30 days after its owner deletes it. From the deletion nothing of it works or shows: its keys, integrations, webhook endpoints, invitations and what AI assistants were allowed to do for it end, and its customers’ licences stop working. Within the 30 days we can bring it back on its owner’s request. Then it is erased: its products, licences, their machines and their record, its keys, integrations, webhook endpoints and the events kept for them, plan and billing records, members, invitations and settings. Only a record that it was erased stays, with counts and no names. The identifiers of its products stay, so that no other product ever takes them. The accounts of its members stay, as above, and so do the entries in their own audit trail that name it by its id (their sign-ups, sign-ins and the AI assistants they allowed), for those entries’ own periods.
- AI assistants: what you allowed one to do stays until you ask us to withdraw it (the Console has no button for it yet) or your account is deleted. An assistant’s refresh token expires after 7 days without use.
- The counters: a minute to a day. bunny.net’s request logs: 3 days; the logs of Sealcord’s servers: up to 5 days. Resend’s record of an email: 30 days, and its backups for 7 days.
- Licence data, its machines and their record are kept as long as Sealcord runs, or until the software maker has the licence anonymised (above), or until the maker’s organization is erased, 30 days after its deletion. A machine’s name, operating system and app version are removed 90 days after it is freed, from the machine and from the record of its activation; the identifier the app made for the machine stays, with the licence it was activated on. Ask the maker, or write to us and we pass your request on.
- The copies of licence changes kept for a maker’s server (outgoing webhooks), and the record of their delivery: 30 days after the change.
- The database is backed up once a day and each backup is kept for 7 days, so a deleted record can still be found in a backup for 7 days.
If you write to us
We use what you write to hello@sealcord.com only to answer you. Legal basis: Article 6(1)(f) GDPR, or Article 6(1)(c) GDPR when you exercise a right under the GDPR.
Your rights
You can withdraw your consent at any time, with the unsubscribe link in every email or by writing to hello@sealcord.com. Withdrawing does not make the emails sent before it unlawful.
You have the right to know what we hold about you, and to have it corrected or deleted, its processing restricted, or given to you in a portable form (Articles 15 to 18 and 20 GDPR). Write to hello@sealcord.com. For licence data, we pass your request to the software maker responsible for it, or you can write to them directly; they can have your licence anonymised (above).
You can complain to a data protection supervisory authority, in particular in the EU country where you live, where you work or where you think the law was broken (Article 77 GDPR).
We make no automated decisions about you and build no profile of you. The sign-in limits refuse requests by themselves, for a day at the most; write to us if they keep you out.
Your right to object
Where we process your data on the basis of our legitimate interests (Article 6(1)(f) GDPR), you can object at any time, on grounds relating to your particular situation (Article 21(1) GDPR).
You can object at any time, without giving reasons, to the use of your address for direct marketing (Article 21(2) GDPR); we then stop using it for that. Use the unsubscribe link in any email, or write to hello@sealcord.com.
Last updated 12 November 2026.