How PlyOps protects local, cloud, and marketplace data
Review the storage boundaries, authorization controls, marketplace token handling, and confirmed-action rules used to protect PlyOps workspaces.
Reviewed August 20, 2026
How does PlyOps approach security?
PlyOps uses separate local and cloud data boundaries. Local work stays in the browser unless exported or moved into a cloud workspace. Cloud and marketplace actions use server-side authorization, workspace scoping, and explicit review gates.
- Local storage
- IndexedDB in the current browser profile
- Cloud access
- Signed-in, workspace-scoped authorization
- Marketplace secrets
- Server-side only, excluded from browser backups
- Listing writes
- Preview and explicit confirmation required
Keep private data scoped to its owner
Cloud records and private assets are organized around a workspace boundary. Client-side filters are not treated as access control. Server endpoints re-check the user, workspace, role, and feature entitlement before sensitive reads or writes.
Keep secrets out of the browser
Service-role keys, marketplace client secrets, access tokens, and refresh tokens do not belong in browser bundles, local storage, URLs, screenshots, backups, or support messages. Connected provider credentials are handled on the server and returned to the interface only as safe account metadata and action summaries.
Put review before marketplace change
Imports are staged for review. Listing creation and updates remain separate actions with provider-specific checks. PlyOps does not use automatic retry loops for destructive operations and does not manage live marketplace inventory quantities.
Understand the shared responsibility
No web application can promise absolute security. Users should keep devices and browser profiles protected, download local backups, use current account credentials, and avoid sending secrets through support channels. PlyOps publishes capability and data boundaries so those decisions remain visible.
Common questions
Are marketplace access tokens included in JSON backups?
No. Marketplace tokens and server secrets are excluded from browser storage, JSON backups, client code, and user-facing job summaries.
Does a public Supabase key grant access to private records?
No. Public configuration identifies the project. Authorization still depends on authenticated sessions, row-level policies, workspace membership, role checks, and server-side validation.
Does PlyOps automatically publish marketplace changes?
No. Supported marketplace actions require a current preview, validation, and explicit confirmation. Provider-specific restrictions can block an action entirely.