Regulatory Framework & Compliance

Privacy & Data Processing Policy

Document Version: 2.2 | Effective Since: March 2026

This document establishes the regulatory guidelines under which SecureZZ (hereinafter, "the Company", "the Provider", or "We") collects, processes, stores, and destroys personal data and corporate information of its users and clients (hereinafter, "the User" or "the Client"). This policy is designed to strictly comply with Regulation (EU) 2016/679 (GDPR), Spanish Organic Law 3/2018 (LOPDGDD), and equivalent international frameworks.

Security Architecture Based on Zero-Trust Principles

The architecture of SecureZZ is built on technical security models and ephemeral processing. The Company implements measures aimed at minimizing data retention, operating under a processing framework designed to prevent structural persistence of digital assets submitted for analysis.

1. Nature of Processed Data & Exclusions

In compliance with the data minimization principle (Art. 5.1.c GDPR), we strictly limit information collection. Below is our zero-retention policy:

  • Files & Payloads: Files processed through our tools are analyzed, to the fullest extent technically possible, in ephemeral execution environments. Once a security verdict is issued, processing incorporates secure deletion or anonymization of assets in accordance with retention policies. The Company implements technical measures aimed at reducing the risk of persistence outside active operations.
  • Metadata Sanitization (EXIF Stripper): Image processing is designed for local execution in ephemeral memory environments. Processed data undergoes secure deletion routines upon completion of the operation. This service avoids communication with external services, mitigating content exposure during runtime.
  • Technical Data: Technical processing does not perform systematic audits of the semantic content of documents. Analysis focuses on binary structure, heuristics, and technical metadata intended for security evaluation.
  • IP Address Analysis (IP Lookup): IP addresses entered by the User in the IP Lookup tool are processed ephemerally for the sole purpose of querying Threat Intelligence databases. SecureZZ does not log, link to the User's identity, or store a history of queried IP addresses. Information obtained from external sources is displayed in real time and discarded once the session ends.

Documents Containing Personal Data (Invoices, Receipts, Contracts)

Certain tools (such as the PDF Scanner) allow uploading documents that may contain personal or third-party data. With respect to these files, the following is expressly established:

  • Role of the Parties (Art. 28 GDPR): When a document contains personal data, the User acts as the Data Controller and SecureZZ acts solely as the Data Processor, limiting itself to executing the requested technical analysis on behalf of the User in accordance with their instructions.
  • Strictly Technical Purpose: The document is processed exclusively to issue a security and structural integrity verdict (detection of scripts, manipulation, technical metadata). SecureZZ does not read, index, commercialize, transfer to third parties, or use for training artificial intelligence models the content or personal data that the document may contain.
  • Ephemeral Processing & Deletion: The file is analyzed in ephemeral memory environments and automatically deleted after issuing the verdict. Neither the file nor the body content of the document is ever retained. Only a technical record of the result may persist: the cryptographic hash, verdict, and technical metadata of the document itself (e.g., producer software, creator, and creation/modification dates), which constitute indicators required for manipulation detection. With respect to any data that such technical metadata might contain, the User acts as the Data Controller under the terms of this section.
  • User Warranty & Liability: By uploading a document, the User represents and warrants that they hold ownership or the necessary legal authorization to process it. SecureZZ shall not be liable for unlawful processing resulting from the User uploading third-party personal data without a valid legal basis, such responsibility resting exclusively with the uploading User.

2. Collected Data & Legal Basis (Art. 6 GDPR)

For the provision of SaaS services and commercial management, the Company acts, depending on the service and applicable contractual relationship, as Data Controller or Data Processor pursuant to Article 28 of the GDPR, processing the following data under criteria of necessity and proportionality:

  • Identity & Access Information: Email address and login credentials (processed using secure one-way cryptographic hash functions).
  • Third-Party Authentication (SSO): When using identity providers (e.g., Google OAuth), we process the authentication token and basic profile data authorized by the user.
  • Transactional & Billing Data: For payment collection and tax compliance, billing data is processed through our payment gateway Stripe, Inc.. In compliance with international security standards, the Company implements a tokenization architecture: credit or debit card details are captured directly by Stripe through its own secure forms. SecureZZ never processes, views, or stores bank card details on its servers, guaranteeing strict PCI-DSS compliance.
  • Technical Analysis Indicators (IoCs): Within Deep Analysis services, we extract and process IP addresses, URLs, and domains detected inside analyzed samples. This processing is performed under Legitimate Interest (Art. 6.1.f GDPR and Recital 49) in order to provide security intelligence and prevent cyberattacks.
  • Telemetry & Audit Logs: Access IP addresses (collected to enforce usage limits, prevent system abuse, and protect platform integrity against evasion attempts via private browsing or multiple identities) and system usage metadata.

3. Retention Policy & Automated History Purging

In accordance with Art. 5.1.e of the GDPR (Storage limitation), SecureZZ implements automated record destruction routines:

  • File Verdict Log (Metadata): To provide the Client with an audit log accessible from their dashboard, we store the following technical metadata associated with each file scan: original filename (e.g., financial_report.pdf), byte size, cryptographic hash (SHA-256), scan verdict (Clean / Suspicious / Malicious), creation timestamp, scan type (Threat Scan, Deep Analysis, Threat Radar, or PDF Scanner), and an internal job identifier (jobId) allowing the Client to reopen the generated technical report without re-uploading the file.
  • URL Verdict Log: For link and domain analyses (Link Guard, Threat Radar), the analyzed URL, verdict obtained, number of reputation engines triggered, and timestamp are stored equivalently, subject to the same retention period and purge routines described herein.
  • Associated Technical Report: Alongside the above metadata, the Company temporarily retains (for the sole purpose of allowing the Client to re-consult the result without reprocessing the file) the technical report generated by local engines (triggered YARA rules, MITRE ATT&CK capabilities detected by CAPA, extracted strings, entropy, and other technical indicators), as well as, where applicable, the natural-language contextual interpretation produced by SecureZZ AI. This report is stored in structured JSON format linked to the jobId and never includes the original file or document body content.
  • Exclusion of Binary Content from Persistent History: The original file uploaded by the Client is never part of the stored history. As described in Section 1, the binary is written only to an ephemeral operational processing area for the time strictly necessary for local engines (YARA, CAPA, ClamAV, etc.) to issue their verdict, and is immediately thereafter subjected to an automated secure filesystem deletion routine whether upon completion or error.
  • 30-Day Retention Period & Automated Purge: The active history displayed in the Client's dashboard shows, for usability reasons, the 20 most recent records within the retention window. All records (metadata, technical report, cached AI interpretation, and completed scan jobs) are subject to a maximum retention period of 30 calendar days from creation. Once this period expires, an automated routine running every 24 hours permanently and securely deletes them from our databases (Art. 5.1.e GDPR).
  • Aggregated Statistical Counters: For purely statistical purposes and to display cumulative activity on the Client's dashboard (e.g., "Total scans performed", "Historical threats detected"), the Company retains anonymized aggregated numeric counters containing no filenames, hashes, or identifiable metadata.
  • Right to Early Erasure (Forensic Wipe): All Clients, regardless of their plan (including the Free plan), have access to the Zero-Trace Wipe feature in their dashboard, enabling immediate deletion (single or bulk) of history records without waiting for the automated purge cycle.

4. Sub-Processors & International Data Transfers

The Company does not sell Client data. Information is shared only with sub-processors strictly required for infrastructure operations (Art. 28 GDPR):

  • Payment Processing: Stripe, Inc. (Billing and tax compliance).
  • File Analysis: Processing of any file or asset submitted for analysis runs entirely locally through our own engines (YARA, CAPA, ClamAV, etc.). Under no circumstances is the physical content of a file transmitted to external engines. External reputation lookups (e.g., MalwareBazaar, WHOIS servers) send exclusively anonymous technical identifiers such as the SHA-256 cryptographic hash.
  • AI-Assisted Threat Interpretation (SecureZZ AI): To provide contextual threat interpretation features included in paid plans (Threat Scan and Deep Analysis), the Company uses the language model inference infrastructure of Groq, Inc. (Mountain View, California, USA), or an equivalent provider.

    Verified Contractual Guarantees of Groq, Inc.: Pursuant to the GroqCloud Customer Data Processing Addendum (available at console.groq.com/docs/legal), Groq acts as a data processor under documented instructions with the following binding guarantees:
    • Absolute Training Prohibition: Groq does not use prompts (inputs) or responses (outputs) generated through its API to train, improve, or fine-tune any AI model.
    • No Default Inference Retention & Zero Data Retention (ZDR): The Company has Zero Data Retention enabled in GroqCloud data controls, eliminating even temporary diagnostic retention.
    • International Transfers: EU→US data transfers are safeguarded by European Commission Standard Contractual Clauses (SCCs), with formally designated EU and UK representatives (DP-Dock GmbH, Hamburg, Germany).
    • SOC 2 Type II Certification and technical controls: encryption at rest and in transit, multi-factor authentication, and zero-trust network access.
    Under no circumstances is the analyzed file, its binary content, Client personal data, credentials, IP addresses, or account identifiers sent to the AI provider. Communication is strictly limited to technical metadata derived from local analysis (triggered YARA rule names, CAPA capability identifiers, and critical system API call names) for the sole purpose of generating a natural-language technical explanation.
  • Web Analytics: We use Google Analytics 4 (via Google Tag Manager) for performance and usability metrics with forced IP anonymization. Users may revoke consent at any time via the Cookie Management Panel.

Technical Note: Upon revoking consent, SecureZZ automatically purges analytics cookies from your browser and ceases all telemetry transmission in the current session.

Data transfers outside the European Economic Area (EEA) to US providers (e.g., Stripe, Groq) are conducted under mechanisms ensuring an adequate level of protection pursuant to Article 46 of the GDPR: the EU-US Data Privacy Framework (DPF) for Stripe, Inc. and European Commission Standard Contractual Clauses (SCCs) for Groq, Inc.

5. Limitation of Liability & Nature of the Service

SecureZZ provides advanced security analysis tools; however, due to the evolving nature of malware, no scan can guarantee 100% accuracy in detecting zero-day threats or targeted attacks. The Company shall not be liable for direct, indirect, or incidental damages or lost profits arising from the interpretation of security verdicts, false positives, or false negatives. The Client is solely responsible for the lawfulness of processed content.

6. Exercising Your GDPR Rights (ARCO+)

The Client holds full rights over their personal data pursuant to Articles 15 to 22 of the GDPR and may exercise them via direct communication:

  • Access: Find out what personal data we hold about you.
  • Rectification: Correct inaccurate or incomplete information.
  • Erasure (Right to be Forgotten): Request permanent account and data deletion.
  • Restriction: Request restricted processing while other rights are verified.
  • Portability: Receive your data in a structured, machine-readable format.

To exercise these rights, the Client may manage preferences directly from their dashboard or send an email to info@securezz.com from the email address associated with their account.

Right to Lodge a Complaint

If you believe that the processing of your data does not comply with current regulations, you have the right to lodge a complaint with the competent Supervisory Authority (in Spain, the Spanish Data Protection Agency (AEPD)) via https://www.aepd.es.

7. Privacy Contact
For legal inquiries, security breach notifications, or formal exercise of rights on behalf of a corporate entity, please contact our regulatory compliance department at: info@securezz.com.