What this site collects, in plain terms

triazz.com does not use tracking cookies, does not run advertising scripts and does not sell visitor data. It is hosted on Vercel, and page visits are counted by GoatCounter (below).

The only analytics on this site is GoatCounter, a privacy-focused counter that, as GoatCounter describes it, works without cookies. It receives your request, so it briefly sees your IP address, but per its own policy it does not store the IP address; it records the page viewed, the referrer, browser and screen size and an approximate country. It also counts clicks on a few named buttons and links (such as “Contact us”, a menu link or a question in the FAQ), only as a name and a count: it never sees what you type, and the questions you type into the chat on the home page are not sent to it. It exists so we know roughly how many people visit; see goatcounter.com/privacy for exactly what it keeps.

The fonts and icons on this site are served from the site itself, so your browser makes no request to Google or any other font service. Your theme choice (light or dark) is kept in your own browser's local storage and never sent anywhere.

If you email us (contact@triazz.com), whatever you send us, such as your email address, name and message, is used only to reply to you. You can write to that address at any time to ask what we hold about you, to have it corrected or deleted, or to make a complaint about how your data is handled. Triazz is an independent project run by an individual in Punjab, India.

Triazz is self-hosted software: when you deploy it, it runs on your own infrastructure, not ours. We don't host your data and don't have access to it. In particular:

• Your mail, chat messages, tasks and the database all stay on the computer or server you run it on.
• What leaves is the specific text sent to the AI model you chose for a given job, the calls to the services you connect, a one-time public playbook download from GitHub, and any optional services you switch on (such as Langfuse tracing, an external log collector or notification email). Nothing goes to a model provider if you run local Ollama. Text goes to Anthropic or OpenAI only if Hosted Models has been switched on (on a shared server, an administrator unlocks it first) and you chose that provider for that job.
• Connection credentials for things like Outlook, Gmail or Slack are encrypted at rest (AES-256-GCM, or the macOS Keychain on a single-person Mac) inside your own deployment, and we never see them.

Where an organisation uses licence checks, the server confirms the licence once a day. The daily check downloads our licence list and sends nothing about you. If we limit a key to a number of servers, the server also sends the licence key and a random install id; we keep that id and its last check-in time; one idle for 4 days is removed at the key’s next check-in. Our licence service, hosted on Vercel with Upstash Redis, sees the caller’s IP address (kept about a minute for rate limiting; Vercel may keep its own request logs) and stores the customer name, seat limit, status and issue dates we set. It sends nothing about your data.

If you have a question about any of this, email contact@triazz.com and we'll answer directly.