Privacy

This page lists what Makeroo collects, who handles it and how to have it removed. It describes what our code does today. We do not sell data.

Listing a product

A submission collects the product name, tagline, description, product URL, an optional logo URL, a category and up to five tags. It can also include pricing, open source status, a repository URL and platforms. Every submission includes a maker email. Makeroo admins also add some listings themselves, with a placeholder address instead of a maker email.

A live listing publishes its name, tagline, description, URL, logo, category, tags, launch date, attributes and whether it is claimed. These appear on the site, in the public API, through the MCP server, in our feeds, in our newsletter issues and in our llms text files. A live listing's page also shows the date and reasons recorded when it was approved. Those reasons come from the AI check or from a reviewer.

The maker email is never published. Makeroo admins see it in the review queue. We use it to match a signed-in maker to their listings. For submissions made through MCP, we email it a confirm link. The web form sends no confirm email.

Anyone who holds a submission id can see that submission's status, verdict and reasons. To check a submission we read the product's site with a crawler named MakerooBot.

Signing in

You sign in with a link sent to your email. The link works once and expires after fifteen minutes. We keep every email address typed into the sign-in form, with the time of the request, whether or not the link is used.

Signing in sets one cookie, named session. It is HttpOnly and Secure and lasts thirty days. Signing out ends the session.

A signed-in maker can claim a listing by proving they own its domain. The proof is an email address at that domain, a file on the site or a DNS record. A claimed listing can be edited from the dashboard.

Newsletter email

Signing up stores your email, when and where you gave consent, your subscription status and a hashed confirm token. You are not subscribed until you click the confirm link. After you unsubscribe, your record stays, marked unsubscribed.

Cloudflare delivers our email. We don't track whether you open a newsletter issue or click its links. We record which issues we sent you, which issue you unsubscribed from, and which issue bounced if your address stops accepting mail, so we can stop sending to it. We don't sell this data or share it with anyone but Cloudflare, which delivers the email.

Every issue has a one-click unsubscribe link.

Orders

Paid options go through Stripe Checkout. We pass Stripe the email you are signed in with. You enter card details at Stripe, and they never reach us.

We store the listing, product, launch date, status, amount and Stripe session id of each order. We also store the id and type of each Stripe event we receive.

IP addresses

We use IP addresses to limit abuse. For listing submissions, newsletter signups and sign-in link requests, we hash the IP address, the email address and the pair of them with a plain SHA hash and no secret key before using them as rate limit keys. The URL prefill on the submit form hashes the IP address the same way. These counters are deleted after two days.

The submit form, the newsletter signup form and the sign-in form use Cloudflare Turnstile to check for bots. Turnstile loads on those forms and receives your IP address.

Analytics

We use PostHog, hosted in the EU. Browser analytics go through our own ingest path, which forwards your IP address to PostHog and strips cookies.

In the browser, PostHog records page views, page leaves, clicks and form submissions, errors and session recordings. A click or submission event includes the text and attributes of the element, never what you type. Recordings mask every form input. They also mask the email shown on your dashboard and the maker emails an admin sees in the review queue. Other text on a page can appear in a recording.

Listing confirmation, newsletter confirmation, unsubscribe and sign-in links carry a private token in their address. We record no session on a page that loads with a token in its address. The button on those pages posts to the page address, so the token is not in the markup that clicks and form submissions report. We also redact token values from the page address sent with an event.

PostHog keeps an anonymous identifier in local storage and in a cookie that lasts a year and can be shared with other makeroo.app subdomains. If your browser sends Do Not Track, the browser analytics do not load. Server events and error capture ignore Do Not Track.

PostHog is set to create person profiles only for identified users. Makeroo never identifies anyone.

Our server sends events when a listing is submitted or verified, a newsletter signup is made or confirmed, an issue is sent, news is ingested, a sign-in link is requested and an MCP tool is called. These events carry no email addresses. They share one server id and create no person profile. Unhandled server errors are sent with email addresses, URL query strings and bearer tokens redacted.

In your browser

Your theme choice is kept in local storage. We do not send it to our server, but a session recording can show it.

Listing logos load from the address the maker gave or, if none, from the icon on the product's own site. Your browser fetches them from there, so that site sees the request.

Who processes data

Cloudflare

Hosts Makeroo on Workers and stores our database. Sends our email, runs Turnstile and answers the DNS lookups for listing claims. Workers logging is on, so Cloudflare may keep request logs.

Anthropic

Claude Haiku checks submissions and fills in listing details. It receives the listing name, tagline, description, URL and category, plus text read from the product's site and its pricing and download pages. For the submit form's prefill it reads text from the page you enter and its pricing and download pages. For news it reads the titles and excerpts of public feed items. It never receives the maker email.

PostHog

Analytics, error tracking and session recordings, hosted in the EU.

Stripe

Takes payments for paid options. Stripe's own privacy policy covers what you enter there.

Makeroo MCP server

The MCP server runs at https://makeroo.app/mcp. It has no authentication and no accounts. It keeps no session between calls.

The read tools search_listings, get_listing, list_categories and get_submission_status write nothing to our database. Each call is counted in analytics by tool name. The query is not recorded. get_submission_status returns the status, verdict and reasons to anyone who holds the submission id.

submit_listing stores the same fields as the web form, including the maker email. The listing starts as pending. We hash the caller's IP address and the maker email for rate limits, as described above. We email the maker a confirm link that expires after two days. The AI check runs after the maker confirms, or after a signed-in maker buys fast-track review. Unconfirmed submissions are rejected.

What gets published and what stays private follows the same rules as any listing. The AI client that calls these tools has its own policy for what it does with the results. That is outside Makeroo.

Keeping and removing data

Nothing deletes listings, rejected submissions, maker emails, accounts, sign-in requests or newsletter records automatically. We keep them until you ask us to remove them.

To remove or correct your data, email admin@makeroo.app. We delete or correct it. Makers can also edit a claimed listing from the dashboard. Every newsletter issue has an unsubscribe link.

Contact

Questions about this page go to admin@makeroo.app.