Privacy policy
Effective [effective date]
Lissoss is run by [company name]. It helps website owners understand why visitors get lost on their sites. That means we handle two different kinds of personal data, in two different roles, and this page keeps them apart.
1. Visitors to our customers' websites
When a business installs the Lissoss snippet on its website, that business decides what is collected and why. It is the controller; we are its processor and act only on its instructions. If you visited a site that uses Lissoss and want to exercise your rights, contact that site. We will help them answer you, and they can delete a visitor's data from Lissoss in one step.
Nothing is recorded until you agree
By default, the snippet records nothing and stores nothing in your browser until you accept its consent banner, or until the site's own consent tool says you have agreed. A site can only switch the banner off if it runs its own consent tool.
What is recorded after you agree
- The pages you view, how long you stay and how far you scroll.
- What you click, including the visible text of the clicked element, and signs of frustration such as repeated clicks on something that doesn't respond.
- How you arrived: the referring site and any campaign tags in the link.
- Your browser, operating system and device type.
- Your approximate location (country, region and city), worked out from your IP address. The IP address itself is also stored unless the site has turned IP collection off.
- Technical errors that happen on the page while you browse.
- Random identifiers for your visit and your browser, kept in a first-party cookie and your browser's storage so that one visit reads as one journey.
What you type into form fields is not recorded, and your screen is never recorded as video. Nothing is used to identify you by name, and nothing is sold or used for advertising.
AI analysis
To explain why visitors get lost, we send summaries of behaviour (pages, clicks, timings, country-level context) to our AI provider. IP addresses are never included, and the provider may not train its models on this data. The AI is told to explain behaviour and never to characterise people by where they are or what device they use.
How long it is kept
Our copy of visitor events is deleted after 365 days, automatically every night. Copies held by our event collection provider follow its retention settings for our project. When a site deletes a visitor, we remove them from our database and caches straight away, and complete the deletion at our event collection provider within 30 days.
2. Our customers: you and your team
For the people who sign up and use Lissoss, we are the controller.
- Account: your email address, your workspace name, your role, and a password that is stored only in hashed form by our sign-in provider.
- Billing: payments are handled by Stripe. We keep your plan and a Stripe customer reference. We never see or store your card number.
- Usage: which AI features you used and when, so that we can apply your plan's limits and keep the service affordable to run.
- Email: sign-in links, invitations, the weekly digest and tracking alerts. You can ask us to stop the digest at any time.
- Errors: if a page breaks, we may record the error, the page path and the technical trace. These reports contain no IP addresses, emails or query strings.
We use this to provide the service you signed up for (contract), to bill you (contract and legal obligation), and to keep it secure and working (legitimate interests).
Cookies and browser storage in the app
The dashboard uses a sign-in cookie, a cookie remembering which of your sites you are viewing, and browser storage for your theme and for recently generated results, so pages load instantly. All of these are needed for the app to work. None are used for advertising or tracking you across sites. Our marketing pages set no analytics cookies.
How long it is kept
We keep account data for as long as your workspace exists. When you ask us to close it, we delete the workspace and its data within 30 days, except for billing records that the law requires us to keep.
3. Who processes data for us
These companies process data on our behalf, under contracts that bind them to our instructions:
| Provider | What for | Where |
|---|---|---|
| Vercel | Application hosting | EU (Dublin) functions; global edge network |
| Supabase | Database, sign-in and file storage | EU (Ireland) |
| PostHog | Collecting and storing website visitor events | United States |
| Anthropic | AI analysis of behaviour summaries (never IP addresses) | United States |
| Resend | Transactional and digest email | United States |
| Stripe | Subscription billing and payments | United States / global |
| Sentry | Error reporting (route paths and stack traces only) (when enabled) | United States |
Where data leaves the European Economic Area, the transfer is covered by the European Commission's Standard Contractual Clauses or an equivalent safeguard.
4. How we protect it
- Everything travels encrypted (HTTPS).
- Each workspace can only read its own data. This is enforced on the server for every request, and requests that aren't properly bound to a workspace are refused.
- Database tables are reachable only by our server, never directly from a browser.
- API keys are stored only as one-way hashes, and third-party keys you give us are never sent back to the browser.
5. Your rights
Depending on where you live, you can ask to see, correct, export or delete your data, or object to how we use it. Write to [contact email] and we will answer within 30 days. If you are a visitor to one of our customers' sites, start with that site (see section 1). You can also complain to your data protection authority.
6. Changes
If we change how we handle data, we will update this page and its effective date. If a change matters, we will email account holders before it takes effect.
7. Contact
[company name] · [contact email]