Your code never leaves your browser
gilika is built so that the one thing you care about, your code, stays on your machine. Here is exactly how, and how you can verify it yourself.
Client-side by design
Every step that touches your code happens in the browser. Syntax highlighting runs locally with Shiki using a JavaScript regex engine and no highlighting server, no round-trip. Your snippet lives only in the editor’s in-memory state, and export rasterizes the rendered preview to a PNG directly in the page. At no point is the code text sent over the network.
Accounts save styles, not code
Saving a style stores only the visual configuration; theme, background, font, aspect ratio, window chrome, and highlight settings. The code itself is stripped before anything is saved and never reaches our database. An account lets you reuse a look across snippets; it never holds your snippets.
Verify it yourself
Open your browser’s Network tab, paste a snippet, and export it. You won’t see your code in any request. The only background calls are a check of your subscription status and (if signed in) auth refresh. Neither carries the code. Fonts are self-hosted, so there are no third-party CDN requests, and gilika sends no analytics or telemetry from your browser.
How that compares
Other tools in this category render your code server-side, which means your code is uploaded to a third party. For anyone working with proprietary code, internal tooling, or anything under NDA, that is a real concern. gilika renders in your browser instead, so nothing leaves your machine.