This notice explains the categories of third-party services that may support Reveiler and how Reveiler distinguishes subprocessors from customer-directed or independent third-party services. It is designed to provide meaningful transparency without publishing Reveiler’s proprietary provider-routing architecture, internal allowlists, or security controls.
A vendor is not automatically a “Subprocessor” merely because Reveiler can technically interact with it. The legal role depends on the service, data involved, instructions, contract, and applicable law. This notice should be read together with the Privacy Policy and DPA.
1. Core platform and operational service categories
2. Named services currently relevant to Reveiler
The following services are currently relevant to Reveiler’s architecture or planned production integrations. Inclusion here does not by itself state that each company is a Subprocessor for every Customer or every workflow.
3. Proprietary intelligence and provider routing
Reveiler may use multiple research, search, retrieval, AI, or enrichment providers. The internal provider registry, allowlist, routing order, fallback logic, economics, and provider-by-data-category matrix are proprietary administrative information and are not exposed to customer users.
This confidentiality does not override legal transparency duties. If a provider qualifies as a Subprocessor and applicable law or a Customer agreement requires identification of that Subprocessor, IBL will provide the required disclosure. Public or licensed information sources that do not process Customer Personal Data on IBL’s behalf are not treated as Subprocessors merely because their information may be referenced by Reveiler.
4. Data-category controls
Reveiler applies a default-deny governance model for external provider use. Approval to process one category, such as a public URL or public professional query, does not automatically authorize processing of customer-confidential Company Brain content, uploaded documents, CRM notes, correspondence, or mailbox content. Provider permissions are administered by Reveiler platform administrators rather than Customer workspace administrators.
5. Customer-directed integrations
When Customer elects to connect Google, Microsoft, or another supported external service, Customer instructs Reveiler to interact with that service for the enabled feature. Customer is responsible for ensuring the connection is authorized. Disconnecting an integration prevents further application use after disconnect processing, but provider-side revocation or deletion is not represented as complete unless confirmed by that provider.
6. Changes and notice
IBL may add, replace, or remove service providers as Reveiler evolves. Where a DPA, applicable law, or Customer agreement requires notice of a new Subprocessor, IBL will provide notice through an appropriate contractual or operational mechanism. This public notice may also be updated periodically.
7. Questions
Questions about subprocessors, third-party services, or data processing may be sent to hello@reveiler.com. Enterprise Customers may request additional information where reasonably necessary for vendor-risk or data-protection review, subject to confidentiality and protection of Reveiler’s security and proprietary architecture.