Contact Us
Our Communication Philosophy
One desk reads every message, so nothing gets lost in a support maze. Email reaches that desk directly: write to desk@warmbalance.com with the page name in the subject line, and your message is answered in the order it arrived, usually inside 48 hours on business days. Every substantive reply comes from the editor who owns the page in question, not from a script, and if your message changes a page you will be told exactly what changed.
Scenario-Specific Inquiries
To route your message faster, tell us which shelf it belongs to:
Fandom & Game IP Names
Convention corrections, missing franchises, or a style that drifts from how a community actually names its cast and clans.
Surnames, Family & Noble
Heraldic accuracy, regional surname patterns, or title formats we have rendered wrong for a tradition you know.
Stage, Artist & Online Handles
Platform naming rules we should respect, or handle patterns that read as dated on a current profile.
Fantasy Races & Characters
Phonetic rules for a race tradition, or invented languages we should treat with more care than we did.
General & Misc Names
Naming puzzles you would like to see covered, together with the convention set you already know from the field.
Places, Worlds & Nature
Toponymy corrections and real-world geography habits we have flattened or misattributed on a page.
Brands, Titles & Objects
Category conventions for products and titles, and lookalike risks a style should be steered away from.
Music, Groups & Fandoms
Genre naming waves, fandom-specific in-group terms, and lineup or group naming customs we have missed.
Linguistic & Cultural Sensitivity Feedback
Some generators borrow phonetic habits from real languages and traditions. If a style reads as flattening, mocking or misrepresenting a tradition you know from the inside, that report outranks every other item in the queue. The style gets pulled or rewritten while the report is verified, and the guide gains a note about the boundary so the same mistake does not come back next quarter.
Technical Model Feedback
Empty results, timeouts, or five names that all ignore your description are bugs, not quirks. Send the generator slug, the style chosen and the description typed, and the failure is reproduced server-side before it is patched. Diagnostic detail travels with the report automatically from the error message, so you never need more than a screenshot and two lines of context.
API & B2B Partnerships
The public generators are the product; there is no paid API and no bulk tier, and we answer partnership mail honestly rather than politely. Proposals to license content or integrate the tooling are read, but anything that would put generated output behind a paywall, resell the guides as a dataset, or wrap the service in someone else's account wall is declined by default.
Editorial & Methodology Consultation
If you want to argue with a guide's method — the phonetic rules, the convention sources, the way styles are split — that conversation goes straight to the owning editor, and it is the kind of mail we most like reading. Method disagreements have changed style sets before, the about page documents the pillars the edits are judged against, and changes that come out of reader argument are credited in the edit history.
Data Ethics & Privacy Commitment
Messages are read by the desk and kept only as long as the matter needs, then deleted. Descriptions typed into generators are passed to the naming model and discarded; they are never sold, never profiled, never used to build an audience segment. The privacy policy covers the full picture in plain language, and the cookie policy lists the tiny storage inventory.
Transparency & Independence
We answer for our own pages only, and we say so when we are wrong. No franchise, platform or brand reviews our output before publication, and no sponsorship shapes a guide or a style set. If that ever changes, this page changes first, dated and visible, rather than a quiet edit slipping past the readers who trusted the old text.
Legal & Trademark Boundaries
Right-holder concerns and takedown claims have a dedicated process on the DMCA page, which exists so claims are handled consistently rather than ad hoc. General trademark questions still get an email answer, usually with the same reminder: the generators invent, they do not clear, and nothing on this site is legal advice.
Communication Guidelines
Plain language gets the fastest answer: what page, what happened, what you expected. Attach screenshots for visual bugs and paste the description you typed for generator bugs. Friendly, specific messages are queued ahead of vague ones, and abuse of the desk earns a filter rather than a debate. Every message is read by a person, and every person here would rather fix a page than defend it.