ReliaRing
Legal and policies

Third-party processing and software notices

How outside services support ReliaRing, what information they receive, and how software licenses apply.

Effective and updated October 20, 2026

ReliaRing uses the following categories of outside services. The services involved depend on your plan, enabled features, region, and the accounts your organization connects. A category does not mean every provider receives every type of information or that every integration is enabled.

Hosting and infrastructure
Operate databases, storage, backups, networks, and service delivery. May process account details, communications and attachments, configuration, access logs, and security records.
Telecommunications and emergency routing
Route calls, messages, faxes, number ports, and emergency calls. May receive numbers, routing and usage records, communication content, registered service addresses, location when permitted, and identity or authorization documents required for provisioning.
Crash reporting and performance
Diagnose failures using crash stacks, app/build and device details, internal user/account identifiers, operation names, and timing. The mobile app filters credentials, communication content, contact values, and precise location from telemetry. Session replay, screenshots, and view-hierarchy capture are disabled. Network connections can reveal IP addresses and approximate geography to the recipient.
Push notifications and app updates
Deliver incoming-call and message notifications, software updates, and app assets. Receive device or installation identifiers, push tokens, delivery metadata, notification payloads, and network/device details needed for delivery. Notification content can appear on your device according to its settings.
Payments and accounting
Process payments, invoices, and reconciliation. Receive billing identity, payment details entered into payment interfaces, invoice amounts, and transaction references. Payment providers can also process information for their own fraud prevention and legal obligations. The mobile companion does not collect payment-method details.
Email and support delivery
Send service, sign-in, and support messages and process replies. Receive recipient addresses, message content and attachments, delivery metadata, and support information relevant to the request.
AI, speech, and transcription
When an AI or speech feature is used, external services may receive call audio, transcripts, prompts, selected business knowledge, caller-provided details, and generated responses to transcribe, synthesize speech, search knowledge, or answer calls. Provider selection and fallback depend on the feature configuration. These services can process data outside Canada.
Website and knowledge import
When you request a website import, a crawling service receives the supplied URL and retrieves page content for your knowledge base. Do not supply private URLs, embedded credentials, or content you are not authorized to use.
Connected business accounts
Optional identity, contacts, collaboration, accounting, ticketing, and alerting connections exchange authorized profile, directory/contact, invoice, ticket, or event data. Customer-designated webhooks, email servers, and external carriers receive the payloads you configure.
Address, maps, and regional preferences
Address and map services receive typed addresses, map requests and location relevant to the feature. IP-location services may receive your connection IP and browser details to suggest country, currency, or time zone. Opening an external map sends the selected destination to that service.
Website measurement
Optional website analytics receives page interactions and browser/network information after analytics-cookie consent. It is not loaded in the signed-in portal or mobile companion. You can change cookie preferences. Operational crash reporting is separate from marketing analytics.
Fraud and abuse prevention
Security checks use account, session, device/browser and network signals to detect suspicious access. Any additional external device-risk service is subject to its enabled configuration and applicable notice and consent requirements.
External content and software distribution
Requested images, documentation assets, app-store downloads, and external links may involve content or distribution services. A connection can reveal IP/browser details to the recipient. Software libraries and self-hosted infrastructure are not automatically separate recipients of customer data.

ReliaRing remains responsible for its handling of personal information. Outside services may act on our instructions, operate under their own legal obligations, or receive information at your organization’s direction. Their published policies do not replace our obligations.

Connect optional accounts only with authority to share the selected information. You can revoke access in the connected service or ask your administrator to disconnect it. Revocation stops future authorized access; it does not automatically erase information already imported or delivered. For access, deletion, or information about the recipients relevant to your account, contact privacy@reliaring.com.

AI and communication content

AI, recording, transcription, and knowledge-import features require the appropriate notice, authority, and consent for the information involved. Permission to use ordinary calling does not by itself authorize unrelated AI use. Review the feature disclosure before enabling it and inform affected callers or participants as required. A policy link alone is not consent. We do not promise zero retention or exclusion from provider model training unless the applicable service terms and settings support that promise.

Processing outside Canada

Our primary hosting is in Canada, but this is not an all-data-in-Canada commitment. Communications routing, diagnostics, push delivery, app updates, payments, email, AI, and connected services may involve processing in the United States and other countries. Information may be accessible to courts, law-enforcement, or national-security authorities under those countries’ laws. Contact privacy@reliaring.com for information about the processing relevant to your service.

Retention and deletion with outside services

ReliaRing’s retention settings do not automatically control copies held by every outside service. Delivery queues, diagnostic events, backups, billing records, customer exports, and information sent to connected accounts can have different retention periods. A disconnection or account-deletion request does not immediately erase all such copies. We assess requests against the applicable retention settings, legal obligations, and the recipient’s role; contact privacy@reliaring.com for help.

Software licenses and attribution

Third-party software remains subject to its applicable license, copyright notices, and any source-code or attribution requirements. Those licenses govern the rights they grant for the relevant components; our Terms do not remove those rights. Library names and copyright holders may appear in required software notices without implying an endorsement or a separate cloud-data recipient.

Mobile software notices are available in Settings → Software licenses. For other software notices or a source-code request under an applicable license, contact help@reliaring.com and identify the product and version.

Open-source license notices

Mobile distribution terms

The application license presented by your app store applies alongside the ReliaRing service terms. Where the App Store standard license applies, it is available at the link below. Your carrier or wireless-data agreement also applies. These notices do not waive rights that applicable law does not allow you to waive.

App Store standard application license

privacy@reliaring.com