Privacy Policy — Assetli browser extension

Last updated: 11 October 2026 Applies to: the Assetli — property check from a listing extension for Chrome, published on the Chrome Web Store

This page describes the browser extension. The Assetli web application at assetli.app has its own privacy policy; unlike the Google Sheets add-on, this extension works together with it, so both apply to you.

1. In short

• The extension reads page content only when you click Analyse — until then it has no access to page content.
• The listing text it reads is sent to assetli.app, where the due-diligence protocol is built. Nothing goes anywhere else.
• It does not track you. No analytics, no advertising scripts, no third-party services.
• Interface settings stay in your browser; analysis options are saved to your Assetli account, so the app and the extension behave the same.
• Without signing in you get a limited taster, and nothing identifying you is stored.

2. When the extension sees page content

The extension uses the activeTab permission: it may read the tab's content only after you click the extension icon or the Analyse button, and only for the tab you currently have open. Nothing runs in the background going through your pages.

The only address permitted up front is the assetli.app domain the extension talks to. No website is pre-approved for reading — for any page, including property portals, the extension asks for access when you first click its icon there, and Chrome asks you to confirm. Until you do, the extension cannot even see the address of the tab.

3. What is sent to assetli.app

When you run an analysis, the following is sent:

• the text of the open listing (the page's visible text, its title and breadcrumbs),
• the page address, so the analysis can be found later,
• details you fill in in the panel — intent, own funds, expected rent, exact address, seller,
• coordinates, if the page itself offers them in a standard machine-readable form,
• the interface language,
• a note that the request came from the extension rather than from the web app (used only for the aggregate counts described in section 4).

Your browsing history, the content of other tabs, other sites' cookies and what you do on the page are not sent.

Seller: the field is optional and is used to query the public insolvency register. We never ask for a birth number and the extension cannot send one; a company ID, or a name and date of birth, is enough.

4. What is stored

In your browser (extension storage): interface language, the expected annual growth you last entered, how many free analyses you have used, and the server address (a developer setting). These never reach us and are deleted when you uninstall the extension.

On your Assetli account (only when signed in): analysis options — whether the AI assessment is generated automatically, whether reading scanned zoning plans is allowed, the default down payment and term, and your ownership-cost assumptions. They live with your account rather than in the browser on purpose: the web app and the extension are then set up the same way and you do not have to fill them in twice.

On assetli.app when you are signed in: the protocol is saved among your analyses so you can come back to it and fill in missing details. Only you can see them and you can delete them in the app at any time.

On assetli.app without signing in: the result is stored briefly under a fingerprint (hash) of the submitted text, so the same listing does not have to be analysed twice. Your identity is not attached to that fingerprint. The number of free analyses is limited: the extension counts them in your browser and the server additionally limits them by IP address — kept for as long as the limit lasts.

We also keep a daily total of free analyses (how many ran, how many were answered from the cache, what they cost us, the country of the property and whether they came from the extension or the web app), and a daily count of how many times the extension panel was opened. These are aggregate numbers with nothing about the person who ran them.

Links from the panel to assetli.app carry a short tag saying they came from the extension. If you create an account through such a link, the account records that it originated from the extension — a single word, so we know whether the extension brings people to Assetli. It is not used for advertising and is not shared.

Queries we send to public registers on your behalf are remembered for 15 minutes, so that recalculating an analysis does not query the same register again. Where such a query contains a name or a date of birth (the insolvency register), it is stored hashed — the cache only needs to recognise the same query, not who it was about.

5. Signing in

Signing in happens on assetli.app in an ordinary browser window. The extension never sees your password and stores no credentials; it only uses the session cookie issued by assetli.app, exactly as an open tab with the app would. Signing out in the extension signs you out of the app as well.

6. Processors

The listing text is processed by the Anthropic (Claude) language model to extract facts (price, area, layout). Anthropic does not use data from our API to train models. We also query public registers (the cadastre, the insolvency register, the national geoportal, the Czech Statistical Office, the Czech Geological Survey, OpenStreetMap and others) — they receive only what the query needs, such as a parcel number or coordinates, never your identity.

Application servers run on Vercel and the database on MongoDB Atlas, both in the European Union.

7. Your rights

You have all rights under the GDPR: access, rectification, erasure, restriction of processing, portability and objection. You can delete saved analyses in the app; for anything else write to podpora@assetli.app and we will respond within 30 days.

8. Changes

If this policy changes, we will update the date above. Material changes will be announced in the app.

Data controller: Ondřej Smutný, operator of Assetli · podpora@assetli.app