Your account and your data

Workspaces and sites

A workspace is your account. A site is one domain inside it. You can track as many sites as your plan allows, and each one gets its own site ID — the sl_… string in its install snippet.

That ID is the thing that matters. Statlark files a hit under whichever site ID the snippet names, so the same domain can exist twice — once with the snippet pointing at it, once not. The second copy will sit at zero forever. If a site says nothing has ever arrived, that’s the first thing to check: see Nothing showing up?

Export everything

Settings → Your data → Export gives you a single JSON file containing your sites, visitors, events, payments, identified people and API key metadata (never the keys themselves, or your Stripe signing secret). It covers the whole workspace, so it is a good thing to take before you delete anything.

Removing one site

In Settings → Sites, each row has a remove control. It deletes that site and everything keyed to it: every visitor, event, payment, identified person, goal alert, exclusion rule and site-scoped API key, plus its Stripe webhook signing secret. Your other sites and your login are untouched.

You’ll be asked to type the exact domain. If the site has actually collected anything — or holds a Stripe signing secret or API keys — we also email you a 6-digit code to enter first. A site you added by mistake five minutes ago goes in one step; one with real data behind it does not.

This cannot be undone. There is no trash and no restore. Export first if you might want the numbers later.

Closing your account

Settings → Your data → Delete account removes the entire workspace: every site, all of its analytics and revenue history, and your sign-in. Type your workspace name, then enter the 6-digit code we email you.

Once that completes there is nothing left to sign in to and nothing to recover — this is a real erasure, not a deactivation.

If the code doesn’t arrive

• Check spam, and give it a minute — the code is valid for a short window.
• Use Resend coderather than starting over, so you don’t hit the send rate limit.
• Still stuck? Email hello@tamadoggo.com and we’ll help.

The code always goes to the address you sign in with, whatever is on screen — that’s deliberate, so a borrowed browser session can’t redirect it somewhere else.