Privacy policy

Effective date: 11 August 2026. Applies to Morphink 0.1.0, in a browser and on a phone.

In one line: Morphink has no accounts, no ads and no trackers, it keeps your play on your own device, and the only things that ever leave are the ones section 7 lists, when you use the feature that sends them.

This page covers two different ways of playing, and they answer differently. Section 2 says which one you have. If you only want the short version, sections 1 and 2 are it.

1. The short version

Morphink is a word game, and the game itself runs on your device. The dictionary, the scoring, the daily word and the solver are all in the download, which is why it works offline.

There is no account to create, no email to give, and no ads. We never ask for your name, and nothing we hold could tell you from anyone else who plays.

Some features need other people, and those cannot happen on your device alone: a duel with someone in another city, a shared event, a place on the daily board. Section 7 lists every one of them, says exactly what it sends, and says which ones are switched off until you turn them on.

2. Which Morphink this covers

The browser version, at app.morphink.app. This is the version you can play today. Loading the page is an ordinary web request: your browser tells our host its address and what kind of browser it is, the same as any site you visit. Once it has loaded, the game runs in the page, and the online features in section 7 can reach our server when you use one.

A downloaded app, from Google Play or the App Store. Morphink is not published in either store yet. When it is, this page will be updated in the same release to say whether that build reaches our server or is built with no server address at all. A build with no address cannot reach us: the features in section 7 are compiled in, but with nowhere to connect they never run.

Everything else on this page is true of both.

3. What we collect

Nothing that identifies you, and nothing at all unless you use one of the features in section 7.

There is no account, no profile and no login. We never learn your name, your email or your phone number. What our server can see, when you use an online feature, is a random key your own device made up (section 6) and the words of the run you chose to send. Nothing joins that key to a person, because nothing anywhere holds a person to join it to.

We also do not:

• ask for or store your name, email, phone number, or address
• read your location
• read your contacts, calendar, photos, camera, or microphone
• use an advertising identifier, or any identifier from Apple or Google
• show ads, or work with an advertising network
• use any third-party analytics service
• profile you, or make any decision about you automatically

4. What the game keeps on your device

Morphink remembers your own play in a database on your device. In the browser version that database lives in your browser's own storage for app.morphink.app, which means a different browser, a different computer or a private window is a different player as far as the game is concerned. That data does not leave on its own. Apple and Google do not count it as collection, but it is your play, so here is what is stored:

• Finished runs: the mode, the starting word, how many morphs you made, your score, how the run ended, and when
• Every word you have played, and how many times (this fills the Word Book and the dashboard)
• Your settings: sound, haptics, reduced motion, dyslexia-friendly type, ink and paper choices, timer preset, keyboard layout, and language
• Two optional names for the players in a hot-seat duel, only so the screen can say whose turn it is. You can leave them blank
• One unfinished run, so closing the app mid-game does not lose it
• Your Folio pages: commissions you have completed, including a full recording of the run that earned each page, so it can play back
• Shared events you have joined, by room code, with the scroll as it stood when the event closed. Other players show up as anonymous keys, never as names
• A short list of recent starting words, so the game does not hand you the same one twice, and a short list of words the Scribe has already shown you
• A random 32-byte key generated by your device (see section 6)

Deleting the app deletes all of it. In a browser, clearing site data for app.morphink.app does the same thing. There is no copy on our side. One caveat that is not ours to control: if your phone backs apps up to your own cloud account, this database may be included. On Android we ship with that switched off. Either way, that copy lives in your account, and we cannot read it.

5. What happens when you share

The summary screen has Share and "Copy as text." Both only run when you tap them.

Share hands one image and one line of text to your device's share sheet. You pick where it goes. Morphink does not choose the destination and does not learn what you chose. Copy puts the text on your clipboard. Neither contacts a server.

The shared image and text include your chain, your score, your fastest morph, and the puzzle number. They do not include the random key from section 6, or anything that identifies your device.

6. The random key

The first time anything needs one, your device generates a random 32-byte key and stores it locally. It is not derived from your hardware, your Apple or Google account, or any identifier those companies issue. The game never learns your name, so the key is not tied to one.

It exists so that a server can tell that two submissions came from the same installation, which is enough to keep a leaderboard honest and to hold your seat in a duel, without knowing who you are.

The key is created only when something needs to sign, and it is sent only by the features in section 7. If you never use one, it is never created.

Want a new one? Delete and reinstall the app, or clear site data in your browser. There is no in-app button for that yet; there should be.

7. Online features, and what each one sends

These are the only things that ever leave your device. Each one runs when you use it, and not before.

Two of them stay off until you ask twice. The daily leaderboard is off until you turn it on in Settings. It starts off on a fresh install and stays off after an update, and the screen tells you what would leave before you opt in. Turning it off again stops new submissions. Rows already on a board stay, and we say so rather than pretending they vanish.

• Daily leaderboards. Off until you turn it on. Submitting a daily result sends that run's words, score, times, and puzzle number, plus the random key, so one entry per puzzle per device can be enforced and so the score can be re-checked. The server replays your run with the same engine your phone used.
• Online duels. Playing someone who is not in the room sends the words you play, when you played them, and the random key to a room on our server for the length of the match. Not your name. The optional duel names above are for hot-seat play on one device only.
• Playing a stranger. Leaving a seal tells our server this installation is looking for an opponent, in which mode and language. If you are paired, both of you play the same starting word alone. Neither sees the other's run until their own is in, then your recording is shown to that one person. A recording left waiting is kept 14 days, then deleted with the challenge.
• Shared events. Joining with a code sends your run to that event so everyone in it can read the scroll. This is the one feature where your play is shown to a group, which is why it is limited to events you join with a shared code. Entries are deleted 30 days after the event closes, along with the event.
• How a word is said. When a pronunciation is not in the download, the game fetches audio for one word. That request has the word and its language, and no key.

Three more are written and are not switched on anywhere. They are described so that a release which turns one on is a change you can see rather than a surprise, and this page will name it again when that happens.

• Word definitions from the internet. When a definition is not in the downloaded glossary, the game could ask our server for one. That request would have the word and its language, nothing else. Our server may pass those two fields to a language-model provider and cache the answer. Nothing in the game calls it today; definitions come from the download.
• Being told something happened. If you leave a seal, the game could tell you when it is answered. That needs a delivery token from Apple or Google, the only item anywhere on this page that would identify your installation to a company that is not us. The browser version has no such feature at all.
• First-party diagnostics. A small fixed list of events (a run started, a run ended, the daily was opened or shared, reduced motion is on, the engine failed to load), with timings measured from the start of your session rather than from your clock. No such code runs today. If it ships, it will be described in the app, and you will be able to turn it off.

Everything in this list is optional. Morphink is meant to be playable with no connection, and no future version will make play depend on one. The one exception is the browser version, which has to be fetched before it can run, and which cannot promise a plane the way a downloaded app can.

8. Where the server is, and who else touches your request

Our server runs on Cloudflare, which operates the network that answers when your device connects. Like any web host, Cloudflare's edge sees the address your request came from and basic details of the connection, and keeps short-lived operational logs for security and reliability. That is true of loading the game in a browser as well as of the features in section 7, and it is true before any of our own code runs.

Our own code writes none of it. There is no cookie, no analytics tag and no logging of our own on any of the three services we run: the site you are reading this on, the page the game loads from, and the server the features in section 7 talk to. The first two hold nothing at all.

We do not use those logs to build a profile, and there is nothing in them we could join to a player: the game sends no name and no account, and the random key in section 6 is not derived from your device or your network.

Definitions, if that feature is ever turned on, are the one place a request would reach a company that is not us or our host. It is named in section 7 for that reason.

This website links out to three other places: the two app stores, and our YouTube channel from the "How to play" page. Following one of those links takes you to that company, and what they do then is theirs and is covered by their own policy. Nothing is loaded from any of them while you are here: the store badges and the codes on this site are files we serve ourselves, and no video is embedded in any page, so no request reaches Apple, Google or YouTube unless you choose to follow a link. The store links carry a label saying which page of ours you came from, which the store counts and we never see.

9. Your choices

You can: leave the daily board switch off, which it already is; skip the optional duel names; not tap Share; play only the modes that need nobody else, which is most of the game; and delete the app, or clear site data in your browser, to erase everything held on your side.

Deletion of anything already sent is a harder problem and we are not going to pretend otherwise. The random key is the only handle on your entries, and only your device holds it, so deletion has to be your own device proving the key is its own. That is a feature we still need to build. Until it exists, write to the address in section 12 and we will do it by hand.

10. Children

Morphink is made for adults and is not directed at children. It does not ask for age, does not show ads, and has nothing to buy. The dictionary is filtered so the game does not put coarse words in front of anyone unprompted.

11. Retention

A leaderboard entry stores a verified summary and chain, keyed by a hash of the run's snapshot. The snapshot itself is checked and then discarded. Disputes are settled by recomputing against that hash from the player's own device.

That is how the code is shaped, not a slogan about careful deletion. A submitted run is re-simulated; the summary from that re-simulation is what gets written; the bytes used for the check are not kept. There is no run recording behind a board row to expire. The board row itself stays. A leaderboard that forgot its entries would not be a leaderboard.

Two other things are stored briefly, and each deletes itself:

• Sealed challenges: the recorded run behind a standing duel, so your opponent can watch it once they have played their own. Kept 14 days, then deleted with the challenge.
• Gathering entries: recorded runs from a shared event, so the scroll can be read after it closes. Kept 30 days after the event closes, then the whole event is deleted.

A duel room holds the match while it is being played and closes with it.

12. Changes to this policy

This page changes in the same release as the thing it describes, and the change is noted in the release notes. The date at the top is when it last changed.

The last change, on 11 August 2026, was this one: Morphink became playable in a browser at app.morphink.app, and that version can reach our server for the features in section 7. The version of this page before it described a build that could not connect to anything, and said so.

13. Who "we" are, and how to reach us

Morphink is made by Vinerals Technologies, a software cooperative in Montréal, Canada. Everywhere this page says "we" or "us", that is who it means. On Google Play and the App Store the developer account is Vinerals Tech, which is the same people.

Questions about this policy, or a deletion request under section 9: eakwofie@vineralstechnologies.com