Privacy policy

Last updated: 2026-11-17

This policy covers the Sumego Account: the single account you use to sign in to the apps of the suite, managed at id.sumego.es. It also covers the sumego.es website, where this policy and the terms are published. That website sets no cookies and does not measure visits; the server does not keep a log of visits. It is written from what the software actually does, not from a template.

What you do inside each app (your tasks in Lumbre, your notes in Hebra, the content of the spaces you share) is not stored by Sumego: it is governed by that app's privacy policy. Of the shared spaces, Sumego only stores who shares each one and with whom (section 4.6).

This policy is available in Spanish, English and German. The English and German versions are translations: if they differ, the Spanish one prevails.

1. Who processes your data

The data controller is David Velasco, a natural person resident in Spain, owner of Sumego and of the apps of the suite. He is the same controller as for Lumbre and Hebra. Sumego is a personal project: there is no company behind it and no partners. Apart from David, your data is processed only by the providers in section 6, and only as far as needed to provide their service.

You can write to hola@sumego.es about anything related to your data, including exercising the rights explained below. It is the official contact channel and it is answered. If you need the full identification details, for example to file a complaint with the Spanish Data Protection Agency or to sign an agreement, write to that address and they will be provided.

2. The short version

Sumego stores just enough to know who you are and let you in: your email, your password (as a digest that cannot be reversed), your passkeys if you use them, your display name and your avatar, and a public key for sharing in encrypted form. It also stores who you share each space with, so that all the apps of the suite see the same spaces and the same access. The content of the spaces does not reach Sumego, and it stores nothing else of what you do in the apps.

It has no analytics, no trackers, no advertising and no profiling. We do not sell or hand over your data to anyone to exploit it. The server is in the European Union. The only automated decision Sumego takes is deleting an inactive account, with prior notice and the right to have a person review it (section 9).

Two things worth knowing from the start:

  • Anyone who knows your exact email can find your account from an app of the suite, to invite you to share something. The app receives your identifier, your display name, your avatar and your public key (section 5).
  • Deleting the account deletes all of it: in Sumego and in every app. You cannot delete just one app (section 10).

3. What Sumego is and what it does not store

Sumego is an identity provider (OpenID Connect). When you press "Sign in with Sumego" in an app, the app sends you to id.sumego.es, you prove who you are there, and Sumego tells the app that it is you. The apps of the suite are currently Lumbre and Hebra, and a chat once it exists. Fragua is not an app of the suite: it only uses your Sumego account to sign in.

Sumego does not store your tasks, your notes, your files, your messages or the content of the spaces you share with other people. All of that lives on the apps' servers and is explained in their own policies. Of the spaces, Sumego only stores who you share them with (section 4.6).

4. What data there is and why

4.1 Access request

Sign-up is closed for now: requests are not accepted, and neither are invitations to people without an account. What follows explains how it works once it opens. Sign-up is not open: it is requested and David approves it by hand. To request it you leave your email on the request page (https://id.sumego.es/pedir-acceso). We store that email, the date of the request, the language you make it in and, if another person invited you, who invited you, and David receives a notice. We do not send a confirmation email, so that nobody can fill another person's mailbox; the page itself shows you the notice. The request does not create any account.

If another person invites you. If someone in the suite invites you to share something and you do not have an account yet, a request is created with your email, which that person provides, not you. The invitation waits until David approves your sign-up, because inviting you does not approve it on its own. If he approves it, the first email you receive from Sumego is the invitation, which says who invited you and carries the link to this policy. If he does not approve it, Sumego does not write to you and the request is deleted within 30 days at most. Your email is not used for anything else.

If David approves the sign-up, you receive an email with a single-use link, valid for 7 days, to create the account with your password. When you create it you confirm that you are 14 or older and accept the terms of use; both are stored with the version of the terms you accepted. That screen shows you and records, each with its version, the terms of Sumego and those of Lumbre.

4.2 What your account stores

  • Your email address and whether you have proven it is yours: To identify you and send you the links to sign in and the security notices. It counts as proven when you use a link that only reached that mailbox (the invitation or resetting the password).
  • Your password: To let you in. The password is not stored: a cryptographic digest (Argon2id) is stored, from which the original cannot be recovered.
  • Your passkeys (if you add any): To sign in without a password. For each passkey we store its public key, an identifier, a signature counter, the authenticator type, how it communicates (for example USB, NFC or the device itself), whether it can be synced and whether it is already backed up in your manager's cloud, the name you give it, and when it was created and last used. The default name comes from the authenticator type and the device, which is deduced from the browser (User-Agent) when it is created; of the User-Agent, only that name is kept. The private key stays on your device or in your password manager: Sumego does not see it.
  • Your profile: display name and avatar: So that the apps and the people you share with recognise you. The avatar is stored in Sumego's database (256 px, 256 KB at most) and replaces the one you had in Lumbre.
  • Your public key (P-256): So that other people can share encrypted content with you. Your account publishes and changes it; the private key never reaches Sumego (in Hebra it lives in your own vault).
  • Your confirmation that you are 14 or older and the accepted terms, with their version: To know that you are of the minimum age and which terms you accepted. It is the only record: the apps do not repeat it.
  • Account status: sign-up date, whether it is suspended, and its role (regular or administration): So that the account works and can be suspended if needed.

If your account came from Lumbre, Sumego copied from Lumbre your identifier, your email, your password digest (Argon2id) and whether it was suspended, and it keeps a fingerprint of that digest to know whether it has already copied it.

4.3 Sessions and what the apps receive

When you sign in, Sumego keeps a session in your browser and, for each app you sign in to, an authorisation with its credentials. On the server, each session, authorisation and credential is a record with your account, the app, its dates and its expiry. Whatever works as a secret (the session cookie, the apps' credentials, the links in emails) is stored as a digest, never in plain text. The access credential an app receives lasts 10 minutes at most; the refresh credential lasts 30 days and changes on every use.

While you are signing in, Sumego keeps that half-finished sign-in, which may include the email you type, for at most one hour. For passkeys and the sensitive actions of your account it also keeps single-use challenges, which expire after 5 minutes, and actions waiting for confirmation, which expire after 10.

The app you sign in to receives: an identifier of your account, which is the same in all apps, your email, whether it is verified, your display name, your avatar, when you signed in, and whether it was with a password or a passkey. Hebra talks to Sumego directly to sign you in, read your profile, look up other people by their exact email, publish and read public keys, and request invitations. Lumbre receives the access token that Hebra presents to its server to sync your notes, which carries your account identifier but not your email or your profile, and the notice that you have signed out. While Hebra syncs through the Lumbre server, that server can also, on your behalf and only when you ask for it from Hebra, look up people by exact email in the directory, publish your public key and request invitations.

To measure inactivity (section 9), Sumego asks each app, server to server, for the date of your last activity in it. It receives nothing else about what you do. Sumego stores, for each account, the most recent date the apps return in the weekly run, and uses it only for the inactivity notice and deletion.

4.4 Security log and IP address

Sumego records the important events of your account in a security log: every sign-in and every failed attempt, requesting and using a password reset link, accepting the invitation, adding, removing or renaming a passkey, changing the password, signing out of all apps, changing the email or the public key, downloading your data, changing your profile, accepting or declining the terms, inviting someone, asking for the account to be deleted, and suspensions and deletions. For sign-ins, failed attempts and security changes, the IP address they came from is stored. It is also stored when you download your data, change your profile, accept or decline the terms, invite someone, ask for the account to be deleted and change your public key. Passwords, links and keys are never stored.

In addition, the IP is used in memory to throttle sign-in and password reset attempts, and then discarded.

The server does not keep a log of every request it receives. The software's technical logs do not store passwords or links, and they rotate by size (at most about 30 MB per container).

4.5 Emails

Sumego only writes to you about your account, and these emails cannot be turned off because they are about security: the invitation, the password reset link, the notice to the old address if the account's email changes, the notices that a passkey was added or removed, that the password was changed and that the public key was changed, and the inactivity notice (section 9). There are no newsletters or advertising.

4.6 Shared spaces

Sumego stores who you share each space with, so that all the apps of the suite see the same spaces and the same access for each account, without losing any space or any access and without you having to do anything. It stores this:

  • The spaces: which account owns each one, its organisation, its visibility, its status, its dates and the catalogue name that the app publishes on purpose. That name is not the title of the space: the title is encrypted and the catalogue name is never taken from it.
  • Their members: each member's role, origin and status, when they joined, left or were removed, and whether that member's agent sees the space.
  • The invitations: who invites which account, their status and their dates. They carry no email.
  • The key envelopes of each space, addressed to a person or to their organisation. They are encrypted and Sumego cannot open them: it stores the bytes exactly as it receives them.

The content of the spaces does not reach Sumego.

Who reads it. Only the servers of the apps of the suite, server to server and with a permission of their own for it: the Lumbre server and the Hebra server. Writing needs a separate permission, which no app has by default. The apps are not third parties (section 6).

How long it is kept and what happens when you delete the account: sections 9 and 10. Downloading your data includes your spaces (section 11).

5. What other people see

The directory. The apps of the suite can look up an account in Sumego by exact email, so that you can invite someone to share something. If the account exists and is active, the app receives its identifier, its display name, its avatar and its public key. The avatar image is served at a public address that does not contain your email or your name. The directory does not allow listing accounts or searching by part of an email, and it answers the same whether an account does not exist or is suspended. This means that anyone who knows your email can find out, through an app, that you have an active account, what your display name is and what your avatar is. In this first phase there is no option to hide from the directory: the search is by exact email only and it does not list or suggest people.

When sharing. Inside a shared space, the other people see your display name and your avatar in the relevant app. What else they see depends on each app and is explained in its policy.

Public keys. Sumego distributes the accounts' public keys. That means trusting the server: one that changed a key could read a space at the moment of inviting. This is an accepted decision, the same one that already exists in Hebra when adding a device of your own. Comparing key fingerprints outside the suite is planned for a later version.

6. Who else is involved (processors)

Provider / What for / Inside the EU?

  • Hetzner Online GmbH: Server where Sumego lives (Helsinki, Finland) (Yes)
  • AhaSend B.V. (AhaSend), Amsterdam, Netherlands (KvK 99533111): Sending email (Yes: AhaSend hosts sending at Hetzner, in Germany and Finland)
  • Filen Cloud Dienste UG (haftungsbeschränkt) (Filen), Recklinghausen, Germany: Storing the backups, encrypted before they leave the server (Yes: Filen states that it stores data in data centres in Germany)

The copies stored by Filen are encrypted with a key that Filen does not have and that is not on the Sumego server either: Filen stores files it cannot read.

The apps of the suite are not third parties: they are run by the same controller. Your password manager or your device's system, where your passkeys live, is chosen by you and does not act on Sumego's behalf.

7. Transfers outside the European Union

The Sumego server is in the European Union. Email is sent by AhaSend, a Dutch company that hosts sending in Germany and Finland. The encrypted copies stored by Filen are in data centres in Germany, as Filen states. There are no transfers of your data outside the European Union.

8. Legal basis for each processing

  • Access request you make and its approval: Steps taken at the data subject's request before entering into a contract (Art. 6(1)(b) GDPR)
  • Request created because another person invites you: Legitimate interest (Art. 6(1)(f)) of the person inviting you in sharing with you and of Sumego in handling that invitation; your email is only used for that and is deleted within 30 days at most if the sign-up is not approved
  • Account, credentials, profile, public key, sessions and signing in to the apps: Performance of the contract (Art. 6(1)(b) GDPR)
  • Directory by exact email: Performance of the contract (Art. 6(1)(b) GDPR): it is what makes sharing within the suite possible
  • Shared spaces: spaces, members, invitations and key envelopes: Performance of the contract (Art. 6(1)(b) GDPR): it is what makes sharing within the suite possible and lets all the apps see the same spaces. Keeping for at most 90 days the membership of someone who leaves or is removed, so that leaving can be undone and for auditing: legitimate interest (Art. 6(1)(f))
  • Record of age and accepted terms: Performance of the contract (Art. 6(1)(b)) and legitimate interest in being able to prove acceptance (Art. 6(1)(f))
  • Account security emails: Performance of the contract (Art. 6(1)(b)) and legitimate interest in protecting the account (Art. 6(1)(f))
  • Security log, attempt throttling and abuse prevention: Legitimate interest (Art. 6(1)(f))
  • Inactivity notice and deletion: Legitimate interest (Art. 6(1)(f)) in not keeping abandoned accounts. As an automated decision, it is necessary for the contract, because the terms provide for it (Art. 22(2)(a)), and it has the safeguards in section 9

9. How long we keep things

  • Your account: for as long as it exists. If you delete it, all of it is deleted (section 10).
  • Shared spaces: for as long as the space and your account exist. If you leave a space or are removed from it, your membership is kept for at most 90 days, so that leaving can be undone and for auditing, or less if the space or your account is deleted first. Deleting the account deletes your memberships, the envelopes addressed to you and the invitations you have sent and those you have received (section 10).
  • Access requests: at most 30 days. If David rejects it, it is deleted immediately.
  • Single-use links: the invitation link expires after 7 days and the password reset link after 45 minutes. Expired ones are deleted every hour.
  • Sessions: your browser session expires after 30 days. Each app's session stays alive as long as the app renews it at least once every 30 days. Expired ones are deleted every hour, except Hebra's authorisations, which are kept, already revoked, until you delete the account.
  • Short-lived technical records: half-finished sign-ins, one hour; passkey challenges, 5 minutes; actions waiting for confirmation, 10 minutes; the apps' access credentials, at most 10 minutes. Expired ones are deleted every hour.
  • Security log: 90 days, including the IP address. If you delete the account, its lines remain until they reach those 90 days, but without your email or your IP. The exception is the line left by the deletion of an account, which is kept without a time limit and also carries neither the email nor the IP (section 10).
  • Inactive accounts: Sumego measures activity across all apps at once, with a weekly run that only looks at the date of your last use in each. If you use none of them for 24 months, we notify you by email and, 30 days after the notice, we delete the whole account, in Sumego and in every app. If you use any app of the suite again after the notice, the deletion is cancelled. It is an automated decision with a significant effect, so it has safeguards: the notice reaches you before anything is deleted, and within those 30 days you can write to the contact address to ask for a person to review it, to express your point of view or to contest it, and the account is not deleted while it is being reviewed. While the review lasts, the deletion is paused until a decision is made.
  • Accounts I close without cause (section 11 of the terms of use): access is cut off immediately and the data is kept for 30 days so that it can be sent to you exported if you ask me; after that the whole account is deleted.
  • Backups: the Sumego database is copied once a day and before each update, and they are kept as follows: daily copies, 14 days on the server itself; copies made before an update, the 5 most recent and never more than 30 days; and the daily copy, encrypted before leaving the server, also outside it for 90 days, the same period as the security log. After those periods the copies are deleted automatically. What is deleted from the service remains inside the copies made before the deletion until that copy is deleted.

10. Deleting the account

You can delete your account yourself from id.sumego.es/cuenta, after confirming again that it is you with your password or a passkey. "Delete account" in any app takes you there.

Deleting means the whole account. When you ask for it, access is blocked immediately: Sumego suspends the account, closes your sessions and asks each app to close its own and delete your data. If an app does not respond, it is retried, and the account stays suspended until all of them confirm; the deletion is completed then, not before. Once it is completed, Sumego deletes the account, its credentials, its passkeys, its sessions, Hebra's authorisations and its links, its memberships in spaces, the key envelopes addressed to it and the invitations it sent and those it received, and removes the email and the IP from the security log lines. You cannot delete just one of the apps.

Afterwards three things remain, none of them with your email or your IP. Two are in the security log: the earlier lines of your account (what happened and when, with the random code that identified the account), until they reach 90 days and are deleted; and a line saying that the account was deleted on a given date, which is kept without a time limit so that the account cannot be recreated on its own. The third is a set of technical sign-out markers (the random identifier of the account, the app and the date), kept without a time limit so that no app accepts a session from an account that has already been deleted.

If your account owned a space, the random identifier of the account also remains as the owner of that space, without email or name, until the app transfers the space. If the space is pending deletion or already deleted, that identifier may stay.

What happens to the content of the spaces you shared is governed by each app's policy.

11. Your rights

You can exercise these rights by writing to the contact address in section 1. We have one month to reply.

  • Access and portability. You can see your email, your passkeys and your sessions at id.sumego.es/cuenta. For a complete copy of what Sumego stores about you, write to us, or download it yourself as JSON from id.sumego.es/cuenta (portability, Art. 20 GDPR). The download includes your spaces: your memberships, the spaces your account owns, your invitations and the key envelopes addressed to you. Exporting your content is done in each app.
  • Erasure. From id.sumego.es/cuenta (section 10). It is a real deletion, not hiding.
  • Rectification. You change your display name, your avatar, your passkeys and your password yourself at id.sumego.es/cuenta. For now, the email is changed by asking at the contact address in section 1; once /cuenta allows it, it will require proof that you control the new mailbox.
  • Withdrawing consent. Sumego does not base any processing on your consent, so there is nothing to withdraw here. Consents you give inside an app (for example, Lumbre's AI features) are withdrawn in that app, as its policy explains.
  • Objection and restriction of processing.

If you believe we have not done things right, you can lodge a complaint with the Spanish Data Protection Agency (aepd.es).

12. Cookies and storage on your device

id.sumego.es only uses technical cookies, all with the __Host- prefix, Secure, HttpOnly and SameSite=Lax:

Cookie / What for / How long

  • __Host-sumego-session: Keeping your Sumego session (30 days)
  • __Host-sumego-interaction, __Host-sumego-resume: The sign-in you are doing (While the sign-in lasts, at most one hour)
  • __Host-sumego-ticket: Staying signed in after setting or resetting the password (15 minutes)
  • __Host-sumego-cuenta: Signing in to your account page (One hour)
  • __Host-sumego-desde: Remembering which app to return to (Until you close the browser)
  • __Host-sumego-aviso: Showing a notice after an action (One minute)
  • __Host-sumego-llave: Marking which passkey this browser signed in with (30 days)
  • __Host-sumego-tras-entrar: Going back to the page you came from after signing in (One hour)

Some have a twin cookie ending in .sig, which is its signature. In addition, the sign-in page stores sumego.oferta-llave in your browser so as not to offer you again to create a passkey.

All of this is technical, so no cookie banner or prior consent is needed. There is no analytics and there are no resources from other domains.

13. Minors

Sumego is not aimed at people under 14, which is the age from which a person can consent on their own to the processing of their data in Spain (Art. 7 LOPDGDD). When creating the account you have to confirm that you are 14 or older.

14. Security

Passwords are stored with Argon2id. Passkeys require verifying that it is you on the device. Everything travels over HTTPS. The links in emails, the sessions and the apps' credentials are stored as digests or encrypted, never in plain text. There are attempt limits per IP address and per account. Changing the password or pressing "Sign out of all apps" immediately voids your sessions in Sumego and notifies each app, which closes its own when it receives the notice or, if the notice does not arrive, at its next renewal. Resetting the password by email also removes all your passkeys, in case someone had added one. Backups are encrypted before leaving the server and stored offsite.

Administrative access is limited to one account, David's, which approves sign-ups, and to the Lumbre server through an internal API that it only uses to manage the accounts that came from Lumbre. The email of someone who requests one is not used for anything else.

15. Changes

If something relevant changes, this page and its date are updated. If the change affects what we use your data for, we will let you know by email.