treg Terms Privacy Support Docs
Legal

Treg Privacy Policy

Last updated: 19 November 2026 Effective: 22 July 2026

The short version

  • We collect almost nothing about you. An email address to sign in, the teams you're in, and a log of which tools were called. That's the account.
  • Your credentials are encrypted and never returned. No stored secret value is ever sent back to a client, shown in the dashboard, or read by us.
  • Minimal tracking. We use product analytics and a support chat, and no advertising cookies. Every page loads Google's gtag.js with all consent signals denied: it sets no advertising cookie and reads none; it sends Google cookieless pings (page views on marketing pages, and one signup event when you create your first team) that Google uses only to estimate whether its ads lead to signups. When you sign up, make your first call, or make your first payment, we also send Google Ads a SHA-256 hash of your email address (Enhanced Conversions) so Google can match that event to an ad you saw or clicked, on any device; Google matches the hash only against its own signed-in accounts and never for personalised advertising.
  • No training, no selling. Your credentials, skills, and connected-account data are never sold and never used to train models.

01Who this covers

This policy explains how Superdesign Dev Pty Ltd ("Superdesign", "we", "us") handles personal data in the hosted Treg (also called "treg" or "tools-registry") service at treg.to. For that service, we are the data controller.

Self-hosted instances are not covered. If you or your employer run treg on your own infrastructure, your data never reaches us and this policy doesn't apply — the operator of that instance is the controller.

Contact for anything privacy-related: jason@treg.to.

02What we collect

Account and identity

We do not ask for your name, phone number, address, photo, or date of birth. Card payments are handled by Stripe; we never see your card number.

Credentials and connections

Usage and audit records

We may keep a copy of a provider's answer so the same question can be answered without a new call, and, for a call that fails, the request and error for a short time to investigate it. A team admin can turn storing answers off.

Content you create

Skills (SKILL.md text and companion files), tool definitions, and their upstream URLs. Treat skill text as visible to everyone in the team it lives in — don't put secrets there.

Technical data

Our hosting provider processes standard server logs (IP address, user agent, request line, timestamp) for security and abuse prevention, retained on their default schedule. We don't build profiles from them.

03Why we're allowed to hold it (legal bases)

DataPurposeBasis (GDPR Art. 6)
Email, team membershipProvide the account; sign-in; invitationsContract
Stored credentials, OAuth tokensExecute the calls you ask for; keep them validContract
Call recordsShow teams who used what; enforce caps; investigate abuseLegitimate interests / Contract
Payment recordsTake payments; keep accounting recordsContract / Legal obligation
Product analytics, support chatImprove the product; answer support questionsLegitimate interests
Server logs, rate-limit countersSecurity, abuse prevention, service reliabilityLegitimate interests
Skills and tool definitionsStore and share what you asked us to shareContract

04What we never do

05Google and YouTube user data — Limited Use

When you connect Google Search Console, Google Analytics, Google Business Profile, Google Ads, or YouTube, treg's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Specifically:

YouTube

The YouTube connection uses YouTube API Services. By connecting a YouTube channel you are additionally agreeing to the YouTube Terms of Service, and Google's handling of your data is described in the Google Privacy Policy.

Google Sheets add-on

The treg for Sheets add-on runs treg tools on the rows of a spreadsheet you have open in Google Sheets.

The same commitments apply to every other provider you connect (LinkedIn, Slack, X, or an API you register yourself).

06Who we share it with

Only the processors we need to run the Service, plus the upstream providers you deliberately point us at.

RecipientWhat they getWhyWhere
RenderApplication hosting and the managed database — all stored dataRuns the ServiceUSA (Oregon)
Amazon Web ServicesEncryption keys and secretsKey managementUSA (Oregon)
CloudflareTraffic to treg.to; stored dataEdge network and storageUSA
StripePayment details when your team adds fundsPaymentsUSA
PostHogUsage of the site and dashboard, including your email address once you sign inProduct analyticsEuropean Union
IntercomYour email address and support messagesSupport chatUSA
GrafanaService logs, without credentialsMonitoringUSA
Vercel AI GatewayRequests to language-model featuresLanguage modelsUSA
WorkOSYour sign-in identity, if your company uses single sign-onEnterprise sign-inUSA
ResendYour email address and the message bodySends sign-in codes and invitationsUSA
Google FontsYour IP address, when you load a treg web pageServes the site's typefacesUSA
Upstream APIs you connectWhatever your call sends themThe call you asked us to makeVaries by provider
DubOnly if you arrived through an affiliate's link: the click id, your team's id, your email address, and your team's payments as Stripe reports themRuns our affiliate program: credits and pays the affiliate who sent youUSA
Google AdsA conversion event (signup, first call, or first payment) with your click id if you arrived via a Google Ads click, and a SHA-256 hash of your email address (Enhanced Conversions for Leads); never the address itselfMeasures whether the ad that brought you convertedUSA

Referrals. If you sign up through someone's referral link, your email address is shown to the person who referred you, along with the date you signed up and whether your team has added funds — that's how they see which of their invitations worked. Nothing else about you or your usage is shared with them. If you'd rather not be visible that way, sign up without using the link.

In the other direction we show you less: if you were referred, we tell you who invited you as a partial address (j•••@theirdomain.com) and never in full. Referral links are often shared publicly, and the full address of whoever posted one is not ours to hand to everyone who clicks it.

We'll also disclose data where legally required, or where necessary to protect the Service or its users from a live security threat. If we're ever compelled to hand over data about you, we'll tell you unless we're legally barred from doing so.

If treg is ever acquired or merged, data may transfer as part of that transaction — you'd be notified in advance and this policy would continue to apply until replaced by one that is no less protective.

07Cookies

treg_session: HTTP-only, SameSite=Lax, secure over HTTPS. It holds a signed session reference and nothing else. It's strictly necessary to keep you signed in, so there's no consent banner and nothing to opt out of short of signing out.

treg_oauth_return and treg_ref: both HTTP-only with the same flags, and both exist only when you've done the thing that sets them. The first holds the page to return you to after a sign-in detour (a few minutes). The second holds a referral code if you arrived through someone's invite link, so we can credit them when you create a team (30 days). Neither identifies you, and neither is used for advertising.

treg_dub: HTTP-only with the same flags, set only when you arrive through an affiliate's link. It holds the click id that link added to the address, so the affiliate can be credited when you create a team (90 days). It is not used for advertising.

treg_partner: HTTP-only with the same flags, set only when a treg login --ref sign-in opens in your browser. It holds the affiliate partner code you typed, so that partner can be credited when you create a team (90 days). It is not used for advertising.

treg_utm: set by our own /sitetrack.js on your first page — if the link you arrived by carried campaign tags (utm_*) or a referring site, it remembers that source so we can tell which links bring people to treg, retained for 90 days. It holds no identifier.

Our product analytics (PostHog) and support chat (Intercom) set their own cookies. They are not used for advertising.

treg_ad: set by our own /adtrack.js, not a Google script — if you arrive from a Google Ads click, it records which ad click led to your visit (the click id and the landing page), retained for 90 days. It exists to tell us whether an ad turned into a signup, an active agent, or a paying team, so we can tell which ads to keep running. It is first-party (set by treg.to, readable only by us, never by Google or any other third party) and it is not shared with third parties beyond the conversion event itself — a signup, a first call, or a first payment — uploaded to Google Ads so it can measure the campaign. Each event carries the click id when there is one and a SHA-256 hash of your email address (Google's Enhanced Conversions for Leads), which lets Google match the event to an ad you saw or clicked on another device; the address itself is never sent, and we tell Google the hash may not be used for personalised advertising. Google's own tag runs with every consent signal denied, so it sets no advertising cookie; it only sends cookieless pings Google uses to estimate conversions. There is no advertising pixel and no cross-site advertising tracker anywhere on the Service.

08How we protect it

No system is perfectly secure. If we become aware of a breach affecting your personal data, we'll notify affected users and any required regulator without undue delay.

09How long we keep it

DataRetention
Account, teams, membershipsUntil you delete the account
Credentials and OAuth tokensUntil you delete them, disconnect the provider, or delete the team
Skills and tool definitionsUntil deleted by you or a team admin
Call recordsWhile the owning team exists; deleted with it
Copies of answers kept to serve a repeat questionUntil no longer needed, or earlier on request. A team admin can stop the storing at any time in the team's settings
Sign-in codes, rate-limit countersMinutes — expired rows are swept automatically
InvitationsUntil accepted, revoked, or expired
Hosting server logsOur provider's default window (short)

Deletions are permanent in the live database. Encrypted backups may retain a copy for a short period before rotating out.

10Your rights

Wherever you live, you can ask us to access, correct, export, or delete your data, and to restrict or object to processing. Depending on your location (EEA/UK under the GDPR, California under the CCPA/CPRA, and similar laws elsewhere) some of these are formal legal rights; we honour all of them for everyone regardless.

California residents: we do not sell or share personal information as those terms are defined by the CPRA, and we have not done so in the preceding 12 months.

EEA/UK residents: you also have the right to lodge a complaint with your local supervisory authority. Data is processed mainly in the United States; where a transfer mechanism is required, we rely on the Standard Contractual Clauses offered by our processors.

11Children

The Service isn't intended for anyone under 16, and we don't knowingly collect their data. If you believe a child has created an account, email us and we'll delete it.

12Changes to this policy

We'll update this page when our practices change, and the "last updated" date always reflects the current version. For material changes — new categories of data, a new processor, or a new purpose — we'll notify account holders by email or an in-app notice before the change takes effect.

13Contact

Privacy questions, requests, or complaints: jason@treg.to. Security vulnerabilities: SECURITY.md.


See also the Terms of Service. Treg is open source — if you'd rather verify than trust, the code that does all of the above is public.