Under GDPR Article 28, we are required to tell you, in advance, who we engage as a sub-processor and to give you a fair chance to object before a new one starts processing your data. The table below is the canonical list. We update it whenever we add, replace, or remove a vendor, and we email everyone subscribed to the change list at least 14 days before any new vendor goes live.
The companies we trust with customer data.
A complete, public list of every third-party service that processes personal data on Veracly's behalf, what they do, where they run, and the data they touch.
Last updated: 2026-08-21
Effective date is the date the vendor began processing personal data on our behalf. For vendors already engaged when Veracly was first built, we show 27 April 2026, the date of the earliest record in our source history. Prighter EU Rep GmbH and Prighter Ltd were added to this list on 21 August 2026; they have acted as our Article 27 representatives since 30 April 2026 and were omitted from earlier versions of this page in error.
Former subprocessors
Vendors we have stopped using. We keep this record rather than deleting the row, because a controller needs to establish when a vendor stopped processing their data and when that vendor's stored copy was destroyed. A decommissioned service that still holds a database is still a subprocessor, so the deletion date is the one that matters.
| Vendor | Role | Traffic ceased | Copy deleted |
|---|---|---|---|
| Amazon Web Services, Inc.United States | Object storage (report PDFs, evidence) | 2026-07-18 | Deletion in progress |
| Anthropic, PBCUnited States | AI inference (report wording) | 2026-07-18 | Deletion in progress |
| Railway Corp.United States | API and worker hosting | 2026-07-18 | 2026-07-19 |
| Supabase, Inc.United States | Managed PostgreSQL (application database) | 2026-07-18 | 2026-07-19 |
| Upstash, Inc.United States | Managed Redis (job queue) | 2026-07-18 | Deletion in progress |
| Vercel Inc.United States | Web hosting and edge network | 2026-07-18 | 2026-07-19 |
How we notify you about changes
When we plan to add a new sub-processor we will: (1) update this page, (2) email everyone on the subprocessor-changes mailing list, and (3) wait at least 14 calendar days before the new vendor begins processing your data, so customers have a meaningful window to object. If you object, we will work with you in good faith to find an alternative; if no alternative is feasible, you may terminate the affected service with a pro-rata refund of prepaid fees, as set out in the Data Processing Addendum.
Get notified when this list changes.
Email privacy@veracly.app and ask to be added to the subprocessor-changes list. We will email you at least 14 days before any new vendor begins processing your data.