1 · What is a sub-processor, and why we use them
A sub-processor is a third-party vendor that Rozper engages to help deliver the Services, and that may, in the course of that work, process personal data on Rozper's behalf as part of our role as a data processor for business customers. Running a global UCaaS and wholesale voice platform across 150+ countries at 99.99% uptime is not something any single company does entirely in-house — it depends on specialized infrastructure, carrier interconnects, and delivery networks operated by trusted partners.
This page discloses who those partners are, in general terms, so that customers acting as data controllers can assess our sub-processing chain as part of their own compliance obligations. It should be read alongside our Data Processing Agreement, which governs how sub-processors are engaged and bound contractually.
Using sub-processors lets Rozper focus engineering effort on the parts of the platform we are best placed to build — call routing, number provisioning, compliance tooling, and the admin console — while relying on partners who specialize in areas like global cloud capacity or carrier interconnect, each operating at a scale and reliability bar that supports our 99.99% uptime commitment. Using a sub-processor never reduces Rozper's responsibility to Customer: Rozper remains fully accountable for any personal data a sub-processor touches on our behalf.
2 · Our vetting & security-review process
Rozper does not add a vendor to this list casually. Before any sub-processor is permitted to touch customer personal data, it goes through a review that covers:
- Security posture. Review of the vendor's certifications (such as SOC 2 or ISO 27001), encryption practices, and incident-response track record.
- Contractual safeguards. A signed data processing addendum requiring confidentiality, appropriate technical and organizational measures, and cooperation with breach notification and audit requests.
- Data minimization. Confirming the vendor receives only the data necessary for its specific function — a delivery partner never receives more than the fields required to route a message or call.
- Transfer mechanism check. Confirming a lawful basis exists for any cross-border transfer the vendor relationship involves, consistent with our GDPR Transfer Pack.
Vendors are re-assessed periodically and whenever their role or risk profile materially changes — for instance, if a vendor expands into a new region, changes its own sub-processors, or discloses a security incident of its own. Vendors that cannot meet our baseline requirements are not engaged, regardless of cost or feature advantages, and existing relationships that no longer meet the bar are wound down on a customer-safe timeline.
3 · Current sub-processor list
The table below reflects Rozper's current sub-processors as of this page's last-updated date. Entries describe categories of vendor and service rather than exclusive commercial relationships, since underlying vendor arrangements can evolve; the current list is the authoritative reference.
| Sub-processor | Purpose / Service | Data location / region | Category |
|---|---|---|---|
| Cloud infrastructure provider (multi-region) | Hosting of application servers, databases, and object storage | United States, European Union, Asia-Pacific (tenant-selectable) | Cloud Infrastructure |
| Secondary cloud infrastructure provider | Disaster-recovery and failover hosting for platform redundancy | United States, European Union | Cloud Infrastructure |
| Carrier interconnect partners | Termination and origination of voice traffic across our 150+ country footprint | Varies by destination country | Voice Termination Partner |
| SMS aggregation partners | Delivery of bulk and transactional SMS to carrier networks worldwide | Varies by destination country | SMS Delivery Partner |
| Transactional email provider | Delivery of account, billing, and product notification emails | United States | Email Delivery |
| Payment processor | Card and bank-transfer payment processing and PCI-compliant tokenization | United States, European Union | Payment Processing |
| Customer support & ticketing platform | Managing support tickets, live chat, and customer correspondence | United States | Support Tooling |
| Product analytics provider | Aggregated usage analytics to improve platform reliability and features | United States | Analytics |
| CRM & marketing platform | Managing sales, marketing, and account-management workflows | United States | CRM / Analytics |
4 · Notification of new sub-processors
When Rozper intends to engage a new sub-processor that will handle customer personal data, or replace an existing one, we will update this page and, for customers under an active Data Processing Agreement, provide advance notice of at least 10 business days before the change takes effect, through the product, email, or both.
Customers who reasonably object to a new sub-processor on data-protection grounds may raise that objection within the notice period by contacting legal@rozper.com. As set out in our Data Processing Agreement, we will work in good faith to resolve the objection, which may include routing the customer's data around the new sub-processor or, failing resolution, allowing the customer to terminate the affected Service without penalty.
Routine changes that do not add a new vendor — such as a sub-processor opening an additional data center in a region we already disclose, or a minor rebranding — are reflected on this page without triggering a fresh notice period, since they do not change who processes customer data or under what safeguards.
5 · Subscribing to update notifications
To receive an email whenever this list changes, ask your account administrator to enable sub-processor update notifications from the admin console, or email legal@rozper.com with your company name and the address you'd like added. You can unsubscribe at any time; doing so does not affect the contractual notice period described above, which is delivered through your primary account contact regardless of subscription status.