Rookly responsibility
See risk earlier. Respond thoughtfully.
Rookly helps B2B teams understand account-health and customer relationship signals, with data permissions and human judgment at the center.
Last updated: October 6, 2026
Our responsibility
Rookly provides early-warning intelligence for B2B account health and client retention. It helps teams interpret customer relationship signals, including sentiment and emotional signals, so they can identify potential risks and respond thoughtfully. Rookly supports customer-retention work; it cannot guarantee that churn will be prevented or that a customer will remain. We are responsible for providing a transparent product, protecting the information entrusted to us, and giving users meaningful control over connected sources.
Your customer information stays yours
You retain your rights to customer, account, and relationship information you provide to Rookly. You are responsible for making sure you have the authority and any required legal basis, notices, and permissions to provide that information and use it for account-health or emotion analysis. Rookly does not take ownership of your information or the insights generated for your use simply because you use the service.
Connected sources and integrations
Rookly can work with customer and account information from sources you choose to connect. You control which sources and integrations you enable and should review their permissions and data practices before connecting them.
- Connect only information you are authorized to share and that is necessary for your intended account-health workflow.
- Consider whether customer communications or other personal information may be analyzed, and provide any notices or obtain any permissions required by applicable law.
- Do not connect production credentials, private keys, access tokens, or other secrets unless they are required for your intended workflow.
- Disconnect a source or revoke its permissions when you no longer need it.
Third-party integrations and analysis providers may be subject to their own terms and privacy practices. Review those terms before enabling an integration. Rookly cannot make promises on behalf of independent third parties.
Website analytics and masking
OpenReplay analytics are off until a visitor chooses to accept them in the cookies and analytics banner. After acceptance, OpenReplay may collect session replay, navigation, clicks, scroll depth, and performance or other technical signals in a masked configuration. Inputs and fields containing personal information are masked or excluded. No names, emails, phone numbers, company names, LinkedIn profiles, messages, prompts, passwords, tokens, or free-text form content are intentionally sent as replay metadata. Users can opt out or re-enable analytics through the analytics preference control on the Privacy Policy page.
Use insights with care
Rookly's account-health, sentiment, and emotion-analysis outputs are estimates based on available information. They may be incomplete or mistaken and should not be treated as definitive judgments about a customer or as a guarantee of future behavior. Review insights in context and use your team's judgment before taking action. You remain responsible for decisions and communications made using Rookly.
Security of the primary release
The primary version of Rookly is built with security as a core product requirement. We use reasonable technical and organizational safeguards appropriate to the service and continue to improve them as the product evolves. Security depends on the full environment, including your account, device, connected platforms, MCP servers, extensions, and credentials, so no software service can promise absolute security.
You help protect your account by using a strong, unique password, keeping extensions and connected services up to date, reviewing permissions, and reporting anything suspicious through the Rookly contact page at /contact.
Responsible use
Do not use Rookly to process information unlawfully, to analyze or access data you are not authorized to use, or to bypass the security controls of a connected service or integration. We may limit or suspend access when necessary to protect users, connected services, or the integrity of Rookly.
Questions and reports
If you have a question about this statement, a security concern, or a suspected misuse of connected data, please contact the Rookly team through /contact. We welcome clear reports that include enough context for us to investigate without exposing additional secrets or personal information.
This statement describes our current responsibility commitments and may change as Rookly adds capabilities, integrations, and controls.