Privacy Policy

RingLink operates RingLink Edge and is responsible for personal information we use to manage accounts, billing, support and our own website. You can contact us at legal@ring.link.

When we carry traffic or process customer-controlled content on a customer's instructions, the customer ordinarily determines the purposes of that processing. We act as a service provider or processor to the extent the applicable agreement and law require. If you use a website or application protected by RingLink Edge, that operator's privacy notice also applies. Send requests about that application's content to its operator; we can assist with requests within our role.

Account and workspace information may include your email, name, organization, role, language, registration country, billing currency and authentication records. Billing information may include company and contact details, address, tax identifier, invoices, payment status, payment-provider identifiers and limited payment-method details.

Service configuration includes domains, origin addresses, IP allocations, ports, protocols, certificates or credentials where required by a feature, API permissions, resource IDs and connector settings. Support tickets, messages and files you choose to submit may contain additional information. Provide only what is necessary and remove unrelated secrets from logs and screenshots.

Operating and protecting the service involves processing source and destination IP addresses, ports, timestamps, protocols, connection and request information, transferred byte counts, errors, health checks, attack indicators and administrative audit events. IP-derived country information is also used for currency selection and account protection; it is an approximate network location, not device GPS.

Traffic content passes through the forwarding path. Visibility depends on protocol and configuration: encrypted traffic is not equivalent to an absence of metadata, and HTTP/HTTPS features that terminate TLS or cache content may process request headers, URLs and content. We do not promise that every mode is content-blind or that all network records are immediately deleted.

We use information to create and secure accounts, authenticate requests, deliver configured network services, provision resources, meter usage, issue invoices, collect payments, investigate abuse, diagnose failures, answer support requests and meet legal obligations. We also use product analytics to understand navigation and improve usability, as described below.

Where a legal basis is required, it depends on the purpose: performance of our agreement for account and service delivery; legal obligations for required financial records; legitimate interests, subject to applicable balancing and objection rights, for proportionate security and fraud prevention; and consent for optional processing where required. Necessary account, security and billing notices are distinct from optional marketing. You can use unsubscribe controls provided in marketing messages.

Essential cookies and browser storage support authentication, language preferences, purchase continuity and security. Currency is determined using IP-derived country and account billing rules. Blocking necessary storage may prevent sign-in or interrupt checkout.

We use PostHog for website and Dashboard analytics, including page visits, button interactions and session replay that reconstructs on-screen interactions. Analytics can include device and browser information, approximate IP-derived location, page paths, timestamps and pseudonymous identifiers. For signed-in users, activity can be associated with internal user and workspace IDs. The configured PostHog processing endpoint is in the United States.

Input fields are masked in replay, and code blocks, sensitive marked elements, payment frames and selected URL parameters are excluded or filtered. These measures reduce capture but are not a guarantee that no personal information can appear. Do not put secrets in service names or ordinary visible labels. Browser privacy controls or content blockers can restrict analytics; contact us about access, deletion or objection requests. This policy does not treat merely reading it as consent to optional tracking.

We use Microsoft Azure for hosting and related infrastructure, Cloudflare and other network partners for delivery and attack mitigation, Stripe for payment processing, PostHog for product analytics, and providers supporting transactional email and operational services. Each receives the information necessary for the function it performs. The relevant payment provider receives payment credentials through its payment interface; our ordinary billing records use provider references and limited method details rather than full card numbers or security codes.

Workspace administrators can see information and activity available to their role. We may disclose information to professional advisers, comply with valid legal requests, protect rights and safety, investigate fraud, or support a business reorganization with appropriate protections. We do not operate a business of selling personal information or using it for cross-context targeted advertising. A provider may act independently for functions such as its own fraud prevention or legal compliance, under its own privacy notice.

RingLink Edge is a globally distributed service. Information may be processed in the United States, locations of our Azure deployment, and regions used by network or other service providers. A chosen origin or advertised network location does not by itself restrict all account, support, billing or traffic data to that country.

Where applicable law requires safeguards for an international transfer, we must use a permitted mechanism, such as an adequacy decision or appropriate contractual safeguards, before that transfer. Contact us for information about the safeguards relevant to your service or to discuss a location-specific requirement before use. We do not claim that every country has identical privacy protections.

We keep information for as long as needed for its stated purpose, taking account of an active account or service, billing reconciliation, legal recordkeeping, security investigations, dispute limitation periods and recovery needs. Account and configuration records are generally needed while the service is active; financial and audit records can remain necessary after closure. Retention periods differ across operational logs, analytics and provider systems.

Deleting an application or cancelling a plan does not automatically erase related invoices or audit records. You may request account closure or deletion through the contact below. We review what can be erased, explain any lawful exceptions, and remove or anonymize information that is no longer needed. Backups may retain information until replaced through their normal lifecycle and are restricted from ordinary use.

We use measures appropriate to the service, including encrypted transport where configured, access controls, scoped API credentials, authentication protections, audit records and restrictions on administrative access. Your account security also depends on protecting keys, reviewing workspace roles and configuring your origin correctly.

No system is completely secure. We investigate suspected personal information incidents and notify affected people or authorities where required by applicable law. Contact us promptly if you believe your account, token or personal information has been exposed.

Depending on your location and applicable law, you may request access, correction, deletion, restriction, portability, information about processing, or object to certain processing. You may withdraw consent where processing relies on it without affecting earlier lawful processing, and complain to the competent data protection authority. Applicable rights to opt out of sale or targeted-advertising sharing remain available even though we do not use information for those purposes.

Send a request to legal@ring.link or use Dashboard support. We may reasonably verify your identity and authority, and will respond within the period required by applicable law. We do not require unnecessary sensitive identity documents as a routine condition. Authorized agents may contact us with evidence of authorization where permitted. Exercising rights will not result in unlawful discriminatory treatment; some necessary processing is required to continue the service.

Kubernetes integrations, connectors and MCP process the resource identifiers, configuration and operations you authorize. If you connect Claude Code, Codex, OpenCode or another third-party AI tool, that tool may receive information through your instructions and credentials; its own provider's privacy terms also apply. Do not grant it broader access than needed.

Automated security systems may classify or block traffic or flag an account for review. Contact support to contest a restriction or request human review. Such systems can make mistakes. This notice does not claim that an AI provider receives all application traffic or that using RingLink automatically sends your code to a model.

Our account-based services are intended for adults and organizations, not accounts opened by children. If you believe a child has provided account information inappropriately, contact us. Customers remain responsible for lawful processing of information about users of their own applications, including children where applicable.

We update this policy when practices or requirements change. We publish the effective date and give additional notice of material changes where appropriate or required. A new policy does not retroactively authorize an incompatible use of previously collected information or replace consent where consent is required.