Privacy Policy

Module Health Index (allservices.one) is an independent project. It is not affiliated with Odoo S.A. or the Odoo Community Association (OCA). Contact: hello@allservices.one.

Who runs this. Data controller: Serhii Vinnikov (Ukraine). Contact: hello@allservices.one.

Browsing is anonymous. The public index (install-test results, methodology, dataset) needs no account and sets no tracking cookies. The dataset is published under CC BY 4.0.

Server logs. Our web server records each request: the time, the page requested (including any query string), the HTTP status, the referring page and the browser's user-agent string when the browser sends them, together with the IP address the request came from. These records are kept for about a day: entries older than 24 hours are removed every hour, so none is kept longer than 25 hours. We use them to see how much traffic there is, which pages are read and which sites link to us, and to find errors. The report we build from them has IP addresses anonymised and crawlers excluded, it is never published, and any request path that could carry a one-time link or an email address is removed before the report is built. No cookies, no scripts and no third-party analytics are used for this.

Accounts. You can create an account with an email magic-link, or by signing in with GitHub or Google. We store your email address, a display name, and the identifier from the sign-in provider you used. We do not store passwords: email sign-in uses a one-time link. We use your account to sign you in, to send alerts you subscribe to, to let you send messages about a module, and to let you submit a module for checking.

Cookies. Essential cookies keep you signed in and nothing else. No advertising or third-party tracking cookies.

Messages you send. A message you send about a module and version is private. It is stored and visible only to the maintainers of this project, used to correct a result or reply to you. It is not published on the site.

Modules you submit. If you submit a repository, we store its git URL, the branch or tag, and the list of modules read from its manifests (name, version, license, dependencies); your code is not executed. We keep the fetched copy of the code on our server, show it to no one, and delete it together with the submission. We fetch the code in one of three ways. A public repository needs no access. With a deploy key, we create a key pair for that one submission: you add the public half to your repository with read-only access, and we keep the private half encrypted on our server and delete it together with the submission. An access token, if you use one, is used once, at the moment you submit, to fetch the code, and is not stored anywhere. You can delete a submission at any time; removing the deploy key or revoking the token on your side ends our access. By default a submission is private and visible only to you. A public repository is added to the public index only if you explicitly opt in. From a private repository nothing is published unless it was submitted with a deploy key and you tick individual modules for publication; for those modules we publish only the module name, version, series, license and dependencies, marked as coming from a private repository, and never the repository address, the code, or your name. You can withdraw that consent at any time, and the module leaves the public index at the next site update.

Alert emails. Alerts are opt-in and you can unsubscribe at any time.

Your rights. You can view, export, or delete your data. Deleting your account removes your messages and your submissions, together with their deploy keys and the fetched copies of the code. Ask at hello@allservices.one or use the in-account controls.

Where data lives. On our own servers (Hetzner, EU). We do not sell or share your personal data. If you sign in with GitHub or Google, that provider processes the sign-in under its own policy.

Changes. We date this page and post changes here.

Last updated: 2026-10-01.