Last updated: 18 November 2026

Privacy Policy

Who we are

Maddox Engine is provided by Grafikui Ltd, a company registered in England and Wales (company number 16426243). We are the controller of the personal data described here, which means we decide how and why it is used.

For any privacy question or request, email support@maddoxengine.com. We are a small company and have not appointed a Data Protection Officer, as the law does not require one for us; privacy questions are handled directly by the company director.

The open-source CLI, agent hooks and GitHub Action

The open-source maddox-engine CLI, its coding-agent and git hooks (maddox check, maddox hook claude-code, maddox hook pre-commit) and local source scans run on your own computer or in your CI runner. Your source code, design tokens, config files and secrets stay on your machines.

No CLI telemetry. The CLI sends no background usage telemetry, analytics events or machine fingerprints. Single-file checks and hooks make zero network requests and never read MADDOX_API_KEY. Session deduplication for the Claude Code hook writes only a local temp file on your machine using a one-way hash of the session ID.

No AI model training. We never use, share, or sell your source code, design tokens, findings, or scan metadata to train, fine-tune, or evaluate machine learning or artificial intelligence models.

The CLI makes network requests only when you explicitly pass flags or tokens asking it to:

  • Dashboard sync (--api-key / MADDOX_API_KEY): fetches your workspace's central rules and uploads scan summaries and findings (file paths, line numbers, matched/drifted values and git branch/PR metadata, never your source files) to your team dashboard account.
  • Live URL scans (--url): fetches the deployed URL you named and its same-origin stylesheets directly from your machine.
  • Figma Variables (--figma-file): calls Figma's REST API directly from your machine using your MADDOX_FIGMA_TOKEN or MADDOX_FIGMA_OAUTH_TOKEN; your Figma token never passes through us.

Installing or running the package via npm or npx contacts registry.npmjs.org under npm's own privacy policy. When you run the GitHub Action in CI, it posts pull request comments directly to GitHub using your repository's GITHUB_TOKEN.

What we collect and why

We only collect what we need to run the Service. For each kind of data, here is why we use it and our lawful basis under UK GDPR.

DataWhy we use itLawful basis
Account: email address, password (stored only as a secure hash), sign-in datesTo create your account, sign you in and send account emails such as confirmationsContract
If you sign in with GitHub or Google: your email address, name, profile picture and account ID from that providerTo sign you in and link the sign-in to your account. We never receive your GitHub or Google passwordContract
Plan and billing: plan, subscription status and Stripe customer and subscription IDsTo provide the plan you pay for. Stripe collects your card and billing details directly; we never see or store full card detailsContract; legal obligation (tax and accounting records)
Scan data: project names, findings (file paths, line numbers, values, nearest tokens, suggested fixes), scan totals and dates, URLs you scan from the dashboard, and for uploads from git: the branch name, commit ID and pull request numberTo show your scan history, trends and reports, and to compare a pull request with your main branch. We do not receive your source codeContract
Workspace membership: who invited whom, when people joined, and invite links (stored only as a one-way hash)To let a paying owner share their workspace with the people they invite, within their plan's seatsContract
API keyTo let the CLI and GitHub Action upload results to your accountContract
Messages you send us: your email address and what you writeTo answer support, privacy and security requestsLegitimate interests (responding to you); legal obligation for privacy requests
Security data: IP address, browser details and sign-in eventsTo protect accounts and the Service from abuse: rate limits, the sign-in security check and investigating misuse. For rate limits we store a one-way hash of your IP address, not the address itselfLegitimate interests (keeping the Service and its users secure)

Public quick scans on our website are not linked to an account: we fetch the page you enter, show you the result, and do not store the page or result. We also receive a notification when someone visits a public page, containing only the page path and the website that linked to it; it contains no personal data.

You need to give us an email address (or sign in with GitHub or Google) to have an account. We do not use your data for automated decisions that have legal or similarly significant effects on you, we do not sell it, and we do not send marketing emails without your consent.

Who we share it with

We use trusted service providers who process data for us under data processing terms. They may only use it to provide their service to us.

  • Supabase: database and authentication, hosted in the EU (Frankfurt, Germany).
  • Resend: sending account emails, such as sign-up confirmations, from noreply@maddoxengine.com. Sent from the EU.
  • Vercel: website hosting and server code.
  • Stripe: payments and subscriptions. Stripe also acts as an independent controller for some payment data, under its own privacy policy.
  • Cloudflare (Turnstile): the security check on email sign-up and sign-in, which uses browser and device signals to tell people from bots.
  • GitHub and Google: only if you choose to sign in with them, under their own privacy policies.
  • ntfy.sh: visit notifications to us, containing no personal data.
  • Zoho Mail: our inbox for messages you send to support@maddoxengine.com or any other @maddoxengine.com address, including privacy requests. Hosted in the EU.
  • Microsoft 365: only if you email us at a grafikui.com address instead.

Workspaces. If you invite people to your workspace (Team and Scale plans), they can see your workspace's projects, scan history and pull request comparisons, and you can see the email addresses of the people you invite. If you join someone's workspace, its owner sees your email address. Members never see the owner's API key or billing details.

We may also disclose data if the law requires it, to protect our rights or users’ safety, or to a buyer if our business is sold, who would have to protect it in the same way.

International transfers

Our database is hosted in the EU (Frankfurt, Germany), which UK law recognises as giving adequate protection. Some of our providers process data outside the UK and EU, including in the United States, where our website’s server code runs. When personal data leaves the UK, we make sure it stays protected: either the recipient is certified under the UK Extension to the EU-US Data Privacy Framework (the “UK-US data bridge”), or the transfer is covered by the ICO’s International Data Transfer Agreement or International Data Transfer Addendum in our provider’s data processing terms. Email us for more detail on the safeguard for a particular provider.

How long we keep it

  • Scan data: for your plan’s history period (30 days on Free, 12 months on Team, unlimited on Scale), then deleted automatically after a further 30 days.
  • Account data: while your account is open. When you ask us to close your account, we delete it and all its scan data within 30 days, including from backups.
  • Billing and tax records: 6 years after the end of the financial year they relate to, as UK tax law requires.
  • Emails you send us: as long as needed to deal with your message, and up to 2 years for support history, unless they are billing records.
  • Hashed IP addresses used for rate limits: normally deleted within a day.
  • Security and sign-in logs: kept by our hosting and authentication providers for a short period, then deleted automatically.

Cookies

We only use cookies that are strictly necessary: to keep you signed in, to protect sign-in (security check), and on Stripe’s checkout pages for payment and fraud prevention. If you use “Continue with Google”, Google may set cookies on its own domain to complete the sign-in you asked for. We do not use analytics, advertising or tracking cookies, so we do not ask for cookie consent.

Your rights

Under UK data protection law you have the right to:

  • get a copy of your personal data;
  • have inaccurate data corrected;
  • have your data deleted;
  • restrict or object to how we use it, including use based on legitimate interests;
  • receive data you gave us in a portable format.

Email support@maddoxengine.com to use any of these rights. It is free, and we will respond within one month. We may need to confirm your identity first.

If you are unhappy with how we handle your data, please contact us first. If you are in the UK, you have the right to complain to the Information Commissioner’s Office (ICO) at ico.org.uk/make-a-complaint or by calling 0303 123 1113. If you are in the EEA or Switzerland, you can complain to your local data protection authority.

If you live in California, you can ask what personal information we collect, use and disclose, and ask us to delete or correct it. We do not sell personal information and we do not share it for cross-context behavioral advertising. We will not treat you differently for exercising any of these rights.

Security

We protect data with encryption in transit, access controls that let each user see only their own data, hashed passwords, revocable API keys and minimal data collection. If a breach puts your rights at high risk, we will tell you without undue delay. To report a security issue, email support@maddoxengine.com or see SECURITY.md in omrdev1/maddox-cli.

Children

The Service is not intended for anyone under 18, and we do not knowingly collect their data.

Changes to this policy

We will post any changes here with a new date, and tell you by email or in the dashboard about significant changes. Our Terms of Service explain the rest of our agreement with you.