Este documento aún no está disponible en español. A continuación se muestra la versión en inglés.

LAST UPDATED · 2026-09-27

Privacy Notice

This Privacy Notice explains how RING 2 AI PTE. LTD. handles personal data when you visit the Ring2.ai website, create an account record, request a demo or partnership discussion, communicate with us, or use a contracted Ring2.ai VoiceAgent service.

1. Scope and responsible organization

This notice applies to website visitors, prospective and current partners, customer and supplier representatives, authorized service users, and other people who communicate with us. The responsible legal entity is RING 2 AI PTE. LTD., headquartered in Singapore, with teams in Australia and China.

For a contracted VoiceAgent deployment, the partner or end customer will ordinarily determine the purpose of the calls, the intended audience, the permitted data fields, and whether recording or transcription is enabled. That organization will ordinarily act as the controller or business, and Ring2.ai will ordinarily act as its processor or service provider. Ring2.ai may separately act as a controller for its own account administration, security, billing, legal compliance, and business relationship records. The signed agreement, Order Form, and Data Processing Addendum define the roles for each deployment.

2. Data collected through the website

Account and commercial inquiry data

The public conversion form collects:

• name and role;
• work email address;
• company name;
• country or region;
• how you heard about Ring2.ai;
• target scenario and expected monthly call volume;
• engagement or partnership type; and
• whether you chose account creation, a demo or a partner discussion.

If a submission is accepted, Ring2.ai creates a stable Lead ID and records the submission time. Self-service registration also creates an Account ID. The current account record does not itself provision telephony or billing access. The form does not ask you to upload recordings, contact lists, credentials, identity documents, payment details, or sensitive personal data.

Attribution and interaction data

The current website may send limited first-party events to Ring2.ai's own event endpoint. Depending on the action, an event may include the event name, time, generated event ID, generated visitor and session IDs, country or region, conversion path, engagement type, target scenario, expected call volume, Lead ID, CTA location, demo type, booking source, UTM source, medium, campaign, term and content, referrer, and landing path.

The implemented browser events include page view, conversion CTA click, demo play, form start, form submission and confirmed booking. The server also records account creation, demo and partner requests, and authorized lifecycle or follow-up changes. A booking event is recorded only when a connected scheduling flow sends a booking confirmation; clicking a scheduling link alone is not treated as a completed booking.

Technical request data

Hosting, content-delivery, security, and network providers necessarily process technical request data such as IP address, browser or device information, requested URL, timestamps, and diagnostic logs when they deliver a page or API response. The current application does not deliberately add an IP address, advertising identifier or device fingerprint to its lead or first-party event record. It does use random first-party visitor and session identifiers as described below.

To preselect the country or region in an enquiry form, your browser may request a country-level estimate from Country (api.country.is), or a configured IP geolocation provider. The provider receives your IP address as part of that network request. Ring2.ai uses only the country code from the response for this feature, does not retain the returned IP address, and does not request GPS access or precise coordinates. You can change the suggested country. If the lookup is unavailable, you can select your country manually and continue.

3. Data collected in business communications

If you email Ring2.ai, attend a briefing, request a proposal, negotiate an agreement, or ask for support, Ring2.ai may process your name, role, business contact details, correspondence, meeting notes, qualification information, proposed market and workflow, technical requirements, and commercial or contractual records. Please do not provide customer-confidential material, call data, or sensitive personal data before an appropriate written agreement and secure transfer method are in place.

4. Data processed in VoiceAgent services

A contracted deployment may process the following categories only to the extent specified in the Order Form, DPA, approved workflow, and service configuration:

• partner, customer, and authorized-user account details, roles, settings, support requests, and billing records;
• caller or recipient telephone numbers and other approved identifiers;
• call time, duration, routing, status, disposition, transfer, and related telephony metadata;
• approved prompts, scripts, knowledge sources, workflow fields, structured outcomes, and integration payloads;
• call audio, recordings, transcripts, summaries, or extracted fields when the relevant function is expressly enabled;
• CRM, scheduling, messaging, or other business-system actions initiated by the approved workflow; and
• operational, diagnostic, fraud-prevention, security, and support logs.

Partners and end customers must not configure a workflow to collect passwords, payment credentials, government identifiers, health information, biometric data, precise location, children's data, or other sensitive data unless the collection is necessary, lawful, expressly approved in writing, and protected by appropriate contractual and technical controls.

5. Sources of data

Ring2.ai obtains personal data directly from website visitors, business contacts, partners, customers, and authorized users; from URL parameters and referring pages; from interactions with the partner inquiry and demonstration; from connected telecommunications, CRM, scheduling, messaging, and other business systems; and from service providers supporting the requested service.

If you provide personal data about another person, you are responsible for having authority to provide it and for giving any notice, obtaining any consent, or establishing any other lawful basis required by applicable law and the signed agreement.

6. Purposes of processing

Ring2.ai uses personal data as reasonably necessary to:

• receive, validate, store, review, and respond to partner inquiries;
• assess partner, customer, workflow, market, and integration fit;
• arrange briefings, prepare requested materials or proposals, and manage pre-contract discussions;
• create, configure, provide, secure, support, and bill for contracted services and integrations;
• route calls, produce approved structured outcomes, support human transfer, and perform approved business-system actions;
• understand which pages, demonstrations, and outreach sources lead to commercial conversations and improve the website funnel;
• authenticate administrators and authorized users, diagnose failures, prevent abuse or fraud, and protect Ring2.ai, its users, and its systems;
• manage supplier, finance, corporate, audit, insurance, and legal records; and
• comply with law, respond to lawful requests, and establish, exercise, or defend legal claims.

7. Legal grounds

Where applicable law requires a legal basis, Ring2.ai relies on one or more of the following: steps requested before entering into a contract; performance of a contract; compliance with legal obligations; legitimate interests in operating a secure B2B website, evaluating partner opportunities, communicating with business contacts, providing and improving services, and protecting legal rights; and consent where consent is required.

The partner or end customer is responsible for establishing and documenting the legal basis for its calling audience, call purpose, use of contact data, recording or transcription, automated follow-up, and any marketing communication. A partner inquiry is not treated as blanket consent to unrelated or indefinite marketing.

8. Business communications and preferences

When you request a briefing or contact Ring2.ai, Ring2.ai may reply, arrange the requested discussion, provide relevant materials, and send closely related follow-up. Ring2.ai may send other relevant B2B information only where permitted by applicable law. You may ask Ring2.ai to stop non-essential promotional communications using the contact method in the message or the privacy contact identified in Section 18. Ring2.ai may continue to send service, security, billing, contractual, or legal messages needed for an active relationship.

9. Cookies, local storage, and external resources

The public website sends page-view, navigation and action-click, scroll-depth, missing-page, and on-site search events, and creates random visitor and session identifiers only after you enable Analytics in Cookie Preferences. Search events can include a term, selected filter, language and result count; terms that appear to contain email addresses or long numbers are excluded. Optional integrations are blocked until their corresponding category is enabled. Services not assigned to a category remain blocked until Uncategorised is enabled.

The website remembers cookie preferences separately for the international and Australian sites for 180 days. Necessary storage supports privacy choices, appearance settings and protected enquiry verification. Disabling Analytics removes browser visitor and session identifiers; withdrawal does not delete enquiry records or information already received.

The protected lead database stores an administrator's Basic authorization value in the current browser tab's session storage after sign-in and removes it on sign-out or when the tab session ends. Website fonts are served from Ring2.ai's own local assets.

Submitting an enquiry or requesting follow-up does not require Analytics consent. The details you submit and the resulting business records are separate from optional website page-view analytics.

The separate Cookie and Tracking Notice explains the available cookie choices, optional integrations and how to change or withdraw your selection.

10. Disclosure of personal data

Ring2.ai does not sell personal data through the current website. Ring2.ai may disclose personal data only as reasonably necessary to:

• authorized Ring2.ai personnel and contractors responsible for commercial follow-up, service delivery, finance, legal, security, or support;
• providers supporting website hosting, persistent storage, content delivery, telecommunications and numbers, speech processing, model inference, cloud infrastructure, security, email, scheduling, support, billing, and business-system integrations;
• the relevant partner, end customer, or authorized users where the data relates to their deployment or Ring2.ai acts on their instructions;
• professional advisers, auditors, insurers, investors, lenders, and transaction counterparties subject to appropriate confidentiality obligations; and
• courts, regulators, law-enforcement bodies, and other recipients when disclosure is required by law or reasonably necessary to protect rights, safety, or service integrity.

The named production subprocessor list, purposes, and processing regions must be completed before paid production processing and reflected in the applicable DPA or subprocessor schedule.

11. Call data location, access and international transfers

Ring2.ai's website, business operations, and service supply chain may involve providers or authorized teams in more than one country. Before production launch, the parties must document the approved service data region and cross-border flows in the Order Form, DPA, or subprocessor schedule. Where applicable law requires a transfer safeguard, the parties will use the mechanism stated in the signed DPA, such as applicable standard contractual clauses, an approved addendum, an adequacy mechanism, or another legally recognized safeguard.

Call data location and access: what to confirm for your deployment. Recording, processing, storage and backups, authorised access and overseas recipients, retention and deletion must be documented separately for website enquiries and voice-service data. This website does not claim that all call data stays in Australia.

12. Security and access

Ring2.ai applies measures appropriate to the data and the deployed implementation. The current website validates required form fields and field lengths, rejects oversized submissions, keeps production storage and administrator secrets on the server side, returns an error instead of a false success when persistence is unavailable, and protects the lead database with configured administrator credentials. Authorized administrators can review and export lead records, update lifecycle stage, owner, response and follow-up times and notes, and inspect the activity history.

Website enquiry records and contracted call data are separate. Access and notification options depend on the configured service. Confirm the access roles, audit records, backup arrangements and retention controls for the deployment you use.

Security measures for contracted VoiceAgent services, including access control, encryption, logging, vulnerability management, backup, recovery, isolation, and incident response, must be stated in the signed DPA or security schedule and must match the deployed architecture. No certification or absolute security guarantee is made in this notice.

13. Retention, return, and deletion

Ring2.ai retains website inquiry data, related first-party events, business correspondence, and preference or suppression records only for as long as reasonably necessary for the purposes described in this notice, including evaluating the inquiry, managing the relationship, protecting the service, and meeting legal or recordkeeping requirements. Contact teams@ring2.ai to request the retention schedule applicable to your enquiry.

VoiceAgent data is retained according to the signed Order Form, DPA, and configured service settings. Recording and transcript retention must be expressly approved for each deployment. At the end of the service or following a valid instruction, Ring2.ai will return or delete data as required by the signed agreement, subject to documented backup cycles, security records, legal holds, and legal retention duties. Deletion from active systems may not immediately remove restricted copies from protected backups; those copies will remain isolated and expire or be overwritten under the approved backup schedule.

14. Individual rights and requests

Depending on the applicable law and your location, you may have rights to request access, correction, deletion, restriction, objection, portability, withdrawal of consent, or information about certain automated processing. You may also have the right to complain to a competent data-protection authority. These rights may be subject to legal conditions and exceptions.

Requests about Ring2.ai's website or Ring2.ai's own business-contact records should be sent to the privacy contact identified in Section 18. Ring2.ai may request information needed to verify identity, authority, and the scope of the request. Where Ring2.ai processes VoiceAgent data for a partner or end customer, call participants should ordinarily direct the request to that organization; Ring2.ai will assist it as required by the DPA and applicable law.

15. Voice communications, AI disclosure, and recording

Ring2.ai does not determine that a proposed call is lawful merely because the technology can place or answer it. Before launch, the partner or end customer must review the target country's rules for telemarketing, business calling, do-not-call or suppression lists, calling hours, caller identity, AI disclosure, recording, transcription, number registration, and cross-border data handling.

Where required by law or the approved workflow, callers must be told the identity of the responsible organization, that they are interacting with an AI system, whether the call is recorded or transcribed, and how to reach a human or exercise an opt-out. The Acceptable Use and Voice Compliance page summarizes operational boundaries but does not replace market-specific legal review.

16. Children's data

The website and partner inquiry are intended for adult business representatives and are not directed to children. A VoiceAgent workflow must not intentionally target or collect personal data from children unless the responsible partner or end customer has completed the required legal review, obtained any required authorization, and entered a written service scope accepted by Ring2.ai.

17. Changes and contract precedence

Ring2.ai may update this notice when the website, service, provider set, or legal requirements change. The page will state the updated date. If a change materially affects an active contracted service, notice will be provided as required by the signed agreement or applicable law.

For paid VoiceAgent services, the signed Partner Agreement or MSA, Order Form, DPA, Acceptable Use Policy, and service schedules control where they address the same processing in greater detail or state an agreed order of precedence.

18. Company and privacy contact