Privacy

macrify.me · last updated 17 August 2026

Macrify sells law firms software built on the premise that their data stays theirs. It would be strange to say that and then be cagey about our own site. So: here is everything macrify.me collects, everything it puts in your browser, and how to switch the measuring off. It is short because the site does very little.

What this covers

The pages on macrify.me — the homepage, /connect, the explainer and demo pages, and the contact forms on them.

Three things it does not cover, each of which is separately governed:

• The products. ScheduleHound, Macriphone, and Arachne are applications you log into, and what they do with a firm's data is set by that firm's own agreement — not by this page.
• sites.macrify.me, which has its own notice for its request-access form.
• Other companies' sites we link to. Once you have left, you are under their rules.

If you fill in a form

There are two: the one on the homepage and the one on /connect. What you type into either is:

• Your name
• Your email address
• Your firm, and its size, if you say
• Which area of interest you picked, if you picked one
• Your message, if you wrote one

The form on /connect adds a short note about how you used the page, and since you did not type it, it should be said out loud. Attached to the bottom of your message, Jake also receives: which of the three engagement paths you opened before writing (if any — it says so plainly when you opened none), which of the seven automation categories you picked, and the heading of the example card on screen when you sent it. That is the whole of it. It is there so he can pick up where you left off instead of asking you to repeat yourself, it goes into the same email as the rest, and it is not sent anywhere else.

That gets emailed to Jacob Schumer, who runs Macrify. It is not written to a database. It travels through Resend, the service that sends the mail, and then it lives in an ordinary email inbox like any other message you would have sent him.

A second email goes out at the same time — to you. It is an automatic acknowledgement confirming the message arrived, sent from "Arachne by Macrify" with replies directed to Jake, and it uses your first name. So your name and address are used twice: once to reach him, once to write back to you. After that it is in your own inbox and your own mail provider's hands, like any other email you receive.

One exception, and we would rather spell it out than let the paragraph above quietly overstate itself. When the form on the homepage sends successfully, two of the fields — the area of interest you picked and the firm size you picked — are also recorded as properties on an analytics event, so we can see which services people write in about. Your name, email address, firm name and message are not sent to analytics, and neither are those two fields from the form on /connect. If you would rather not send even that, the analytics switch further down turns it off.

The function receiving the form also sees your IP address, which it uses to stop one visitor from submitting the form fifty times. It is held in memory only — never written to disk or to a database — and it is discarded when the server instance restarts, which happens on its own schedule and is not something we can promise a time for.

Analytics, and the cookie it sets

Most pages here run PostHog, which counts how the site gets used. To tell a returning visitor from a new one it stores an identifier in your browser — a first-party cookie and a matching entry in local storage. That is the only cookie this site sets.

What it records is the shape of a visit: pages viewed, how far down a page you scrolled, which links and buttons you clicked, which outbound links you followed, plus the ordinary technical details any web server sees — approximate location from your IP address, your browser, and whether you arrived from a search engine or a link somewhere.

It also runs PostHog's autocapture, which is on by default and which we have not turned off. That means interactions are recorded automatically rather than only where we wrote code to record them — clicks on page elements generally, form fields changing, forms being submitted, and along with each one some detail of the element involved, including its visible text. Autocapture reads the event, not the contents of what you type: it does not send the text you enter into a field. Combined with the paragraph above, the honest summary is that a fairly complete picture of how a visit moved through the page is recorded, even though none of it is attached to your name.

Two things it deliberately does not do. It does not build a profile attached to your name or email, because it is configured to create a person record only for someone who has actually identified themselves, which nobody does on a marketing site. And it is not advertising — there is no ad network here, no retargeting pixel, and nothing that follows you to other websites. It is used to work out which pages are worth writing more of.

Session replay — this one is worth reading

PostHog's session replay is switched on. It is the most invasive thing on this site and the least obvious, so it gets its own heading rather than a clause in a list.

What that means: alongside the events above, your visit is recorded as a replayable reconstruction — what was on the screen, how the mouse moved, what was scrolled, what was clicked, and how you moved between pages. Someone at Macrify can play that back afterwards and watch the visit as if over your shoulder.

Two limits, both worth stating exactly. It is this site only — the recording stops at the edge of macrify.me and nothing follows you elsewhere. And PostHog masks the contents of form fields by default, so what you type into the contact form is not supposed to appear in the recording; we have not written any masking configuration of our own, so that protection is PostHog's default behaviour rather than something we built on top.

This page is the exception: it does not record you. Replay would otherwise start the moment the page loads, well before you could scroll to the switch below — which would mean recording someone's visit while they read about being recorded. So it is turned off here specifically.

What the switch below can and cannot do, plainly. It stops capture from that moment on, everywhere on the site, replay included. It cannot reach back: if you browsed other pages before arriving here, those visits may already have been recorded, and opting out does not delete them.

You can have those deleted, but there is a practical catch we would rather explain than gloss. Your visits are stored under a random identifier and nothing connects that identifier to your email address — so an email saying "delete my recording" gives us nothing to search for. To make the request actionable, include the identifier below. It is the one your browser is using right now, it is not derived from anything about you, and showing it to you is the only way this promise means anything.

What "anonymous" does and does not mean

Those events are stored individually, each stamped with the random identifier in your browser — they are not merged into a bare count, so one unnamed visitor's activity sits together and can be read as a single sequence.

And we should not claim more than that. If you submit the form on the homepage, the analytics event recording your choices and the email carrying your name arrive at essentially the same moment — so on a site with this little traffic, the two could be lined up by timing and matched to each other. We do not do that, and have no reason to. But "nobody could" would be a stronger promise than the setup can honestly support, so we are not making it.

What gets loaded from other companies

Your browser fetches a few files from elsewhere to render these pages. Each of those companies sees the request for the file, which necessarily includes your IP address — that is how fetching a file works, not a tracking arrangement.

• Google Fonts — the two typefaces the site is set in.
• jsDelivr — a public code library host, for the animation library some pages use.
• PostHog — as described above.
• Vercel — hosts the site and runs the contact form, so it handles every request by definition.

The personalised demo pages under /demo/ pull a little more, because each one is built for a specific person. Some load a styling or icon library from a public CDN (cdn.tailwindcss.com, unpkg.com). Some load photographs from Google's image CDN, or directly from the website of the firm the page was made for — so that firm's web host sees the request too. If you would rather not, those pages are not linked from anywhere on the site; they are only reachable if someone sent you the address.

How long any of it is kept

• Form submissions — as long as the email conversation is useful, then deleted on request.
• Analytics events — retained on PostHog's standard schedule for the account. As above, they are per-visit events carrying a random identifier, not a bare count, and not attached to your name or email.
• Session recordings — kept for whatever replay-retention period PostHog applies to this account, which is set on their side rather than ours. Opting out stops new ones being made; ask if you want an existing one deleted.
• The identifier in your browser — two parts with two different lifetimes. The cookie expires on its own or when you clear cookies. The matching local-storage entry does not expire and survives clearing cookies; it stays until you clear this site's data or browsing storage. So clearing cookies alone leaves you recognisable.

Children

This is a site that sells software to law firms. It is not directed at children and we do not knowingly collect anything from them.

If this page changes

The date under the title moves. Material changes to what we collect will be described here rather than quietly folded in.

Questions

Email jake@macrify.me. A person answers — usually within a day, often within an hour.