TRANSPARENCY / PRIVACY
Privacy notice
This notice concerns vigialabs.net, the public identity website for VigiaLabsBot.
Updated on 12 November 2026.
Controller and legal information
| Legal name | ABE International, SL |
|---|---|
| Legal form | Societat Limitada (SL) |
| Andorran tax number (NRT) | L-717679-Z |
| Company register | Registre de Societats Mercantils d’Andorra, núm. 22603, llibre S-432, folis 31-40 |
| Registered office | Av. Prat de la Creu, 59-65, esc. D, planta 3, porta 5AB · AD500 Andorra la Vella · Andorra |
Privacy and data rights: privacy@vigialabs.ai
Privacy policy questions and requests concerning your personal data.
| EU representative | Prighter EU Rep GmbH, Schellinggasse 3, 1010 Vienna, Austria |
|---|---|
| UK representative | Prighter Ltd, 20 Mortlake High Street, London SW14 8JN, United Kingdom |
Scope and applicable rules
ABE International, SL, established in Andorra, is responsible for the personal data processed for this identity website and its contact channels. Andorran Law 29/2021 applies. The GDPR and UK data protection rules apply where their territorial criteria are met; a visitor’s language or the location of a server alone does not determine this.
This site provides identity information and a public key directory. It does not run audits when you visit, sell services, create customer accounts or make automated decisions with legal or similarly significant effects about visitors. A private preview may require Cloudflare Access authentication.
Data, purposes and legal bases
Delivery and security: IP address, requested resource, timestamp, browser headers and technical security events may be processed to serve the site and prevent or investigate abuse. The basis is the legitimate interest in operating a secure, identifiable service, subject to necessity and balancing against individual rights. This is not a basis for advertising or visitor profiling.
Contact: your email address, message and relevant evidence are used to answer identification, exclusion or incident enquiries. The basis is the legitimate interest in answering requests and managing responsible operation. Pre-contractual necessity applies only if you personally request steps towards a contract. Exercising data protection rights is handled to meet the controller’s legal obligations. Sending an email is not consent to unrelated processing.
Messages are voluntary. Without sufficient contact or issue details, we may be unable to investigate or reply. Do not send passwords, session cookies, tokens, private keys or unnecessary personal records. We do not require an identity document by default; additional proportionate information may be requested where identity or authority is reasonably in doubt.
Cookies, preferences and private access
Selecting a language or theme stores vl-language and vl-theme in localStorage to provide your requested appearance. These entries contain no identifier or browsing history and remain until you change them or clear site data. The necessary vlbot-consent entry records your analytics choice, notice version and choice/expiry timestamps for 180 days, without a visitor ID. On your next visit after expiry or a notice version change, a new choice is requested. Clearing site data also clears this choice. No advertising tools are used.
Where Cloudflare Access protects a private preview, authentication can process an email address, login events and a CF_Authorization cookie. That cookie is for access control, not advertising; its lifetime depends on the configured session. The identity provider may process its own authentication data. Blocking the authentication cookie can prevent access to the private preview. This is separate from the public site’s language and theme preferences.
Optional analytics and cookies
Only if you accept analytics, ABE uses Google Analytics 4 (GA4), loaded through Google Tag Manager (GTM), to measure page visits, sessions and basic engagement and improve this technical site. The basis is your consent (GDPR Article 6(1)(a), where applicable, and applicable device-storage rules). Rejecting or closing the notice does not grant consent and does not restrict the site. Google scripts and analytics requests are blocked until acceptance: this is basic Consent Mode, without pre-consent or rejected-consent measurement pings.
After acceptance, Google receives pseudonymous cookie identifiers, the public page address and title, visit/event times and technical browser/device information. The network connection reveals an IP address to Google; this service is not anonymous. We do not send email addresses, message contents, form data or a User-ID. Analytics is disabled on addresses containing query parameters or fragments and on unknown pages; page referrers are not sent as analytics parameters. Enhanced measurement, Google Signals, advertising personalisation and user-provided data collection are disabled. GTM manages the single analytics tag and does not itself require an analytics cookie.
GA4 sets first-party cookies on vigialabs.net: _ga distinguishes browsers and _ga_<ID> maintains session state. Both are configured for a maximum of 180 days without refreshing their expiry on each visit. GA4 user and event data is retained for 14 months to support year-on-year analysis, without resetting user retention on new activity. This limit does not apply to standard aggregated reports. It is separate from the retention periods for bot evidence, enquiries and security records.
You can withdraw consent as easily as you gave it: open Cookie preferences in the footer and choose Reject all. Collection is disabled, accessible first-party _ga cookies are deleted and an active analytics page reloads without Google tags. Withdrawal does not affect earlier lawful processing and does not automatically erase data already received by Google. For erasure or other rights, use the privacy contact above. If the browser cannot store your choice, analytics remains disabled.
Google provides Analytics and Tag Manager under its applicable service and data-processing terms. Processing may involve Google Ireland Limited, Google LLC and their subprocessors, including in the United States. Google describes adequacy frameworks and standard contractual clauses for applicable international transfers in the documents linked below; their application depends on the data flow and jurisdiction, including Andorra. The privacy contact can provide information about the applicable safeguards and a copy. Acceptance of analytics is not a blanket waiver of transfer safeguards.
Google Search Console reports indexing and search performance to the site operator. Ownership verification uses a static HTML meta tag, without downloading Google scripts or setting visitor cookies. It is independent of your analytics choice and does not grant the site operator access to your Google account.
Google Privacy Policy · Google Ads Data Processing Terms · Google international data transfers
Recipients and international processing
Cloudflare supplies hosting and security infrastructure; the mail domains route email through Google. Prighter provides the confirmed EU and UK representation and its rights-request portal. Access must be limited to authorised personnel and providers performing the relevant service. Providers may act as processors for customer data and as separate controllers for some service or security data, according to their contracts.
These services may involve processing outside Andorra, the EEA or the United Kingdom. European node locations do not guarantee exclusive European storage or support access. The applicable adequacy decision or other lawful transfer safeguards must be established for each data flow, including Andorran requirements. We do not claim that the EU-US Data Privacy Framework alone covers every transfer. Ask the privacy contact for information on the applicable safeguards and how to obtain a copy.
Retention policy
ABE adopted the following limits on 11 November 2026. They are purpose-specific limits, not statutory minimums or a general right to retain all data. Unnecessary data must be removed sooner.
- Ordinary enquiries and incidents: up to 180 days after closure, to handle follow-up and recurring issues. Only relevant correspondence and evidence are retained.
- Own security logs, if enabled: up to 180 days from each event, for incident investigation and correlation. This Worker has no persistent application logging enabled. Cloudflare’s own retention depends on the contracted service and configuration; this limit does not describe or change it.
- Rights requests: while being handled, then up to three years after closure for a minimal record of the request, response and measures taken. Identity documents and unnecessary attachments must be deleted once no longer needed. This is an accountability limit, not a universal limitation period.
- Exclusion rules: while the exclusion must be respected, keeping only the domain or paths and the rule needed to prevent renewed collection. Contact details follow the ordinary enquiry limit unless needed for a documented dispute.
- Audit evidence: up to 180 days from collection for relevant technical evidence, to compare observations and investigate findings. Irrelevant personal data must be filtered or deleted sooner. Historical statistics may be kept longer only if genuinely anonymised; pseudonymised data remains subject to data protection law.
A specific legal duty or actual claim may justify restricted preservation of the necessary subset for the applicable period, with a recorded reason, access restriction and review date. It does not extend the whole database indefinitely. Backups and provider copies need their own verified deletion cycle.
Exercise your rights
You may request access, rectification, erasure, restriction and, where the conditions apply, portability. You may object to processing based on legitimate interests on grounds relating to your situation. Any consent can be withdrawn without affecting earlier lawful processing. Use the privacy email, postal address or Prighter portal above; owning the audited domain is not required to exercise rights over your own personal data.
Rights requests are handled without undue delay and normally within one month. Where the applicable law permits an extension for complexity or number of requests, we will explain it within the initial period; the extension may be up to two further months. No fee is charged in the ordinary case. Any refusal must explain its grounds and the available complaint routes.
You can complain to the Andorran Data Protection Agency (APDA) and, where relevant, to the competent EEA supervisory authority or the UK ICO. You do not have to complete an internal complaint before contacting a competent authority.
Crawler activity and third-party data
The service includes examining publicly accessible websites without prior permission from their owners. Public availability does not remove data protection, copyright, database or access restrictions. A client’s contract does not itself provide a contractual legal basis for processing unrelated people’s data.
Processing personal data requires a specific purpose, necessity and an applicable legal basis. Reliance on legitimate interests requires balancing individual rights and applying safeguards. Indirect collection requires the applicable transparency measures; a public notice alone is not an automatic exemption from individual information duties. High-risk processing requires the corresponding impact assessment.
Evidence can include HTML, cookies, browser storage, network metadata, screenshots and historical observations. Collection must exclude unnecessary personal data, private areas and sensitive or criminal-offence data lacking a valid legal condition. The bot does not access visitors’ devices or personal browser sessions. Collected content will not be used to train AI models.
Technical findings are evidence for review, not a legal ruling or certification of compliance. Applicable rules depend on the operator, audience, processing and territorial scope, not just a node’s IP address.