Trekport's data processing model
Trekport Studio runs entirely on customer infrastructure. Source database credentials, schemas, table data, and migration output never leave the customer environment. As a consequence, Trekport is not a Data Processor for your migration data under most regulatory frameworks (GDPR Art. 28, CCPA, etc.).
We are a Data Controller only for the limited information collected via trekport.sh (contact form, download lead capture) and the license-validation traffic from Trekport Studio.
Subprocessors
For website operations and customer communications, we use:
- Vercel. Hosting (US).
- Resend. Transactional email (US).
- Cloudflare. Bot protection (global).
- PostHog. Product analytics (US).
- Sentry. Error monitoring (US).
Custom DPA
Enterprise customers requiring a counter-signed DPA, BAA, or equivalent should contact us. The Trekport team will work with your legal team to put one in place.

