Privacy policy

Statlark is revenue-aware web analytics. This policy explains what we collect, why, and the choices you have. It covers our website and the Statlark service.

Three roles

For the analytics we collect on your visitors, we act on behalf of our customers. When a site owner installs Statlark on their website, that owner decides what is collected and why — they are the data controller, and we are their processor. If you are a visitor to a site that uses Statlark, the site owner’s privacy policy governs, and requests about your data should go to them. A data processing agreement (DPA) is available to customers on request.

For our own customers’ account information, we are the controller. That means the email you sign up with and the workspace details you give us.

And on this website, we are the controller. We use Statlark on Statlark — statlark.com runs our own tracker so we can see which pages actually lead people to sign up. It behaves exactly as described below, with one difference that matters: nothing is set until you choose. We ask every visitor, wherever you are — not only where the law requires it — so no analytics cookie exists before you accept, and if you decline we record nothing about your visit. You can change your mind at any time via Cookie settings in the footer. The rest of this policy describes all three roles.

What the tracker collects

When a page on a customer site loads our script, we record, for that site:

• The page visited and the referring source — including UTM tags and ad-click IDs (gclid, fbclid, msclkid) when present.
• Approximate location — country, region, and city — derived from the request. We do not store your full IP address.
• The device type, derived from the browser’s user agent (we don’t store the raw user-agent string).
• A first-party identifier in a _slk_vid cookie, so return visits from the same browser can be counted as one visitor.
• Any properties the site owner attaches to a goal or custom event (for example, the destination of an outbound link). These are open-ended, so owners are responsible for keeping sensitive data out of them.

If the site owner chooses to call our identify() function — for example, after a visitor signs in — we also receive the details they pass to link that visitor to a known person. These may include a user id, a name, an email address, a profile-image URL, and any custom traits the owner attaches. Because traits are open-ended and set by the owner, owners are responsible for not sending sensitive personal data.

Payment data from Stripe

If a customer connects their Stripe account, Stripe sends us payment events (for example, a completed checkout or a paid invoice) so we can attribute revenue to the visitor and source that earned it. From those events we keep the amount, currency, a transaction identifier, and the customer email used at checkout. We also retain the complete Stripe event for reconciliation and debugging, which can include other details Stripe includes, such as a billing name or address. We never receive or store a Stripe API key for your connected account — every event is verified with a per-site signing secret kept encrypted in our vault. Billing for Statlark itself runs through our own separate Stripe account, described below.

Cookies

Statlark sets two first-party cookies: _slk_vid, which recognises a returning browser, and _slk_vds, which records the domain that identifier is scoped to. Resolving that scope also writes a _slk_p probe cookie, deleted immediately in the same step. We do not set third-party cookies and do not track people across sites or sell data to ad networks. Customers are responsible for providing their visitors any notice or consent their jurisdiction requires for analytics.

On this website those same three cookies are used, and none of them is written until you accept the banner. Decline and none is ever set. To change a choice you already made, use Cookie settings in the footer.

How we use data

• To provide the analytics service and attribute revenue to sources.
• To operate, secure, debug, and improve Statlark.
• To send transactional email, such as your sign-in codes.
• To bill for paid plans and send billing notices.

We may use aggregated, de-identified statistics (that don’t identify any person or customer) to understand and improve the product.

Who we share data with

We use a small set of infrastructure providers (sub-processors) to run the service:

• Supabase — database and authentication.
• Vercel — application hosting and content delivery, including approximate location derived at the edge for sites that route their tracker through Vercel.
• Resend — transactional email (sign-in codes).
• Stripe — subscription billing for Statlarkitself: a customer identifier, your subscription status and your invoices. Card details are held by Stripe, never by us.
• Cloudflare — DNS, and approximate location derived at the edge — both through our default hosted collector (used by the standard one-line install) and when a customer routes their tracker through Cloudflare. The full IP address is used only for this lookup and is never stored.

Stripe appears twice here, in two separate roles. For a customer’s own connected Stripe account we only observe the events it sends us. For Statlarksubscriptions, Stripe is our payment processor. We don’t sell personal data.

How long we keep it

We keep analytics and account data while the account is active. When a workspace or account is deleted, its collected data is removed and the subscription is cancelled. Billing records — customer and subscription identifiers here, invoices at Stripe — are kept for as long as tax and accounting law requires. You can ask us to export or delete your data at any time — see below.

Your rights

Depending on where you live, you may have rights to access, export, correct, or delete your personal data. Account owners can export the whole workspace as a single file, and delete the workspace and its login for good, from Settings → Your data — see your account and your data. For anything else, reach us at hello@tamadoggo.com. If you are a visitor to a customer’s site, contact that site owner, who controls the data.

Security

Each customer’s data is isolated at the database level, secrets such as Stripe signing keys are stored encrypted, and we hold no Stripe API key for your connected account (billing for Statlark itself uses our own Stripe account). No system is perfectly secure, but we take reasonable measures to protect your data.

International transfers

Our providers may process data in regions outside your own. Where that happens, we rely on those providers’ safeguards for international transfers.

Children

Statlarkis a business tool and is not directed to children. We don’t knowingly collect personal data from children.

Changes

We may update this policy as the product evolves. We’ll change the “last updated” date above, and for material changes we’ll give account owners reasonable notice.

Contact

Questions about this policy or your data? Email hello@tamadoggo.com. See also our terms of service.