Website privacy policy
This policy covers the ragatm.com website only. It does not describe the RAGatm Open software, which runs on each operator’s own infrastructure.
Last verified: 11 November 2026
What the site does not do
- No audience measurement tool (no Google Analytics or equivalent).
- No advertising script, no tracking pixel, no font loaded from a third-party server.
- No cookie set by the site. Any preference (such as a table filter) stays in your browser and is never transmitted.
- No form: the only contact channel is contact@ragatm.com.
- No external JavaScript dependency at runtime; pages are readable without JavaScript.
Web server logs
Like any website, the server hosting ragatm.com records technical logs (IP address, date and time, requested page, declared browser). They are used exclusively for security and hosting diagnostics.
- Legal basis
- Legitimate interest (security and proper operation of the service).
- Retention
- 14 days, then automatic deletion (daily rotation of the hosting logs). Proposed duration, to be confirmed by the owner
- Recipients
- The hosting manager only; no transfer to third parties.
E-mails received
If you write to contact@ragatm.com (including to report a vulnerability), your message and address are kept while your request is handled, then archived or deleted. To be confirmed: e-mail provider and archiving period.
Third-party sites
Links to GitHub or other external sites take you off ragatm.com. Those sites apply their own privacy policies.
Your rights
Under the General Data Protection Regulation (GDPR) and French data protection law, you may request access to, rectification or erasure of data concerning you by writing to contact@ragatm.com. You may also lodge a complaint with the CNIL, the French supervisory authority.
What about the RAGatm Open software?
RAGatm Open is designed to run on your own infrastructure with locally executed AI models: in the qualified Compact configuration, no document is sent to a remote AI provider and no fallback to an external service exists in the published code. GDPR compliance of a deployment nevertheless depends on the operator (hosting, backups, access rights, retention periods): the software does not guarantee it on its own.