Skip to main content
TayStack

Draft: not legal advice, review before launch.

This page was written from what the product does today. It must be reviewed by the operator or a lawyer before real customers use TayStack. Text in [square brackets] still has to be filled in.

Privacy

TayStack is operated by [Operator legal name]. You can reach us at [contact email]. This draft was last reviewed on [date of last review].

It describes what TayStack actually does with data today. It will change as the product changes.

Who this covers

Four groups of people: visitors to a website whose owner uses TayStack to measure traffic, people who sign in to TayStack, people who join the waitlist, and visitors to this website (taystack.com), which we measure with our own tracking script.

What the tracking script sends

When a site owner installs the TayStack script on their pages, it sends one message to TayStack for each page view and for each custom event the site owner chooses to send. A message contains:

  • the host name and the path of the page (not the query string, apart from the campaign parameters below);
  • the campaign parameters utm_source, utm_medium, utm_campaign, utm_term, utm_content and ref, when they are in the address;
  • the address of the page you came from, cut down to its site and path (its query string and fragment are dropped);
  • your screen width;
  • a random visitor id and a random session id, kept in cookies (see Cookies);
  • if the site owner turns on outbound link or download tracking: the address of the link clicked (without its query string or fragment) or the file path and extension;
  • for custom events: the event name and any extra properties the site owner chose to send;
  • if the site owner calls the identify function: the user id they pass, and an email address if they pass one.

What TayStack adds on its servers

The browser name and version, operating system and device type are worked out from your browser user agent text, which is not stored in full. The country, region and city come from a location lookup made by our hosting provider from your IP address. TayStack also adds the time the message arrived and sorts the visit into a channel such as search or social.

The owner of a site can see, in their TayStack dashboard, a list of recent visitors to that site and the pages each one viewed, in order, with a generated name such as "hazel snail" that is made from the random visitor id. If the site passes a user id or email to TayStack, the owner sees it on that visitor profile. Only the owner of that site can see this. The dashboard also shows the owner how many visitors are on the site now and which pages and countries they are in, refreshed about every 15 seconds.

IP addresses

TayStack does not store raw IP addresses in its database. An address is used in memory for two things: counting requests to limit abuse, and the location lookup described above. It is then discarded and is not written to the stored events.

Our hosting provider receives your IP address in order to deliver the request and may handle it under its own terms and logs. We cannot describe those logs for them.

Cookies and local storage

The script sets up to three first-party cookies on the site where it is installed:

  • taystack_visitor_id: a random id that lasts one year;
  • taystack_session_id: a random id that lasts 30 minutes from the last activity;
  • taystack_user_id: only if the site owner uses identify, the user id they passed, for one year.

The cookies are set for the domain you give the script and its subdomains (for example example.com and www.example.com share them); if the browser refuses that, they stay on the single host. The cookies are not marked HttpOnly, use SameSite=Lax and, on https sites, Secure. The script does not use session storage. It uses local storage for one key only, taystack_ignore, which a site owner sets in their own browser to stop that browser being counted; the script stores nothing else there. Its requests go to the TayStack address, and the browser may attach the cookies of that address to them; the script adds no cookies from other sites.

Signing in and this website

If you sign in, TayStack sets HttpOnly sign-in cookies that keep you signed in for up to 30 days unless you sign out. The light or dark theme you choose is saved in your browser local storage under the key theme. This website loads no third-party scripts, fonts, images or analytics: the only tracker on it is our own script.

Account and site settings

For people with an account, TayStack keeps in Supabase (a hosted database and sign-in service): your email address and sign-in credentials, the authenticator app (second step) you may have set up, and your sites (domain, site id, creation date), goals and funnels. Sign-in attempts are rate limited using your IP address in memory only.

Who processes data for us

  • Tinybird stores and queries the event data. Our workspace is in AWS us-west-2 (Oregon, United States).
  • Supabase stores accounts, site settings and the waitlist. Region: [Supabase region].
  • Netlify hosts the website and runs the server code that receives events. Region: [Netlify region].

The waitlist

The home page has a waitlist form. If you use it, TayStack stores in Supabase:

  • the email address you typed, trimmed and in lower case;
  • the campaign labels in the address of the page you came from, if there are any (utm_source, utm_medium and utm_campaign, each cut to 100 characters), and which form on the page you used;
  • the time you joined.

We use this only to invite you to TayStack when it opens to more people. Only the person who operates TayStack can read the list, from the database. The list is held for us by Supabase (the database host), and the website that receives it runs on Netlify (the hosting provider); both process it on our behalf and only to run TayStack (see Who processes data for us). We do not give it to anyone else and do not use it for advertising. Your IP address is used in memory to limit repeated requests and is not stored with your address. We keep the list for [waitlist retention period].

No email is sent when you join, and no confirmation email is sent yet. When invites go out, they will be sent to this address. To be removed from the list, write to [contact email] and we will delete your row. Joining the waitlist is not an account and does not give you access.

How long data is kept

Retention is not yet limited: stored events are kept until they are deleted. There is no automatic deletion yet. To have data deleted, write to [contact email]. We will add a retention period later and update this page when we do.

Selling and sharing

We do not sell data and we do not use it for advertising. Data is shared only with the services listed above, which we use to run TayStack.

Your choices

The owner of a website decides to install TayStack there and is the first person to ask about what is measured on that site. To ask us about data, to have it deleted, or about this page, write to [contact email].

This draft does not claim that TayStack meets any particular privacy law. A reviewer should check which rules apply to the operator and to its customers.

Changes

We may change this page as TayStack changes. The date of the last review is at the top.