Whispr is a hosted reporting and case-handling product, not a legal-compliance substitute
The customer remains responsible for lawful use, governance, escalation, and internal decision-making.
Trust Center
Service scope, responsibilities, and contract boundaries
Use this page to understand the operating and commercial boundaries around Whispr: what the product covers, what remains the customer’s responsibility, and which commitments belong in signed agreements.
A clearer split between product scope and contractual promises
Whispr does not publish unsupported promises here about SLA, uptime, refund timing, or post-termination access windows.
Review signed commercial documents for exact terms
If your organization needs negotiated support, liability, data handling, or offboarding terms, confirm those in contract.
Whispr provides hosted reporting, case management, and supporting workflow tools
- Reporter intake and mailbox-style follow-up
- Administrative case handling, routing, and audit-related activity
- Role-aware access and operational settings
- Export, attachment, and legal-hold related controls in supported workflows
The customer remains responsible for lawful and appropriate use
That includes deciding who may access cases, how reports are handled, which retention rules apply, when legal review is needed, and how escalation should work within the organization’s own policies.
The product must not be used to abuse others or bypass security
- No unlawful, abusive, or retaliatory use of the platform
- No attempts to bypass access controls or access another customer’s data
- No use of the service as an emergency-response substitute where it is not designed for that purpose
Commercial and legal specifics should come from the order form or enterprise agreement
Support tiers, negotiated liability caps, DPA language, implementation commitments, SLAs, and any offboarding timing should be confirmed in the signed commercial documents. Those documents take precedence.
Product and documentation can change over time
Features, workflows, and trust materials may evolve. Procurement-critical commitments should be captured in writing rather than assumed from a website page alone.