プライバシー

Two different things.

This notice covers the public marketing site at sveda.dev. It does not replace the privacy practices of anyone who self-hosts Sveda. If you run sveda-server, you are the operator of that runtime. Your users' prompts and code stay with you unless you send them somewhere else. The iOS app has a separate App Store policy at /app/privacy. The Android app has a separate Play policy at /android/privacy.

Optional Sveda Cloud is a different product: isolated cells we operate, documented at Cloud Privacy. There is no Cloud account signup on this marketing domain. The docs copilot on this site is a demo runtime, not a paying cell.

Self-hosted product data.

When a team embeds Sveda, the JS client talks to that team's sveda-server. Embed tokens, stream events, tool calls, workspace index reads, and host MCP traffic stay on the infrastructure those operators choose.

sveda.dev does not process those payloads. We do not see your visitors' messages, your source files, or your model keys because they never pass through this marketing site.

What this static site collects.

The site is static HTML. Pages do not ship an extra application runtime. There is no sign-in, no cookies we set ourselves for accounts, and no form that posts personal data to us. Cookie consent is stored in this browser with localStorage, not as a cookie.

A content delivery network may keep ordinary request logs — for example IP address, user agent, URL, and time — to serve files and absorb abuse. We do not use those logs to build marketing profiles, and we do not sell them.

Links to GitHub leave this site. GitHub's own privacy policy applies when you open the repository.

Analytics, only if configured.

Production builds of this site include Cloudflare Web Analytics when PUBLIC_CF_BEACON_TOKEN is set. That beacon does not use cookies. It reports aggregated page views, performance, and coarse location derived from IP to Cloudflare so we can see whether the marketing site is used. Cloudflare's Web Analytics documentation describes what that product stores.

Google tags stay optional and wait for the cookie banner. If PUBLIC_GTM_ID is set and you accept, Google Tag Manager loads. If that ID is empty and PUBLIC_GA_ID is set, Google Analytics (gtag) loads after accept instead. Decline keeps those scripts off. If both IDs are empty, neither Google Tag Manager nor Google Analytics is included, and Partytown is not added to the build.

When Google tags are present and accepted, Google may set cookies or similar identifiers and process page views, approximate location derived from IP, device data, and referral information under Google's terms. We do not use that stack to identify you as a named person, and we do not combine it with a Sveda account — this site has no account system.

You can change the choice from Cookies in the footer. You can also block scripts in your browser. If a given measurement ID is not configured on a deployment, that vendor's script is not there to block.

What we do not do.

We do not create user accounts on the marketing site. We do not run a newsletter signup here. We do not serve personalized ads. We do not sell personal information. We do not use the marketing site to train models on your prompts, because the marketing site never receives them.

This site is not directed at children. We do not knowingly collect personal information from children.

Because we do not keep marketing-site accounts, there is no profile to download or delete on sveda.dev. Cloudflare Web Analytics is aggregated and cookieless; Google identifiers, when those tags are enabled and accepted, are controlled through the cookie banner, Google's tools, and your browser. For questions about this notice, write to hello@sveda.dev or message Telegram. You can also open an issue on the repository.

We may update this page when the site changes. The date at the top is the current version.