Privacy Policy

Your email address (to sign you in), the prompts you submit (to build your sites), your credit ledger and plan status (so billing is auditable, including plan renewals), and operational logs for your sites (for routine upkeep such as uptime checks and self-healing).

We don't sell your data. We don't show ads. We don't read your sites' customer data for anything other than operating your sites.

Card details go directly to Stripe and never touch our servers. Any payouts from your sites go to your own connected Stripe account.

Sites run on Cloudflare's edge network. Account data lives in our database with per-tenant isolation enforced at the database layer (row-level security).

Nopen sets no advertising or analytics cookies, and nopen.co loads no third-party tracking scripts. On nopen.co there is exactly one cookie, and only if you choose to sign in with Google: a short-lived nopen_oauth_state value that protects the sign-in round-trip against cross-site request forgery. It is HTTP-only, SameSite=Lax, expires after ten minutes, and is deleted the moment you land back on Nopen.

Your signed-in session is not a cookie. It's a bearer token your browser keeps in local storage and sends in an Authorization header on each API call. Signing out removes it from your browser and revokes it on our side.

Besides that token, local storage holds four things and nothing else: your light/dark preference; the idea you typed on the landing page; the plan generated from it, so it survives the trip into your dashboard; and a snapshot of your credit balance taken when you start a purchase, so we can tell when it has completed. A session-storage flag helps a stale browser tab recover after we ship an update. All of these stay in your browser. The local-storage items stay in your browser until you clear them or sign out; none of them is used to track you across sites.

Sites Nopen builds for you carry a cookieless pageview beacon so your dashboard can show traffic. It reports the page path and the referring URL — no cookie, no device or cross-site identifier, no visitor profile. Your visitors' IP addresses are used transiently for rate limiting and are not stored with the pageview. Those sites are served from Cloudflare's network, which may set its own security cookies on your site's domain under Cloudflare's policy, not ours.

Nopen is a small service standing on other people's infrastructure. These are the subprocessors it relies on — the whole set, with a note where one only comes into play if a particular feature is switched on:

• Amazon Web Services — hosting for the Nopen application and its Postgres database (US East region). This is where your account, sites, prompts, and credit ledger live.
• Cloudflare — DNS, the edge network your sites are served from, and domain registration when custom domains are enabled.
• Stripe — credit purchases (credit packs and monthly plan billing, including renewals), and, when payment collection is enabled for your site, the connected account that receives your own sales. Card details go to Stripe, never to us.
• Anthropic and OpenAI — the models that plan and write your site, and the model that screens ideas against our Acceptable Use Policy. Your prompt is sent to them to do that.
• Zhipu AI or OpenRouter — whichever is configured, and only if the economical builder and reviewer path is switched on. It is off by default, so on a standard build neither one sees your prompt.
• E2B — the isolated sandbox your site's code is written and assembled in.
• Amazon SES — the email this platform sends: transactional messages to you (sign-in links, welcome, site-live, build-failed, work-paused, refund and domain-renewal notices, and lead-capture form-submission notices), and the delivery email a buyer receives for a digital product purchased from your site, sent on your behalf. Nothing is sent to leads.
• Google — only if you choose Google sign-in, and only to confirm your email address and name.

Each processes your data on our instructions and for these purposes only. If this list changes we'll update this page.

An emailed sign-in link is single-use and stops working after 15 minutes. The short code used to pair the CLI must be redeemed within 15 minutes; the token it hands back then runs for 90 days. A signed-in web session expires 30 days after it's issued. Signing out revokes the token immediately rather than leaving it to expire: in the dashboard, "Log out" ends that session and "Sign out of all devices" ends every session, including CLI logins; in the CLI, nopen logout signs that machine out.

Your account data — email address, the prompts you submitted, your sites and their activity, and your credit ledger — is kept for as long as your account is open, because it's what the product is made of: your ledger has to stay auditable and your sites have to keep running. We don't have a shorter clock we quietly apply; if you want it gone, ask us and we delete it.

After deletion, records we're legally required to keep — chiefly payment history — are retained for as long as tax and accounting law requires, and nothing else. Stripe keeps its own transaction records under its own policy.

The data controller for your account is Hasna, Inc., 131 Continental Drive, Ste 305, Newark, DE 19713, United States. For privacy questions or to exercise your data rights, email hello@hasna.com.

Email hello@hasna.com from your account address to request deletion of your account and its data. We'll respond to and complete your request within 30 days — the deadline data-protection law sets — except records we're legally required to keep (like payment history).