Privacy notice
How Namefold handles naming requests, on-device favorites, optional accounts, and essential preferences.
Last updated: 2026-10-28

Scope of this notice
Namefold is a creative naming workspace. This notice describes its current rule-based name generation, name insights, browser-based shortlist, and optional account features. The service uses Cloudflare Workers and D1 for hosting and application data. If additional integrations are enabled, this notice should be updated to reflect their actual data flows.
Naming requests
The description, category, style, output language, and constraints you submit are sent to this application's server to generate results. A name submitted for an insight is also processed there. The current naming services do not save these request bodies to the application database and do not send them to an external AI provider. Avoid including confidential material or another person's private information in a brief.
The server briefly uses a request identifier derived from connection information to limit request frequency. Cloudflare may process connection and request metadata to provide hosting, security, and operational logs; those logs follow the hosting configuration. Do not place sensitive content in a shareable URL: studio descriptions and name-insight inputs can appear in URL parameters and browser history.
Your shortlist stays in this browser
Saved names, associations, category, and style are stored in browser local storage, with a limit of 100 ideas. They are not synchronized with an account. Other people using the same browser profile may be able to see them. Removing a favorite updates this browser's list; clearing this site's browser storage removes the local collection. Exported text files remain wherever you save them and must be managed separately.
Optional accounts and support
If you create an account, the application stores the account information you provide and authentication records in its configured database. Password authentication uses the authentication provider's password handling; a login session uses essential cookies. Account settings and support tickets are separate from the local naming shortlist. Content you put in a support ticket is stored so the operator can respond and manage the request.
Use account settings to review available profile controls. For an access, correction, or deletion request that cannot be completed there, contact the operator through the support area. Removing browser storage does not delete an account or a support ticket from the server.
Preferences, fonts, and integrations
The site remembers language and display preferences using browser storage or cookies. Interface font files and illustrations are served with the application; the Chinese serif font stylesheet may request resources from Google Fonts. Visiting a cited reference opens that external site, which applies its own privacy practices.
Analytics, advertising, chat widgets, social login, email delivery, and payment providers are optional template integrations. They are not part of the current naming engine. Enabling one requires the operator to review its actual data use, update this notice, and configure any applicable consent controls before public use.
Storage and protection
Account and support records are stored in the service's Cloudflare D1 database. Access is governed by the application's account and administrator controls, and the public site uses HTTPS. This notice does not promise a fixed retention period that the current application does not implement.
Questions and changes
The account support area can be used to submit a request after signing in. A public contact email and support administrator have not yet been configured, so responses may not be available immediately. The date above identifies the most recent content revision; material changes to data handling should be reflected here.