Privacy and Local Storage: How SlashSnip Handles Your Data

SlashSnip is designed around a local-first baseline.

What stays local

Core snippet usage keeps data inside the browser:

• snippets
• categories
• settings
• clipboard history

Current storage is based on Chrome storage APIs for extension data.

Clipboard history limits

SlashSnip keeps up to:

• 100 clipboard items
• 15000 characters per clipboard item

That gives you enough room for practical reuse without pretending it is a cloud knowledge base.

What is not part of the current public flow

• mandatory account creation (no signup required to use the extension)
• cloud sync between devices (snippets stay local by default)

Those boundaries matter because they change the privacy story. The website should only claim what is already true in the current release phase. Public Stripe checkout is live — when you buy PRO, we process billing metadata (email, subscription status, license key) via Stripe; snippet content is never sent.

Moving data between devices

Automatic sync is not finished yet, but manual transfer is available through import/export.

That makes the current product honest:

• local by default
• portable when needed
• not oversold as a cloud workspace