Everything about the product, in one place. Contact us if something is missing.
Create a project, then copy the one-line script tag from the project's Settings tab and paste it into your site's HTML head. It works on any site, not just SvelteKit. Data appears in the dashboard within seconds of the first pageview.
No. Pageviews, referrers, devices, and session recordings all work from the tag alone, including navigation inside single-page apps. Calling identify() and track() is optional and only needed if you want to tie activity to your own user accounts or record specific actions.
Yes. Each site is its own project with its own write key, settings, and data. Projects are grouped into a workspace, and you can switch between them from the dashboard.
The most common cause is the write key's origin allowlist: a key only accepts data from the origins listed on it, so add your domain in the project Settings tab. Bot traffic is also filtered out, which includes most headless browsers used for testing.
A reconstruction of the page and the interactions on it: clicks, scrolls, navigation, and DOM changes. It is not a video of the screen and never touches the camera or microphone.
No. Text typed into form fields is masked by default, so passwords, payment details, and message contents are never captured. You can also mark any element with data-replay="false" to exclude it from recordings entirely.
Yes, per project, with the Record session replays toggle in Settings. You can also exclude specific paths, such as admin areas, from both analytics and recording.
Thirty days by default, set per project. Older recordings are deleted automatically by a daily job. Pageview and event data is kept until you delete the project.
Not on your site. Visitor and session identifiers are random values kept in the browser's local and session storage, scoped to your site alone, so they cannot follow anyone across the web. The UsageStory dashboard itself uses one cookie to keep you signed in.
By default yes, and they are used to derive a country and to limit abuse. Each project has an IP anonymisation setting that truncates addresses before they are stored, so 41.81.240.73 becomes 41.81.240.0 and no full address is ever kept. Country still resolves correctly with it on.
You do. For visitor data you are the controller and UsageStory is the processor, meaning we only handle it on your instructions. We never sell it, and we do not use it to train models. See the Data Processing Agreement for the full terms.
On servers in London, United Kingdom. Encrypted backups are held off-site. The full sub-processor list is in the Data Processing Agreement.
Deleting a project removes its pageviews, events, and recordings from the live database immediately. Individual recordings can be deleted from the Replays tab. Deleted data can persist in encrypted backups until those age out, within about five weeks.
UsageStory is free while in beta. Paid plans will come later, and you will be told before anything starts costing money.
Use the Forgot link on the sign-in page. We email you a link that lets you set a new password; it lasts one hour and works once.
Team members in your workspace can be given owner, admin, member, or viewer roles, and see only your workspace's projects. Invite-by-email is still being built; contact us in the meantime.