What this website doesn’t do
- No tracking cookies. We set no cookies ourselves. The network this site runs on (the Internet Computer) sets a
technical session cookie named
ic_env. It only holds public information about the network (its public key and this site’s identifier), is the same for every visitor, says nothing about you and is deleted when you close your browser. Your choice between light and dark design is stored only in your browser (local storage) and never sent anywhere. - No tracking, no analytics tools.
- No third parties on a visit. Fonts, images and scripts come from this site itself, not from Google Fonts or other services.
Hosting
This site runs as a canister on the Internet Computer, a public network of independent data centers. When a page is requested, the machines involved process technically necessary data such as your IP address in order to deliver it. The customer account and customer sites also store their data as canisters on Internet Computer machines in several countries. The data is not additionally encrypted there; whoever runs a data centre could technically look at it.
Next to the canisters, we run a single service for rendering and for the assistant (see below). It runs on a server with a provider in Switzerland or the EU.
Contact by email
If you write to us, for example to request an access code, we use your email address and details only to reply to you. We do not pass them on. Emails to pilot@lidarc.io arrive in our mailbox at Google Workspace (Google); Google processes the message technically for that.
Customer account (portal)
- Sign-in with Internet Identity (
id.ai, a service of the Internet Computer): your browser opens the sign-in there and receives a key for the customer account. We only learn a pseudonymous identifier (principal), no email address and no name. If you sign in with a passkey instead, the customer account stores that account’s email address. - Cookies:
emdash_session(your session) andemdash_ii(5 minutes, only while signing in). Both are technically necessary. - Stored in your browser: the Internet Identity sign-in key (IndexedDB) and your choice between light and dark design (local storage).
- Connections: calls to the customer account go through the Internet Computer’s gateways (
icp-api.io). - Stored in the customer account: your sites and how far each is set up (template chosen, pages designed, agent connected, published; four yes/no answers your site reports to the customer account), the access code you opened your account with, access codes you pass on, and your consent when you allow a site to be deleted. Payments are switched off during the pilot, so there is no credit and there are no bookings.
- Invitations: Whoever passed an access code on to you sees for that code only whether it was used and whether a website came of it (they then get a place to pass on back). The customer account does not show them who you are or which website it is.
- Feedback: what you write in the “Your feedback” box is stored with your account (its identifier, plus email address and name if your account has them), your rating (“Going well”, “So-so”, “It gets stuck”), the site it’s about and any contact details you choose to give. Only we, as operators, can read it.
- After the pilot, we reset everything: we then delete the accounts, access codes and feedback from the pilot, and the pilot sites with all their content. We’ll tell you the date at least 30 days in advance; until then you can download your site under Website → Backup.
Your site’s admin
- Cookies:
emdash_session(your session) andemdash_portal_state(10 minutes, only when signing in through the customer account). - Passkeys stay on your device; the site stores only the public part.
- Stored in your browser: admin settings such as the store’s address (local storage, session storage) and the history of a conversation with the assistant (session storage, only in that tab).
- Connections: the admin loads themes and blocks from the Lidarc Store (also a canister). If your site knows our service’s address, the admin registers it there, and the assistant talks to the service directly from your browser. Plugins are switched off during the pilot, so the admin doesn’t open the area with EmDash’s public plugin list.
- Backup: when you download your site under Website → Backup, the file is put together in your browser. It also contains your users’ email addresses; keep it somewhere safe.
Our service for agents and the assistant
Our service next to the canisters only works for sites that are connected to it. Like any server, it sees the IP address a request comes from.
- Viewing pages for agents: when an agent has a page checked or the site re-rendered, the service opens your site in a browser of its own, including drafts that are to be checked. For that it holds a key of your site that may publish; your admin creates it and registers it with the service. The service stores the addresses of connected sites and these keys. It sends pictures of checked pages back to your site, where they are deleted after one hour.
- Assistant: when you use the assistant in the admin, your browser sends the conversation to the service: what you write and what the assistant reads on your site to answer (content, settings, results of its tools). The service fetches the tools and instructions from your site and passes everything on to Anthropic (next section). It does not store conversations. It stores usage per site, daily totals and, for the last 300 requests, the site, time, model, duration, outcome, number of tokens and cost, without any content.
Anthropic (assistant only)
The assistant’s answers are written by Claude, a language model by Anthropic PBC (USA). Only when you use the assistant does what you write, and what the assistant reads on your site, go to Anthropic through our service. We query Anthropic with our own access, not yours. The assistant also says so below its input box.
Visitors of your site
- Your Lidarc site sets no cookies for visitors and loads fonts and demo images from its own canister.
- Blocks with embeds (video from YouTube, maps from OpenStreetMap or Google Maps) load that content only when a visitor clicks on it; then from there. You are responsible for your site; name such services in your own privacy policy.
- What visitors send through your site’s forms (enquiries, newsletter sign-ups) stays in your site, in the admin’s inbox, until you delete it (at most the latest 2000 messages). Lidarc does not read it.
Transfers abroad
Some recipients are abroad: Google (USA) for emails to us, Anthropic (USA) when you use the assistant, and the Internet Computer’s machines in several countries.
Your rights
You can ask what data we hold about you and have it corrected or deleted. Just write to pilot@lidarc.io.
Responsible
Lidarc
Email: pilot@lidarc.io