About DPPera

Who writes this

DPPera is written and built by Łukasz Głuch, working solo. Not a law firm, not a consultancy, not a team of analysts - one person who reads the source documents and writes down what they actually say.

The background is design and physical products rather than compliance consulting. I also run QRSona, a product built around QR codes on physical goods, which is where the practical side of this comes from: how a code survives a print run, what a label supplier actually needs to receive, and why an address that dies with a subscription is a problem when it is already sewn into a garment. Those turn out to be the parts of the passport conversation that most compliance material skips.

Write to me at contact@dppera.com. If an article on this site is wrong, that address is the fastest way to get it fixed.

Why this site exists

Information about the EU Digital Product Passport currently comes in two flavours. Vendor marketing, which wants you to believe the deadline is closer and scarier than it is. And legal analysis, which is accurate and unreadable if you are a twelve-person clothing brand trying to work out whether any of this applies to you yet.

DPPera is the missing third option: plain language, aimed at small and mid-size brands, with the regulation cited so you can check the claim yourself. There is also almost nothing on this subject written in Polish, which is why every article here exists in both English and Polish.

How the content is made

What DPPera offers

Independence

DPPera is self-funded. No investors, no vendor sponsorships, no affiliate commissions on the tools mentioned in articles. When an article names a competitor or a standard, there is no money behind the mention. DPPera does sell its own tool, and articles that touch it say so openly.

Where it runs

The site is built and hosted in the EU. Data handling is described in the privacy policy.