TARX

Legal / Privacy

Privacy Policy.

This policy explains what TARX handles, why, and how to make a privacy request. It covers the web app, TARX_OS where available, and connected features.

Last updated November 10, 2026. Legal review pending.

01

What we collect

Account data: the email address or account identifier you use to sign in, and the session or device credentials needed to keep you signed in.

Product data: the prompts, messages, files, and connected-service inputs you choose to send to TARX. In the web app, a prompt you send is transmitted to TARX to produce a response. In TARX_OS, inference runs on your computer where available.

Operational data: request timestamps, model and tool route, error codes, device class, and bounded usage counters needed to run, secure, and improve the service.

Support data: the message and contact details you provide when you contact us.

02

How we use it

To answer your request, run the capability you asked for, keep your account and channels working, and return a result.

To protect the service from abuse, enforce limits, debug failures, and understand aggregate product usage.

To respond to support, privacy, and security requests.

We do not sell personal information.

03

Web app, TARX_OS and Supercomputer

The web app runs in your browser, but the request is sent to TARX infrastructure to produce the answer. That is how the web app works.

TARX_OS is designed for local-first execution on a supported Mac. Where a feature runs locally, the work stays on your computer; where a feature uses Supercomputer or a connected service, the request data needed for that feature is sent to the configured service.

A capability shown in a catalog, setting, or connection list is not proof that it is connected or that data is being sent. The product shows the current execution and connection state.

04

Website analytics and attribution

TARX uses Vercel Analytics and related hosting tools for site operation and aggregate event measurement. Analytics may include route, campaign parameters, device class, and event names.

Optional first-party landing attribution is not currently enabled. If it is later enabled, it uses bounded campaign fields, the public entry path, and the referrer host. It never uses the referrer path, referrer query, or message text.

05

Third parties

TARX uses hosting, email, authentication, analytics, and SMS providers to operate the service. Those providers process information only for the purposes TARX configures.

When you connect a third-party service, that service receives the data you authorize under its own terms and privacy policy.

We may disclose information where required by law or to protect the service, our users, or the public.

06

Retention

We keep account and product data for as long as needed to provide the service, meet legal obligations, resolve disputes, and prevent abuse.

Some operational logs and security records may be retained for a limited period after an account is closed.

07

Your rights

You can request access, correction, export, or deletion of personal information by emailing privacy@howdytarx.com.

Some records may be retained where required for security, legal compliance, or abuse prevention.

08

Contact

Privacy requests: privacy@howdytarx.com.

Company: TARXAN INC., Austin, Texas.