Last updated: June 5, 2026
Snippit does not collect, sell, or transmit your snippets to our servers.
Snippets, settings, and history are stored locally in Chrome storage on your device. Network requests you run via the Fetch/GraphQL tools are initiated by you and sent only to URLs you specify.
Snippit is a Chrome extension that lets you write, save, and inject code snippets—JavaScript, CSS, HTML, JSON, GraphQL, fetch requests, and more—directly on webpages you are viewing. This policy describes how information is handled when you use Snippit.
Snippit stores information you create or save in the extension, including: snippet names, descriptions, tags, code content, version history, injection history, templates, workspace settings, UI preferences, keyboard shortcut mappings, console output you choose to keep, fetch/GraphQL request definitions and history, and local audit log entries if you enable governance features.
When you inject a snippet, Snippit runs the code you wrote on the active tab (or tabs matching your URL patterns). The extension may read page structure when you use the element picker or when injection requires interaction with the current document.
By default, this data is stored locally on your device using Chrome extension storage APIs. Snippit does not transmit your saved snippets, settings, or history to servers operated by the developer for storage, analytics, or advertising.
No account or login is required. All storage is local unless you choose to export files yourself.
Snippit may make network requests when you explicitly use Fetch, GraphQL, or similar tools, or when injected code you wrote performs fetches. Those requests go only to URLs you specify and are initiated by your actions—not to a Snippit-operated backend.
Injected scripts run in the context of the page you are viewing and are subject to that page’s security policies (CORS, CSP, and similar).
When you copy snippet content, selectors, console output, or shared library packs, Snippit writes the selected text to your system clipboard so you can paste it elsewhere.
If you export a .snippit/ bundle, workspace backup, org library pack, or Playwright .spec.js file, your data is written to files or folders you choose on your device. The developer does not receive those files unless you send them separately.
Org library export/import, approved-snippet gates, and local audit logs operate entirely on your device. Snippit does not sync snippet packs to a cloud service operated by the developer.
Snippit is intended for developers and testers working on their own sites, staging environments, or with explicit permission. It is not designed to modify third-party websites without authorization. You are responsible for how you use injection features on pages you do not own or operate.
Data remains until you delete it in the extension, clear extension data in Chrome, or uninstall the extension (subject to how your browser handles extension data removal). You can delete individual snippets, clear history, or remove all Snippit data from Chrome extension settings.
Snippit is not intended for children under 13, and the developer does not knowingly collect personal information from children.
The developer may update this policy from time to time. The “Last updated” date will change when it does.
Questions or feedback?
If you have any questions about this privacy policy or Snippit, please contact:
nurulamin.tds@gmail.com