Privacy policy

Life Engine · effective 10 September 2026

Life Engine has exactly one user: its owner and operator. It is a personal system running on hardware its owner controls. It is not offered to anyone else, has no accounts to register, and processes no other person's Google data.

1. Who this covers

This policy describes how Life Engine handles the Google account data of the single individual who owns, operates and is the sole subject of the system. That person is both the operator and the data subject. No third party's Google account is ever accessed.

2. What data is accessed, and why

Life Engine requests the narrowest Google scopes that let it do its job, and no others.

Data	Access	Why
Google Calendar	Read all calendars; write only to a dedicated calendar the system creates and owns	To see what time is already committed, and to place its own proposed time blocks in a separate layer that can be hidden or deleted wholesale without touching the owner's real calendars
Google Tasks	Read and write	To publish the currently actionable subset of the owner's own task list to their phone
Google Health — sleep	Read only	Sleep duration and stages, to inform how demanding a week the system proposes
Google Health — activity and fitness	Read only	Steps and workouts
Google Health — metrics and measurements	Read only	Heart rate and heart-rate variability

Life Engine does not request access to Gmail, to Drive file contents, to contacts, to photos, or to location history.

3. Where the data is stored

On a single private virtual server controlled by the owner, as plain Markdown files and a derived local SQLite index.
In a private Git repository, used as version history and off-server backup. It is not public and has no other collaborators.
In encrypted snapshots (GPG, AES-256), which are useless without a passphrase held outside the server.

4. Third parties the data reaches

This is the section that matters most, and it is stated plainly rather than buried. To interpret the owner's own data, Life Engine sends portions of it to language-model APIs. Text derived from calendar entries, health measurements and the owner's own notes is transmitted to:

Anthropic (Claude), for reasoning and summarisation.
Google (Gemini), for mechanical extraction and embedding.
GitHub, which stores the private repository described above.
Telegram, which carries messages between the owner and the system when they are away from their desk. Anything the owner sends or receives that way passes through Telegram.

Each of these processes the data under its own terms and privacy policy. Beyond them, no data is shared, sold, licensed, rented, published, or handed to advertisers, data brokers or analytics providers. There are no advertising or tracking technologies anywhere in the system, and this website sets no cookies and runs no analytics.

5. How long it is kept

Indefinitely, by design. The system's purpose is to remember its owner's life over years, so records are kept until the owner deletes them. Deletion is unconditional and immediate on request — the owner controls the server and can destroy the archive, the index and every backup at any time.

6. Withdrawing access

Google access can be revoked at any moment, independently of the system, at myaccount.google.com/permissions. Revocation takes effect immediately and stops all further reading of Google data. It does not by itself erase data already stored; erasing that is done on the server, as described above.

7. Security

Credentials are stored outside the data archive, readable only by the account that runs the system. Traffic to this domain is served over TLS. Backups are encrypted before they leave the server. This is a personal system on a single host, and it is described here honestly rather than dressed up: it carries no security certification and makes no claim to one.

8. Children

Life Engine is used by one adult — its owner — and is not directed at children.

9. Changes

If the system's data access changes, this page changes with it before the new access is requested. The effective date above is the record of when it last did.

10. Contact

Questions about this policy: ludo.bouan@gmail.com