Privacy Policy

Last updated: October 2026
This is a plain-language starting point, not a substitute for legal advice. It describes what Gydmation actually does with data, based on its real architecture. If you're relying on this for compliance purposes (GDPR, CCPA, India's DPDP Act, or otherwise), have it reviewed by a qualified lawyer for your specific situation and jurisdiction.

The short version

Gydmation is self-hosted software. It runs in a Docker container on your own machine. Your prompts, generated workflows, and n8n credentials are stored locally, on your computer — not on our servers. We only hold what's needed to run your account and licence: a basic sign-up record, your gydmation.com account (if you create one), and — on a paid plan — your billing and licence status.

What we collect

App account

When you create an account inside the Gydmation app, your email address and an encrypted password hash are stored in your own local installation, not on a database we control. The app also sends us a one-time sign-up record — your name, email address and approximate country — so we know who uses Gydmation and can contact you about your account.

gydmation.com account (optional)

If you sign in at gydmation.com to subscribe or manage your plan, we store your email address and, if you add them, a display name and profile photo. Sign-in uses one-time codes sent to your email — we never store a password for this account. We keep a record of your signed-in sessions so you can sign out of other devices.

Sign in with Google: if you choose "Continue with Google", Google shares your name, email address and profile photo with us, and confirms that the email address belongs to you. We use these only to create or sign in to your Gydmation account — the name and photo are used only if you haven't set your own. We don't receive your Google password or access to any other Google data (such as Gmail or Drive), and we don't post anything to your Google account. You can remove Gydmation's access at any time from your Google Account's security settings. Google's handling of your data is covered by Google's Privacy Policy.

How you found us: if you arrived at gydmation.com from a link (for example a post that adds ?utm_source=reddit) or from another website, your browser tab remembers that source in its own temporary storage until you close the tab. It is sent to us only if you create a gydmation.com account, and stored with that account: the link's source, medium and campaign, the referring website's name and the first page you landed on. No cookie is used for this, and apart from the demo counts below, nothing is recorded if you don't create an account.

Free validator and demo page (gydmation.com/n8n-workflow-validator): when you use the validator or the example runs there, your browser sends us a short note of each action so we can count how the demo is used: which action (page opened, workflow checked, example played, own request typed, download, "Get Gydmation" clicked), the check result and number of steps and errors, a random number your browser tab creates for that visit (kept in temporary tab storage, not a cookie), the source you came from as above, and your account number if you are signed in. We never receive the workflow you check or anything you type, and we don't store your IP address with it. If you then create an account in the same tab, that random visit number is stored with the account, so we can count how many people sign up after trying the demo. The validator also keeps the last workflow you checked, and a list of your five most recent checks, in your browser's own storage (localStorage) so they're still there when you come back; they stay on your device, are never sent to us, and the Clear and Clear history buttons remove them.

Billing and licence information (Pro plan only)

Payments are handled by our payment providers: Razorpay for payments in Indian rupees, and Dodo Payments for international payments. Dodo Payments acts as the merchant of record for international purchases, which means it sells the subscription to you and handles sales tax, VAT or GST. We never receive or store your card or bank details — each provider handles them under its own privacy policy.

On our central server we store your licence key (only in hashed and encrypted form), your subscription status and renewal date, and your remaining credit balance — this is necessary to verify your entitlement and meter usage.

Devices using your licence

Each Pro licence works on a limited number of computers. To enforce this, the app sends a random installation identifier and a device name (such as your computer's name and operating system) with each licence check. We store only a hashed form of the identifier, together with the device name and when it was last used, and show them to you on your account page so you can remove a device.

Security logs

To stop abuse (for example, guessing licence keys or flooding inboxes with sign-in codes), we count recent requests per IP address and email address. These counters are stored only in hashed form and are cleared automatically.

What we do not collect

  • The workflows you generate
  • Your prompts or conversation history
  • Your n8n instance URL or API credentials
  • Any BYOK (bring-your-own-key) API keys you add for other AI providers

All of the above stay in your local Docker volume, encrypted where applicable, and are never transmitted to us.

AI assistants connected through MCP

If you connect an AI assistant (such as Claude Code, Claude Desktop, Cursor, Windsurf or VS Code) to your Gydmation install through MCP, it talks to the Gydmation app on your own computer. The workflow data it reads or creates goes between your assistant, your Gydmation install and your n8n — not through our servers. Connection keys are stored on your install only in hashed form, and a log of recent assistant actions is kept on your install so you can review it. What your assistant does with the data is governed by that assistant provider's own terms and privacy policy.

Using Gydmation from Claude.ai, ChatGPT or your phone. Cloud assistants can't reach your computer directly, so if you link your computer, your Gydmation app keeps a connection open to our relay (run on Cloudflare's network), and requests from the assistants you allowed pass through it to your app and back. The relay passes these messages through without storing them. To make this work we keep, with your gydmation.com account: the computers you linked (name, link date and last connection), the AI apps you allowed (name and dates), and the sign-in tokens issued to them (stored only in hashed form, except short-lived signed access tokens that aren't stored at all). You can remove any computer or app at any time in Account → Connected apps; removing one stops its access immediately.

When your Gydmation app isn't connected. If no linked computer is running — or you use Gydmation from Claude.ai or ChatGPT without installing the app — the relay answers some requests itself: node look-ups, guides, template search, and checking or explaining workflow JSON your assistant sends. That workflow JSON is processed in memory to produce the answer and is not stored. For template search, the search text is turned into a numeric representation by Cloudflare Workers AI (also run on Cloudflare's network) so templates can be matched by meaning; it isn't stored by us. Requests that need your n8n or Gydmation's own AI are not handled this way — your assistant is asked to start the app instead.

Third-party AI providers

When you generate a workflow, your prompt is sent to whichever AI model is processing that request, so it can be understood and turned into a workflow. Depending on your plan and model choice, this may be:

  • Anthropic (Claude Sonnet 5, Claude Opus 5) — used for Pro-tier generations
  • Groq — used for free-tier and BYOK generations
  • OpenAI-compatible providers (e.g. GPT-5.6 Terra), or any other provider you've explicitly added your own API key for — used for BYOK generations, on any plan

On Pro, these requests are routed through our proxy so your own API keys are never required — but your prompt content still reaches the underlying model provider to generate a response. Each provider processes that data under its own terms and privacy policy; we don't control how they handle it beyond the request itself, and we don't send them your account email, payment details, or n8n credentials.

On the Free plan with your own API key, your prompt goes directly from your machine to the provider you configured — we're not in that path at all.

How we use what we do collect

  • To authenticate you and keep your account secure
  • To verify your Pro subscription status and enforce usage limits
  • To process payments via Razorpay and Dodo Payments
  • To limit each licence to its allowed number of computers
  • To send you sign-in codes, licence keys and essential account emails
  • To respond if you contact us for support
  • To count, in total, which channels people sign up from (for example "5 signups from Reddit this week"), so we know where to share Gydmation

We do not sell your data, and we do not use it for advertising — Gydmation doesn't run ads.

Data retention and deletion

Your local data (workflows, history, settings) persists in your Docker volume until you delete it yourself — we have no access to it and no way to delete it remotely. Account and billing records on our server are kept while your account is active. You can delete your gydmation.com account yourself under Account → Settings, which removes your profile, photo and sign-in sessions. To remove your billing, licence and usage records as well, email support@hacroo.com. Payment providers keep their own transaction records as required by law.

Your choices

  • Use your own API key instead of Pro, if you'd rather your prompts never pass through our infrastructure at all
  • Remove a computer from your licence, replace your licence key, or delete your gydmation.com account at any time from your account page
  • Ask us to delete your billing and usage records by emailing support@hacroo.com
  • Uninstall Gydmation and delete its Docker volume to remove all local data immediately

Contact

Questions about this policy: support@hacroo.com