Security and data

The log has no eraser.

It records who changed what, and when, and every time a worker reads your mailboxes. Then the storage refuses to change or erase a single line of it.

Example: the night of a scheduled mission

  1. 02:00:00The “Night sweep” trigger started a run.
    No.
    4127
    When
    2026-10-13T02:00:00+02:00
    Who
    The “Night sweep” trigger
    Via
    trigger
    Action
    trigger.fired
    Object
    run
  2. 02:00:06Incoming invoices searched the mailbox index.
    No.
    4128
    When
    2026-10-13T02:00:06+02:00
    Who
    Incoming invoices
    Via
    “Night sweep” mission
    Action
    index_search
  3. 02:01:41Incoming invoices uploaded a document “invoice-sorel-0412.pdf”.
    No.
    4129
    When
    2026-10-13T02:01:41+02:00
    Who
    Incoming invoices
    Via
    “Night sweep” mission
    Action
    file.uploaded
    Object
    document “invoice-sorel-0412.pdf”
  4. 02:01:42Incoming invoices uploaded a document “credit-note-breval-0098.pdf”.
    No.
    4130
    When
    2026-10-13T02:01:42+02:00
    Who
    Incoming invoices
    Via
    “Night sweep” mission
    Action
    file.uploaded
    Object
    document “credit-note-breval-0098.pdf”
  5. 02:03:15Incoming invoices created a task “Sorel invoice 0412: is the amount 1,240.00 euros?”.
    No.
    4131
    When
    2026-10-13T02:03:15+02:00
    Who
    Incoming invoices
    Via
    “Night sweep” mission
    Action
    task_create
    Object
    task “Sorel invoice 0412: is the amount 1,240.00 euros?”
  6. 02:03:16Incoming invoices paused the run.
    No.
    4132
    When
    2026-10-13T02:03:16+02:00
    Who
    Incoming invoices
    Via
    “Night sweep” mission
    Action
    run.paused
    Object
    run
  7. 07:48:52Claire Dumas changed the task “Sorel invoice 0412: is the amount 1,240.00 euros?”.
    No.
    4133
    When
    2026-10-13T07:48:52+02:00
    Who
    Claire Dumas
    Via
    screen
    Action
    task_update
    Object
    task “Sorel invoice 0412: is the amount 1,240.00 euros?”
  8. 07:48:53Incoming invoices resumed the run.
    No.
    4134
    When
    2026-10-13T07:48:53+02:00
    Who
    Incoming invoices
    Via
    “Night sweep” mission
    Action
    run.resumed
    Object
    run

Example, fictitious data. The entries, formatted from the log export and translated from French.

a worker a person a trigger, set by a person

Each entry is chained to the previous one: a rewrite breaks the chain, and it shows.

The log can be exported in full.

Request a call back What if someone bypassed it?

The proof

What if someone bypassed it?

The storage refuses every change and every erasure of an entry, whoever the caller: a worker, a person, or us. To rewrite a line, you would have to bypass the storage itself. Try it: the chain breaks, because each line carries the fingerprint of the previous one.

  1. 4130Incoming invoices uploaded a document “credit-note-breval-0098.pdf”.previous fingerprint
  2. 4131Incoming invoices created a task “Sorel invoice 0412: is the amount 1,240.00 euros?”.previous fingerprint
  3. 4132Incoming invoices paused the run.previous fingerprint

The storage answers in its own words, the product’s: journal : ajout seul, une entrée ne s'efface pas (French for “log: append-only, an entry cannot be erased”)

Where your data is

Your data stays under your control

We do not promise that nothing ever leaves. We promise that you stay in charge: where your data is, who reads it, what the workers are allowed to do, and the record of everything they do.

  • Hosting in France

    The platform runs on a server we operate ourselves, in France. An installation on your premises is considered case by case.

    The risk removedData going who knows where.

  • Open models, run locally if needed

    The workers can run on open models installed locally. No content then goes to a model provider.

    The risk removedDependence on a single model provider.

  • When an external model is needed

    Some cases benefit from a more powerful model. We only call it on your data with your written agreement, after telling you who its provider is and in which country it processes your data. Each work cycle keeps a record of the provider called.

    The risk removedA transfer nobody decided on.

  • No training without your agreement

    The models installed on our server learn nothing from your data. For an external model, we give you its terms, training included, before your written agreement, and you can require an offer without training.

    The risk removedYour files in someone else’s corpus.

GDPR

Who does what under the GDPR

  • For the data the platform processes for you, your company is the controller, and Anthelixa its processor.
  • It is processed in France, on our server, and we only entrust it to an external model with your written agreement.
  • The log records who changed what, and when, as well as every time a worker or a search reads your mailboxes; it can be exported in full.
  • Your job descriptions, your rules and your log remain yours: we hand them over to you in an open format, whether or not you continue.

Overnight, without you

What a worker cannot do, even on its own

These limits do not depend on what the model is asked. They are written into the platform and into the storage.

  • Touch your money

    The workers read your bank accounts. They never touch them: no payment tool, anywhere.

  • Rewrite its own job description

    A worker does not change its rules. Only a human can: your team, or us with your agreement.

  • Set its own clock

    Only a human decides when a worker starts work.

  • Erase what it has done

    It can erase neither its memory nor the log.

  • Step outside its scope

    Each workspace is isolated, and the number of actions per work cycle is capped.

  • Send without you

    Anything that would leave your company, an email for example, it prepares as a draft, and a human sends it.

The proof

Every action is recorded, and the record cannot be rewritten

  • An append-only log

    Every action is recorded: who acted, human or worker, on what, when, with a summary in French. The log accepts additions only. Each entry is chained to the previous one: a rewrite breaks the chain, and it shows.

    The risk removedThe action nobody can explain.

  • Files that can be frozen

    A document can be locked, a file frozen. On the day of a dispute or an inspection, the file is there, dated.

    The risk removedThe file nowhere to be found on the day of the dispute or the inspection.

  • The history of every line

    Information that is changed keeps its previous version. You know what changed, and when.

    The risk removedThe change nobody remembers.

  • Readable by your chartered accountant

    The log and the files are in French, in an open format. They can be read without us.

    The risk removedProof that only the vendor can read.

In the morning, you decide

Your rules, in French, in a file

A worker’s rules are not programmed into the software. They are documents stored in your workspace, which your team reviews and edits itself: no ticket, no waiting.

Every job description we write has a “what it never does” section, which the worker rereads in every work cycle.

The risk removedA development ticket to change a threshold.

Spending

Capped in advance

Your subscription covers a number of operations, not a compute bill. At the cap, the chain stops and a task asks you to decide.

The risk removedThe compute bill that spirals at the end of the month.

A specific question

Your IT manager’s questions

Hosting, models, log, contract: we answer them in writing, during the audit or before.

Request a call back Write to us
Request a call back