Privacy
Privacy policy
Private-beta draft for the current MYTHME app. This is not legal advice and it is not a claim that MYTHME complies with COPPA, GDPR, CCPA, or any other law. Questions and removal requests: Mythmeofficialteam@gmail.com.
What MYTHME processes
When someone who says they are 18 or older forges a myth, MYTHME receives the photo they choose, plus the language, mythic world, and character vibe they select. The app then receives the generated character name, species, power, weakness, lore, rarity, and portrait. People who choose 13–17 or under 13 are not asked for a photo.
Your photo
The photo is sent to the AI provider (xAI) so it can write the character and paint the portrait. Under the current architecture, MYTHME does not intentionally store that original photo after the request finishes. Creating a myth does not publish the photo or the result. MYTHME does not claim ownership of your photo.
MYTHME has not verified how long xAI or any other provider keeps a request, and this policy does not promise that a provider will delete it.
What is stored
MYTHME stores the generated portrait and the character text (name, species, power, weakness, lore, rarity, language, mythic world, character vibe, and the time it was created). It also stores whether the myth is unlisted or public, a private creator token used only to publish, feature, or delete that myth, the consent times below, and — for myths forged after the age question — that the person attested “18 or older,” plus the time of that attestation. It does not store a birth date. The creator token is not put in the share link and is not shown to Gallery visitors. Age and consent records are not shown on the Gallery, public myth pages, or link previews.
On the device that forged the myth, the browser keeps a copy of that creator token in local storage so you can manage the myth after you close the tab. Clearing site data on that device removes the token. The myth itself stays until it is deleted. The same device also keeps a separate random id, described under Cookies and analytics, used only to count product steps.
Unlisted, Gallery, and links
A new myth is unlisted. People who have its unique link can open it. It does not appear in the Gallery until you separately confirm publishing. Publishing makes the generated myth publicly viewable in the Gallery and shareable by that same link. Publishing does not by itself allow MYTHME to post the myth on official social channels.
Social featuring
A person who attests they are 18 or older may optionally allow MYTHME to feature a published myth on MYTHME’s own official social media channels. That choice starts unchecked, is not required to use MYTHME or to publish, and can be turned off later from the device that forged the myth. It is not offered for anyone under 18. It is not permission for movies, casting, advertising or endorsements, merchandise, third-party licensing, cryptocurrency or token promotions, or selling a likeness.
Consent records
If an adult confirms the upload checkbox, MYTHME stores the time of that confirmation and the “18 or older” attestation. If they confirm publishing, MYTHME stores the time of that confirmation. If they allow or revoke social featuring, MYTHME stores that choice and the time it last changed. These records do not include the original photo or a birth date. Choosing 13–17 or under 13 does not create a stored profile, photo, or email.
Cookies and analytics
This private beta does not use a third-party advertising tracker and does not sell usage data. It does keep a first-party count of product steps — opening Home, starting Create, uploading a photo, forging a myth, downloading, sharing, copying a link, opening someone else’s myth link, forging a myth after opening someone else’s link, publishing to the Gallery, and opening Create Merch — so the operator can see how the beta is used. The browser stores a random id in local storage for that count. If you open someone else’s myth, it also stores a yes-or-no mark so a later myth you create can be counted. The record does not include a name, email, photo, birth date, IP address, or the creator token, and it is not placed in the share link. Clearing site data starts a new id. It does not ask you to create an account.
Service providers
The photo and the generation instructions are processed by xAI to produce the myth. Generated myths are stored in MYTHME’s database, which is hosted Postgres. The app itself is hosted so it can be opened on the web. Each provider processes data only as needed to perform that role. This draft does not describe their separate retention rules.
Your choices
You can leave a myth unlisted, publish it, allow or revoke social featuring when that control is offered, and delete the stored myth from the device that forged it. Deleting removes MYTHME’s copy of the generated portrait, character text, age attestation, and consent record for that myth. It does not reach into an AI provider’s systems. Unchecking featuring withdraws that optional permission.
To ask for a removal you cannot make yourself, or to withdraw a permission, email Mythmeofficialteam@gmail.com.
Age
Before a photo, MYTHME asks whether someone is 18 or older, 13–17, or under 13. It does not ask for a birth date.
Only “18 or older” can upload a photo and forge a myth, and only after a separate unchecked consent box. That attestation is what the person says; this beta does not independently verify their age.
Ages 13–17 cannot forge a myth. A minor’s own checkbox is not treated as parent or guardian permission, and this beta has no way to verify a parent or legal guardian. No photo is requested. This is not a claim that a future parental-consent system would be legally sufficient.
Under 13 is not supported. That screen does not collect a photo, birth date, email, or other personal information.
Creating a myth does not publish it. Gallery publishing is a separate confirmation. Official social featuring is another separate choice and is not offered for anyone under 18. Myths created before the age question have no age group stored; their existing publish and featuring controls are unchanged.
See also the Terms of Use.