Snapshot 7514
Raw (normalized text)
Scripts and page chrome removed; this is what change detection compares.
Press CTRL+K to open search Powered by Subprocessors Prev Next Effective Date: March 6th, 2025 We have updated this policy. For the previous version of this policy, please visit the agreements and policies history. The list below identifies subcontractors (subprocessors) that Rocket.Chat may be used to process personal data while provisioning our services. What is a Subprocessor? A subprocessor is a third-party data processor engaged by Rocket.Chat, including entities from within the Rocket.Chat Group, who has or potentially will have access to or process Service Data (which may contain personal data). Rocket.Chat engages different types of subprocessors to perform various functions, as explained in the tables below. Due diligence Rocket.Chat undertakes to use a commercially reasonable selection process to evaluate the security, privacy, and confidentiality practices of proposed subprocessors that will or may have access to or otherwise process service data. Infrastructure subprocessors – service data storage and processing Entity name Purpose Data hosting location Amazon Web Services, OVH We use OVH to underlying the infrastructure of our hosted offering, marketplace, open community server, and other services such as push notifications. We use a hybrid deployment. Generally speaking, after June 2020, all workspaces run on OVH. United States. The customer determines the location where an instance of our hosted offering is deployed during onboarding. Please reach out to support if you want to know the concrete subprocessor for your case. AWS Infrastructure that runs the cloud deployments and supports Rocket.Chat's internal processes United States MongoDB Cloud Analytics and Backup Management United States Service-specific subprocessors Entity name Purpose Data processing location Stripe Billing platform United States Zoho Corporation Business operations such as email marketing, newsletter, CRM, customer support (Zoho Desk); electronic document signing: United States Apple Push Notification Service, Firebase Push notification service for iOS devices United States Google Email, file storage, collaboration tool United States Atlassian Task management software (Jira), internal documentation (Confluence) United States Document360 Public documentation, terms and policies. United States Oracle Financial transactions, procurement, supply chain operations United States Innovation service-specific subprocessors Entity name Purpose Data processing location Clearbit Account Enrichment United States Appollo.io Marketing and Sales Intelligence. United States Rocket.Chat affiliates Rocket.Chat affiliates involved in processing personal data will depend on the location of our users and their customers and the nature of the services we provide to you. By agreeing to the DPA, you agree that all of these Sub-Processors may have access to Customer Data. The following entities are members of the Rocket.Chat Group. Accordingly, they function as sub-processors to provide the Services. Entity name Data processing location Rocket.Chat Technologies Corp. United States Rocketchat Tecnologia LTDA Brazil Objecting to a subprocessor You may object to a subprocessor by submitting your objection by email to privacy@rocket.chat with the subject line “Subprocessor Objection," along with your name, company name, and name of the Rocket.Chat service, name of the subprocessor, and objectively justifiable grounds for objection unless otherwise provided for in your service agreement with Rocket.Chat which terms control. Updates to this page Due to the nature of our business, we are consistently updating the list and controls of our subprocessors. For more information on Rocket.Chat's privacy practices, please visit our privacy policy. If you have questions regarding this page, please get in touch with us at privacy@rocket.chat. Rocket.Chat is committed to transparency as part of its values. As such, we provide previous versions of our agreements and policies in our agreements and policies history. Was this article helpful?