SECURITY / DOCUMENTED PRODUCT CONTROLS
Plynt documents how identity, workspace membership, role-aware actions, HTTPS and change history are intended to reduce risk. No software can promise absolute security.
Report a security concern↗IN TRANSIT
ACTION SCOPE
DISCLOSURE
Access starts with an individual account and workspace membership. Administrators are responsible for reviewing members, roles and former collaborators.
Public Plynt surfaces are served over HTTPS. Storage-level and infrastructure protections depend on the hosting environment and are reviewed during plan-specific security discussions.
Workspaces are intended to define the tenant boundary. Queries and actions should evaluate the active workspace and membership before accessing a record.
Material state changes are designed to retain actor, action and time context. Audit coverage, customer visibility and retention vary by feature and plan.
Email info@plynt.us with SECURITY in the subject. Describe impact and reproduction safely; do not access, retain or disclose other users' data.
ONE WORKSPACE / CONNECTED OPERATIONS