Rinhelp is designed to investigate technical support issues inside a narrow boundary: tenant-scoped access, read-only investigation context, and human review before anything reaches the customer.
Security boundary
Rinhelp is built for AI support diagnosis, not autonomous operations. The service gathers context needed to investigate technical issues, produces an internal draft, and keeps a human review step before any reply, fix, or escalation.
That narrow scope is part of the product design. It reduces the amount of access the system needs and keeps the output framed as a draft for review rather than an action taken on your behalf.
What Rinhelp can access
Support and technical context
Workspace-scoped account data
What Rinhelp cannot do
Human review
Rinhelp returns a diagnosis draft or investigation draft for internal review. Founders or engineers stay responsible for deciding whether the output is grounded, what action to take, and what to tell the customer.
When the evidence is weak, the system is meant to fall back to an investigation draft with explicit gaps instead of forcing a confident answer.
Data handling
Rinhelp uses encrypted transport, access controls, and workspace-scoped integration handling where appropriate. The service is built around least-privilege access to connected systems.
Customer data is processed to operate the service, run the investigation flow, return internal drafts, and support the workspace. For more detail on privacy and data handling, see the privacy policy.
Security contact
Security questions or reports go to support@rinhelp.com.
Include the workspace name, the affected system, and enough detail for us to understand the issue quickly.
This page describes the current product-authored security boundary and should be reviewed alongside legal and infrastructure materials before broader launch.