Last updated: 2026-11-10. This page describes what Track (Agent Led Growth, "we") collects, why, and how long it is kept. It covers two different data flows, and they are worth keeping apart: your customers' event data, which your server sends us; and this website's own data, which we collect when someone visits alg.katrinalaszlo.com.
Contact, including for any request in this policy: kat@katrinalaszlo.com.
1. Your event data
When you install @katrinalaszlo/track in your API, your server sends us the requests it handles: the path, method, status code, timing, user agent, an event name, your project id, your key id, and a customer identifier you choose (accountIdOf). Depending on what you send, an event may also carry your own properties, a session hint, and a hashed client IP (ip_hash).
- The customer identifier is hashed with a salt that you set (
AGENT_TRAFFIC_ACCOUNT_SALT). We never see the
customer's email, name, or account id in the clear, and we cannot reverse the hash without your salt.
ip_hashis hashed too, with a key that changes every UTC day. It is never stored on an event that already has a
customer identifier, is cleared at most 48 hours after it arrives, and is never forwarded.
- Raw events are kept 14 days. Sessions, journeys and the daily snapshots the reports are built from are derived
from those events and kept for the reporting window.
- Forwarding is opt-in. Events reach PostHog or GA4 only when you turn forwarding on for a project. Otherwise they
stay in Track.
- Browser snippet events are accepted only for the domain you set on the project, and are not forwarded unless you
turn that on separately.
There is no per-visitor advertising or profiling here: this is your operational and product data, processed to show you where agents get through and where they stop.
2. Who else processes it
| Provider | What for |
|---|---|
| Vercel | Hosting the site and the API |
| Supabase | Managed PostgreSQL: the event store and the workspace records |
| Clerk | Signing a person in and owning a workspace |
| PostHog | Product analytics for this website; also a forwarding destination, only if you turn it on |
| Google Analytics 4 | A forwarding destination, only if you turn it on |
We do not sell data, and we do not share it with anyone else except where the law requires it.
3. This website's own data
- Sign-in cookies.
agent_traffic_key(30 days) keeps an API-key sign-in.track_workspace(30 days) remembers
which workspace a person is looking at. Both are HttpOnly, Secure, and SameSite=Lax, and both are set only when you sign in or open a workspace.
- Clerk cookies. Clerk sets its own session cookies when a person signs in with an account. Those are Clerk's, under
Clerk's cookie policy.
- This site's analytics cookies.
track_j(14 days) groups the pages one visitor reads into one session, so a report
can say where a visit started; PostHog's device cookie ph_…_posthog (1 year) does the same for its own events. Both are first-party and Secure; track_j is HttpOnly and SameSite=Lax, and PostHog's is readable by the page so its library can use it. Neither is used for advertising, neither is shared across sites, and neither is set on /demo, which is served from a shared cache. Blocking either in your browser leaves the site working.
- Site analytics. When enabled, this site uses PostHog with a first-party key to count page views and product
events. It sends ids — a Clerk user id and a workspace id when signed in — and never an email address or a name. No advertising cookies, no cross-site tracking.
- Server logs. Like any web service, the hosting platform logs requests (IP address, path, status) for
troubleshooting and abuse prevention, and keeps them for a short operational window.
4. Retention and deletion
- Raw events: 14 days by default.
ip_hash: cleared at most 48 hours after it arrives.- Claim links: valid 7 days.
- A workspace and its API keys do not expire. Deleting a project or workspace deletes its events; you can also write to
us at the address above and we will delete a workspace on request.
5. Your rights
Depending on where you live, you may have the right to access, correct, export, or delete personal data, and to object to some processing. Most of the data we hold is your customers' data, processed on your instruction — in that case, you are the controller and we are the processor, and requests from your customers should come to you first. We will help you answer them.
6. Security
API keys are stored only as a SHA-256 hash. Traffic is served over TLS. Access to the event store is limited to the application and to people who need it to run the service.
7. Changes
This is a pilot. If this policy changes in a way that matters, the date above changes and, for a material change, we will say so on this site or by email to the person who claimed a workspace.