Privacy Policy
Iron Brothers Ventures, LLC · Last updated March 2026
Last updated: March 2026
Iron Brothers Ventures, LLC
We built RTMify for engineers at companies where data privacy isn't optional. This policy explains what we collect, what we don't, and why.
The short version
- ✓ RTMify Template: We collect nothing. It's a file download.
- ✓ RTMify Trace: Runs entirely on your machine. Your requirements data never leaves your computer.
- ✓ RTMify Live: Runs on your machine. Your requirements data stays local. We do not have access to your Google Sheet or your repository.
- ✓ This website: We use counter.dev — privacy-first, no cookies, no cross-site tracking, no personal data collected.
01 —
The RTMify website (rtmify.io)
We use counter.dev for site analytics. counter.dev does not use cookies, does not collect personal data, and does not track users across sites. It counts page views and referrers in aggregate. We cannot identify individual visitors.
When you download the free template, your browser makes a standard HTTP request. We do not log IP addresses or associate downloads with individuals.
02 —
License purchases
License purchases are processed by our payment processor. When you buy a license, the processor collects your name, email address, and payment information. We receive your email address and order details so we can issue your signed RTMify license file. We do not store payment card information.
We use your email address to deliver your signed license file and, if you have active maintenance, to notify you of updates. We do not send marketing email. We do not sell or share your email address with third parties.
03 —
RTMify Trace
RTMify Trace is a local binary. It reads your .xlsx file, processes it in memory, and writes output to your local filesystem. No data is transmitted to any server. No telemetry is collected. No analytics are reported. The binary operates entirely offline.
License verification is fully local. RTMify Trace reads a signed ~/.rtmify/license.json file and verifies its HMAC signature on your machine. No license validation requests are sent to RTMify servers.
04 —
RTMify Live
RTMify Live runs as a local process on your machine. It connects to Google Sheets using a service account credential you provide. That credential is stored locally on your machine; we do not have access to it.
Your requirements data — the contents of your Google Sheet — is fetched to your local machine, processed locally, and stored in a local SQLite database (graph.db) on your machine. It is never transmitted to RTMify servers. We have no access to your requirements, tests, risks, or any content of your sheet.
The MCP server runs locally on your machine and responds to requests from local clients only (e.g., Claude Desktop, Cursor). MCP traffic does not pass through RTMify servers.
Git repository scanning operates entirely locally. No source code, commit history, or annotation data leaves your machine.
License verification works the same as for RTMify Trace: the signed ~/.rtmify/license.json file is checked locally on your machine. RTMify Live does not phone home for license validation.
05 —
Support and contact
If you contact us at hello@rtmify.io, we will use your email address to respond. We do not add support contacts to any mailing list.
06 —
Data retention
We retain license purchase records (email and order details) for as long as the license may be active — which, given our perpetual license model, means indefinitely. You may request deletion of your email address from our records by contacting us; note that deletion will void our ability to reissue your signed license file.
07 —
Your rights
If you are in the EU or UK, you have rights under GDPR including the right to access, correct, or delete personal data we hold about you. Contact hello@rtmify.io to exercise these rights.
08 —
Changes to this policy
We will post updates to this policy at rtmify.io/privacy with an updated date. We will not retroactively change how we handle data already collected.