Privacy and access to Argos reports
Information updated on 16 October 2026. Antoine Le Louët EI, a sole trader in France under the microenterprise scheme, operates Argos to support his professional activity.
On this page
- Accounts and closure
- Data received for an audit
- Report access and sharing
- Retention and expiry
- Measurement services and logs
- Protection against bots
- Premium waiting list
- Preferences and other interactions
- Traffic and optional cookies
- Account notifications
- Usage measurement
- Contact and your rights
- Account emails and recipients
- Signing in with GitHub or LinkedIn
- Signing in with Google
- Bugs, suggestions and false positives
- Service terms
- Contact the operator
Accounts and closure
An account is optional for audit journeys that support this. If you create an account, your email address, display name, sign-in identities and sessions are stored to manage your access. Your password is stored as an Argon2id hash, never in plain text. Sign-in providers are contacted only at your initiative; Argos does not retain their tokens.
The user session cookie is HttpOnly and limited to 15 minutes, renewable within a server session lasting at most 12 hours, with a 30-minute limit on inactivity in account operations.
Closing your account archives it: access is revoked, but the account record, technical references and statistics are retained. Previously shared report links remain readable until their usual expiry, without extension. Neither reactivation nor automatic anonymisation is offered. Account security logs are purged after 90 days when the next log entry is written; they are distinct from the technical infrastructure logs described below.
Data received for an audit
The submitted URL, domain, processing dates and statuses, and technical results are stored to run the audit and display the report. The measurement browser loads the public page and its resources. Do not submit a URL containing confidential information or credentials.
Report access and sharing
A report summary is available without signing in to anyone who has its link. Detailed findings require a verified account. Access to your personal area and its history remains authenticated; having a link does not grant access to its owner’s account.
The owner can create, replace or revoke a sharing link. They can choose an expiry of 7 or 30 days, or no additional expiry; report retention still applies. Revoking this sharing link does not revoke the original report link. Only share links with your intended recipients.
The operator has administrator access. Public report pages and responses ask search engines not to index them and are not listed in the sitemap. This instruction is neither access control nor an absolute guarantee that reports will not appear in search results.
Retention and expiry
The default period of access to reports is three years from their creation. A shorter expiry still applies if one was assigned. Expiry immediately blocks access through the link and to the associated status. An hourly task deletes expired reports and clears the internal results of their completed runs, in batches of 500. Audit, domain and run metadata are retained; this task does not delete backups. Purging may take longer if many reports expire at once or if the task is unavailable. Contact the operator to request deletion.
Measurement services and logs
Playwright and Lighthouse load the page and its resources to take measurements. The SSL Labs and Mozilla Observatory modules may send the domain name to their configured services to supplement security checks. Activation depends on configuration; Argos hosting does not describe the location of these third-party services.
As confirmed by the operator on 16 October 2026, production technical logs and backups are retained for three years, exclusively on local infrastructure in Belgium, manually hosted and administered by the operator, without GAFAM hosting for this storage. This statement does not cover sign-in or email providers.
Application-level deletion of a report does not remove copies from backups before their own retention period ends. Account security logs, notifications and user feedback have their separate 90-day application retention periods described on this page.
Protection against bots
When protection is enabled, sensitive public forms use Cloudflare Turnstile. The script loads on submission and may ask for interaction. Cloudflare receives the IP address and browser signals needed to detect automation; Argos does not send your form fields, passwords or report links in the server verification request. Argos does not retain anti-bot proofs. This integration does not enable Cloudflare pre-clearance cookies. This provider’s processing may be international: see Cloudflare’s privacy policy. If verification prevents you from using a form, contact the operator via the service information page.
Premium waiting list
With your explicit agreement, your email and language are stored to contact you about future Premium offers, possible early access or a discount, without a commercial guarantee. The consent date and version are recorded in a list separate from the newsletter. No account or newsletter subscription is created and no confirmation email is sent.
Retention is limited to 12 months after the initial signup; duplicate requests do not extend it. An hourly task deletes expired entries in batches of 500; delays are possible if it is unavailable or volumes are high. Backups follow their own retention. You can withdraw consent and request deletion at any time by emailing the Argos contact below from your registered address. Signup requests do not log your email address.
Preferences and other interactions
Your theme preference may be remembered in the browser. Administrator sign-in uses a session cookie. If you subscribe to a newsletter offered by the service, your email address is sent to the backend and stored for that subscription. Email and LinkedIn links open the chosen service only at your initiative, without prefilling a report.
Traffic and optional cookies
Traffic measurement is disabled by default and requires consent separately from product measurement. You can accept all, reject all or customise; “Manage cookies” lets you withdraw consent. First-party preference and visit cookies are HttpOnly and last for the browser session. The visit marker is a boolean with no personal identifier. Only predefined public routes, language and direct, search, referral, campaign or internal categories are aggregated. UTM values, full URLs, tokens, accounts, IP addresses, device and country are not recorded in these counters. No third-party provider receives this measurement. Aggregates are retained for 90 days and purged hourly. Withdrawal deletes the visit marker and stops future collection; existing anonymous aggregates remain. A browser session is not a unique visitor. Refusals and blockers limit coverage.
Account notifications
Completed or failed analyses, discoveries and batches generate private notifications: internal reference, domain, result type, date and read status. They support the requested service, remain stored while you are signed out and are retained for 90 days before hourly purging. They contain no submitted URL, token or raw technical error. Reading them requires your session and grants no additional access to results.
Usage measurement
Internal product measurement is disabled by default. If enabled, explicit consent is requested before any collection. Accept and refuse are offered together; you can withdraw your choice from “Manage cookies”. The choice cookie lasts for the session and contains no visitor identifier. Event names, predefined pages, language, placement, sign-in method and error categories are counted. After renewed consent, internal account, session and analysis references are used only to deduplicate registrations, sign-ins, report claims and return days, and to calculate activation and retention cohorts. These references are pseudonymous, not anonymous; only aggregates are exposed to administration. The HttpOnly SameSite Lax cookie preserves this choice during a social sign-in callback. A consented audit is associated with its internal identifier to measure its status and the first display of its report; no submitted URL, token, email address, IP address or report content is stored in these tables. No third-party provider receives these measurements. Retention is limited to 90 days, with hourly purging. Withdrawal stops new collection from the browser; already aggregated counters and the states of previously consented audits are not reversed.
Contact and your rights
For questions or requests to access, correct or delete data about you, contact Antoine Le Louët using the details below. Avoid sending a report link in your first message. You can also consult the CNIL about your rights and how to lodge a complaint.
Account emails and recipients
Email verification, password reset, identity confirmation and alerts about password or sign-in method changes are sent through OVH’s SMTP service. OVH receives the recipient address and message content, including the confirmation link or code when needed. Each message states its validity period, which depends on configuration.
These emails manage and protect your account. They do not subscribe you to a newsletter. Contact links may open your email service or LinkedIn at your initiative.
Signing in with GitHub or LinkedIn
Google, GitHub and LinkedIn are the sign-in providers confirmed by the operator. Their use is optional. GitHub uses the “read:user” and “user:email” permissions; LinkedIn uses “openid”, “email” and “profile”. The chosen provider receives the exchanges needed for the requested sign-in or linking operation.
Argos stores the provider’s stable identifier, email address and verification status when available, and display name to manage the account. Provider tokens are not retained, and these identities are not sent to audit modules. You can remove a sign-in method while keeping at least one other usable method.
Signing in with Google
If you choose Google to sign in or link a sign-in method, Argos requests only the “openid”, “email” and “profile” identity permissions. Google provides a stable account identifier, your email address and its verification status, and your display name. Argos uses this information to recognise your identity, create your account on an eligible first sign-in or link Google to an existing account. No access to Gmail, Google Drive or your contacts is requested.
The Google identifier, email address, verification status and display name needed for your account are stored in the Argos database. Tokens received from Google are used to validate sign-in and are not retained. Google identity data is used to manage your account and access; it is not sent to the modules that analyse websites. When you choose this provider, Google receives the exchanges required for authentication, without receiving your report links in those exchanges.
You can remove Google as a sign-in method from your account while keeping at least one other sign-in method. This disables that method; its technical identifier, your account and analyses are retained. Closing your account archives it as described above. Contact the operator to request deletion of your data. You can also manage connections to apps in your Google Account.
Bugs, suggestions and false positives
Feedback is private and handled by administrators. The type, description and chosen page context are stored, along with optional reproduction fields for a bug. An internal report reference may be attached with your consent; a false positive also includes the finding key after access is checked. Website URLs you choose to enter are stored as text and are never visited. No cookie, report token or browser screenshot is stored in these tables. Status changes are recorded with the administrator’s identifier. Feedback and its history are retained for 90 days from submission, then deleted by an hourly task; backups follow their own retention period. A submission does not automatically change the score. Do not include secrets or personal data in free-text fields.
Service terms
Also read the Argos terms of use and service information.
Contact the operator
A question about Argos or its fixes? Write to Antoine Le Louët.
Contact by email : a.lelouet.freelance@gmail.comView the LinkedIn profile