Laubling

Privacy

We remember almost nothing.

No account, no email, no phone number, no ads, no tracking. Here is exactly what Laubling stores, who sees it and how you get rid of it again. We write it so that children and parents can understand it without a law degree.

1. Who is responsible

Chris Zemmel (Zyric)
Ostendstraße 1
75331 Engelsbrand, Germany
Email: chris@zyric.de

For anything about data protection, write to this address: questions, access, rectification or deletion. There is no separate data protection officer; you reach the person responsible directly.

2. The essentials in brief

  • You need no account. Your Laubling is recognised by a random key that lives in your browser.
  • All that is stored: first names, the sentence for a cutting, what your Laubling looks like, who is related to whom, times and a few game items (decorations, stamps).
  • No email address, no phone number, no address book, no IP address in the database.
  • No ads, no statistics tools, no cookies, nothing from third-party servers.
  • Notifications on your phone only come if you turn them on.
  • You can delete your Laubling yourself at any time (section 11).

3. What Laubling stores

3.1 Your Laubling

When you plant a Laubling (as a wild seed or from a cutting link), Laubling stores:

  • Your first name, exactly as you type it (at most 12 characters). If you come through a cutting, it is pre-filled with the name the sender typed in. You can change it right after hatching, and later by email on request.
  • What your Laubling looks like: its traits and whether a trait is new.
  • Relatives: which Laubling it descends from, which generation it is, how many cuttings were opened and how many descendants it has.
  • Timestamps: when it was planted, when its deadline runs out, when it was saved or wilted.
  • A fingerprint of your key as a SHA-256 hash, never the key itself. More in section 4.
  • The golden wreath: whether your Laubling has collected all the stamps.

3.2 Cuttings and their sentence

When you cut a cutting, Laubling stores the first name of the person it is meant for, your sentence (3 to 80 characters, optional), a random code for the link, the spot (1 to 3) and times. Once the cutting is planted, Laubling remembers which Laubling grew from it.

Who sees the sentence:

  • You, for your cuttings and, in the family tree, for your own children.
  • Whoever opens the link, as long as the cutting has not been planted yet. So only send the link to the person it is meant for.
  • The new Laubling itself, later in its origin story.

The sentence never appears in public, not on the leaderboard, not in the Garden, and other relatives do not see it in the family tree. Once a cutting is planted, the link shows neither names nor the sentence any more.

A link is valid for 7 days. If nobody opens it, the name and sentence stay stored until you give the spot away again or delete your Laubling. If you give an unopened cutting away again (after 24 hours at the earliest), the name and sentence are deleted. All that remains is the old code, your Laubling as the sender and the time, so the old link can say kindly that it went to someone else.

3.3 Who sees your first name

  • Everyone, even without a Laubling of their own: the leaderboard and the Garden show the first name, look, stage and number of descendants of the biggest Laublings and families.
  • Your family: parents, children, grandchildren and other relatives see your first name in the family tree, in the origin story and on greetings.
  • Whoever opens a cutting link from you sees your first name as the sender.

So: enter only your first name, no surname, no nickname people at school would recognise you by, no address.

3.4 Greetings

Laublings in a family can send each other greetings. There is no free text, only ready-made sentences. What is stored: who sent whom which of the ready-made sentences, when, and which stamp is on it. Plus whether your Laubling accepts greetings and whether you want a notification for a greeting. Greetings are deleted after 30 days; Laubling tidies up every hour for this.

3.5 Decorations, codes and stamps

  • Decorations: which meadows your Laubling has, where from (code, purchase or gift) and since when, and which one is on.
  • Codes: which code your Laubling redeemed and when, so that a code works only once per Laubling.
  • Stamps: which stamps your Laubling has collected, when, and which one currently goes on its greetings.

Meadows come from a code, as a purchase for one of your own Laublinge or as a gift (section 8).

  • Gifts: the gift code, which meadow is inside, whether the link preview should show it, the number of the payment session at Stripe, whether it is paid, unwrapped or refunded, and on unwrapping, which Laubling got it and when. Laubling does not store who bought the gift. The details stay as long as Laubling exists, because codes never expire and every code may only work once.

3.6 Wishes

On the Support page you can send us a wish. We store only the text (at most 300 characters) and when it arrived: no name, no Laubling, no address. The text goes through the same word filter as names and sentences. Only the operator can read it. We delete it once we have read it, at the latest after one year.

3.7 What Laubling does not store

No email address, no phone number, no address book, no surname, no date of birth, no IP address in the database, no location. Laubling uses neither the camera nor the microphone nor your location.

4. Your key and what stays in your browser

Instead of an account, your browser rolls a random key and keeps it in the browser's storage (localStorage). That is how the server recognises your Laubling. The server only stores a fingerprint of it.

The key is never part of an address (URL). When you plant, it goes to the server in the body of the request, otherwise in the “Authorization” header, which is not logged. The live connection (WebSocket) sends it as its first message once it is open.

You can copy it yourself as a transfer code to take your Laubling to another device. Whoever has your transfer code has your Laubling: do not pass it on. If you clear your browser data, the key is gone. Without the transfer code you can no longer reach your Laubling, and we cannot give it back to you either.

Laubling keeps these entries in your browser. They stay on your device until you delete them. The server does not get them, except for the key itself, as described above.

  • laubling.schluessel.v1 (localStorage): the keys of your Laublings in this browser, at most three.
  • laubling.aktiv.v1 (localStorage and sessionStorage): which of your Laublings is being shown.
  • laubling.offen.v1 (localStorage): a freshly rolled key, until planting has been confirmed. If the answer gets lost, Laubling finds the same Laubling again.
  • laubling.zustand.v1 (localStorage): whether each of your Laublings is running, saved or wilted, for the picker.
  • laubling.farbe.v1 (localStorage): the colour of each of your Laublings, for the picker.
  • laubling.gruesse.gesehen.v1 (localStorage): up to when you have seen greetings, per Laubling.
  • laubling.briefe.offen.v1 (localStorage): which letters you have already opened, per Laubling. Contains the time and the senders' first names.
  • laubling.gemeldet.v1 (localStorage): which Laublings you reported because of their name, so you no longer see those names.
  • laubling.toene.v1 (localStorage): whether sounds are on or off.
  • laubling.kauf.offen.v1 (localStorage): started purchases of a meadow (payment session number, for which Laubling, when), so the meadow arrives even without the return from Stripe. Deleted after two days.
  • laubling.geschenke.v1 (localStorage): the gifts you bought in this browser (code, meadow, time), for the list “Your gifts”.
  • laubling.geschenk.wartet.v1 (localStorage): a gift code waiting for your first Laubling. Deleted after unwrapping.
  • laubling.sprache.v1 (localStorage): your language choice, German or English.
  • laubling.tipp.platz.v1, laubling.tipp.menue.v1 (localStorage): whether a tip has already been shown.
  • laubling.app.spaeter.v1 (localStorage): when you chose “Later” on the tip to install the app. It comes back after three days at the earliest.
  • laubling.inapp.weg.v1 (sessionStorage): whether you dismissed the tip to open Laubling in your real browser, for this tab only.
  • laubling.messen (sessionStorage): only for debugging, when someone adds ?messen to the address. Otherwise it is not set.
  • laubling-v3 is the service worker cache: offline page, fonts, stylesheet and images, so the site shows a friendly message without a connection. No game data.

Laubling sets no cookies.

Change of address. Laubling used to be at laubling.zyric.de. Anyone who opens the old address is taken to laubling.com, and the Laubling entries in your browser come along: they travel in the part of the address after the # sign, which the browser never sends to a server, and laubling.com removes them from the address bar right away.

5. Hosting, access log and protection against abuse

Where it runs. Laubling runs in a container on a server of Hetzner Online GmbH in Germany (Nuremberg data centre). It is operated through the responsible person's platform Foundation. The database is a file on this server's disk.

Access log. Every request first reaches the web server Caddy, which accepts the encrypted connection (HTTPS) and passes it on to Laubling. Caddy logs every request with IP address, time, requested address (without the part after the question mark), browser identifier and headers. Credentials (the Authorization and Cookie headers and similar ones) are removed first. The address of a cutting link contains the link code and therefore appears in the log, but no names and no sentences. The log is kept for at most 7 days and then deleted.

Laubling itself writes no IP addresses into its database and does not log requests. Its own log contains only operational messages, such as whether a notification was delivered, without names and sentences.

Protection against abuse. So that nobody floods the service with requests or plants wild seeds by the hundred, Laubling counts requests per sender. For this, the IP address (for IPv6 only the network part) is combined with a random salt into a short fingerprint. Counting happens in memory only, never in the database. The salt is new after every restart. The counters disappear after a few minutes, after about an hour or, for wild seeds, shortly after the end of the day.

6. Notifications on your phone (optional)

Notifications are off until you turn them on and your browser asks whether you allow them. Children under 16 should only turn on notifications with their parents' permission.

What is stored. Your browser gives us a delivery address at your device's push service and two keys. We store them with your Laubling, without names or contact details, for at most five devices per Laubling. If a sixth is added, the oldest one is dropped.

When a notification comes. Someone opened your cutting (the notification names their first name), or your family reached a new stage. In addition, only if you turn it on separately in the settings: someone from your family sent you a greeting (with their first name, without the sentence). And a test notification when you request one in the settings.

Who delivers them. Notifications go through the push service your device or browser uses: Apple, Google, Mozilla or Microsoft. We encrypt the content before it goes there. The push service cannot read the text (including the first name). It sees that a notification from Laubling is coming to this device, when, and how big it is. It holds it for at most 24 hours in case your device is off.

Outside the EU. Some of these providers are based outside the EU, mainly in the USA. The legal basis is the consent you give when you turn notifications on. For transfers to the USA, the providers name their own safeguards in their privacy notices.

Turning them off. In the app, in the settings. Then we delete this device's delivery address for all Laublings in this browser, and the browser unsubscribes from the push service. Or in the settings of your device or browser. If the push service reports an address as expired, we delete it automatically.

7. No ads, no tracking, no third-party servers

  • No ads, no analytics or statistics tools, no cookies.
  • The site loads nothing from other servers (only those who support or buy a meadow switch to Stripe’s payment page, section 8): fonts, images and code come from laubling.com. The site’s security rule, the Content Security Policy, enforces this too.
  • Laubling does not pass on where you came from when you click a link (referrer).
  • If you share a cutting link, that happens through your device's share function, with the app you pick there, for example a messenger. The suggested text names both first names; you can change it before sending. What that app does with it is up to its provider. The link itself only contains a random code, no name and no sentence.

8. Who receives data

  • Hetzner: the server is in the data centre of Hetzner Online GmbH in Nuremberg. A data processing agreement under Art. 28 GDPR is in place with Hetzner.
  • Stripe, only if you support Laubling with money or buy a meadow. Payment happens on Stripe’s page (Stripe Payments Europe, Limited, Dublin, Ireland). There you enter your card and email address; Stripe sends you the receipt and, for monthly support, the way to end it. Laubling does not receive this data. For voluntary support Laubling stores nothing about the payment. When you buy a meadow, Laubling gives Stripe the internal number of your Laubling and the meadow you bought, so the meadow is credited to exactly this Laubling after payment; afterwards Laubling only notes that the meadow came from a purchase. For a gift, Laubling only gives Stripe the gift code and the meadow; the code is in the item name and so on your receipt (legal basis: contract, Art. 6(1)(b) GDPR). Stripe is responsible for this itself; Stripe’s privacy policy is at stripe.com/privacy. For bookkeeping, the operator sees the amount, time and the details you entered in the Stripe account.
  • Push services (Apple, Google, Mozilla, Microsoft), only if you turn on notifications, and only encrypted content plus the delivery address. More in section 6.
  • Nobody else. We sell no data, give nothing to advertising partners and use no analytics services.

9. For parents: children on Laubling

Laubling is made for families, children included. That is why we built it so that as little as possible becomes known about a child:

  • No account, no email, no phone number, no photos, no location.
  • First names only. Names and sentences go through a word filter with fixed lists; phone numbers, links and messenger names are not allowed. No filter catches everything, so names and sentences can be reported (section 10).
  • No chat and no free text between Laublings, except the one sentence for a cutting. Greetings are ready-made sentences.
  • No ads, no purchases, no countdowns. Grown-ups can support Laubling voluntarily; it changes nothing in the game, and the game never asks children to do it.

What you should know:

  • Your child's first name can be visible to everyone on the leaderboard and in the Garden, and is visible to its own family in the family tree (section 3.3). Talk with your child about using only a first name or a made-up name.
  • The sentence for a cutting can be read by anyone who has the link, until the cutting is planted.
  • Notifications are optional. They are based on consent, and for children under 16 that needs the parents' permission (Art. 8 GDPR). So children under 16 should only turn on notifications with your permission.
  • Deleting: your child can delete their Laubling themselves in the settings (section 11).
  • Access and deletion: you can also request these for your child by email (section 14). Because there is no account, we can only recognise your child's Laubling by its transfer code or by the first name together with a cutting link; please have one of them ready.

10. Reporting

If a name or a sentence does not seem okay to you, you can report it: names in your family and in the Garden, a sentence on the page where a cutting arrives. What is stored:

  • What was reported: which Laubling (for a name) or which cutting (for a sentence). We do not store a copy of the text.
  • Who reported: which Laubling. For a sentence on the arrival page, no Laubling is stored.
  • The reason, one of four fixed answers: mean or insulting, not for children, phone number, address or link, something else.
  • Whether the report counts and when it came in.

A report only counts if it comes from a Laubling that is at least a day old, has sent a cutting itself and has not often reported without reason. That way nobody can get others hidden with freshly planted Laublings.

A reported sentence is hidden right away. A name is hidden for everyone as soon as two counting Laublings have reported it. Whoever reports a name stops seeing it on their device right away. The operator reads reported names and sentences in his admin console and decides: block or fine. A Laubling itself is never blocked or deleted, only the name or the sentence. Reports are deleted after 90 days.

11. Deleting

In your Laubling's settings there is the button “Delete this Laubling”. You hold it for 5 seconds and confirm once more.

Right away:

  • Your name is gone for everyone.
  • Nobody can send you greetings any more, and notifications stop. The delivery addresses for notifications are deleted.
  • Your Laubling disappears from this browser.

For 14 days you can bring it back with your transfer code, with everything it had. Copy the transfer code beforehand if you want to keep that option open.

After that, these are deleted for good:

  • your name,
  • all sentences you wrote yourself and the first names you typed in for your cuttings,
  • cuttings nobody has opened yet (those links stop working) and cuttings you gave away again,
  • greetings you sent or received, your stamps, your decorations and your settings,
  • reports your Laubling made, and reports against its name.

Your key becomes invalid, and the transfer code no longer works.

What remains:

  • A pale Laubling without a name in the family tree, with its look, its place in the family, its numbers and the times. That way the family keeps counting, and your children's and grandchildren's Laublings do not lose their origin.
  • Sentences others sent to your Laubling. They belong to the sender.
  • Which codes your Laubling redeemed and when, without a name.
  • Reports against a sentence you wrote. They contain no text and are deleted after 90 days.
  • On your device: small notes about your Laubling from section 4 (such as its colour or which greetings you have read), until you clear your browser data.

By email: You can also have your Laubling deleted. Write to chris@zyric.de and include your transfer code, or, if you no longer have it, your first name and a cutting link.

12. How long we keep data

  • Your Laubling (first name, traits, relatives, times, wreath, fingerprint of the key): as long as it exists, because it is part of a family tree. After deletion, section 11 applies.
  • Cuttings with the recipient's first name and sentence: until you give the spot away again or delete your Laubling.
  • Cuttings given away again (code, sender, time): until you delete your Laubling.
  • Greetings and the stamp on them: 30 days.
  • Greeting settings: until you change them or delete your Laubling.
  • Decorations and stamps: until you delete your Laubling.
  • Redeemed codes: as long as the Laubling exists, also after deletion, without a name.
  • Reports: 90 days.
  • Wishes: until we have read them, at most one year.
  • Delivery addresses for notifications: until you turn notifications off, delete your Laubling, the push service reports them as expired, or a sixth device is added.
  • Counters against abuse: in memory only, from a few minutes to at most about a day.
  • Web server access log: at most 7 days.
  • Browser entries: until you delete them.

13. Legal bases

  • Laubling, cuttings, greetings, decorations, codes and stamps (section 3): Art. 6(1)(b) GDPR. They are the game you want to use.
  • The recipient's first name, typed in by the sender: Art. 6(1)(f) GDPR, the sender's legitimate interest in sending a cutting to a person personally. The recipient can change the name right after hatching or have it deleted by email.
  • Access log and counters against abuse (section 5): Art. 6(1)(f) GDPR, secure operation and protection against abuse.
  • Report (section 10): Art. 6(1)(f) GDPR, protecting players, especially children.
  • Wishes (section 3.6): Art. 6(1)⁠(f) GDPR, our interest in developing Laubling according to its players’ wishes. Because nothing links it to you, a wish only contains personal data if you write something about yourself into it.
  • Support (section 8): Art. 6(1)⁠(b) GDPR for the payment you make, and Art. 6(1)⁠(c) GDPR for keeping the accounting records that tax law requires.
  • Notifications (section 6): Art. 6(1)(a) GDPR, your consent, which you can withdraw at any time.
  • Browser entries (section 4): § 25(2) no. 2 TDDDG (German Telecommunications Digital Services Data Protection Act), strictly necessary for the service you explicitly use.

14. Your rights

You have the right of access (Art. 15 GDPR), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), data portability (Art. 20) and objection to processing based on legitimate interest (Art. 21). You can withdraw consent (notifications) at any time with effect for the future (Art. 7(3)). To do so, write to the address in section 1.

Because there is no account, we can only recognise you reliably by your transfer code. Without it, we cannot clearly match some requests (Art. 11 GDPR); in that case we will tell you.

You can also complain to a data protection supervisory authority. The one responsible for us is:

Der Landesbeauftragte für den Datenschutz und die Informationsfreiheit Baden-Württemberg (State Commissioner for Data Protection and Freedom of Information)
Lautenschlagerstraße 20
70173 Stuttgart, Germany
www.baden-wuerttemberg.datenschutz.de

15. Changes

If Laubling starts storing something new, we update this policy beforehand.

As of 20 November 2026.