V1.7 draft · Updated July 22, 2026

Privacy Policy

Namiscape minimizes the data it collects. Project ideas and brainstorming conversations are sent to the configured AI provider to prepare the editable naming brief and generate results, but Namiscape does not store their raw contents or the structured brief in its database or security logs. Guest shortlists stay in your browser; signed-in shortlists are stored with your account. Brainstorm history is off by default. If you explicitly enable it, up to 20 recent conversations with up to 20 successful generation rounds each, including their original text, naming brief, settings, and candidates, remain only in this browser for up to 30 days; they are not synced to your account, and you can pause saving or delete individual or all entries at any time. If you explicitly allow experience data, Namiscape records first-party anonymous timing, error-code, viewing-count, save, exploration, top-choice, and Web Vitals events. These events use a random per-brainstorm session ID and do not contain project descriptions, conversations, AI summaries, domain names, user IDs, full URLs, raw error messages, full email addresses, or raw IP addresses. Raw experience events are retained for up to 30 days and aggregate daily metrics for up to 180 days; you can change this preference from the footer. Cloudflare Turnstile processes necessary device and network signals to prevent automated abuse. If you upload an avatar, Namiscape re-encodes it and stores only the resulting public WebP image in Cloudflare R2; anyone with its URL may access it, so do not use a sensitive image. Removing an avatar or account removes the product reference immediately, while a cached copy may remain available for up to about 24 hours. Before authentication, a one-time workspace snapshot may temporarily remain in this tab for up to two hours so the current brainstorm can be restored after sign-in; it is removed after restoration and is not sent to Namiscape merely by being stored. Essential cookies and local preferences support authentication, security, abuse prevention, language, and optional history. Namiscape does not use advertising cookies, cross-site tracking, session replay, or experience data for model training. Google and GitHub process account information only when you choose those sign-in methods; Namiscape accepts only a provider-verified email. The restricted operations console shows aggregates, controlled event categories, and masked identifiers, never raw creative content. Contact the site operator for access, correction, deletion, or privacy questions.