Morphiq

Docs / Get Started / Privacy

Privacy

What Morphiq keeps about you, who else handles it, and how to have it removed. Last updated 3 November 2026.

In short: an email address, your plan and a fingerprint of your key. No passwords, no card numbers, no ads, and nothing is sold.

Who runs this

Morphiq is made and run by Pratham Patel. Where this page says Morphiq, that is who it means.

What Morphiq keeps

You can use the demos, read the free components’ source and install them without an account, and then Morphiq stores nothing about you; the host keeps its ordinary request logs, described under Who else handles it. An account is for buying Pro and for the key that installs it, and these are the only things an account holds.

Email address
The one you signed up with, or the one Google or GitHub hands over when you sign in with them. It is how your account is found and where sign-in codes are sent.
Sign-in record
Kept by Supabase, which runs sign-in: when the account was made and last signed in, which ways of signing in it has used, and for each sign-in the IP address and browser it came from.
Plan
Whether you have Pro, which plan, when it ends if it is annual, the payment provider’s reference for the order, and how much of it was paid and not refunded, before tax. Nothing else about a purchase.
CLI key
Only a one-way fingerprint of your key (a sha-256 hash) and its first few characters. The key itself is shown to you once and is not kept, so nobody, Morphiq included, can read it back.
Request counts
How many requests for a Pro component each key made in a given minute, to hold the rate limit. Not what was asked for, and nothing is counted for a free component. Old counts are swept away.

Morphiq has no passwords to keep, and does not store card numbers, phone numbers or postal addresses. Google or GitHub may send a name and a picture along with your email address, and Supabase may keep them as part of the sign-in record. Morphiq’s own code does not read, show or use them.

Signing in

By email, Morphiq asks Supabase to send you a code, and you type it on the page. The email is sent by Supabase for Morphiq.

With Google or GitHub, you are sent to them, they confirm who you are, and they send you back with your email address. Morphiq asks only for the basic identity they offer. It never asks to read your repositories, files or contacts, or to act for you, and it never sees your password there.

To slow down scripts, the sign-in form counts how often it is asked from one place: a scrambled form of your IP address and a number, a minute at a time. The scrambled form cannot be turned back into your address, and old counts are swept away.

Google user data

If you sign in with Google, Morphiq receives your Google email address and the basic profile Google shares with it. It uses them for one thing: finding or making your Morphiq account. They are not sold, shared for advertising or shown to anyone else, they are kept only as long as the account, and they are deleted with it.

Morphiq’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Who else handles it

Supabase
Holds accounts and the database, runs sign-in and sends the sign-in emails.
Vercel
Hosts the site and the install registry. Like any host, it keeps ordinary request logs: the address asked for, the time and the IP address.
Google Analytics
Counts visits, as described below.
Google Fonts
The site’s text is set in Inter and Product Sans, loaded from Google’s servers, so Google sees your IP address and browser when a page opens.
Google and GitHub
Only if you choose to sign in with them. Their own privacy policies apply to what they hold.
Cloudflare
Checks that a person, not a script, is asking for a sign-in code (Turnstile). The check runs on the sign-in page only, so Cloudflare sees your IP address and browser there.
Polar
Once paying is switched on, Pro is sold through Polar, which is the seller on the receipt: it takes the card, works out the tax and sends the invoice. Card details go to Polar and never touch Morphiq. Polar is given your email address and your account’s id so the purchase reaches the right account, and Morphiq keeps Polar’s order reference, the plan, its status and the amount paid and not refunded.

Analytics and your browser

Morphiq uses Google Analytics to count visits: which pages are opened, roughly where from, on what kind of device. Google sets its own cookies for this and receives the page address, your browser and device details and your IP address. If a sign-in code is in the address while you come back from Google or GitHub, counting waits until it is gone, so a code is never sent to Google.

Morphiq itself sets no cookies. It uses your browser’s storage for your colour theme, for your sign-in session so you stay signed in, for a short note of which sign-in buttons to show, and, while you sign in, for the page to bring you back to. Signing out removes the session. You can clear the rest in your browser’s settings.

There are no ads, no profiles built about you, and no data is sold or rented.

Keeping and deleting

An account is kept for as long as it exists. “Delete your account” on the account page, after you type your address to confirm, removes the sign-in, the key, the Pro record and the request counts at once. It cannot be undone.

It does not reach components already installed in your projects, which are yours; anything a payment provider keeps about a purchase; visits Google Analytics has already counted; or the host’s ordinary logs, which are cleared on its own schedule.

Your say

Your email, plan and key prefix are on the account page, where you can also sign out or delete the account. To ask for a copy of what is kept, to have something corrected, or if deleting did not work, write to me@prathampatel.design.

Morphiq is a tool for people who build websites. It is not meant for children.

Changes

If this page changes in a way that matters, the date at the top changes with it.