← Back to relayplus.app

Subprocessors

The list

Three, and we would rather keep it that way. Each operates under a data processing agreement with the same obligations we owe you.

Our marketing website

Google also receives visits to relayplus.app through one tag, which runs only as your cookie choice allows and receives nothing from the product itself:

This service receives visits to relayplus.app only; it is not a subprocessor of your workspace data, so the objection process in “Adding one” does not apply to it.

What we do not use

Worth stating, because an earlier version of our privacy policy named four companies that never received anything, and a subprocessor list is only useful if it is exact.

Adding one

We will post the change here and email every workspace owner at least 30 days before a new subprocessor begins processing. If you object within that window, tell us and we will either exclude your workspace where that is technically possible or let you terminate for the remainder of your term with a pro-rata refund. That is a real commitment and not a formality, but be aware that objecting to Meta means objecting to the product working at all.

Where processing happens

Meta Platforms, our cloud infrastructure provider and Google (the three subprocessors in “The list” above) operate in and transfer data across multiple jurisdictions. Transfers out of the EEA and the UK rely on the European Commission’s Standard Contractual Clauses. We do not currently offer a choice of data region, and we will say so here before that changes.

Questions

Write to [email protected]. Data processing agreements, subprocessor terms and the identity of our infrastructure provider are available to customers on request, under NDA for the last of those.