WildComb← Simulation
ImprintTermsRight of withdrawalPrivacyDisclaimerSourcesWithdraw from contract

Privacy Policy

Version: 21 November 2026

1. Controller

The controller within the meaning of the GDPR is WildComb (sole proprietorship), owner Gor Davidovic Gevorkjan, Teichmummelring 65, 12527 Berlin, Germany, email hello@wildcomb.app. No data protection officer has been appointed because there is no legal obligation to do so.

This policy covers wildcomb.app and the simulations run there (WildComb Simulation). ElternPlan (elternplan.app) is governed solely by the privacy policy published on that site.

2. Principle

WildComb processes as little data as possible. There are no ad trackers, no analytics cookies and no sale of data. The simulations work without an account. What you enter is not stored, except that Pro simulations and beams (see 7) are sent to the server and discarded immediately after the response.

The game T.O.U.G.H. runs entirely in your browser. It stores no name and no date of birth. It stores a game state in two cases only: on your device at the limit of the trial life (see the next paragraph), and with WildComb if you yourself save a life under “My lives” with Pro access (see the two paragraphs after it). The look back at the end of a life, that is your leanings in the game, how others saw you and the sentences on where you could start, is likewise computed only in your browser, not stored and not transmitted to WildComb. No profile is built from it, not on the server either. If you choose the start “From today”, what you enter for it (age, family, ages of the children, your own net income, account, funds, home, debts, housing, place of residence) likewise stays only in your browser. It is not sent, not counted and not stored. During a round the game sends only the events of the game listed below to the server, without any identifier. When the page is closed the round is gone, except at the limit of the trial life.

Trial life (without Pro access). Without Pro access and without an account you play one fixed trial life in T.O.U.G.H., the same for everybody. Nothing is asked before the start, neither an email address nor a name. When the trial life reaches its limit, the game keeps the game state in your browser’s local storage (localStorage) under a single entry: your decisions on the cards of the trial life and the game values that follow from them. The entry carries no identifier, does not leave your device and is not transmitted to WildComb. Its only purpose is that your life can go on at exactly this point after you acquire Pro. It is strictly necessary for that, and no consent is required (§ 25 (2) no. 2 TDDDG). The account page reads the entry to show you the way back into the game after a purchase. If you play the life on with Pro or play the trial life again, the game deletes the entry itself. You can delete it at any time by deleting the site data of wildcomb.app in your browser.

Cards seen. So that a new life in T.O.U.G.H. shows other cards than the last ones, the game keeps a single entry in your browser’s local storage (localStorage) with the short names of the cards you have already seen, at most those of the last three lives. The entry carries no identifier and no decision, does not leave your device and is not transmitted to WildComb. It is strictly necessary for that, and no consent is required (§ 25 (2) no. 2 TDDDG). You can delete it at any time by deleting the site data of wildcomb.app in your browser.

My lives (Pro access only). At the end of a life you can keep it in your account with the button “Save this life”. Only this click transmits the record to the server. Stored per life: the date, the chosen length, the kind of start (random start, headwind, time travel or “From today”, without its values), the random number of the start, your decisions per card (identifier of the card and the way chosen), game values per phase of life (assets, debts and account rounded to a thousand euros, months below zero), your position at the end, the five leanings of the look back and the places where your twin decided differently in the game, and your sex only if you state it in your account yourself. Never stored: the life situation a life can begin in (such as immigration, illness, care in the family, basic income support), decisions on cards that only occur in such a situation, the values of “From today” and free text. At most 30 lives per account. The purpose is the Pro feature “My lives”: finding your lives again and seeing your leanings across several lives. Legal basis: Art. 6 (1) (b) GDPR (contract). Storage location: Upstash Redis, data centre Frankfurt, linked to your account. You delete single lives or all of them under “My lives” in your account. They are also deleted when your account is deleted. Until then they remain stored.

Comparison values from “My lives”. Once a day sums are counted over the saved lives: how often a way was chosen on a card and how many lives lie high, medium or low on each leaning, by sex only where it is stated in the account. Only the result is stored, without account, date or random number, and every group of fewer than 50 lives is discarded. No inference about a person is possible from it. Legal basis: Art. 6 (1) (f) GDPR (legitimate interest in showing players comparison values from lives played). You can object to the count at any time with the switch “My lives count in the comparison values” in your account. Once switched off, your lives no longer count from the next count on.

3. Hosting and server logs

The site is hosted by Vercel Inc. (USA). On access Vercel processes technically necessary data (IP address, time, requested URL, user agent) in server logs that are deleted after a short period. Legal basis: Art. 6 (1) (f) GDPR (operation and security). Vercel is certified under the EU-US Data Privacy Framework. Standard contractual clauses are in place in addition.

If you come to NextGen through a link from ElternPlan (elternplan.app), the requested URL may carry your child’s year of birth or the year of the expected due date, as a four-digit year. The year only sets the age the dial on the page starts at. The page then removes it from the address. It is not stored, counted or passed on. It can appear only in Vercel’s server logs, which are deleted after a short period, like every requested URL.

4. Cookies

WildComb only sets technically necessary cookies that require no consent (§ 25 (2) German TDDDG):

  • language and currency, 12 months
  • sign-in session, 30 days, only when signed in

Hint about the app icon. Once you have seen a first result in the simulator or in Beam, a small hint may appear at the bottom offering to put WildComb on your home screen as an icon. If you choose “Not now” or “Got it”, the page keeps a single entry with the time of that choice in your browser’s local storage (localStorage), so that the hint does not come back for 30 days. The entry carries no identifier, does not leave your device and is not transmitted to WildComb. It is strictly necessary for that, and no consent is required (§ 25 (2) no. 2 TDDDG). You can delete it at any time by deleting the site data of wildcomb.app in your browser.

There is no cookie banner because there is nothing to consent to.

5. Anonymous country statistics and where a visit came from

To see which regions show interest, WildComb increments a counter for the country of the request when you arrive on a page from outside this website (from a search, a link, a bookmark or the typed address). Moving between the pages of this website does not count. Whether a request comes from outside is something your browser states itself with every request. Nothing is stored in your browser for this, no cookie and no other storage. The hosting derives the country from the network zone. The IP address is not stored. Only the country code and a number are stored. No person can be identified. The statistics can be viewed at /simulator/stats. That page is part of Pro access. The anonymous usage counters described in section 6 are separate from this and can be viewed by nobody.

At the same moment, and under the same rule, WildComb increments a second counter for where the visit came from. To do so the server reads the address of the page you came from (the referrer your browser sends) and assigns it to exactly one of four words: Instagram, search, direct or elsewhere. Only that word and a number are stored. The address itself is not stored, not logged and not passed on. It exists for the length of the assignment and is then gone. A search term, a profile or a single page therefore never reaches WildComb’s store. The legal basis is Art. 6 (1) (f) GDPR, WildComb’s legitimate interest in knowing which route to this service is used at all. Retention: 400 days per daily counter, after which it falls away by itself.

Where you arrive over a partner’s link that carries the addition “?von=” with that partner’s label, WildComb also increments a counter for that label when the page first loads. The page then removes the addition from the address at once, so that a reload does not count again. Nothing is stored in your browser for this, no cookie and no other storage. All that WildComb stores is the partner’s label and a number, nothing about you. The legal basis is Art. 6 (1) (f) GDPR, WildComb’s legitimate interest in knowing which partnership brings visitors. Retention: 400 days, after which the counter falls away by itself.

Where you arrive over a short link of the form “wildcomb.app/m/” with a partner’s word, the server counts that request under the word and leads you on to the target page. Where you open an action link of the form “wildcomb.app/a/” with the name of an action, the server counts the request under that name. In both cases nothing is stored in your browser, no cookie and no other storage. All that WildComb stores is the word or the name and a number per day, nothing about you. Where you unlock a test access over an action link, this happens with your account: WildComb creates a test code for it and notes, under a checksum derived from your account identifier that cannot be traced back to your email address, that this account has received the access of this action. In this way each account receives it only once. The legal basis is Art. 6 (1) (f) GDPR, WildComb’s legitimate interest in knowing which partnership and which action brings visitors, and in handing out a limited test access only once per account. Retention: 400 days, after which the counters and the note fall away by themselves.

6. Anonymous usage counters

To see which steps of the product are actually used, WildComb counts thirty-four predefined events:

  • page view
  • view of a public lesson page
  • click on the Pro notice on such a page
  • completed simulation
  • beam created
  • beam shared
  • shared link opened
  • simulation after a shared link
  • reply created
  • Pro page viewed
  • checkout started
  • purchase completed
  • click on the button to ElternPlan on the NextGen page
  • click on “Back to the simulation” on the NextGen page
  • view of a search page of a tool
  • click on the button into the tool on such a page
  • a Pro lock coming into view (a locked control or area with the mark “Pro”)
  • click on a Pro lock, which opens the note about Pro
  • click on “Unlock Pro” in that note
  • view of the Atlas
  • choice of an asset in the Atlas
  • opening a crisis on the time axis of the Atlas
  • switching on a layer in the Atlas (money supply, balance sheets, policy rate)
  • opening the look back at the end of a life in T.O.U.G.H.
  • sharing the look back as a card
  • a click on “Another life” after the look back
  • saving a life under “My lives”
  • opening the page “My lives”
  • switching off “My lives count in the comparison values”
  • a click on “The same life to a friend” in T.O.U.G.H.
  • starting a life from such a link
  • start of the trial life in T.O.U.G.H.
  • reaching the limit of the trial life
  • purchase of Pro after reaching that limit in the same browser, counted on the click on “Play on” with which the trial life is continued with Pro

For each event it is also noted which of nineteen predefined entry points the page was opened through (for example the front page, a story from the area Money IRL, a shared link, a shared link from a beam that came about through Instagram, a search page, from ElternPlan after a finished plan or from the plan email, or directly). For the two events of the search pages it is also noted which search page it was, as a name from a fixed list. For the three events of the Pro lock it is also noted at which place in the product the lock stood, likewise as a name from a fixed list. All that is stored is one number per day, event and entry point, and for the steps named in the next paragraph also one number per day, step and country. Neither an IP address nor an identifier, a cookie or any of your inputs are stored. None of your inputs go into these counters. So that a purchase, too, is counted under its entry point, the open page keeps the entry point of the visit in your browser’s memory until you leave or reload it, with no cookie and no other storage of your browser. When you buy, it goes to the payment service Stripe (see 11), where it stays with the payment. WildComb only increments the number per day and entry point, nothing of it on your account. No person can be identified from this. Legal basis: Art. 6 (1) (f) GDPR (legitimate interest in a data-minimising measurement of reach and function). Storage: Upstash Redis, Frankfurt data centre. Retention: 400 days. These numbers are not public.

For the following steps WildComb also counts the country: simulation run, beam created, purchase page viewed, purchase completed and account created, and in addition the three events of the Pro lock per place, the three steps of the trial life in T.O.U.G.H. and where the visit came from under section 5 as one of four words. The hosting derives the country from the request. For a purchase it is the country of the billing address. Only the word, the country code and a number are stored, neither IP address nor identifier nor cookie. No person can be identified from this. Purpose: to see in which regions the product is not only visited but used. Legal basis: Art. 6 (1) (f) GDPR. Storage: Upstash Redis, Frankfurt data centre. Retention: 400 days per daily counter.

For the way through the tools WildComb also counts seven steps of a visit: entry, first tool opened, first dial moved, another tool opened, view of the Pro page, click on the purchase button and completed purchase. Counted beside them are the change from one tool to the next, the place where the page is left, and for the line with the next step under a result whether it came into view and whether it was clicked. Five features are recorded with the steps, each as a word from a fixed list: the tool of the entry or the topic named by a link from a post of WildComb, the stage of life such a link names, the identifier of that post or without such a link a fixed word for the origin (“direct”, “search”, “Money IRL” for a visit through a story from that area of wildcomb.app or, for a visit through one of the links in WildComb’s Instagram profile, the target of that link, see 7a), the region of the request (USA, Canada, Germany, United Kingdom, rest of Europe or rest of the world) and an age band. The hosting derives the region from the request, no country is stored here. An age band (18 to 24, 25 to 34, 35 to 44, 45 to 54, 55 to 64 or 65 and over) only comes about if you move the dial for your age in the Beam yourself. Your browser forms it from that age and transmits the band alone, never the age. For an age under 18 no band is formed, in every other case it reads “unknown”. The open page keeps these features in your browser’s working memory until you leave or reload it, without a cookie and without any other storage of your browser. No way per visit is recorded: all that is stored is one number per day and field, neither IP address nor an identifier of your person, neither country nor amount nor exact age. WildComb counts the purchase from what lies with the payment anyway under this section (entry point) and under section 7a (identifier of the post or target of the link in the Instagram profile), and from the region of the billing address. When you buy, the tool of the entry or the topic of such a link also goes to the payment service Stripe (see 11) as one word from the fixed list of the seven tools, where it stays with the payment, so that the purchase is counted under a tool. If the visit has neither such a tool nor such a topic, nothing is transmitted for it. The age band does not go to Stripe. No person can be identified from this. Purpose: to see which topics reach whom and at which place a visit ends. Legal basis: Art. 6 (1) (f) GDPR. Storage: Upstash Redis, Frankfurt data centre. Retention: 400 days per daily counter. The sums over all days stay stored for good, without a day.

On the front page of wildcomb.app WildComb also counts how often the page was shown, how often the figure of the question of the day was revealed, how often a vote was cast and how often a way to a product, to a reel or to Instagram was clicked, each as one number per day and fixed field. For a vote only the answer chosen (A or B) is counted as a sum per question. Neither an IP address nor an identifier nor a cookie is stored, and nothing is stored in your browser for it. No person can be identified from this. To limit load, the same limit per requesting party applies as described in section 7. Purpose: to see whether the front page leads to the products. Legal basis: Art. 6 (1) (f) GDPR. Storage: Upstash Redis, Frankfurt data centre. Retention: 400 days per daily counter, 40 days per vote.

7. Beam

At /simulator/beam you can issue a beam: a card that says in which year a goal you chose would be reached under a return assumption you chose. The result is first computed by your browser. Only when you issue the beam are your inputs sent to the server once: age, goal amount, starting capital, monthly contribution, assumed return, currency and language, and for Pro access additionally the tax region you selected.

At /simulator/nextgen you can issue the same card for a child. Only when you issue the card are your inputs sent to the server once: the age of the child in whole years, the monthly amount, the amounts given once a year, a single amount at the start, the yearly rise, the assumed return, currency and language. The name, date of birth and sex of the child are neither collected nor transmitted. What comes back is only the year of birth, the year of the eighteenth birthday, the amount, the assumed return, currency and language. Everything else in this section applies to this card unchanged.

The purpose is to repeat the calculation on the server and to sign the result. Without that signature anyone could put figures of their choosing under the WildComb brand and pass them off as a simulation by WildComb. Legal basis: Art. 6 (1) (f) GDPR (legitimate interest in the authenticity of cards distributed under the WildComb brand). For Pro users additionally Art. 6 (1) (b) GDPR (contract).

Your inputs are used for this one calculation and discarded afterwards. They are not stored, not logged and not passed on to anyone. They appear in no error message and in no operational alert to WildComb. They are transmitted in the body of the request and not in the address line, which the host records in its server logs (see 3).

What comes back is only what a card is allowed to say: age, goal amount, arrival year, year of issue, assumed return, currency and language, and for Pro additionally the share of the simulated runs that reach the goal in the arrival year and the arrival year after taxes, costs and inflation. The starting capital and the monthly contribution are in neither the link nor the picture. The same values are in the link in plain sight so the card can be drawn from them. Whoever receives the link can read them. Whether and to whom you pass the link on is yours alone to decide: WildComb sends nothing, asks for no recipient address and stores no recipients.

To limit load WildComb counts requests per requesting party. For that a hash is formed of your IP address together with a secret known only to WildComb and shortened to 16 characters. All that is stored is this value, as the key of a counter that expires after an hour at the latest. Your IP address itself is not stored for this. The picture of a card is not limited per requesting party but per card, because the same card is fetched by many servers at once when it is shared into a group.

Recipients: Vercel Inc. (hosting, see 3) and Upstash Inc. (counters and rate limiting, Frankfurt data centre, processor with standard contractual clauses). That a beam was issued or shared additionally increments the anonymous counters under section 6, into which none of your inputs go. The only exception is the age band under section 6, if you move the dial for your age yourself.

7a. Instagram

Comments under the posts of WildComb’s Instagram account are answered automatically. If you state your age under one of these posts, you thereby request your beam, an example calculation for your age. The reply with the number appears publicly under your comment, and the beam comes once by direct message. It contains your example calculation with the standard values and the link to your beam. Anyone under 18 gets no number and no direct message. Only people who commented under these posts or wrote to WildComb first are written to.

Some posts do not ask for your age but for a guess: the age at which you think you would be financially free. If you state a number under such a post, a public reply says that your guess is noted, and the link to WildComb’s game comes once by direct message. There is no example calculation in this case. If you then state a second number under the same post, it counts as your result from the game and is confirmed publicly. So that the second number is recognised, your first number is stored together with the hash described two paragraphs below for 30 days.

For this WildComb receives from Instagram, through its official interface, the comment with its identifier, the identifier of your account and the text. Stored for 30 days are the identifier of the comment, depending on the post your age or your guess as a number if you state one, the detected language, the time, the reply template used and whether the reply and the direct message were sent. Your user name is not stored. The text of the comment is stored only where it has to be read by hand, that is a question no template fits, or a comment marked as spam or abuse. Then, too, for 30 days at most.

The identifier of your account is not stored in plain text but as a hash formed with a secret and shortened to 16 characters. It serves only to give at most two automatic replies per person and post and to ask for the age only once, and it expires after 30 days. After a direct message it is kept for seven days so that your reply can be answered once. The content of your messages is not stored. In addition it is counted per day how many comments, replies and direct messages there were, as a number only. Retention of these numbers: 400 days.

If you write “Stop” as a comment or as a message, you no longer get automatic replies. For this the hash described in the previous paragraph is kept for one year.

The link in the direct message contains your age, the amount of the example calculation, the standard values (5,000 starting capital, 200 a month, the return of the S&P 500 over the past ten years as a historical value, no forecast), language, currency and the entry point “ig”. Like every address it appears in the server logs described in section 3. If you open it, sections 6 and 7 apply.

The links in the profile of WildComb’s Instagram account lead directly to the front page of wildcomb.app or to a tool. They carry no identifier of a post, only a fixed word for their target (front page, Simulation, Beam, T.O.U.G.H. or NextGen). If you open a page through such a link, WildComb counts the visit under this word as described in section 6. The open page keeps the word in your browser’s working memory until you leave or reload it, without a cookie and without any other storage of your browser, and takes it out of the address shown. If you go on from the front page to a tool, the page hands the word on in the address of that one step, where it is taken out of the address shown again. If you buy Pro in the same visit, the word goes to the payment service Stripe (see 11), where it stays with the payment, so that the purchase is counted under this link. WildComb stores only one number per day and field, nothing of it on your account. No person can be identified from this. The address wildcomb.app/ig, the former target of the link in the profile, redirects to the front page and counts like the link to the front page. The list of posts and the field for the age that stood there no longer exist. Legal basis: Art. 6 (1) (f) GDPR (legitimate interest in knowing which links lead to visits and purchases). Storage and retention: as in section 6.

Links in replies, direct messages and stories of WildComb’s Instagram account carry the identifier of the post and the kind of link (reply, direct message or story). If you open a page through such a link, a counter per day, post, kind of link and country is incremented. The hosting derives the country from the request. Your IP address is not stored for this. If you create an account or buy Pro in the same visit, the counter of new accounts or of purchases and the amount of the purchase are incremented for the same post. For this the open page keeps the identifier in your browser’s memory until you leave or reload it. No cookie and no other storage of your browser is used for it. When you buy, the identifier and the country go to the payment service Stripe (see 11), where they stay with the payment. WildComb stores only one number per day and field, nothing of it on your account. No person can be identified from these counters. Legal basis: Art. 6 (1) (f) GDPR (legitimate interest in knowing which posts lead to visits and purchases). Storage: Upstash Redis, Frankfurt data centre. Retention: 400 days per daily counter.

Purpose: to answer your request, made publicly under WildComb’s posts. The public replies under these posts also make WildComb’s service known. Legal basis: Art. 6 (1) (f) GDPR (legitimate interest). You can object at any time (Art. 21 GDPR), with “Stop” as above or by email to hello@wildcomb.app. How to ask for the deletion of your Instagram data is set out on the page Deletion of your Instagram data.

Recipients: Meta Platforms Ireland Limited operates Instagram and processes comments, replies and messages as a controller in its own right under its own terms, including in countries outside the EU. Information on this: privacycenter.instagram.com/policy. At WildComb the data is held by Upstash Redis, Frankfurt data centre (see 10), and Vercel provides the hosting (see 3).

Statistics (Insights): For the statistics of its Instagram account WildComb is a joint controller with Meta Platforms Ireland Limited (Art. 26 GDPR), under Meta’s addendum for Insights. Under it Meta takes primary responsibility for this processing and for your rights as a data subject. WildComb receives only aggregated figures per post, nothing about individual people. The basis is Meta’s Page Insights Controller Addendum: https://www.facebook.com/legal/terms/page_controller_addendum. The lead supervisory authority is the Irish Data Protection Commission.

7b. Monthly look

If you enter your email address under a Beam, you receive a mail with a confirmation link. The sign-up only holds once you press the button on the page behind that link (double opt-in). Without confirmation the details are deleted after 48 hours. After that you receive a mail once a month with your number, worked out again from the values of your Beam. For this only your email address, your language, the input values of the Beam (age, goal, starting capital, monthly amount, return, currency) and the moment of the confirmation are stored, under a key formed from the address that does not contain it in plain text. Whether you open a mail is not recorded. One click in every mail unsubscribes you, and the details are then deleted at once.

Legal basis: your consent, Art. 6 (1) (a) GDPR, revocable at any time with effect for the future. Sending via Resend (see 12). Storage: Upstash Redis, Frankfurt data centre.

8. Licence codes

A licence code unlocks Pro access for the term recorded on it. For every code issued the following is stored: a hash of the code, a label for the batch, the kind of code, the term in days or months, the date of issue, the status and, where the code is time-limited, the date of expiry. A bought code is not time-limited and does not expire. The code itself is not stored. When a code is redeemed, the time of redemption and a hash of the redeeming account are added. The same hash is also stored once together with the batch label, so that the account knows which round of issue it belongs to. The label is a name chosen by WildComb, such as “probelauf”, and says nothing about you.

Purpose: a code must be redeemable exactly once, and misuse must be detectable. Legal basis: Art. 6 (1) (b) GDPR (contract) and Art. 6 (1) (f) GDPR (legitimate interest in a single redemption). Storage: Upstash Redis, Frankfurt data centre (Upstash Inc., processor with standard contractual clauses). Retention: until one year after the code is redeemed or blocked. For as long as a bought code has been neither redeemed nor blocked, the entry stays, because the code does not expire and could not be redeemed without that entry. Time-limited codes issued without payment, for instance for testing, are deleted one year after they expire.

Where an account that redeemed such a code later buys Pro access, a number for the batch label is incremented, once per account. So that the same purchase is not counted twice, the hash of the account under the previous paragraph is stored once as a marker. Only the sum per label is visible, not which account bought. Purpose: to know whether the codes handed out lead to purchases. Legal basis: Art. 6 (1) (f) GDPR (legitimate interest in the effect of one’s own spending). Retention: the marker for 400 days, the number per label until the batch is deleted.

8a. Licence batches for companies

Where a company buys a batch, the following is stored: the company name, the date of purchase, the number of licences, the Stripe invoice number and the email address the reports are to go to. The billing address and the VAT identification number are collected by Stripe for the invoice, where WildComb can see them (see 11). The names of employees are not collected, and WildComb does not learn who redeemed a code either: for every redemption only the hash of the redeeming account under section 8 is stored.

The report to the company contains sums only. Which code was redeemed when is not given to the company, not even on request, and where there are one or two redemptions the report says “fewer than three” instead of the number. The reason is the protection of the people redeeming the codes: with a small batch, a number with a date would allow conclusions about individual people.

Purpose: performance of the contract and the agreed report. Legal basis: Art. 6 (1) (b) GDPR (contract) and Art. 6 (1) (f) GDPR (legitimate interest in information about one’s own batch). Storage: Upstash Redis, Frankfurt data centre. Retention: for as long as codes from the batch are open, then the periods of commercial and tax law. The reports can be stopped at any time using the unsubscribe link in every report, including through the unsubscribe function of the email client.

9. Feedback

At /simulator/feedback you can answer three questions. Every answer is voluntary and may be left empty. No name, no address and no way of replying to you is asked for. For the answer to a feedback request, section 9a applies instead.

Your text is not stored. It is transmitted once to the owner as an email, over the mail service Resend, and is not kept in WildComb’s systems afterwards: not in a database, not in a file and not in a log. What remains is one number per day and batch, from which no person can be identified. If you have redeemed a licence code, the batch label under section 8 is transmitted with it. Your email address and your account identifier are not. Please do not write personal details into the fields, as their content can no longer be controlled once it has been transmitted.

Purpose: to improve the product from what readers say. Legal basis: Art. 6 (1) (f) GDPR (legitimate interest in feedback on one’s own product). Recipient: Resend as a processor under section 12. No transfer to a third country takes place for this. The message is deleted from the mailbox of the owner once it has been read. Retention at WildComb: none, apart from the counter named above, which expires after 400 days.

9a. Feedback requests and voices

WildComb keeps a list of the accounts that have or had a Pro licence. For each account it notes whether and when feedback was asked for and in which way (by email, in person or with a line in the tool), the state of the request (not asked, asked, feedback received, declined) and a classification by the owner of how he knows you (family, friend, tester, buyer not known to him). To give a reminder of a request, it is evaluated whether and since when lives are saved under “My lives” in your account (see 2). In addition, the day on which you first ran a Pro calculation in the simulation is noted for your account. Only this one date is noted, not your inputs, not a result and no later calculations. Purpose: to ask for feedback and to ask nobody more than once. Legal basis: Art. 6 (1) (f) GDPR (legitimate interest in feedback on one’s own product without repeated requests). Retention: as for the account (see 10).

You receive a request by email only if you have consented to it, and at most once. Legal basis: Art. 6 (1) (a) GDPR. You can withdraw the consent at any time with effect for the future, in your account and through the link in the request. Sent via Resend (see 12).

If you answer a request in the form, the following is stored: your answers to the questions, your first name if you give one, the language, the date and the version of the note above the send button. By sending, you consent to your answer being shown with your first name on wildcomb.app and in posts by WildComb, for instance on Instagram, and to grammar or language mistakes being smoothed out without changing the meaning. Legal basis: Art. 6 (1) (a) GDPR. Only the first name and the text are shown, without surname, email address or classification, and only once the owner releases the answer. Nothing is shown without a first name. For this, your original answer, the wording shown and the date of release are recorded.

You can have your answer deleted at any time, on the page “Your voice” through the link in the request or signed in, or by email to hello@wildcomb.app. The deletion takes effect at once: the answer disappears from the list from which the website and posts take the voices they show. Posts in which it was shown are removed once the deletion is received. Retention: an answer that is not released is deleted twelve months after it was received. A released answer stays until you withdraw or until the account is deleted. Storage: Upstash Redis, Frankfurt data centre.

10. Account and sign-in

For Pro access the following is stored: your email address, the account creation time, the expiry date of Pro access, the Stripe payment reference and your preferred language. Sign-in links are valid for 15 minutes and deleted afterwards. Legal basis: Art. 6 (1) (b) GDPR (contract). Storage: Upstash Redis, Frankfurt data centre (Upstash Inc., processor with standard contractual clauses). Retention: until you ask for the account to be deleted, at the latest three years after the last Pro access expired.

11. Payment, billing country and consent log

Payments are processed by Stripe Payments Europe Ltd. (Ireland). Stripe receives your payment details, your email address and your billing address and processes them as an independent controller, including for fraud prevention. WildComb receives no full card data from Stripe, only payment status, amount, currency, reference and the country of your billing address. Legal basis: Art. 6 (1) (b) GDPR (contract).

The country of your billing address is stored in your account as evidence of the place of supply for VAT purposes and to monitor the distance-selling thresholds (§ 3a (5) German VAT Act, Art. 24b VAT Implementing Regulation). Legal basis: Art. 6 (1) (c) GDPR (legal obligation). In addition WildComb keeps an anonymous counter of sales per country and year that contains no personal data.

To evaluate turnover by region, WildComb reads the country of the billing address from the payments at Stripe and forms sums per region. Nothing is stored in addition for this and no further detail about you is read. Legal basis: Art. 6 (1) (f) GDPR (legitimate interest in evaluating its own turnover).

Your consent to immediate performance and your acknowledgement of losing the right of withdrawal (§ 356 (5) BGB) are logged with a timestamp and kept together with the payment record for three years (Art. 6 (1) (c) and (f) GDPR, burden of proof and standard limitation period). Stripe's privacy notice: stripe.com/privacy.

Consent to a feedback request at purchase

At the buy box you can tick, voluntarily, that you agree to be asked for feedback. The box is not ticked in advance and has no effect on price or purchase. If you tick it, your consent with its time and the version of the wording is passed to WildComb with the payment data at Stripe and stored in your account. Purpose: to ask you for feedback by email at most once. Legal basis: Art. 6 (1) (a) GDPR. You can withdraw the consent at any time with effect for the future, in your account and through the link in the request. A withdrawal is noted with its date, so that no request goes out. Retention: as for the account (see 10). The order confirmation contains no request for feedback.

Reminder before the end

If a paid yearly licence is about to end, a reminder goes to the address of your account 30 days and 3 days before and on the day it ends, as a notice about your contract. For this the account notes which reminder has been sent. “No more reminders” in every reminder stops them at once. Legal basis: Art. 6 (1) (b) and (f) GDPR.

Withdrawal via “Withdraw from contract”

If you declare a withdrawal via the online function, your name, email address, your optional details (order reference, message) and the time of receipt are stored in order to confirm receipt and process the withdrawal (Art. 6(1)(b) and (c) GDPR). Storage: Upstash Redis (see 10). Retention: three years (regular limitation period). The acknowledgement of receipt is sent via Resend (see 12).

Blocklist in case of abuse

After a chargeback, or from the second refund of the same account onwards, a hash of your email address formed with a secret is stored, so that no new purchase can be made with the same address. The address itself is not stored for this. The purpose is protection against repeated abuse of the payment route, the legal basis is Art. 6 (1) (f) GDPR (legitimate interest). A refund that WildComb issues itself because of a sales country it cannot serve creates no entry. The retention period is three years, and a block is lifted on request to hello@wildcomb.app.

12. Email

Sign-in links and order confirmations are sent via Resend Inc. (USA, processor with standard contractual clauses). Recipient address, subject, content and delivery status are processed. WildComb sends no marketing emails. Reminders before a paid yearly licence ends: see 11, “Reminder before the end”.

13. Market data

Market data and official statistics are fetched by the server or by a scheduled run from the offices named under sources. No user data is transmitted to them in the process.

14. Your rights

You have the right of access, rectification, erasure, restriction, data portability and objection (Art. 15 to 21 GDPR) and the right to lodge a complaint with a supervisory authority, e.g. the Berlin Commissioner for Data Protection and Freedom of Information. Account and data are deleted on an informal email to hello@wildcomb.app, unless retention obligations apply (invoice and tax data: ten years, § 147 German Fiscal Code).

Data subjects in the United Kingdom have equivalent rights under the UK GDPR and the Data Protection Act 2018 and may contact the Information Commissioner's Office (ICO). For residents of the United States: WildComb does not sell personal data and does not share it for advertising purposes.

15. Security

Transmission is encrypted only (TLS). Accounts have no password, so no password leaks. Sign-in and calculation endpoints are rate limited.

Simulation, not advice. Results are mathematical projections from your own inputs and historical data. They are not a forecast and not investment, tax or legal advice. Past performance does not predict future returns.

A product of WildComb
ImprintTermsRight of withdrawalPrivacyDisclaimerInstagramWithdraw from contract