Companies / TRecs / Subprocessors
Subprocessors of TRecs
TRecs declares 8 subprocessors.
From the company's own list.Read the source
| Subprocessor | Purpose |
|---|---|
| Support and bug-report triage — tracking issues raised through the in-app feedback reporter and support requests. | |
| Consent management platform — banner, consent ledger, and cookie-inventory scanner. | |
| Application logs, error monitoring, real-user monitoring (RUM), performance traces. | |
| Application hosting, managed PostgreSQL, document object storage, Pub/Sub event bus. | |
| Bot and abuse protection on public forms (waitlist signup, login, password reset). | |
| Product analytics, feature flags, and consent-gated session replay. | |
| Identity (KYC) and business (KYB) verification of organisations and their users, including sanctions and PEP screening. | |
| Transactional email — account verification, waitlist confirmations, system notifications, support replies. |
Vendor's own statement, retrieved from the source URL on the date shown. StrataDB does not verify the underlying claim. Data sources.
See TRecs's full stack
Every vendor with its source and date, and an alert when TRecs adds or drops one. The same lookup works for any company.
- Every company and vendor, with its public source
- 100 API calls a month, plus MCP and the Chrome extension
- Work email only. No card, no sales call