Subprocessors
Vryne processes your documents on behalf of your organisation. For parts of the processing we use service providers. Data processing agreements under Art. 28 GDPR exist with all of them.
This is the English translation of the German original. In case of discrepancies, the German version prevails.
As of: 30 August 2026
| Provider | Purpose | Processing location |
|---|---|---|
| Sliplane | Hosting of application, database, document storage, search instance | Falkenstein, Germany |
| Melious | Generate answers, embed text, convert files | Germany |
| CopeCart | Payment processing and invoicing for credit purchases | Berlin, Germany |
| Fathom | Cookieless reach measurement | EU (EU endpoint) |
| Resend | Sending of sign-in links, invitations and purchase confirmations | USA — temporarily |
An analytics service with profiling, error tracking, a content delivery network or external font delivery are not among them.
Resend is a temporary arrangement
Of all the building blocks, mail delivery is the only one that leaves the EU. That does not match what Vryne otherwise promises, and is therefore explicitly marked as an interim state: we are looking for a delivery service based and processing in Europe and will replace Resend as soon as the choice is made.
Until then: only the recipient address and the content of the respective message are transmitted — a sign-in link, an invitation or a purchase confirmation. Documents, text passages and conversations never go to the delivery service. The transmission is based on standard contractual clauses under Art. 46 (2) lit. c GDPR.
Payment via CopeCart
CopeCart (CopeCart GmbH, Berlin) acts as the merchant when credits are purchased: the purchase contract is concluded there, CopeCart issues the invoice and pays the VAT. When the payment page opens, we pass your organisation’s identifier as a tracking key; in return we receive the order number, product and amount. We do not see payment data.
Reach measurement with Fathom
Fathom counts page views without cookies, without an identifier and without recognition; the script is loaded through an EU endpoint. If you object to the measurement, it is not included at all — see the cookie policy.
What the model provider gets to see
Not your entire knowledge base, only the text passages used for the respective question — together with the question itself and the agent’s system prompt. On upload, the file itself is sent there as well, in order to extract text from it.
Content transmitted through the interface is not used to train models.
Web search
Web search is optional and runs through a search instance that we operate ourselves — no third-party search API is connected. This instance is, however, a metasearch engine: it passes the search terms on to public search engines. If a model then fetches a page, its operator sees that access.
Only the search query or the address fetched is transmitted, never a document from your knowledge base. If web search is not configured, the tools are not offered to a model at all.
Changes
We announce new subprocessors with 30 days’ notice so that organisations can object.
Back to the privacy centre.