Plynt's security posture is expressed in how the product is shaped: scoped access, isolation, and audit at every layer.
Access to a workspace is granted per member. Roles determine which modules and actions are reachable. Session state is bound to the identity, not shared across workspaces.
Traffic between your browser and Plynt is served over HTTPS. Additional protections applied by our infrastructure providers cover storage-level protections; contact us for details relevant to your review.
Workspaces are the fundamental unit of isolation. Queries and records remain scoped to the active workspace. Identity can move between workspaces; data does not.
Every state change writes to an append-only log with actor, action and timestamp. Admins can review the log for their workspace.
If we identify an incident affecting your workspace, we contact affected admins by email, describe the impact, and follow up in writing once resolution and root-cause review are complete.
For responsible disclosures and security questions, email us. We reply to every message.
Email security