Privacy policy

When you visit verklet.com we record standard request logs — IP address, user agent, referrer, requested path, timestamp — kept for up to thirty days for abuse detection and capacity planning. We don't run third-party analytics, advertising trackers, or session-replay tools on the marketing site.

@verklet/sdk executes in the visitor's tab. When it boots, it may send a usage ping with your public project ID, SDK version, origin, and a random browser installation ID. We use that to serve compatible runtime assets and package registry URLs, and to compute Monthly Active Browsers.

Usage pings can happen on each boot. Billing and dashboard reporting deduplicate them server-side, so one browser reloading the runtime many times in a month still counts as one MAB. We do not fingerprint, IP-track, or correlate browser installation IDs across origins — see pricing for the mechanics.

Files the SDK writes — projects, package caches, user output — live in the Origin Private File System (OPFS) of the page that booted the runtime. OPFS is sandboxed per origin: another website can't read it, and we can't read it either. Clearing site data in the browser deletes it.

Verklet does not upload runtime files anywhere. If you build a product on top of Verklet that uploads files, that's your product's behaviour and your product's privacy disclosure.

The marketing site does not set tracking cookies. We use a small number of strictly-necessary cookies for things like remembering whether you've dismissed a banner. They expire with the browser session and are never shared.

Hosting and CDN delivery (Vercel) and email (whichever vendor we're using when you contact us) necessarily see request metadata or message content respectively. We don't sell data to advertisers or marketing brokers.

If you believe we hold information about you and you want a copy of it, a correction, or for us to delete it, write to [email protected]. We aim to respond within fourteen days.

When we change this policy materially we update the "last updated" date at the top of the page and announce the change on the website. We don't re-issue notifications for typo fixes or clarifying edits.