Timestamped at source
Each entry carries its date, its time and the identity of its author at the moment the action is taken: no reconstruction from memory, no date “rounded off” several days after the incident.
Evidence & architecture · the foundation and the trace
Each register entry keeps its author, its timestamp, its context and the items it is linked to. The register is designed to reconstruct a timeline and export a file that management, an auditor or an authorised third party can use.
Understand the risk. Take back control. Stay the course.
Append-only log · timestamped · hosted in France by Scaleway · Mistral AI (EU) · your data remains exportable.
Trust
is proven.
“Sovereign” has become a marketing argument. We prefer verifiable facts: the hosting country, the name of each subcontractor, our AI provider, the exact nature of the encryption, and an explicit list of what we do not do. An organisation does not entrust its cybersecurity to a promise: it entrusts it to an architecture it can read, audit and submit to its own DPO.
You do not have to “remember to document”. Every action taken in the console (a crisis decision, a treatment measure, a compliance gap closed, an IOC analysis) feeds the register as it happens, with its timestamp and its author. Evidence is not a report written after the fact: it is the trace of what actually happened.
Each entry carries its date, its time and the identity of its author at the moment the action is taken: no reconstruction from memory, no date “rounded off” several days after the incident.
A piece of evidence never stands alone: it is linked to the risk, the incident, the playbook or the regulatory requirement that produced it. You can trace back from the fact to the decision, and from the decision to the fact.
Decisions, hypotheses, event logs, screenshots, exchanges and attachments: the file builds up continuously, ready to be reviewed by a third party who was not in the room.
Retention by category and purpose, proportionate: incident files are archived for evidential purposes for up to 5 years (the general limitation period for civil actions is five years under Article 2224 of the French Civil Code); accounts, 24 months after the last activity. Never indefinite.
A log is only worth something if it cannot be doctored after the fact. The Galyct Pro decision log works on an append-only basis: entries are added, the past is never silently deleted or modified. Correcting a decision means writing a new entry that explains the correction; the original entry remains visible. How the log is sealed and verifiable →
Each decision records: what was decided, by whom, when, on the basis of what information was available at the time, and why. A later revision is stacked on top without erasing what came before. The thread reads in order, from the first signal to closure.
This is exactly what an insurer handling a claim, a regulator checking that a deadline was met or a judge reconstructing a timeline expects: a timeline that no one could alter after the event.
The most costly mistake, in a crisis as in an audit, is to present a hypothesis as a fact. Galyct Pro explicitly qualifies every item in the file: on rereading it, you know what had been demonstrated and what was still an assumption when the decision was made.
An established fact, backed by a verifiable trace: an event log, a screenshot, a document, a technical confirmation. Something that can be shown to a third party.
A working hypothesis, useful for moving forward but not demonstrated. It is labelled as such: decisions are made on that basis knowingly, without disguising it as a certainty.
A clue worth noting without drawing a conclusion. Recorded so that it is not lost, it may be confirmed (or refuted) as the file progresses.
The direct consequence: no attribution without evidence. No culprit and no root cause is asserted until the technical or contextual evidence supports it. What cannot be demonstrated is still presented as a hypothesis or a limit.
An evidence register is only useful if it leaves the tool. Galyct Pro produces structured exports from the same facts, adapted to who reads them. One truth, several levels of reading: management, the bank, the insurer, the lawyer, the auditor and the regulator do not receive contradictory versions.
Incident timeline and measures taken: enough to support a fraud report, a request to block a payment or a recovery file, with the dates that matter.
A well-documented claim file: timestamps, decisions, logs and evidence of remediation, the supporting documents insurers often ask for, depending on your policy.
An unaltered timeline, distinguishing facts and hypotheses: the basis for filing a complaint, a notification or a defence, with no grey area about what is proven.
Evidence linked to requirements (ISO 27001, NIS 2, DORA): the documentation points to real practices and traces, not to statements of intent.
Notification of a data breach on time (72 hours under the GDPR), with a record of the decisions taken: the regulatory clock and the log speak the same language.
A concise report, focused on decisions and budget: what happened, what was decided, what remains to be done, all backed by the detailed file.
Open formats that can be read outside the platform. See the frameworks covered →
Evidence is not manufactured at the end: it is laid down at each link. Because risk, analysis, incidents and compliance live in the same place, nothing is entered twice and nothing gets lost between two tools. Any item in the file can be traced back to its origin.
An evidence register locked inside a tool you do not control is not evidence: it is a dependency. With Galyct Pro, your data remains yours, hosted in France by Scaleway, and you export it whenever you want, including to leave the platform.
Your evidence and your logs are hosted in France, with Scaleway. The AI assistant relies on Mistral (EU), under human oversight: no processing outside the EU behind your back.
The register, the decision log and the documents can be exported in open formats: you need neither our agreement nor our tool to reread your own file.
Leaving must remain possible. You get back the complete history of your decisions and your evidence: traceability does not disappear because you change solutions.
We never ask for your access codes to your banks, email or third-party services. Evidence is built from what you observe and decide, not from access to your accounts.
Hosting, backups, logs and evidence items stay in France (EU), with Scaleway. The optional external checks (DNS resolution, URL reputation, leak lookup) are triggered in a controlled, documented way: for each one, you know which data is transmitted and to which service. Facts, described, not a marketing absolute.
Servers operated in France by Scaleway, a hosting provider without SecNumCloud qualification. The data on your incidents, your risks and your evidence does not leave the EU in the normal course of the service.
Sensitive data is encrypted at rest; exchanges go over TLS (HTTPS), with hardened security headers (HSTS, CSP). Encryption protects the data; it is never an excuse for recording nothing.
Each organisation (and each entity in a group) has a partitioned space. One subsidiary does not see another’s data; sharing, where it exists, is an explicit, logged choice.
Regular backups and exportability of your data: your evidence, your registers and your logs belong to you. You leave with what you have produced, with no hostile retention.
Roles (administrator, editor, member), least privilege and traceability of access. Sensitive actions are timestamped: who saw what, who decided what, and when.
The Galyct Domain component queries DNS in encrypted form (DNS-over-HTTPS) through non-filtering public resolvers in the European Union, Mullvad (Sweden), Freifunk München (Germany) and LibreDNS (Greece), with FDN in France as a fallback: only the domain name being checked is transmitted, no personal data. Controlled observation, described as it is.
Your tools remain yours. The connectors (EDR, firewalls, backup, intelligence) work read-only: “the customer brings their own instance”. Galyct reads your events and never controls your tools: no Galyct agent is required for these connectors. An optional endpoint sensor (“Endpoint agent”) is also available, if you want to enrich the telemetry. See the connectors →
The Galyct Pro assistant relies by default on Mistral, a French provider whose models are operated in the European Union. AI prepares, proposes and speeds things up; the decision remains human, and every output can be verified.
AI processing takes place at Mistral (France/EU). The choice of provider is governed on the server side: you know which engine processes your requests, and nothing is sent to a model outside the EU without your knowledge.
AI drafts a playbook, proposes a qualification, summarises an incident: a person approves. No irreversible action is triggered by the assistant without a decision by the operator.
Automated analysis of files and indicators relies on an analysis engine that does not leave the EU, alongside recognised open sources. Advanced analysis capabilities are being added in waves: some are coming soon, and we say so rather than let anyone believe otherwise.
Use of AI is governed by consent and a log: a risk screen spells out what is sent to the model. You stay in control of what is submitted, and of what is not.
Galyct Pro’s AI is not meant to replace an analyst: it saves them time on repetitive work, so they can focus on the decision. See the analysis area →
Galyct Pro provides tools for the frameworks your stakeholders require. The platform helps you document and meet your obligations: it issues you no state label, and it replaces neither your DPO nor your auditor.
Record of processing activities, impact assessments, procedure for notifying a breach on time. You are the data controller; we are the processor, with a dedicated contractual framework (DPA).
European directive: obligations, governance, control of third-party risk and compliance trajectory. The platform structures the evidence; the assessment remains a matter for you and your authorities.
Operational resilience for the financial sector: ICT third-party risk management, testing, major incidents and reporting. Each requirement is linked to decisions and exportable evidence.
Trust is verified along the subcontracting chain. Here are the key providers involved in the service, their role and where they operate. The full list is kept up to date (last review: 15 August 2026) and made available within the contractual framework (DPA).
| Subcontractor | Role | Location |
|---|---|---|
| Scaleway / Online Hosting provider |
Hosting of the service’s infrastructure, databases, backups and logs. | France |
| Mistral Artificial intelligence |
Provider of the AI model that assists with analysis and drafting, under human oversight. | France / EU 🇪🇺 |
| Stancer Payment |
French payment provider for subscriptions and passes. We do not store your card details: they go through the provider. | France |
Publisher of the service: Datashield Risk Consulting (SAS), which publishes the Galyct ecosystem. Any change to this list is communicated to you within the contractual framework. Legal notice →
A trustworthy platform can also be recognised by what it refuses to ask you for. These rules are not sales promises: they are prohibitions our teams apply to themselves.
If a message claims to come from Galyct and asks you for any of these things, it is an attempted fraud. If in doubt: report an incident →
A register documents what happened; an architecture reduces exposure. Neither rewrites history, guarantees an outcome or replaces the judgement of your advisers. Saying so is precisely what gives them their value.
Documenting a decision does not guarantee that it was the right one, or that an incident will be avoided: no result is guaranteed. The register proves what was done and when, not that it will be enough.
A timestamped, consistent log is solid evidence: its exact weight before an insurer, a regulator or a court is for them to assess, with your legal advisers, not a promise on our part.
We use neither “unbreakable”, nor “100% secure”, nor “guaranteed”. The aim is to reduce exposure and keep the evidence; a limited check never proves the total absence of risk.
The platform documents; it issues no label. Documentation must match real responsibilities and practices: we document what is done, not the other way round.
Galyct is a provider listed on Cybermalveillance.gouv.fr, a sign of seriousness, not a state certification, and we never present it as one. It does not prejudge how a given incident will be qualified.
Galyct Pro steers day to day. For audit, EBIOS RM, forensics, crisis management or an outsourced CISO/DPO, the firm steps in on quotation: the human layer cannot be replaced by a ticked box.
Suspected intrusion, ransomware, compromised account, data leak: stabilise without destroying the evidence. We open a crisis cell, keep the decision log and build the file as things happen.
Tour the cockpit freely with sample data, or request a 30-minute demo: ask your questions about traceability, hosting and subcontracting. No commitment, processing in the European Union, your data remains yours.