Privacy

Privacy Policy.

How Eldric handles your data — the short answer: the desktop app keeps it on your device; when you sign in to an Eldric server, that server stores what you send it.

Last updated: October 2026

Eldric is local-first. The desktop app keeps your data on your device unless you explicitly configure connections to third-party AI services. One exception: when you sign in to an Eldric server with the Eldric Mobile app (or another client), that server stores your account and what you send it. If you sign in to chat.eldric.ai, that server is operated by us; section 6 explains what it processes. If you sign in to your organisation's own Eldric server, your organisation operates it and is responsible for it.

1. Who we are

Eldric is developed and published by [core] Informationstechnologie, Jürgen Paulhart, based in Austria. We build local AI infrastructure software that runs entirely on your hardware. See the Impressum for full legal details.

2. Data the desktop app does not collect

The Eldric desktop application does not collect, transmit, or store any of the following:

No user accounts or registration required
No telemetry or usage analytics
No tracking pixels, advertising identifiers, or fingerprinting
No crash reports sent to our servers
No personal data transmitted to Eldric or [core] servers, except the daily update check described below

We have no analytics SDKs, no third-party tracking libraries, and no server-side data collection infrastructure for the application itself.

Update check. Once a day the desktop app asks repo.eldric.ai whether a newer version exists. Like any web request, this sends your IP address and the app's identification (user agent) to our server. The server records it in its access log together with the time, the address requested, the result and the size of the answer; the log is deleted after about 11 days. The request contains nothing else: no account, no content and no usage data.

3. Data stored locally on your device

Eldric stores all application data locally on your Mac (or other device) in your user directory. This includes:

Chat history and sessions — all conversations are stored locally in ~/.config/eldric/ and are never transmitted to any server
Configuration and preferences — stored in a local SQLite database on your device
Prompt library and knowledge bases — stored locally for RAG (Retrieval Augmented Generation) functionality; see How Eldric knows things
Vector database files — embeddings and indexes remain on your device

You have full control over this data. Deleting the Eldric configuration directory removes all stored data.

4. Third-party API keys and connections

Eldric supports connections to third-party AI inference services such as OpenAI, Anthropic, Groq, Together AI, and others. When you choose to configure these:

API keys are stored locally on your device only, in Eldric's configuration database. The file is set to owner-only permissions (0600) and is never transmitted to us — but it is not encrypted at rest, so it is protected by your account and your disk encryption rather than by a passphrase of its own. If your Mac has FileVault enabled, that covers it at rest.
Direct connections — Eldric connects directly to the third-party service. We never proxy, intercept, relay, or log these connections
No key transmission — your API keys are never sent to Eldric, [core], or any server other than the provider you configured
Your responsibility — usage of third-party services is subject to their respective privacy policies and terms of service

By default, Eldric uses local AI backends (such as Ollama) that run entirely on your machine. No third-party connections are made unless you explicitly configure them.

5. Eldric cluster license validation

Eldric includes optional distributed cluster functionality that requires a license. If you activate an enterprise license, the following limited communication occurs:

The Eldric Controller may contact the Eldric license-validation service to validate your license and check for software updates
This communication transmits: machine ID, hostname, Eldric version, and license ID
No chat content, user data, API keys, or personal information is transmitted during license validation
License validation can operate in offline mode using a locally stored signed license file, requiring no network communication

6. Eldric Mobile and chat.eldric.ai

Eldric Mobile is a client for an Eldric server: it needs an account on a server you sign in to. If that server is chat.eldric.ai, we ([core] Informationstechnologie, Jürgen Paulhart) operate it and are responsible for the data it processes. If it is your organisation's own Eldric server, your organisation is responsible, and its own privacy notice applies.

What the server stores and processes

Your account: user name or email address, display name and role.
What you send: chat messages, files you upload, knowledge-base documents, and the results of tools you ask the assistant to use. If you ask it to use your contacts, calendar, reminders or mail, the details it needs for that request are sent to the server as part of the conversation.
Technical data: the server keeps an audit log of actions (who did what, when, in which tenant, with what result), without message content, and the time of your last sign-in. Each Eldric server also keeps an access log for security and access control: one entry per request to administrative, identity, security, cluster, user-management and system interfaces, and for every refused request. An entry holds the time, the server, the request's method and address, its result, your IP address, your user or key identifier and your tenant. It never holds the content of the request, a key or your name. Entries are deleted automatically after 2 years. To limit repeated failed sign-ins, the server also counts attempts per IP address in memory for at most 15 minutes. The operator's top-level administrators (super-administrators and administrators not bound to a tenant) can read the whole access log; administrators of your tenant see only your tenant's entries.

Who at the operator can see what. Your data is kept within your tenant (your organisation's area on the server). The operator's top-level administrators of chat.eldric.ai (super-administrators and cluster administrators not bound to a tenant) have technical access across tenants: they can read stored conversations, personal memories, knowledge collections (knowledge bases and their documents) and the audit log of every user and tenant. They use this access only to operate and support the service. Administrators of your own tenant see only your tenant.

Permissions on your device. Contacts, calendar, reminders, photos and the camera are used only when you ask for them, after iOS asks for your permission. Speech recognition runs on your device; audio is not sent to the server. The app asks for permission to show notifications, but the current version does not register for notifications and sends no push token to the server.

Where it is processed. chat.eldric.ai runs on servers we operate ourselves, on our own premises in Vienna, Austria, in our own network behind our own firewall; no hosting provider processes your data. Its internet connection is provided by Nessus GmbH, Vienna.

Cloud models. Some models offered on chat.eldric.ai are run by third-party providers. If you choose such a model, your message and the conversation context needed to answer it are sent to that provider, under its own privacy terms. Models run on our own hardware send nothing to third parties. The third-party providers currently connected are Ollama Cloud and the Hugging Face inference service. The model picker shows which model you are using.

How long it is kept. Conversations have no automatic expiry: they are kept until you delete them or your account is deleted. Audit records (identifiers and actions only, no content) are deleted automatically two years after they were written, and backups after 30 days; the access log, which is also contained in backups, is kept for 2 years. Billing and usage records are kept for 7 years and then deleted automatically. After an account is deleted and its 30-day trash period has ended, your identifier in them is replaced by "deleted-user"; when a whole tenant is deleted, its usage records keep the tenant's identifier so the final invoice can be issued.

Deleting your data. You can delete individual conversations in the app, and you can delete your account in the app. Deleting an account removes the personal data stored with it: your account, conversations, settings, memories, your messaging accounts and messages, sessions, files and artifacts you created, and the parts of knowledge bases you uploaded. Documents you added to a shared knowledge base before 25 October 2026 are recorded as belonging to your tenant rather than to you, so they are deleted with the tenant, not with your account; ask us if you want them removed earlier. Deleted data first goes into a trash for 30 days, from which an administrator can restore it on request, and is then permanently erased. The audit log keeps only identifiers and actions (who did what, when), not the content. The security access log keeps your identifier and IP address for up to 2 years after your account is deleted; it is a tamper-protected security record and is not changed by a deletion. You can also ask us to delete your account by writing to office@eldric.ai.

No tracking. Eldric Mobile contains no analytics, advertising or tracking code, and we do not use your data for advertising or to build profiles.

7. Website

The Eldric website at eldric.ai is a static HTML site. It does not use cookies, does not run analytics scripts and does not track visitors. Like any web server, it records each request in its access log: your IP address, the time, the page requested, the result, the referring page and your browser's identification (user agent). The log is used only to operate and secure the site and is deleted after about 10 days. The documentation site docs.eldric.ai works the same way. The package server repo.eldric.ai, from which Eldric servers and the desktop app fetch updates, records requests the same way and deletes its log after about 11 days.

8. Data sharing

We do not sell, trade or rent your personal data. The desktop app sends us nothing beyond its daily update check (section 2). For chat.eldric.ai, data reaches a third party only when you choose a cloud model (section 6); we use no data brokers, advertisers or analytics services.

9. Children's privacy

Eldric is not directed at children. chat.eldric.ai accounts are not intended for children under 16 (or the applicable age in your jurisdiction), and we do not knowingly store personal information of children.

10. Data security

The desktop app's data remains on your local device under your operating system's security controls. chat.eldric.ai requires a sign-in, and connections to it are encrypted (HTTPS). API keys stored in Eldric's configuration are protected by your system's file permissions. Enterprise license files use Ed25519 cryptographic signatures for integrity verification.

11. Your rights

For the desktop app, all data is stored locally on your device, and you have complete control:

Access — all your data is in ~/.config/eldric/
Deletion — remove the configuration directory to delete all data
Portability — copy your configuration directory to transfer data between machines
Restriction — no data processing to restrict, as we do not process your data

For chat.eldric.ai you have the rights the GDPR gives you: access, correction, deletion, restriction, data portability and objection, and the right to lodge a complaint with a supervisory authority (in Austria: the Datenschutzbehörde). Write to us to use them.

12. Changes to this policy

We may update this Privacy Policy from time to time. Changes will be posted on this page with an updated revision date.

13. Contact

If you have any questions about this Privacy Policy or Eldric's data practices, please contact us:

[core] Informationstechnologie
Jürgen Paulhart
Email: office@eldric.ai
Web: eldric.ai

Full legal details: Impressum.