Savage Privacy Policy

Last updated: 2026-07-26

Savage converts SVGs into native, editable Google Slides shapes (or a PNG when a shape can't be represented). All conversion happens locally in your browser.

Clipboard

When a Google Slides tab gains focus (or you press Ctrl/Cmd there), Savage reads your clipboard to check whether it holds an SVG. If it does, the SVG is converted locally and the clipboard is rewritten with the result plus the original markup. Clipboard contents are processed in memory only, never stored, logged, or transmitted anywhere.

Storage

One number is saved in Chrome's extension storage: your chosen PNG output size (used only for the fallback path). Nothing else is stored.

Network

Savage makes no network requests during normal use. There are two exceptions, both triggered only by an action you take and both requiring the optional "fetch from any site" permission described below:

In both cases only the request for the resource itself is sent, nothing about you or your documents.

Optional permission

By default Savage has no access to websites' data. The optional "fetch from any site" setting grants host access solely for the two fetches above (dragged-SVG URLs and Google Fonts). It is off unless you enable it, and you can revoke it in the popup at any time; without it, dragged SVGs still work from sites that allow cross-origin requests, and SVG text falls back to a bundled font.

What Savage does not do

Contact

Questions or issues: github.com/vizkid/savage/issues