Privacy policy
What Myrlin Studio stores about you, why it is stored, and who else handles it.
Your account
Sign-in is handled by Clerk. Myrlin receives and stores your Clerk user ID, email address, name, profile picture link and the time you last signed in.
When an account is created, Myrlin records the IP address it was created from. To stop one person from collecting the signup bonus many times, Myrlin also keeps a device fingerprint for seven days: a one-way hash of browser details (user agent, language and compression settings), stored with the account ID, IP address and time.
For the same reason, when you are signed in the site sends your browser tab's random session ID (the one described under usage measurements) with its requests to Myrlin's API, unless your browser sends Do Not Track or Global Privacy Control. Myrlin stores a one-way hash of it with a new account, so several accounts made in the same browser tab can be recognized and the signup bonus given once.
To keep the signup bonus to one per person, the site also keeps a random ID in your browser's local storage and sends it to Myrlin's API with signed-in requests, even when your browser sends Do Not Track or Global Privacy Control. It is used only to recognize several accounts made in the same browser, not to track what you do on the site: Myrlin stores just a one-way hash of it, does not use it for usage measurements and never shares it with anyone else.
What you create
Myrlin stores what you put into Myrlin Studio and what it builds for you: prompts, reference pictures you upload, generated models, textures, preview and inventory images, animations, effects, exports and your build history. Files are kept in Cloudflare R2 storage and records in Myrlin's database.
To build a model, your prompt and reference pictures are sent to the AI model providers that Myrlin Studio uses.
Your builds are not shown to other users unless Myrlin features one in the public gallery. A featured build shows the model, its texture, preview images, its name and its prompt, without your name or account. To have a featured build removed, email arthur@myrlin.io.
Payments
Payments are handled by Stripe on its own checkout page, so Myrlin never receives your full card number. Myrlin keeps records of your purchases, subscription status, credit balance and credit history, including bonuses, spending and refunds of credits.
When you copy another creator's model, Myrlin records the copy, its price, which of your credits paid for it and both accounts, so it can credit the creator, apply its limits and handle refunds. To find copies between linked accounts it compares the same signals it keeps to spot duplicate accounts. Creators see how many copies were made and what they earned, never who made them, and buyers never see who made a model.
Usage measurements and error reports
The site records a small set of its own events, such as page views, how long a page was visible, clicks on named buttons and whether a build was attempted. They are sent to Myrlin's API with a random session ID kept in your browser tab's session storage. Page addresses are reduced to the section name, for example /pricing, so search terms and other values in the address are not kept. Each batch also names the site address that sent it, for example forge.myrlin.io, and whether the browser reports that automation software controls it, so our own test runs and preview copies of the site are not counted as visitors. When you are signed in, these events can be linked to your account.
When you arrive from a link with campaign tags (such as utm_source or utm_campaign) or an ad click ID (such as gclid or fbclid), or from another website, the site keeps those tags, the click ID, the other website's domain name (not the full address) and the first page you landed on in your browser's local storage for up to 90 days. If you create an account, they are sent with your first signed-in visit and saved once with your new account, so Myrlin can tell which links and ads bring new accounts. With the account, Myrlin keeps only the utm_source tag, the name of a Myrlin campaign, the other website's domain name, the first page and whether an ad click ID was present (never the ID itself) for as long as the account exists, and deletes them when the account is deleted. Once sent, they are removed from your browser, which keeps only a short one-way code of the account so they are not sent twice.
Myrlin Studio also records which version of My assets you saw, whether you switched between the new and the old page, which buttons you press on it and which options you pick there, such as the game, the armour piece or the Minecraft version, and how far you got from opening a set to exporting it. These are fixed labels and IDs, never the names, prompts or pictures of your assets.
When Myrlin Studio asks whether your prompt or picture describes several assets, it records that the question appeared, whether it was on screen, which answer you picked or that you left it unanswered, and the build it belonged to.
When you arrive on Myrlin Studio, the first page you open in a browser tab also tells us where that visit came from: the name of the site that linked you (for example reddit.com, never the full address), any campaign tags in the link, the names but never the values of ad click identifiers, the page you landed on, and a random first-visit number that your browser keeps for up to 90 days so we can count how many visits from each source later led to a sign-up; nothing of this is sent when Do Not Track or Global Privacy Control is on, and these records are deleted after 90 days. It also says whether this browser has signed in to Myrlin Studio before, as a yes or no, without saying which account.
If your browser sends Do Not Track or Global Privacy Control, these events are not sent, and a sign-up source already kept in your browser is removed.
When something breaks in the website, an error report goes to Sentry so it can be fixed. Session replay is turned off.
Sometimes Myrlin Studio shows two versions of a page or screen to learn which one works better. To show you the same version each time, your browser keeps a random ID in local storage; it is not tied to your name or email. When you see a version that is being compared, the site records which comparison it was and which version you saw, with that random ID, or with your account when you are signed in, so we can count how many people on each version went on to sign up or buy. These records are not sent when Do Not Track or Global Privacy Control is on, and they are deleted after 90 days. In the EU, the EEA, the UK and Switzerland, a visitor who is not signed in is not part of these comparisons: no ID is kept and the usual version is shown. When a comparison is about what you can buy, Myrlin's server picks your version and keeps it with your account, so you see the same offer on every device.
If you visit from outside the EU, the EEA, the UK and Switzerland, and your browser does not send Do Not Track or Global Privacy Control, the site also sends PostHog, a product analytics service, a record of which pages you opened and which buttons you used, how far you scrolled, and signs of trouble such as an error message or repeated clicks on the same spot, so we can see where people get stuck or leave. Each record uses fixed labels, such as which page, which button or whether the screen is phone-sized. It comes with a random ID that lasts while your browser tab is open, and after you sign in, a one-way code made from your account ID, not the ID itself. Outside session recordings, PostHog never gets what you type or upload, your name, your email address or your IP address: the records pass through our own server first. That ID is made from the short-lived ID our own analytics already keeps for your browser tab; nothing more is stored on your device for PostHog. If you are in the EU, the EEA, the UK or Switzerland, or your browser sends Do Not Track or Global Privacy Control, nothing goes to PostHog. When session replay is turned on for a sample of visits, PostHog also gets a recording of the page as you saw it, including what you typed into the prompt box and other product fields, while masking password, email, code and key fields, skipping sign-in, sign-up, payment, account and admin pages, and never recording in the EU, the EEA, the UK or Switzerland or when Do Not Track or Global Privacy Control is on.
Messages to Myrlin
Messages you send through the contact form are emailed to Myrlin and stored so they can be answered.
Cookies and browser storage
Clerk sets cookies to keep you signed in. Create and the Editor keep some settings and unfinished work, such as a draft prompt, in your browser's local storage. The site also keeps how you first arrived there for up to 90 days, as described under usage measurements. It also keeps the random ID that keeps the signup bonus to one per person, described under your account. When a page is being compared in two versions, it keeps a random ID that shows you the same version each time, described under usage measurements.
Myrlin plugin for Hytale
The Myrlin plugin is a free mod for Hytale worlds and servers. It contacts Myrlin's servers (api.myrlin.io) only when a player types /myrlin get with an install code, or when the server's owner has turned on Myrlin accounts. For /myrlin get it sends the code and the plugin and game versions. Our server receives the network address of the computer or server running the game and uses it to limit repeated wrong codes. If accounts are on and a player links their Myrlin account, the plugin sends that player's Hytale id and name, the game, and whether the server checks player identity, together with the server's own connection key, so the website can show which server is linked and let the player remove it. The plugin downloads only asset packs (models, textures and data) made from models the code's owner has on Myrlin Studio, and keeps them on the machine running the game. It sends no analytics, telemetry or advertising data, and nothing about players who do not use these commands.
Services that handle your data
- Clerk: sign-in and account management
- Stripe: payments and subscriptions
- AI model providers: turning your prompt and reference pictures into a build
- Cloudflare R2: storage for uploaded pictures and generated files
- Vercel: hosting for this website
- Fly.io: hosting for the Myrlin API
- Sentry: error reports from the website
- Resend: delivering contact form messages to Myrlin
- PostHog: measuring which pages and buttons people use, so we can see where they get stuck
Deleting your data
To delete your account and the data stored with it, email arthur@myrlin.io. When an account is deleted, its models, pictures and other files are erased. Payment and credit records are kept with your personal details removed.
Records of copies you made or sold are kept with your personal details removed. Copies other accounts made of your models in the 14 days before the deletion are refunded to them.
Contact
Questions about your data go to arthur@myrlin.io. The terms of service explain credits, payments and the gallery.