Lichen Privacy Policy

Last updated: 8 November 2026

This is a translation of the Spanish privacy policy. If they differ, the Spanish version prevails.

This policy explains what data Lichen processes, what for, who it is shared with, how long it is kept and what you can do about it. It applies to all of Lichen:

• The desktop application, free of charge (formerly Axon Terminal).
• The Lichen account and its web and MCP service (today at axon.neuralflow.es), the hooks and CI Guardian.
• The product websites (terminal.neuralflow.es and uselichen.com), with their download form and their waiting list.

1. Who is the controller

No data protection officer has been appointed.

2. Two different roles

• Your account, usage and security data: the controller in section 1 decides how they are processed. This policy describes them.
• What you or your agents write in Lichen (issues, memories, comments, client contacts…): you decide what is stored. If it contains other people’s data and you use Lichen in your professional activity, you are the controller of that data and Lichen acts as processor, under the data processing agreement (ask for it at hola@neuralflow.es). Those people should contact you first.

3. What data is processed, what for and on what legal basis

Today Lichen charges no one, so no payment data is processed. When there is billing, this policy will be updated before anyone is charged.

You can object to anything based on legitimate interest (section 8). Giving the account data is necessary to use Lichen; everything marked “if” is optional.

The desktop application

The application runs on your PC and does not need an account. With no linked account, the only things that leave it towards Lichen’s servers are these:

• Checking for a new version, at startup and every 2 hours, and reading the news. It is an empty request: it does not carry your version or any identifier, but the server sees your IP.
• List of revoked licenses, once a day. Also empty, except for the IP.
• Telemetry and error reports, only if you say yes on first launch (no option is preselected) or later in Settings → Privacy. They carry a random identifier, the version, the system and usage events: chosen model, theme, language, window size, length of your messages (not their text), number and type of attachments and length of sessions. Errors carry up to 100 characters of the error message and, in crash reports, the full trace, which may include paths on your computer or the name of a remote server.

If you link the PC to your account, also:

• When linking: a hash of the computer’s Windows identifier, a hash of a random number of the installation, the computer’s name (the one it has in Windows, or the one you give it) and the version. They are used to count your devices and renew the license.
• Claude spending, only if you turn on the upload (not preselected): figures per hour and per model, readings of the weekly % and a hash of your Claude account, never its email. No prompts, paths, projects or session identifiers.
• Orb notices: the summaries the orb leaves you (what each tab has done, boards, options) are stored in a mailbox in your account, so they are not lost if you close the app. Their text comes from what your agents do, so it may contain file names or parts of the work.
• “Your day” reads your issues and, if you use Pragma, starts and stops its timer.

What your agents send does not go through Lichen. Claude Code, Codex and OpenRouter receive your prompts and the files they read directly, with your account and under their terms. The application also uses your Claude account for tasks of its own: the voice assistant (the orb), explaining in one sentence what a permission or an unknown command asks for (on by default, with a daily spending cap) and summarizing steps (off by default). That consumes your subscription and is processed by Anthropic.

Voice:

• Reading aloud. The default engine is Microsoft Edge’s read-aloud service: the text being read goes out to Microsoft. It is only used if you turn on voice or talk to the orb. You can replace it with ElevenLabs or OpenRouter, with your own key, or with a local engine.
• Dictation. With Whisper, the audio is transcribed on your PC and does not leave it. Until you choose a Whisper model, the speech recognition of the built-in browser (WebView2, by Microsoft) is used. That recognition may send the audio to Microsoft’s servers to transcribe it. If you do not want the audio to leave your PC, choose a Whisper model.

From your phone: the phone connects directly to your PC, over your network or through Tailscale. Messages and attachments do not go through Lichen’s servers. Attachments are kept on your PC for 7 days.

On your PC your conversations, logs, screenshots, attachments, spending indexes and settings stay in %LOCALAPPDATA%\axon-terminal. Only the keys and tokens (your Lichen key, those of OpenRouter or ElevenLabs) are encrypted, with Windows data protection. The rest is in plain text, protected by your Windows account.

Uninstalling does not delete that folder. If you uninstall with the .exe installer, tick the “Delete the application data” box. That box deletes the com.jarkillo.axon-terminal folders in %APPDATA% and %LOCALAPPDATA%, but not %LOCALAPPDATA%\axon-terminal. To remove everything, delete %LOCALAPPDATA%\axon-terminal by hand afterwards.

The websites

• Download form and waiting list: your email and, if you give them, your name, which plan interests you, whether you want updates, and the IP and browser you signed up with. To let you know about what you asked for (basis: consent) and to be able to prove that you asked for it (legitimate interest).
• Analytics: both websites use Umami, installed on Lichen’s own server. No cookies, no cross-site tracking, no third parties. On both it counts visits, the website you came from and the campaign of the link, and clicks on “Download”. On uselichen.com it also counts submissions of the waiting list form (only the chosen plan, never the email). On terminal.neuralflow.es it also counts submissions of the download form (without the email), which version of the home page you got (because we test several), clicks on the home page menu and on links to other websites, how far you scroll on each page and which sections of the home page you see. Umami does not store your IP: it identifies the visit with a salted hash, and that salt changes from time to time. It stores the country, the region, the city, the browser language, the browser, the operating system, the type of device and the screen size.
• The account website does not load analytics.

What is not collected

• The full content of your files. Paths go out and, with CI Guardian, the function index described above. If you do not want it to go out, exclude those paths in checks.function_index.exclude_paths or do not use CI Guardian.
• The rest of the conversation with your agent, unless you turn on AXON_SESSION_EXTRACT=1 on your computer (see section 4).
• Third-party analytics: there is no Google Analytics, Sentry, Mixpanel or anything similar. The only analytics are those of the websites, our own, described above.
• Your .env or the system credentials: from your .env the hooks only read AXON_URL and AXON_API_KEY, to connect, and they do not send it. But what you or your agent write in a message, an issue or a memory does reach the server: do not paste secrets there.
• Anything from folders without a Lichen project.

4. Who it is shared with

Data is not sold or used for advertising.

Providers that process data on Lichen’s behalf, always:

Today there is no payment provider, because Lichen charges no one. When there is billing, this policy will be updated before anyone is charged.

Account emails go out from our own mail server (mail.neuralflow.es), and from there to the recipient’s provider. Semantic search uses our own service on the same server; it does not go out to third parties.

Security: the server analyzes its logs with CrowdSec to block attacks. If your IP address triggers an alert, it is shared with the CrowdSec network (CrowdSec SAS, France) so that others can block it. Only the IP, the type of alert and the time are sent. No log lines or your content are sent. The legal basis is the legitimate interest in the security of the service.

Only if you turn it on:

Only if the operator turns it on (off today): the tasks of summarizing, extracting or merging memories go to our own model or, as plan B, to Anthropic’s API. If plan B were turned on, the text of those tasks would go out to Anthropic (USA). Before turning it on, Anthropic will be added to the providers table and customers will be notified. It is never sent to OpenAI.

Data would also be given to an authority if a law or a court requires it.

Outside the European Union: Google may process the backup files outside the European Economic Area. There are two safeguards: the EU-US Data Privacy Framework, under which Google LLC is certified, and the European Commission’s standard contractual clauses. In addition, the files are encrypted and Google does not have the key. The services you turn on yourself (table above) are processed by each provider under your account and its terms.

5. Who can read your data inside Lichen

Lichen has no end-to-end encryption: whoever operates the server can technically read your content. They only do so when it is necessary to maintain the service, to solve a problem you have asked to be solved or to comply with an obligation.

6. How long it is kept

7. Deleting your account

You can request closure from your account. You have 30 days to cancel it. After that period, your content, your keys and your integrations are permanently deleted from the database. You can also delete a single memory at once; the normal deletion hides it and the permanent one (hard_delete=true) removes it.

The following is kept, with no link to your account:

• The audit log, without IP, browser or email, up to 365 days.
• Usage and search counters, without the text of your searches.
• The fingerprint of the PC where the trial started and the identifier of the hand-signed license you moved to your account, so that deleting the account does not give another trial or free that license.
• The account row, with the email replaced and without password or second factor, to record that it was deleted.

Backups: server backups expire after 7 days and Google Drive backups after 30, so deleted data disappears from the backups within 30 days at most. Backups are not used except to recover the service after a disaster. If one had to be restored, the closures the backup already knew about are applied again. A closure requested in the hours between the last backup and the failure would be lost with the rest of what was done in that time, and you would have to request it again: we would let you know.

8. Your rights

You have the right to access your data, rectify it, erase it, restrict its processing, object to it, take it to another service and withdraw a consent at any time, without affecting what has already been done.

• Without asking anyone: the full ZIP export (GET /api/users/me/data-export) and account closure also work without an active subscription.
• By email: write to hola@neuralflow.es. We reply within one month at most.
• Complaints: if you disagree, you can go to the Spanish Data Protection Agency (aepd.es) or to the authority of your country.

Lichen does not make automated decisions with legal effects on you or build profiles of you for that purpose.

9. Security

• Communications go over HTTPS.
• Passwords with bcrypt and API keys with SHA-256; not even the operator can recover them.
• Data separated per user in the application, with automated isolation tests.
• Server administration goes over SSH with a key only, no password and no direct root access.
• The database does not accept connections from the internet: it only listens on the private administration network, not on the public IP.
• Second factor available.
• Daily backups encrypted before leaving the server, with tested restore.
• The database is not encrypted at rest, except for some fields: the second-factor secret, the GitHub token, the Jev key and the spending detail.

If a security breach put you at high risk, we will let you know without delay.

10. Cookies and local storage

The account uses a single cookie, axon_session (the technical name is kept), first-party and technical, to keep you signed in: it lasts 7 days and can be deleted by signing out. The account website also stores the state of the welcome screen in your browser (localStorage). terminal.neuralflow.es stores in your browser (localStorage, key axon-lang) only the language you choose: it is not sent anywhere and it is deleted by clearing the site’s data. uselichen.com stores nothing in your browser. There are no analytics or advertising cookies, so no consent is asked for them.

On your computer, the hooks store in the temporary folder counters, caches, the session state (which memories your agent has seen, to warn you if one is corrected) and part of the initial context waiting to be delivered. Their names start with axon_. In ~/.claude/axon they store, per project, which memories turned out to be useful.

11. Minors

Lichen is intended for people over 18. If you know that a minor has given us data, write to us and we will delete it.

12. Changes

If something important changes, we will let you know by email at least 30 days in advance, unless the law requires it sooner. Earlier versions can be requested at hola@neuralflow.es.