Offline-by-design boundary for SlashSnip

SlashSnip is offline-by-design for the core snippet workflow. That means the browser extension can store snippets locally and expand them in browser text fields without needing a hosted snippet workspace.

It does not mean every product surface avoids the network. Billing, license activation, support messages, optional email updates, and browser-store listing interactions have explicit network boundaries.

What stays local?

The core extension workflow stores operational data in Chrome extension storage:

• snippets, shortcuts, template bodies, and categories;
• extension settings, theme preference, favorites, and local usage counts;
• optional profile fields used by smart variables;
• clipboard history when Save Clipboard History remains enabled.

Those records are used by the extension runtime for //shortcut, ///, @@shortcut, smart variables, import/export, and local ranking. They are not part of a hosted team library.

Network boundaries

Surface	What can be sent	Why
Stripe checkout and billing portal	Payment and billing metadata handled by Stripe	Paid plan purchase and subscription management
License activation and status refresh	License key, customer email, and license status metadata	PRO access validation and offline grace handling
Help, uninstall, and feedback forms	The message and optional contact details you type, plus small surface metadata	Support and product feedback
Optional tips and updates emails	The email address submitted on the welcome flow	Product updates only after opt-in
Browser-store listing	Store-level listing interactions handled by the store provider	Store listing lifecycle

Snippet content, clipboard contents, template bodies, profile fields, license keys, page DOM, and form values are not included in the feedback widget payload. The full legal wording lives in the Privacy Policy.

Permission boundary

SlashSnip asks for broad browser access because text expansion needs to work in many websites and editors. The permissions are documented in the Privacy Policy and constrained by extension guards:

• storage keeps snippet data in Chrome extension storage;
• scripting supports page-context helpers for editors that need them;
• tabs opens and finds extension surfaces such as the dashboard and side panel;
• contextMenus powers the right-click snippet menu;
• sidePanel opens the browser side panel;
• alarms schedules background checks such as trial expiration;
• downloads writes local export files;
• host permissions let content scripts see editable fields on websites.

Broad permission scope is not the same thing as uploading snippet data. It is the browser capability needed for a text expander that runs across many sites.

What to say publicly

Use precise language:

• "Core snippet expansion works locally."
• "Snippets are stored in Chrome extension storage."
• "Paid plans use Stripe and license-status metadata."
• "Support and feedback forms send only the message/contact details you submit."

Avoid absolute claims that promise a completely disconnected product, imply no server involvement, or imply the extension has no access to sensitive browser contexts.

The correct message is narrower and stronger: SlashSnip separates local snippet content from the networked surfaces that are necessary for billing, support, and distribution.

Local verification checklist

Before repeating a privacy or offline claim, verify the current repo state:

1. Run the extension network guard: bun run check:extension-network.
2. Run the manifest permission guard: bun run check:manifest-permissions.
3. Check marketing copy: bun run check:marketing-truth.
4. Re-read the Privacy Policy and installation guide.

Those checks do not replace browser QA or store review, but they keep the repo-side privacy story aligned with shipped code.