Privacy policy
Effective 6 September 2026.
This covers three things: this website, the platform behind it, and the parts of the Makit app that talk to us — your account, and the count of how many copies of the app are installed.
This website collects nothing
There are no accounts here, no cookies, no session, and no analytics of any kind. Pages are rendered on our server and cached, so your browser never asks our platform for the contents of a page. The fonts are served from this domain rather than from Google, and the pictures are our own copies rather than links to somewhere else, so loading a project page does not tell any third party that you looked at it.
The one exception: the open count
When you click “Open in Makit”, your browser sends us one request so the number on the page can go up. It carries no identity. To count one person once a day we take your IP address, join it to today’s date, hash the two together, and keep the first sixteen characters of that hash.
The address itself is never written down. Because the date is inside the hash, a row from yesterday matches nothing today, so the table cannot be read back as a list of who looked at what — it can only answer “have we already counted this one today”.
Your account
Accounts exist only in the app. Sign-in runs through Supabase, using Google. We ask Google for the ordinary sign-in scopes and receive your email address and basic profile — your name and picture. We do not ask for anything else and we cannot read anything else in your Google account.
The session token lives on your own machine, encrypted, in the app’s local database. Signing out signs out that machine and leaves your other machines alone.
What the platform stores about you
- Your profile: handle, display name, picture, and a short description if you write one.
- Which repositories you listed, and the record that you proved you can push to them.
- A cached copy of what we read from those repositories — the title, the pictures, the parts list and so on. That is content, not personal data, and it can be rebuilt from the repository at any time.
- What you post: comments, ratings, builds and their photos, bookmarks.
Comments, builds and profiles are public. Bookmarks and your individual ratings are not shown to anybody else.
Install analytics, and the setting that does not cover it
The app tells us when it is installed for the first time, and when it is updated to a new version. Each message carries an install identifier, when the install happened, and the app version — nothing about you, your projects or your files.
The setting in the app that turns off usage reporting does not turn this off. It is how we know how many people are running Makit at all, and it stays on. We are telling you plainly rather than letting the wording of that switch imply otherwise.
What it cannot tell us: uninstalling sends nothing, and reinstalling on a machine that kept its settings looks like the same install rather than a new one. These records are kept indefinitely, because a count of installs that shrinks as old rows expire is not a count of installs.
Who else touches any of this
- Vercel runs this website and the platform, and keeps the ordinary request logs a web host keeps.
- Supabase holds the database and runs sign-in.
- Google, if you sign in with it — they know you signed in to Makit.
- Resend delivers the only two letters we send: somebody has asked to take over one of your listings, and one of your listings has been hidden.
We do not sell anything to anybody, and there is no advertising here to sell it for.
Seeing it, changing it, deleting it
Your profile and your posts are editable in the app. Closing your account deletes your listings, deletes your bookmarks and ratings, and takes your name off your comments and builds — the writing stays, because it is part of somebody else’s project page, and it stops being attached to you.
If you want a copy of what we hold, or want something removed that the app will not remove, write to hello@makit.build.
Children
Makit is not meant for children, and an account needs you to be old enough to hold one where you live. If we learn that an account belongs to a child, we close it.
Changes
If we start collecting something new, this page changes before the collecting starts, and we say so rather than quietly editing the text.