GDMacros

Privacy

Accounts on GDMacros are optional. Browsing and downloading macros needs no account and collects nothing about you. If you do create one, the only personal data involved is your email address. This page covers the website only.

What is stored in your browser

A few small preferences are kept in your browser's local storage. This is not a cookie, it is never sent to a server, and it never leaves your device. This is separate from the account session cookie described below:

  • gdmacros:recent: the last few macros you opened, for the "Recently viewed" row.
  • gdmacros:favorites: the macros you starred.
  • gdmacros:sort and gdmacros:view: how you like the catalog ordered and laid out.

Because it lives on your device, this list does not follow you to another browser or another phone, and clearing your browser data clears it.

If you create an account

Accounts are handled by Supabase, which stores your email address and a hashed password on your behalf. We never see or store your password ourselves.

An email address is required so the account can be verified and so a password can be reset. Those emails are delivered by Resend, which handles the sending on our behalf and therefore sees the address the message goes to. Nothing else about you is collected, and there is no profile, no display name and no public page.

Being signed in sets a session cookie so the site knows it is you between pages. Signing out removes it and revokes the session.

You do not need an account to use this site, and having one changes nothing about what you can download. Favorites and recently viewed are still stored in your browser rather than on your account, so they do not follow you between devices.

Analytics

The site uses Vercel Web Analytics and Vercel Speed Insights, from the company that hosts it. They count page views and measure how quickly pages load.

Neither sets a cookie, and neither builds a profile of you across sites. What they record is the page visited, a coarse location such as the country, and technical details like browser and device type, plus loading measurements. There is no way for us to look up an individual person in it.

A content blocker or a "do not track" style extension will block both, and the site works exactly the same with them blocked.

Translation

The language picker uses the Google Translate website widget. If you do not use it, it does nothing.

If you do pick a language, Google sets its own cookies to remember that choice and the text of the page is sent to Google to be translated. That is Google's processing, under Google's privacy policy, not ours. Apart from these and the account session cookie, the site sets no cookies at all.

Video embeds

Macro pages embed the showcase video from YouTube. Playing one connects you to Google's servers, and from that point Google can set cookies and log the view under its own policy, exactly as it would on YouTube itself.

The thumbnails are loaded as plain images from YouTube and play nothing on their own.

Downloads

Macro files are hosted on MediaFire. Every download button says so, and names the file, before you click it. Following one takes you to MediaFire, which is a separate company with its own privacy policy, its own cookies and its own adverts.

GDMacros does not see who downloads what. There are no download counters tied to a person and no redirect tracker in the middle.

Reporting and submitting

Report a broken macro opens an issue on our public GitHub repository. Anything you write there is public and is handled under GitHub's privacy policy. You need a GitHub account to post one.

Submitting a macro uses a Google Form, so what you enter goes to Google and then to us. Only send what you are happy for us to have.

Changes

Accounts arrived in August 2026, and this page was updated before they went live rather than after. If anything else changes about what is collected, this page changes first.

Questions, or something here that looks wrong? Open an issue on the repository.

See also the FAQ and the guidelines.