Sub-processors

Last updated 1 September 2026 · Version 1.0-draft

Draft — not yet reviewed by counsel.

This document is published so it can be read and corrected. It has not been through legal review and it does not yet bind anyone. If you are evaluating Rutba and need agreed terms, ask us and we will tell you where the review stands.

The short version

A short list, and shorter than most, because Rutba runs its own mail transfer agent, its own media file server and its own database infrastructure rather than renting them. What is left is hosting, and analytics you have to consent to before it loads. Where something is not yet settled — a payment processor, for one — this page says so with a date rather than leaving a gap that reads as an answer.

1. The list, as at 1 September 2026

Sub-processor	What it does	Where	Data it reaches
Infrastructure hosting provider	Virtual machines, block storage and network for the control plane and hosted tenants	European Union	All customer data at rest and in transit, encrypted. The provider has no access to keys or application data in the ordinary course.
Google Analytics (Google Ireland Limited)	Aggregate visit counts for rutba.io only	EU/US, under the EU-US Data Privacy Framework	Site visitors only, and only after consent. No customer data, and nothing from inside any product. See the cookies page.

Where a name is generic above, it is because the contract is being finalised rather than because we are being vague. Write to privacy@rutba.io and we will tell you the entity, the region and the terms in force for your deployment today.

2. What we run ourselves

These would be sub-processors on most vendors’ lists. They are not on ours, because they are our own software running on our own infrastructure — which is a better answer to “where does my data go” than a vendor name, and worth stating so the absence is not mistaken for an omission.

Mail. Outbound and inbound mail for the platform and for Rutba Mail is handled by our own mail transfer agent. Message content does not pass through a third-party email service.
Files and media. Uploads, documents and media are stored and served by our own media file server.
Databases. PostgreSQL, run by us, with backups held on the same infrastructure and encrypted.
Identity. Authentication, sessions and tokens are ours. There is no third-party identity provider in the path unless you choose to federate to one.
Fonts. Typefaces are self-hosted at build time. This site makes no runtime request to a font CDN, so visiting it does not disclose your IP address to one.

3. What is not on the list yet, and why

No payment processor. Card capture is not built. Invoices are raised and subscriptions are tracked without one, and payment is arranged directly. When a processor is engaged it will appear here 30 days before it handles anything.
No customer support platform. Support runs on our own helpdesk software rather than a third-party desk.
No advertising, marketing-automation or data-enrichment vendors. There is nothing to add here, and if that changes it will be listed before it is used.

If this section is ever shorter than the truth, that is a defect in this page and we want to hear about it.

4. Notice of changes, and objecting

We give 30 days’ notice before adding or replacing a sub-processor. Notice goes to the administrative contact on each organization and is published here with a revised date.

If you object on reasonable data-protection grounds within that period, section 6 of the data processing agreement says what happens: we look for an alternative, and if there is none you may terminate the affected subscription with a refund of the unused prepaid portion.