The verified channel between law enforcement and companies
Requests land in one place, fake requests are blocked and replies can be automated.
Why we built Reqport
Reqport started over a coffee. A friend with years of experience in law enforcement described how slow and manual it is to request data from companies: emails, phone calls and weeks of waiting on answers that investigations depend on.
Erik Vesterlund recognised the other side of it. As COO of a regulated exchange, he had handled the same requests by email, verifying each one by hand and tracking every deadline, with no easy way to tell a real request from a fake one. The process was failing both sides.
Erik Obitz joined soon after, with 25+ years of experience in critical IT infrastructure, several of them focused on secure data exchange. Together they started building Reqport.
Law enforcement
Sends a request securely through Reqport.
Reqport
Verifies the sender, encrypts the content and structures the request.
Companies
Receive the request in one place and reply securely, manually or automated.
The founders
Erik Vesterlund
CEO and co-founder
8+ years in fintech and financial crime compliance, most recently as COO of a regulated crypto exchange, where he handled law enforcement requests.
LinkedIn
Erik Obitz
CTO and co-founder
25+ years in IT. Former chief architect at Swish, with architecture roles at the Swedish central bank, the national grid operator Svenska kraftnät and several large enterprises.
LinkedInWhat we hold ourselves to
Verified at the gate
Only verified officers can send requests. Everything else is stopped before it reaches your team.
Confidential by design
Requests are processed in a confidential computing environment. Not even Reqport can see the contents.
Fast for both sides
Structured requests and automated replies shorten the time from request to answer from weeks to minutes.
We want every legitimate request answered in seconds, and every fake one stopped.
See how Reqport works.
Request a demo