Contact Us
Hello — welcome to the contact page for Mindful Days. One desk reads every message that arrives, whether it is a correction, a convention dispute or a generator bug, and the reply comes from a person who owns the page in question. Here is how to reach us and what to expect back.
Editorial & Methodology Consultation
If you want to argue with a guide's method — the phonetic rules, the tradition sources, the way styles are split — that conversation goes straight to the owning editor, and it is the mail we most enjoy. Method disagreements have changed style sets before, the about page documents the pillars the edits are judged against, and reader-driven changes are credited in the page history.
Legal & Trademark Boundaries
We do not provide legal or trademark advice by email, and nothing a reply says should be treated as clearance. The generators invent; they do not check registries. Right-holder concerns and takedown claims have their own process on the DMCA page, and general trademark questions get the same honest answer either way: verification is the adopter's job.
Scenario-Specific Inquiries
To route your message faster, tell us which shelf it belongs to:
Business & Ventures
Industry conventions we have flattened, sign-test failures, or a style that drifts from how real businesses in your field actually name themselves.
Creative & Everyday
Platform naming rules we should respect, handle patterns that read dated on a current profile, or a naming puzzle you would like covered.
Fantasy & Gaming
Lore corrections, phonetic rules for a tradition we mishandled, or a franchise family whose conventions deserve their own tuning.
People & Cultures
Accuracy notes on any living tradition, spelling or diacritic mistakes, and reporting any output that reads as caricature rather than craft.
These four cover the library. Whatever the shelf, expect a targeted reply rather than a form letter — the person answering owns the pages involved.
Linguistic & Cultural Sensitivity Feedback
Some generators borrow phonetic habits from real languages and traditions, and we hold that borrowing to a standard: pattern-honest, never mocking, never flattening. If a style reads as a costume of a tradition you know from the inside, that report outranks everything else in the queue. The style gets pulled while the report is checked, and the guide gains a note about the boundary so the same mistake does not return next quarter.
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 travel to the naming model for a single run and are discarded; they are never sold, never profiled, never turned into an audience segment. The privacy policy covers the full picture in plain language, and the cookie policy lists the tiny storage inventory we actually set.
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, visible, and before the quiet edit could slip past the readers who trusted the old text.
Communication Guidelines
Plain language gets the fastest answer: what page, what happened, what you expected. Screenshots help for visual bugs; the typed description helps for generator bugs. Friendly and 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.
API & B2B Partnerships
The public generators are the product; there is no paid API, no bulk tier and no white-label program, and we would rather answer honestly than politely. Proposals to resell the guides as a dataset, wrap the service in someone else's account wall, or paywall generated output are declined by default. Licensing conversations that would not change that are still read with interest.
Technical Model Feedback
Empty results, timeouts, or five names that ignore your description entirely are bugs, not quirks. Send the generator slug, the style chosen and the description typed, and the failure is reproduced on our side before it is patched. The error message already carries diagnostic detail, so a screenshot and two lines of context are all we need.
Our Communication Philosophy
We believe good naming tools improve fastest through conversation, so we treat every message as input rather than interruption. Write to desk@mindfuldays.cloud with the page name in the subject line, and your message is answered in arrival order, usually inside 48 hours on business days. Replies come from the editor who owns the shelf involved — never from a script — and if your message changes a page, you will be told exactly what changed.