Privacy Policy

Effective 2026-10-30. 0saas is a single-operator, no-database static site published from github.com/finkitx/0SaaS. This page describes what actually happens in the code, not a generic template.

What 0saas does not collect

• No accounts or passwords. There is nothing to sign up for.
• No server-side storage of your drafts. Every tool renders in your browser; nothing you paste or generate is sent to a 0saas server. The in-browser runtime's own code comment states this directly: a purchased unlock's confirmation step reads back from Stripe and never stores a copy anywhere 0saas controls.
• No AI provider key ever reaches 0saas. If you use the built-in key vault, the key is kept in your browser's sessionStorage (cleared when you close the tab) unless you explicitly check "Remember on this device," which keeps a plaintext copy in that browser's own localStorage — still never transmitted to any 0saas server. The key is sent only to the AI provider you choose, directly from your browser. If you use Copy-Paste Relay instead, no key touches this site at all.
• No ad trackers, no third-party share SDKs, no social pixels. Share buttons link straight to each network's own share page; nothing loads from X, LinkedIn, Facebook, etc. until you click one.

What 0saas does collect

• Anonymous page-visit counts. 0saas uses Cloudflare Web Analytics, a cookieless beacon script (static.cloudflareinsights.com/beacon.min.js) that counts visits without planting a tracking cookie or fingerprinting you individually. It does not receive your drafts, your key, or what you share. See Cloudflare's privacy policy.
• Standard web server logs. Cloudflare, as the hosting provider, necessarily processes requests (IP address, user agent, requested URL) to serve the site and apply basic abuse protection, the same way any web host does. 0saas does not separately export or analyze these logs.
• Payment details, handled entirely by Stripe. If you buy a one-time tool unlock, you are sent to a Stripe-hosted Payment Link page. Stripe collects whatever it needs to process the charge (card details, billing email). 0saas never receives or stores your card number. After payment, 0saas's server-side function reads back a Checkout Session from Stripe's API (by session id only) to confirm the charge happened, and the device-level unlock is recorded only in your browser's localStorage — not in any 0saas database. See Stripe's privacy policy.
• An email address, only if you type one into the subscribe form. The home page has an optional "subscribe" form. As of this writing no subscription provider is wired to the deployment; the endpoint it posts to answers honestly that nothing is stored until one is configured, rather than pretending to collect it. If and when a provider is connected, this policy will be updated first, and that change will be dated here.

Cookies

0saas does not set its own cookies. The only third-party script loaded unconditionally is Cloudflare's cookieless analytics beacon, described above. Stripe may set its own cookies once you reach its hosted checkout page, governed by Stripe's own policy.

Children's privacy

0saas is not directed at children under 13 and does not knowingly collect information from them. Because there are no accounts, there is no persistent collection to begin with.

Your choices

• Clear your browser's site data for 0saas at any time to remove any locally stored key or unlock record — this is entirely under your control, not something 0saas can do for you remotely.
• Use Copy-Paste Relay instead of the key vault to avoid storing any AI provider key in the browser at all.
• Block or disable the Cloudflare beacon script with any standard content blocker; it is not required for a tool to function.

Changes to this policy

Material changes will update the effective date above and, where they affect data already collected, will be announced via the public issue tracker and the project's Atom feed.

Contact

0saas is operated by a single individual (the maintainer of github.com/finkitx/0SaaS). The fastest and only monitored contact route today is the public GitHub issue tracker — mark a privacy question as such and it will be answered there, on the public record.

This page is a plain-language description of this project's actual, current practices. It is not a substitute for legal advice and does not create a contract.