Privacy Policy

Last updated: November 4, 2026

This policy explains what personal data we collect through ueconduit.com and the UE Conduit plugin, why we collect it, who receives it and what choices you have. If you use the plugin, sections 2 and 3 set out what leaves your computer and what does not. The rules for buying and using UE Conduit are in our Terms of Service.

1. Who we are

Jag Journey, LLC ("we", "us") operates UE Conduit at ueconduit.com and is the controller of the personal data described in this policy. Our home jurisdiction is Texas, USA, and we handle personal data in the United States.

The site runs on VoVo, our own website platform, so we host it ourselves rather than through an outside host.

2. What the plugin sends to us

The plugin sends data to us in two ways: the license check and bug reports.

License check

The plugin checks its license when the editor starts and every 12 hours while the editor stays open. Each check sends only these four things:

  • your license key
  • a hash of your Windows machine ID (not the ID itself)
  • the plugin version
  • the SHA-256 hash of the plugin's own DLL file

The site also sees the network (IP) address the request came from.

We use the check to confirm your license, confirm that it is on its one computer, and spot tampering. The site answers with a signed lease that lasts 7 days. A second computer on one license is refused.

Signs of tampering raise a flag on the license, and a person reviews that flag. A flag does not cancel anything by itself. These are the signs:

  • the DLL hash matches no released build
  • the lease signature fails, or the clock runs backward
  • repeated attempts from other computers

When a bug report is sent

  • The editor crashes while a Conduit command is running. The report is written to disk and sent the next time the editor starts.
  • A command ends in an internal error.
  • You press Report a bug in the panel, or an AI agent calls the report tool.

Ordinary errors do not send anything.

The first two cases are automatic reports. Automatic reports are on by default. The plugin shows a notice on first run, and a setting turns them off. A report you send by hand is always your choice.

What a bug report holds

  • License: your license key. The site looks up your name and email address from your order. The plugin does not know them.
  • Computer: computer name, Windows version, CPU, GPU, GPU driver, memory and disk space.
  • Product: plugin version, engine version, MCP server version and enabled plugins.
  • What happened: crash call stack, error text, the last tool calls from the journal and the end of the editor log.

What a bug report never holds

  • API keys or tokens. Keys are removed from reports before sending.
  • Your assets, source code or project files.

What a bug report can still show

Log text and tool calls can still show project names, asset names and folder paths, and a folder path can contain your Windows user name. If you do not want that, turn automatic reports off.

What happens to a bug report

Reports become support tickets on this site. You get one email for each new bug and none for repeats. Repeats of the same bug add to a count on the same ticket, and the number of tickets per license per day is capped.

3. What stays on your computer

  • The plugin and MCP server run on your computer and talk to each other over localhost. Your projects, assets and code are not sent to us. The names and paths a bug report can show are covered in section 2.
  • Your AI provider API keys are stored on your computer and are never sent to us.
  • When you use an AI provider (Claude, OpenAI, xAI, Google Gemini, a custom endpoint, or Ollama running locally), your prompts and editor data go directly from your computer to that provider under that provider's terms. We are not part of that exchange and never see it.

4. What the website collects

Account and order details

Your name, email address, billing details, order history, license keys and the computer a license is locked to.

Payments

Stripe processes card payments. We never see or store full card numbers.

Support tickets

What you write in a ticket and anything you attach.

Site visits

Your network (IP) address, browser and device details, pages viewed, the referring page and the results of security checks. A site firewall checks visitors to block attacks and automated abuse.

5. Cookies and browser storage

The site uses exactly these cookies and browser storage items:

Name Type What it does
_ra_vid Our own analytics A random visitor ID that lasts across visits
_ra_sid Our own analytics A random session ID that ends with the session
_ra_la Our own analytics The time of last activity, which ends with the session
XSRF-TOKEN Essential Keeps forms and sign-in secure
Session cookie Essential Keeps forms and sign-in secure
theme and theme-preference Browser storage Remember light or dark mode

Cloudflare Web Analytics runs on the site and gives us privacy-focused page statistics. It does not use cookies.

The site loads some code from the jsDelivr public CDN, which sees your network address as any web server would.

We use no advertising cookies. You can clear or block cookies in your browser settings, but forms and sign-in may stop working without the essential ones.

6. Why we use your data

We use personal data to:

  • process orders, provide licenses and answer support tickets
  • confirm licenses and keep each license on its one computer
  • find and fix bugs
  • protect the site and the product against attacks, fraud and tampering
  • understand how the site is used
  • send the emails described in section 8
  • meet tax, accounting and other legal duties

Legal bases for visitors in the EEA and UK

  • Contract: to fill your order, provide your license and support you as a customer.
  • Legitimate interests: security, anti-fraud, fixing bugs, license enforcement and understanding site use.
  • Legal obligation: to keep the records the law requires and to answer lawful requests.
  • Consent: where the law requires it. You can withdraw consent at any time.

7. Who we share data with

We do not sell personal data, and we do not share it for targeted advertising. We share it only with:

  • Stripe: payments
  • Cloudflare: network, security and analytics
  • jsDelivr: code delivery
  • The mail delivery service that sends our emails
  • Authorities or others: where the law requires it or to protect rights
  • A buyer or successor: in a merger or sale of the business

Nobody else receives it.

8. Emails

We send order and license emails, and bug report emails as described in section 2. We do not send marketing email without your permission.

9. How long we keep data

  • Orders and license records: as long as the license lasts, and then as long as tax and accounting law requires.
  • Support tickets and bug reports: as long as needed to deal with the issue and keep a support history. You can ask us to remove them.
  • Analytics and logs: only as long as they are useful for security and statistics.

10. Security

We use encrypted connections and limit who can access personal data. No system is perfectly secure, so we cannot promise that data will never be exposed.

11. Your rights

EEA and UK

You have the right to:

  • access your personal data
  • correct it
  • delete it
  • receive a portable copy of it
  • object to how we use it
  • restrict how we use it
  • withdraw consent
  • complain to a data protection regulator

You can also bring a complaint to us first through a support ticket.

California and other US states

Depending on where you live, you have the right to:

  • know what personal information we collect and how we use it
  • delete it
  • correct it
  • use these rights without discrimination

We do not sell or share personal information, as those words are used in these laws.

How to make a request

Send your request through a support ticket. We verify who is asking before we act, and if someone else asks for you, we also verify that you authorized them. We answer within the time the law that applies to you allows.

We may have to keep some data after a request to delete, where the law requires it. Deleting an account can end license access.

If we turn down a request and your state gives you a right to appeal, you can appeal through a support ticket. If we turn down the appeal, we will tell you how to complain to the state authority that handles privacy complaints.

12. International transfers

We handle data in the United States, and our customers can be anywhere. If you use the site or the plugin from another country, your data goes to the United States, where privacy laws may differ from those in your country.

13. Children

UE Conduit is for developers. It is not directed to children under 13 (under 16 in the EEA and UK), and we do not knowingly collect their data. If you believe a child has given us personal data, tell us through a support ticket.

14. Changes to this policy

When we change this policy, we post the new version here with a new date.

15. Contact

For any privacy question or request, open a support ticket.