NamingSignalalpha

Trust center

Privacy policy

Naming searches can reveal unreleased products. This policy explains the data NamingSignal needs, what may leave the device, and the controls available to account owners.

Who operates NamingSignal

NamingSignal is operated by Zena Labs LLC (“Zena Labs,” “we,” “us”). This policy applies to namingsignal.com, the hosted API, and account-connected CLI or MCP use. Local-only repository reading by the CLI remains on the user's machine unless the user approves a bounded request to the hosted service.

Data we collect

Account and authentication

Clerk processes sign-up, sign-in, Google OAuth when selected, bot protection, sessions, and user-owned API keys. NamingSignal receives the Clerk user identifier and authentication result. We do not give users our Clerk secret key, and API-key secrets are shown through Clerk's key-management flow.

Private project history

For signed-in users, Supabase stores account-owned naming projects and analysis runs. A record may contain submitted project context, bounded import previews, the editable brief, generated candidates, domain and namespace evidence, shortlist or rejection decisions, founder iteration feedback and round history, finalist research, founder-entered resonance, the selected winner, and usage summaries. Row-level security restricts these rows to the account owner.

API usage and service records

Supabase is the source of truth for monthly credits and request usage. The ledger records user and credential identifiers, token type, route, operation, units, credits, request identifiers used for service integrity, timestamps, and retention markers. It does not store the API-key secret.

Product analytics

When configured, PostHog receives privacy-bounded navigation and explicit product events. Browser autocapture, session replay, exception capture, persistent browser storage, and PostHog person profiles are disabled. Browser events are not deliberately sent with email addresses, API keys, project briefs, generated names, checked domains, or request bodies.

For authenticated API adoption analysis, a separate event may contain the Clerk user ID, route, operation, unit count, credit charge and balance, token type, plan, and deployment environment. The Supabase ledger—not PostHog—controls quotas and future billing.

Information sent to service providers

  • Vercel hosts the application and may process normal request, security, and firewall logs.
  • Clerk provides authentication, Google OAuth, bot protection, sessions, and user API-key management.
  • Supabase stores private account history, domain observations, usage ledgers, and bounded product-learning records.
  • PostHog receives the limited product events described above when its token is configured.
  • OpenRouter and upstream model providers may receive the bounded text of a public page that the user explicitly asks NamingSignal to read, and receive an edited, bounded naming brief when generation or ranking runs. Pasted or uploaded source text is not sent for brief inference.
  • Exa receives finalist names and focused category queries only when finalist research runs.
  • Registry RDAP and supported namespace providers receive the domain or exact name required to perform a requested check.

We do not sell personal information. Third-party providers process information under their own terms and privacy commitments.

Shared caches and product improvement

Fresh exact domain observations may be cached without a user ID or project context so the service can reuse a time-stamped registry answer and conservatively recheck stale evidence. A separate server-only learning ledger may record names shown, bounded structured brief labels, creative direction, selected TLDs, evidence, shortlist/reject/restore actions, deeper-analysis clicks, winner selections, and registrar-link clicks. Raw pasted text, uploaded file contents, fetched-page previews, and the full private project snapshot are not copied into that cross-user ledger.

Retention and deletion

Private account projects remain until deleted or the account is removed. Identifiable API-usage and product-learning rows carry a two-year retention marker; Zena Labs must run and verify the corresponding purge process before broad commercial launch. User-free aggregate counts and domain observations may remain because they do not identify who supplied them.

Users can revoke API keys in the developer console, clear browser storage, and request account/history deletion through the contact route below. Deleting the profile cascades through identifiable account rows; aggregated records without a user ID may remain.

Security and data choices

Do not put API keys, passwords, private keys, unpublished credentials, or regulated personal data into a naming brief. Imports screen for common secrets and block private-network destinations, but no filter is perfect. Use a separate revocable key per client and keep it in the local environment.

Depending on applicable law, users may request access, correction, deletion, or a copy of personal data. Contact Zena Labs LLC through the MoeLueker.com portfolio contact channel. We may need to verify the account before fulfilling a request.

Children and changes

NamingSignal is not directed to children under 13, and we do not knowingly collect their personal information. Material policy changes will update the effective date and, when appropriate, be communicated in the product.