Supplementary portal and product notice
Version of 7 November 2026. This notice complements the website privacy policy. It is neither a compliance attestation nor a statement that every service described in the code is enabled in production. GaLiLo is a personal pre-release project, with no commercial activity.
1. Controller and contact
The controller for portal administration is the website publisher, reachable for privacy and rights at rgpd@galilo.io. The account is used to take part in the pre-release and to follow assistance. No sale or paid offer is presented. This notice covers processing received by the project services, not every local use of files by the appliance administrator.
2. Tickets and assistance exchanges
To answer a request and follow an incident, the service processes: account identifier and email, display name, subject, ticket text and replies, priority, stated version, status, dates, author and chosen attachments. The portal stores these elements in Supabase. Internal notes are available to authorized people, not to participants. Notifications go through Cloudflare and Resend, to the ticket owner or the publisher’s Gmail mailbox depending on the author. An email reply can be added to the ticket after the sender and the ownership are checked. Do not attach a password, token, secret or unnecessary information.
Basis: legitimate interest in providing the assistance requested in the pre-release, while limiting the data. Useful content is necessary to handle the incident. Attaching a file remains optional.
3. Logs and diagnostic bundles
Files are added voluntarily from the portal or by a send action from the appliance. A bundle can contain application or system logs, versions, service and storage state, configuration, installation identifiers, machine names, accounts, paths or network information. The code masks known secrets on a best-effort basis, without a guarantee that every secret is removed: review the file before sending and reduce it to what is needed. Attachments are stored in the private Supabase bucket ticket-logs and linked to the ticket. Download links generated by the portal expire after 120 seconds, which is not the file’s retention period. The upload notification can contain the file name, the installation and the storage path, without attaching the archive itself.
Basis: legitimate interest in diagnosis and security for the data that is necessary. A voluntary send is not a general consent to process other people’s data. The administrator checks that they are entitled to transmit it.
4. Technical licences and installations
Licences are software access mechanisms, not a commercial offer. The service can process: linked email, licence and installation identifiers, technical type, issue and expiry dates, allowed features, capacity, technical assistance level, status, revocation, notes and activation events; optional hostname and last seen time. Notifications and licence tokens are sent by email when that function is used. The account can be linked to the appliance for licences and updates. A session refresh token is stored locally, not the password, according to the module reviewed.
Basis: legitimate interest in running the pre-release, its access, its updates and abuse prevention. Linking, activation and update checks can produce presence and version data even when telemetry sending is disabled. The code reviewed does not show any payment or card collection.
5. Telemetry
Software telemetry is enabled by default. The basis is the website publisher’s legitimate interest: tracking installed versions in order to ship security fixes. It is not processing based on consent.
The data sent are: installation_id, version, hypervisor, licence type and number, counters of shares, files, volumes and SMB users, high-availability indicator, and first-installation date. The hostname is sent only if the administrator has checked it.
Sending is daily. The administrator can disable it at any time in System › Privacy. Disabling stops later sends. It does not delete data already received, nor the separate licence and update exchanges.
These data are pseudonymous and linked to the licence. They are kept for the life of the licence plus 12 months. After that, only an anonymous aggregation is kept, with no time limit: data that can no longer be linked to an instance or a licence.
6. Software assistant
The website does not process any AI-assistant content. The api.galilo.io/ai gateway is disabled by default.
The software assistant has two modes. Both are disabled by default and require explicit activation by the administrator.
- Mistral key provided by GaLiLo, an option disabled by default, kept in particular for proofs of concept. Once this mode is activated, content sent to the assistant is transmitted to Mistral AI. GaLiLo does not keep the content of requests or responses once the response has been generated. Data transmitted to Mistral AI is processed according to Mistral AI’s retention policy for its API.
- BYOK. The administrator provides their own key to an OpenAI-compatible endpoint, for example Mistral, OVH AI Endpoints or a local Ollama. The key is stored encrypted and is not logged. Data is processed under the terms of the provider chosen by the customer. The screen for this mode is planned for release 0.65.10 (issue 79). It is not delivered in the version described here.
The legacy relay to Anthropic (POST /ai/proxy) has been removed. Do not enter a secret or confidential information before checking the scope of the messages that are sent. Answers can be wrong and must be checked before any action. No exclusively automated decision with legal effect is documented.
7. Recipients, places and safeguards
The publisher and strictly authorized people; Cloudflare, Supabase, Resend and Google/Gmail according to the flows above. When the GaLiLo-provided Mistral key mode is activated, content sent to the assistant is transmitted to Mistral AI. For BYOK, the recipient will be the operator of the endpoint configured by the administrator, when the screen planned for release 0.65.10 is delivered. Primary Supabase: eu-west-1, Ireland, as confirmed by the publisher. Cloudflare’s network, email and other services can involve access outside the EEA. Contracting entities, access, backups, agreements and transfer safeguards are to be confirmed. This notice does not state where Mistral AI processes the content. No guarantee of an exclusively French location, or of a location limited to the EEA, is given.
8. Retention and rights
The periods already selected in the website policy remain: active account then 12 months after closure, contact exchanges 12 months after closure, technical logs managed by the publisher 30 days outside an incident, and the other periods in that policy’s table. Pseudonymous telemetry linked to the licence is kept for the life of the licence plus 12 months, then as an anonymous aggregation, with no time limit. GaLiLo does not keep the content of requests or responses of the Mistral-key assistant once the response has been generated. Periods specific to tickets and attachments, and to licences and events, are not established by the files reviewed. Signed links of 120 seconds, quotas and abuse-prevention TTLs are not deletion periods for this data. Whether erasure of databases, archives, email and provider copies is effective remains to be confirmed.
Rights of access, rectification, erasure, restriction, objection and, where its conditions are met, portability. Contact: rgpd@galilo.io. Reply within the legal period, generally one month. Proportionate identity check if needed. Complaint to the CNIL, or to the competent authority. Closing an account is not an instant deletion from every system.
General website contact: contact@galilo.io.