MergeSafe
← mergesafe.ai

Privacy

Last updated 27 October 2026.

This page covers this website, its mailing list, and the MergeSafe product. Before signup opened to everyone, people could join the list through a form on this site. For people on that list we keep the email address you give us and a one-way hash of your IP address, which is there only to stop the form being flooded and is short-lived. That is everything the mailing list holds about you. If you sign in to the MergeSafe app or install the GitHub App, we also hold the data the product needs, described below under “Your code and pull requests”. We also count visits to this site and to the app's sign-in page, and the campaign tags on the links that brought them, without cookies: we store no IP address or other personal data for it, only totals and approximate location (country and region) — see “Counting visits” below.

Separately from that, the server the form talks to keeps an ordinary operational log of the requests it handles — not who made them. It is described below, under logging, because it is a real record even though it does not identify anyone, and a privacy page that mentions only the tidy half is not worth reading.

Who is responsible

Z Squared Technologies LLC, 31560 Crabtree Lane, Solon, Ohio 44139, United States, is the controller of the personal data described here. For anything on this page, write to privacy@mergesafe.ai.

What we collect

Reading this site is not logged. Request logging is not switched on for the pages themselves, so we hold no record of who visited, when, or what any one visitor read; the visit counts described under “Counting visits” are totals, not records of anyone. Your browser still has to reach a server, and Amazon — who serve the pages for us — process that request to deliver it under their own operational terms. We do not receive, store or analyze it.

Requests to our API are. The form posts to an API that we also use for our own dashboard, and that API records every request it handles — signups and our own administrative traffic alike — for 30 days: a request identifier, the method and route, the response status and its size, and, when our own code fails, that failure's error message (a timeout, say — never anything you sent). It is there so we can tell a broken form from an empty one.

What that record does not contain is anything pointing back to a person: no email address, no IP address, no account. A line in it says a request of some kind happened and how it ended. We would rather describe it plainly than claim a tidier "no logs at all", which stopped being true the moment the form went up.

Counting visits

We count visits to this site and to the sign-in page of the app at app.mergesafe.ai ourselves, without cookies and without any third-party analytics service. Each page sends a small request to our own app when it opens, and another when it is hidden or left (again if you come back to it and read on), and what we keep from it is a set of daily totals: how many visits, from which country and region (and, where available, city) — approximate location that the request already carries, never a precise one — the page visited, the name of the site that linked here (just its name, such as news.ycombinator.com, not the address of the page), and the campaign tags in the link (utm_source, utm_medium, utm_campaign, utm_term, utm_content). Tags that look like an email address or an identifier are dropped, and advertising click identifiers are never stored — only that a visit came from a paid click. We also count how many people press “Sign in with GitHub” and how many finish signing in. On the pages of this website (not the app's sign-in page) we also count how long they are viewed and how far they are scrolled, without cookies or personal data: kept only as totals, with the request counted under the same daily visitor hash described below.

We store no IP addresses and no other personal data for this. To count a visitor once a day rather than once per page, we keep a one-way hash of the IP address and the browser's user-agent string, made with a secret that changes every day. It cannot be turned back into either and cannot be matched to the next day's. It is marked for deletion 48 hours after it is made, and the database removes it shortly afterwards rather than at that exact moment. The address itself is never written down, and the request is logged only as an operational line (its route, response status and timing), never with its address or contents. The totals are kept in our own database on AWS, and no one else receives them.

What we do not collect

No third-party analytics, no advertising or marketing trackers, no third-party scripts, and no tracking cookies. The one cookie these pages read is set by app.mergesafe.ai when you sign in: it holds only the value “1”, nothing about you, so the menu can say “Dashboard” instead of “Sign in”, and signing out removes it. These pages load nothing from anyone else's domain — the only requests beyond the page itself are the visit counts above, sent to our own app.mergesafe.ai — which you can check in your browser's network tab, so no third party learns you were here. Amazon still serve the page and therefore see the request, as described above; the claim is that nobody else is invited in, not that the request reaches us by magic.

Why we are allowed to hold it

You gave us the address so we could contact you about MergeSafe, which is consent. Withdraw it whenever you like by asking us to delete it — see below. The hashed IP rests on our legitimate interest in keeping a public form from being abused, which is why it is minimised and short-lived.

What we use it for

To email you about MergeSafe, and for nothing else. No newsletters, no product announcements, no “we thought you might also like”. We do not sell or rent the list and we do not share it with anyone for their own purposes.

Who else touches it

Amazon Web Services only. The site is served from AWS in the United States (us-east-1), your address is stored there, and the mail we send you goes through Amazon SES. AWS processes all of it on our instructions and for no other purpose.

Google Workspace carries mail sent to privacy@mergesafe.ai, so if you write to us about this page, Google handles that message.

How long we keep it

Your address stays on the mailing list until you ask us to remove it. We set no expiry on it and have no other use for it, so if you decide you are not interested, say so and it is gone. The hashed IP is short-lived, as above.

Your rights

Wherever you live, you can ask us to show you what we hold, correct it, delete it, or send it to you in a portable form — and you can object to us holding it at all. Depending on where you are, these may be rights under the UK and EU GDPR, or under California law, but we apply them to everyone rather than checking your location first.

Write to privacy@mergesafe.ai and we will act within 30 days. If you are in the UK or EU and think we have handled this badly, you can also complain to your national data protection authority.

Your code and pull requests

When you sign in with GitHub and install the GitHub App, we hold your GitHub account and organization identifiers, the repositories you choose, your review settings, and a record of each review and what it cost. To review a pull request we read its code and diff.

More detail is on Security and data retention.

Changes

If this page changes we will update the date at the top. If a change materially affects what we do with an address we already hold, we will email you rather than quietly amending this page.