Levee
  • Features
  • Work together
  • Download
  • Docs
  • Blog
EN DE
Sign in Get Levee

Privacy

This notice covers this website and the Levee application at https://app.levee.deichrakete.com. Neither sets tracking cookies or follows you around the web. The website counts visits with Plausible, without cookies and without personal data; the application counts nothing. What happens to your data when you sign in, work in a team or share a document is described below in full.

This is a translation. The German version of this notice is the binding one.

  1. Controller
  2. What this notice covers
  3. Hosting and server logs
  4. Cookies and local storage
  5. Visitor statistics with Plausible
  6. Your Levee account
  7. Documents in the cloud
  8. Working in a team
  9. E-mail from the application
  10. The Levee desktop application
  11. How long we keep data
  12. Service providers
  13. Contacting us
  14. Your rights
  15. Changes

1. Controller

The controller responsible for data processing on this website and in the Levee application is:

Stephan Plöhn
deichrakete
Burfehner Weg 74
26789 Leer (Ostfriesland)
Germany
E-mail: moin@deichrakete.com

The controller is the natural or legal person who alone or jointly with others decides on the purposes and means of processing personal data.

2. What this notice covers

  • this website, levee.deichrakete.com,
  • the Levee application at https://app.levee.deichrakete.com: signing in, teams, documents in the cloud, the browser preview, comments and share links,
  • the connections the Levee desktop application makes on your computer.

Using Levee on files on your own computer needs no account, and those files never leave your computer. Links to other sites, such as deichrakete.com, lead to sites with privacy notices of their own.

3. Hosting and server logs

The website and the application are hosted by Hetzner Online GmbH, Industriestr. 25, 91710 Gunzenhausen, Germany, on servers located in Germany. The application's server is set up and maintained with ploi, a server management service of WebBuilds B.V., Amperestraat 16J, 3861 NC Nijkerk, the Netherlands, which has administrative access to that server. Both process data on our behalf under data processing agreements in accordance with Art. 28 GDPR.

When you open a page, the web server records the request in a log file, which contains:

  • the IP address of the requesting device,
  • date and time of the request,
  • the requested address and the HTTP status returned,
  • the page you came from (referrer), if your browser sends one,
  • the browser and operating system your browser reports (user agent).

The application's sync server, which keeps open documents in step between everyone working on them, also records the e-mail address of the account and the ID of the document each time someone opens a document or is refused access to one. Errors are logged together with the request they occurred in.

These logs are needed to deliver the website and the application, to keep them stable and secure, and to investigate faults and attacks. The legal basis is our legitimate interest in a secure and working service, Art. 6 (1) (f) GDPR. Log files are deleted automatically after 14 days unless a specific entry has to be kept longer to investigate a security incident. The logs are not merged with other data and are not used to build profiles.

4. Cookies and local storage

This website sets no cookies and does not use advertising or social media plugins. Stylesheets, scripts, icons, images and the site's font are all served from this domain. The one request that goes elsewhere is the small analytics script described in section 5.

The application sets two cookies, and only once they are needed:

  • a session cookie, once you sign in, open an invitation or unlock a share link that has a password. It keeps you signed in, and your browser discards it when you close it;
  • a security cookie when you submit a form, which proves that the form was sent from the application and not from another site.

When you open an address of this website without a language in it, such as the bare domain, English or German is picked from the languages set as preferred in your browser (the Accept-Language header), and you are sent to that version. The choice is not stored: the language is part of the address, and the switch at the top of every page changes it.

Both are strictly necessary to provide the service you asked for, so no consent is needed, § 25 (2) No. 2 TDDDG. If you comment as a guest on a share link, the name and e-mail address you type are also kept in your browser's local storage, so that you do not have to type them again. They stay on your device until you delete your browser data.

Everything the application shows is served from its own address as well. Documents use typefaces from Google Fonts: our server fetches each one from Google once and then serves it itself, so Google sees our server, not you.

5. Visitor statistics with Plausible

To learn which pages are read and where visitors come from, this website uses Plausible Analytics, provided by Plausible Insights OÜ, Västriku tn 2, 50403 Tartu, Estonia. Plausible processes all data on servers within the European Union.

Plausible works without cookies and stores nothing on your device. When you open a page, its script reports the page address, the site you came from, your browser and operating system, the type of device, and the country and region you are visiting from. Your IP address is used only to determine that country and to count you once per day: it is combined with a salt that changes daily and hashed, and the hash is thrown away after 24 hours. No IP address is stored, and no identifier exists that would let anyone recognise you tomorrow or on another site.

What remains is aggregate statistics: how many people read a page, not who. The legal basis is our legitimate interest in understanding how this site is used, Art. 6 (1) (f) GDPR. Because Plausible does not read or store anything on your device, no consent under § 25 TDDDG is needed and no cookie banner is shown. Plausible processes the data on our behalf under a data processing agreement, Art. 28 GDPR; its own data policy lists exactly what is collected.

These statistics run on this website only. The Levee application and the sign-in area at https://app.levee.deichrakete.com do not load Plausible or any other analytics. Since nothing identifies you, there is no per-visitor opt-out; a content blocker that stops the Plausible script works, and the site works fine without it.

6. Your Levee account

Accounts are created by invitation: an admin of a team invites you by e-mail, as described in section 8. When you register, we store your name, your e-mail address and your password as a one-way hash, so the password itself is never stored. Your name is what your teammates see beside your cursor and on your comments. Before you can sign in, you confirm your address with a link we e-mail to you; changing the address later works the same way. Your settings record whether you want comment e-mails.

In the browser, the session cookie from section 4 keeps you signed in. In the desktop application, you sign in with your e-mail address and password, and our server gives Levee a key that it keeps on your computer. We store only a hash of that key, the program version that signed in (such as Levee/0.8), and when the key was created and last used. A key that has not been used for 90 days stops working. The settings page in the application lists every device that is signed in and lets you sign any of them out; changing your password signs out all of them.

To slow down password guessing, failed sign-ins are counted per e-mail address and IP address; the counter holds only a hash of both. Forms that send an e-mail, such as registration and password reset, are limited per IP address, and that counter expires after at most two hours.

The legal basis for the account is the contract of use, Art. 6 (1) (b) GDPR, and for the limits our legitimate interest in protecting accounts from misuse, Art. 6 (1) (f) GDPR.

7. Documents in the cloud

A document you create or import in a team is stored on our server: the file itself, with every picture placed in it as it was added, a preview of the document for the browser, and a thumbnail. Pictures keep the metadata they carry, and a photo taken with a phone can hold the place it was taken, so remove that before placing a photo if it matters. For each document we also record who created it, who has edited it and when each of them last did.

While a document is open, Levee keeps it in step over a connection to our sync server: every change goes through the server to the others in the document. Where your pointer is on the canvas is passed on to them as it moves and is not stored.

A document belongs to its team, not to the person who made it. The legal basis is the contract of use, Art. 6 (1) (b) GDPR. If your team puts personal data of other people into documents, such as names or photos of customers, we process that data on the team's behalf; write to us for a data processing agreement under Art. 28 GDPR.

8. Working in a team

A team is a shared workspace. Its admins decide who belongs to it and what each member may see, and what members see of each other follows from that. This section describes it in detail.

Teams, projects and roles

A team holds projects, and a project holds documents. A document in no project is in the team's Drafts. Every member has one of three roles:

Admin Editor Viewer
Sees every project and document, and everyone's drafts the projects and documents shared with them, and their own drafts the projects and documents shared with them
Opens documents in Levee yes yes no, only the browser preview
Comments yes yes yes, in the browser
Makes share links yes for the documents they can see no
Invites people, changes roles yes no no

Sharing a project shares every document in it, including the ones added later. A single document can also be shared on its own.

Invitations

Only an admin can bring someone into a team. They enter an e-mail address, a role and the projects to share, and we send one e-mail with a link. We store the address, the role and projects, who sent the invitation, and when and by which account it was accepted. The link works for 14 days, and we keep only a hash of it, so it cannot be read back from our database. Inviting the same address again withdraws the earlier link.

Someone without an account registers through the link at the invited address. Someone who already has an account accepts the invitation with that account, so an invitation should not be passed on.

What your teammates see of you

What Who sees it
your name, e-mail address, role and the projects shared with you the team's admins, on its People page
your name, initial and colour, while you have a document open everyone who has the same document open in Levee
your pointer on the canvas, as it moves everyone who has the same document open in Levee
your comments, with your name every member who can see the document, and guests on a share link that allows comments
that you created a document every member who can see the document
that you made a share link admins and editors who can see the document

Your e-mail address is shown to the team's admins only. Other members and guests see your name.

Comments and comment e-mails

A comment is stored with its document: the text, the author's name, where its pin is, when it was written, and whether and by whom it was resolved. We e-mail new comments to whoever created the document, everyone who has edited it and every member who has commented on it, for as long as they can see it, and never their own comments. The mail waits until a thread has been quiet for two minutes, so a conversation arrives as one mail. Every comment mail has a link to stop them for that document or altogether; the settings page in the application turns them back on.

While a document is open in Levee, a new comment can also appear as a notification on your computer. It comes from your operating system's own notification service and is not sent anywhere else.

Sharing with people outside the team

Admins and editors can put a document at a share link. The link opens the browser preview of that document and nothing else of the team. It can have a password, which we store only as a hash, a last day on which it works, and permission for guests to comment. Deleting the link stops it working.

From the application you can send a link by e-mail to up to ten addresses at a time. We do not store those addresses. The mail names you and has your e-mail address as its reply address, so the recipients can answer you directly. The password is never in the mail.

Guests on a link that allows comments write under a name of their choice and may give an e-mail address, which is not checked. Both are stored with their comments, which are marked as written by a guest. A guest who gave an address gets an e-mail only when a member of the team replies in a thread the guest took part in, and that mail contains only what members wrote. Its unsubscribe link deletes the address from the guest's comments on that document. To stop misuse, guest comments are counted per link and IP address, and that counter expires after at most twenty minutes.

Leaving a team

An admin can remove a member at any time. The membership and the projects shared with it end at once. A document the member already has open stays open in that window until it is closed. The account stays, and so do the documents and comments the member wrote, which belong to the team. A comment keeps its author's name even after the account is deleted, so the conversation still makes sense. To leave a team yourself, ask one of its admins or write to us. Deleting an account or a whole team is described in section 11.

9. E-mail from the application

The application sends e-mail only when something concerns you:

  • an invitation to a team,
  • a link to confirm your e-mail address, when you register or change it,
  • a link to reset your password, which is also sent when someone tries to register with your address,
  • a notice that your password was changed,
  • a share link someone sends you,
  • new comments on documents you take part in, and replies to guests.

The mails are sent through mailbox.org, a service of Heinlein Hosting GmbH, Schwedter Straße 8/9A, 10119 Berlin, Germany, under a data processing agreement in accordance with Art. 28 GDPR. They contain no tracking pixels and no images, so we cannot see whether or when a mail was opened. Until it is sent, a mail waits in our database, and it is deleted from there once it has gone out. A mail that cannot be delivered is kept until we have checked the error, and then deleted.

10. The Levee desktop application

Levee sends no usage statistics and no crash reports. It connects to the internet only for the following:

  • Fonts. A typeface is fetched the first time a document uses it, from https://app.levee.deichrakete.com, also when you are not signed in. Our server gets it from Google Fonts, so Google sees our server, not you. When our server cannot be reached, Levee loads the font from Google directly and shows you a notice. In Preferences you can turn that off, or choose to fetch from Google directly. A request to Google gives Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland, your IP address, which Google may also process in the USA. A fetched typeface is kept on your computer and not fetched again.
  • Updates. An installed Levee on macOS checks once at startup whether a newer version exists. The request sends nothing but Levee's version number. On Linux, your software centre updates the Flatpak from our server.
  • Cloud documents. Once you sign in, Levee works with our server as described in sections 6 to 8. While a cloud document is open, it fetches new comments every 15 seconds.
  • Photo and icon search. The search in the Tools menu sends your search terms to Unsplash (Unsplash Inc.) for photos or to Iconify (Iconify OÜ, Estonia) for icons, and loads the results from them, which gives them your IP address. Unsplash also processes data outside the European Union. These requests happen only when you search.
  • AI agents. An AI agent can work in Levee through its MCP server, which runs on your computer. Levee itself sends nothing to an AI provider; what your agent sends to its provider is a matter between you and that provider. When an agent asks Levee to place a picture from a web address, Levee fetches it from there.

Requests you start yourself, such as a search, rest on Art. 6 (1) (b) GDPR; fetching fonts and checking for updates on our legitimate interest in a program that draws text correctly and stays up to date, Art. 6 (1) (f) GDPR.

11. How long we keep data

Data Kept
account: name, e-mail address, password hash, settings until you ask us to delete it
sign-in of a device until you sign it out, or 90 days after it was last used
invitations the link works for 14 days, the record stays with the team
documents, comments and share links until they are deleted in the application, or the team is deleted
a guest's e-mail address until the guest unsubscribes, or the document is deleted
server logs 14 days
counters against misuse that hold an IP address at most two hours
daily backups of the application's server 7 days

Deleting a document in the application removes it, with its comments and share links, from the team at once. Its files stay on our server until the team is deleted or you ask us to remove them.

The application has no button yet to delete an account or a team. Write to moin@deichrakete.com from the address of your account, and we delete the account, or at the request of one of its admins the team with all its projects, documents, comments and files, within 30 days and confirm it to you. The name on comments you wrote stays with them unless you ask us to remove it as well. Copies in backups are gone 7 days later.

12. Service providers

We do not sell data. We pass it on only to the service providers below, who process it on our behalf under data processing agreements, Art. 28 GDPR, and all of them in the European Union:

  • Hetzner Online GmbH, Germany: hosting of the website and the application, and backups,
  • WebBuilds B.V. (ploi), the Netherlands: management of the application's server,
  • Heinlein Hosting GmbH (mailbox.org), Germany: sending the application's e-mail,
  • Plausible Insights OÜ, Estonia: visitor statistics for this website.

Inside a team, other members see what section 8 describes. Data leaves the European Union only when you use the desktop application to reach Google, Unsplash or Iconify directly, as described in section 10.

13. Contacting us

If you write to us by e-mail, we process your address and what you send us in order to answer you. The legal basis is Art. 6 (1) (b) GDPR where your request concerns a contract, and otherwise our legitimate interest in answering enquiries, Art. 6 (1) (f) GDPR. We keep the correspondence for as long as the matter is open and as long as statutory retention periods require.

14. Your rights

Under the GDPR you have the right to:

  • access the personal data we hold about you (Art. 15),
  • have inaccurate data corrected (Art. 16),
  • have your data erased (Art. 17),
  • have processing restricted (Art. 18),
  • receive your data in a portable format (Art. 20),
  • object to processing based on legitimate interests (Art. 21),
  • withdraw a consent you have given, with effect for the future (Art. 7 (3)).

To exercise any of these rights, write to moin@deichrakete.com. You also have the right to lodge a complaint with a data protection supervisory authority. The authority responsible for us is the State Commissioner for Data Protection of Lower Saxony (Die Landesbeauftragte für den Datenschutz Niedersachsen), Prinzenstraße 5, 30159 Hannover, Germany.

15. Changes

This notice describes the website and the application as they are today. If either starts doing more, or the way visits are counted changes, this notice will be updated before that happens. Last updated: 26 October 2026.

Levee

A design tool for apps and websites.
On Linux and macOS.

Product

  • Features
  • Export
  • Work together
  • Download
  • Sign in

Learn

  • Documentation
  • Support
  • Blog
  • Feed

Legal

  • Imprint
  • Privacy
A project from deichrakete
EN DE
© 2026 deichrakete