Privacy policy

Our single purpose

Rung helps an insurance broker draft, safety-check, send, and review broker-approved SMS conversations inside the broker's own OnlySales account. Rung does not use this access for a general browsing, advertising, or data-broker purpose.

Data Rung handles

Account and authentication information

The extension stores the Rung licence key, tenant identifier, setup choices, and safety settings in the broker's Chrome profile. It reads the broker's existing OnlySales access token from OnlySales browser storage solely to make authenticated requests directly to OnlySales. The OnlySales access token is not sent to the Rung Worker or to the model provider.

If a broker enables account recovery, Rung uses the submitted email address to send a short-lived verification or recovery link. The address is normalised and converted to an opaque keyed digest before selecting its recovery record; the plaintext address is not stored in that record. Rung stores the licence association and a digest of the current single-use recovery token. Cloudflare processes the destination address to deliver the requested email.

Contact information and website content

For allowlisted conversations, Rung may process contact names, phone numbers, tags, location or address fields, date of birth when present, lead source, and other contact fields rendered by OnlySales. These fields are used to identify the intended conversation, apply jurisdiction and suppression rules, and give the reply enough context.

Personal communications

Rung processes the relevant SMS history, broker message templates, message-delivery state, and broker-approved corrections. Conversation text may incidentally contain sensitive or health-related information, such as a person's mention of doctors, prescriptions, or medical conditions. Rung uses that content only to support the requested inbox workflow and to apply safety holds; it is not used to provide medical advice.

Operational and safety records

Within OnlySales, Rung checks tab visibility, focus, and composer or template activity to avoid interfering while the broker works. It does not monitor unrelated websites for advertising or general browsing analytics.

Rung keeps limited records needed to avoid duplicate sends, enforce opt-outs and rate limits, retry lawful deferrals, show review queues, attribute outcomes, and preserve approved playbook revisions. Those records can include conversation identifiers, timestamps, decision reasons, and approved wording.

How data is used and shared

Rung uses data only to provide and improve the broker-requested OnlySales SMS assistant, maintain security, diagnose failures, comply with law, and provide user-requested support. We do not sell user data, use it for targeted advertising, or transfer it to data brokers.

• OnlySales is the inbox and CRM from which the broker directs Rung to read and write data.
• Cloudflare hosts the Rung Worker and the storage used for tenant configuration, safety state, and approved playbooks.
• Anthropic processes the minimum conversation and playbook context needed to draft a reply or create a broker-reviewable playbook proposal. Model output must pass Rung's safety filters before it can be sent or stored as approved guidance.
• Stripe processes checkout and billing information. Rung receives customer, checkout, subscription, invoice, and payment-status identifiers needed to provide account access and billing controls. Rung does not receive complete payment-card details.

Service providers receive data only for the functions described above and are subject to their own contractual and legal obligations. Rung may also disclose narrowly necessary information when required by law, to protect users, or to investigate abuse or a security incident.

Storage and retention

When a broker explicitly transfers an existing account to the Chrome Web Store version, the two known Rung installations exchange the account's settings, playbook setup, pending delivery records, and safety holds within Chrome. The service verifies account ownership and reconciles durable safety state before the destination can be enabled. The previous installation is kept paused and its local records are retained. The transfer does not create a new license or change billing.

Extension settings and operational queues remain in the broker's local Chrome extension storage until they are cleared or the extension is removed. Approved tenant configuration, consent, opt-out records, safety state, playbook revisions, outcome records, and an enabled recovery association are retained for as long as needed to provide the service, enforce safety, resolve disputes, or meet legal obligations. Recovery tokens expire after ten minutes and are replaced or deleted when a newer link is issued or a link is redeemed.

Raw conversation history sent for an individual reply is processed transiently and is not intentionally saved as a persistent copy of the broker's entire inbox. During playbook learning, selected thread text is processed to create a pending proposal; only broker-approved playbook content is applied to the serving tenant.

Broker control, access, and deletion

Brokers can disable Rung globally, limit it to an allowlist tag, edit or reject proposed guidance, and remove the extension. To request access, correction, or deletion of Rung-held account data, contact us through the verified publisher contact shown on the Chrome Web Store listing. We may need to verify the requester and retain records that remain necessary for legal or safety obligations.

Chrome Web Store Limited Use

Rung's use and transfer of information received from Google APIs and the Chrome extension complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. Human access to user data is limited to cases where the user gives specific consent for support, where access is required for security or abuse investigation, or where law requires it.

Security and changes

Rung limits browser access to OnlySales, keeps model credentials in the server-side Worker, validates tenant configuration, and fails closed when a reply cannot be safely completed. No system is perfectly secure. Material policy changes will be published on this page with a new effective date.