Bug Bounty

If you find an error in the shop and you are the first to report it through a support ticket, we credit €25 to your wallet as a reward. You choose when to spend that balance.

Why your report helps

We automatically run many shop flows from sign-in through to the order. Those tests follow fixed paths. They do not see every variation: a different device, a different browser, another language, another balance, another cart, a specific batch, or a combination that only shows up for you.

That is where we rely on what you send us. You see the shop the way it arrives for you. That catches errors the fixed tests never hit.

What we reward

A concrete shop error we can follow. That includes a function that does not work as intended, a break in checkout, and display errors.

A display error is text that overlaps or gets cut off, the wrong language, a missing image, a document that does not match the batch on screen, or a layout that breaks differently on a phone than it should. The report still matters when the button itself still works.

We reward the first report of that error. Later tickets about the same error do not receive credit.

An example

For 7-Hydroxy Mitragynine Powder, the lab test of an older batch was stored as the active test. The product page did not show the test for the current batch. We wrote up what happened here: Wrong lab test: 7-Hydroxy Mitragynine Powder, batch 10/26.

An automated test does not see that kind of mix-up in every content variant. If something on a page does not belong together, batch, file, price, text, or image, that is a report we need.

How to report it

  • Sign in to your account. The ticket and the credit are tied to that account.
  • Open a support ticket.
  • Write what you expected, what happened instead, and what you did just before the error.

If you are not into the technical side

A screenshot or a screen recording is enough in most cases. Add a short description of what led to the error: which page, what you clicked, and what you expected to see.

You do not need to send more than that. We retrace the flow ourselves afterwards.

If you are comfortable with the technical side

Then it also helps to see what the page returns in the background. Open the browser developer console and attach the relevant parts to the ticket.

  • Error messages from the console
  • the request involved, for example an Ajax call: URL, status code, and the response
  • browser and approximate window size, when the error only happens there

Leave out passwords, full session cookies, and payment details. The status code and the server response are enough.

What you receive

Once we confirm the error and it has not been reported before, we credit €25 to your wallet. That is the reward. You decide on which order you use the balance.

What is not included

  • Questions about products, orders, or shipping
  • Requests for new features
  • A second report of an error we already know
Only necessary cookies accepted

You have decided to accept only the necessary cookies - a choice that we fully understand, as protecting your privacy is our highest priority.

We respect this decision and therefore do not use additional tracking tools such as Google Analytics or similar analysis services. This means you can use our website without additional data being collected or passed on to third parties.

Your trust in the responsible handling of your data is important to us, and we do everything we can to offer you a safe and data protection-friendly visitor experience.