How SnIPPETsX Keeps Your Code and Snippets Safe

Security model

Sandboxed execution. Every time you press Run, your code executes in an isolated, ephemeral container with memory and time limits and no access to other sessions. The container is destroyed when the run finishes, so nothing persists between executions.

Encryption in transit. All traffic between your browser and SnIPPETsX, including the real-time collaboration channel, is served over TLS.

Access control. Snippets are unlisted by default, so only people with the link can open them. Pro adds private snippets and a read-only mode for sharing code for review without allowing edits. Workspace snippets are restricted to members, with owner, admin and member roles.

Expiry and burn-on-view. Snippets can expire on a timer from two minutes up to 30 days, or burn after the first view. Expired snippets are swept from storage on a regular schedule so they do not linger.

Frequently asked questions

Can other users see my code when I run it?

No. Each execution runs in its own isolated, short-lived container that is destroyed afterwards and has no access to other sessions.

How do I share code that should not stay online?

Use an expiring link or burn-on-view. Burn-on-view snippets are deleted after the first view, and timed snippets disappear when their timer runs out.