Trust & Enterprise

Built for the questions HR, legal, and IT ask.

A plain-language overview of how RITE™ handles data ownership, retention, legal holds, and discoverability — the questions enterprise buyers ask before rolling RITE™ out to their leaders.

Clear data ownership

Conversations belong to the user who created them. Enterprise workspaces extend that to the organization, with admin controls over export and deletion documented in the DPA.

Configurable retention

Set retention windows that match your records policy — auto-delete after 30, 60, 90 days, or longer. Users can also delete their own conversations at any time.

Legal hold support

When a matter requires preservation, enterprise admins can place a hold that suspends auto-deletion for the affected users until the hold is released.

Security & encryption

Data is encrypted in transit (TLS 1.2+) and at rest. Access is scoped by role, and we follow least-privilege practices for the small team that supports the platform.

Frequently asked

If an employee issue becomes a lawsuit, would the organization be required to produce coached conversations?

Possibly — the same way emails, Slack messages, or prep notes can be subject to discovery if they are relevant to a matter. RITE™ does not change the legal standard; it simply creates a new category of business record that follows your existing retention and legal hold policies. We do not assert that conversations are privileged. In practice, most organizations find that a thoughtfully prepared conversation reduces risk rather than creating it — it demonstrates intent, care, and consideration of the employee's perspective, compared to a reactive message sent in frustration.

Who owns the conversation content?

For individual accounts, conversations are personal preparation notes belonging to the user — similar to a private journal. For enterprise workspaces, the organization is the data controller for conversations created under its workspace, and those records follow the company's retention and legal hold policies as outlined in the DPA.

Can we set retention windows or auto-delete?

Yes. Enterprise customers can configure retention windows (e.g., 30, 60, 90 days, or longer) so conversations are automatically purged after a defined period. Users can also delete individual conversations on demand.

Can we honor a legal hold?

Yes. Enterprise admins can place a hold that suspends auto-deletion for affected users until the hold is released. Held records remain accessible for export.

Are conversations attorney-client privileged?

No. RITE™ is a coaching tool, not a legal service. Privilege requires the involvement of an attorney acting in a legal capacity. If your team needs privileged preparation, route that work through counsel.

Does RITE™ use our conversations to train AI models?

No. Customer conversation content is not used to train foundation models. It is processed to generate coaching responses for the user and is governed by our Privacy Notice and DPA.

What does aggregated reporting expose?

Leadership Communication Intelligence (LCI) reports are aggregated and de-identified by design. Admins see themes, volume, and category patterns across the organization — not the contents of any individual conversation.

Where is data hosted?

RITE™ runs on enterprise-grade cloud infrastructure in the United States. Data is encrypted in transit (TLS 1.2+) and at rest. Access is scoped by role with least-privilege practices.

Can we get a DPA, security questionnaire, or SOC report references?

Yes. Reach out via the Organizations page and we will share our standard DPA, complete your security questionnaire, and provide references for the underlying infrastructure we rely on.

Talk with us about your organization

We are happy to walk your legal, HR, and IT teams through the data model, DPA, and security posture in detail.

Contact our team

This page is informational and does not constitute legal advice. For specific obligations under your jurisdiction or industry, consult your counsel. See our Privacy Notice and Terms for the governing agreements.