GDPR · European Union

GDPR and security logs, kept where you decide.

IP addresses, user names and device identifiers make security logs personal data. What the GDPR asks about collecting, keeping, securing and transferring them, and how a SIEM you run in your own environment keeps that processing with you. Your logs never reach nano.

Buy nano
Talk to sales
What the GDPR says

The articles a SIEM touches.

The Regulation's own words, what they mean for security logs, and where nano fits.

Why security logs are personal data

Ref What the text says In plain English How nano helps
Art. 4(1) · Recital 30 Personal data is information about an identifiable person, identifiable "by reference to an identifier such as a name, an identification number, location data, an online identifier". Recital 30 names "internet protocol addresses, cookie identifiers". EUR-Lex · GDPR User names, email addresses, device IDs and IP addresses make almost every security log personal data.
Treat the SIEM as a system that processes personal data. nano runs in your environment, so that processing stays with you.
C-582/14 Breyer "a dynamic IP address registered by an online media services provider when a person accesses a website that the provider makes accessible to the public constitutes personal data" where the provider has the legal means to identify the person with additional data the internet service provider holds. CJEU · C-582/14 Even a dynamic IP address in a web or firewall log can be personal data. The Court ruled under the GDPR's predecessor, Directive 95/46/EC.
IP addresses are first-class fields in nano's OCSF events: easy to search during an investigation, and covered by the same access controls as the rest of the log.
Recital 49 · Art. 6(1)(f) Processing "to the extent strictly necessary and proportionate for the purposes of ensuring network and information security" is a legitimate interest of the controller. EUR-Lex · GDPR Security monitoring has a recognized legal basis, as long as it stays necessary and proportionate. Public authorities performing their tasks cannot use 6(1)(f) and usually rely on 6(1)(c) or (e).
You decide which sources to onboard; every install starts with zero log sources.

What the GDPR asks of the logs themselves

Ref What the text says In plain English How nano helps
Art. 5(1)(c) Personal data shall be "adequate, relevant and limited to what is necessary in relation to the purposes for which they are processed ('data minimisation')". EUR-Lex · GDPR Collect the logs your detections and investigations need, not everything by default.
Collection runs in your environment, so you choose which sources and events are collected at all.
Art. 5(1)(e) Kept "in a form which permits identification of data subjects for no longer than is necessary for the purposes for which the personal data are processed". EUR-Lex · GDPR Set a retention period you can justify, and delete after it.
You set the event retention window (365 days by default). Expired events are deleted from your store automatically, and retention changes are recorded in the platform audit log.
Art. 25(2) "by default, only personal data which are necessary for each specific purpose of the processing are processed. That obligation applies to the amount of personal data collected, the extent of their processing, the period of their storage and their accessibility." EUR-Lex · GDPR Defaults matter: how much you collect, who can see it and how long you keep it.
Roles and source visibility limit which teams see which logs. Settings also includes a GDPR erasure function for one person's data, run as a background job and limited to roles with its own permission.
Art. 30(1)(f), (g) The record of processing activities contains, "where possible, the envisaged time limits for erasure" and "a general description of the technical and organisational security measures referred to in Article 32(1)". EUR-Lex · GDPR Security monitoring is a processing activity: write down its retention period and how the logs are secured.
Retention, access roles and where the data sits are settings you control and can describe exactly, because the install is yours.
Art. 32(1)(b), (d) Appropriate measures including "the ability to ensure the ongoing confidentiality, integrity, availability and resilience of processing systems and services" and "a process for regularly testing, assessing and evaluating the effectiveness" of those measures. EUR-Lex · GDPR Protect your systems, and keep checking that the protection works. Logs are how you check.
Detections and alerts watch the systems you onboard; searches over retained logs show controls working. The log store sits behind your own access controls and backups.

Breaches and transfers

Ref What the text says In plain English How nano helps
Art. 33(1), (5) Notify the supervisory authority "without undue delay and, where feasible, not later than 72 hours after having become aware of it", and "document any personal data breaches, comprising the facts relating to the personal data breach, its effects and the remedial action taken." EUR-Lex · GDPR 72 hours from awareness, and a written record of every breach, notified or not.
Search across sources to establish what was accessed, when and by whom; the case holds the facts, effects and actions you document. Notifying stays with you.
Art. 34(1) Where a breach "is likely to result in a high risk to the rights and freedoms of natural persons, the controller shall communicate the personal data breach to the data subject without undue delay." EUR-Lex · GDPR High-risk breaches also go to the people affected.
Logs show whose accounts and data were reached, so you can scope who to tell.
Art. 44 · Art. 46(1) Transfers to a third country take place only if "the conditions laid down in this Chapter are complied with"; without an adequacy decision, only with "appropriate safeguards" and enforceable data subject rights and effective legal remedies. EUR-Lex · GDPR Sending logs to a SIEM vendor in another country is a transfer that needs a basis.
nano never receives your log content, so using nano creates no transfer of log data to nano. Run it in the EU region or data center you choose.
Articles 33 and 34

72 hours from awareness.

The clock starts when you become aware of a personal data breach. Working out what was accessed, and whose data it was, comes from the logs you already hold.

  1. 0 h

    Aware of a personal data breach

    Unless it is unlikely to result in a risk to people's rights and freedoms.

  2. 72 h

    Supervisory authority

    Where feasible; a later notice gives reasons for the delay (Art. 33(1)). Every breach is documented, notified or not (Art. 33(5)).

Regulation (EU) 2016/679, Article 33.
Processors and transfers

Who else processes your logs?

With a SaaS SIEM, the vendor processes the personal data in your logs. With a SIEM you run, nobody else does.

nano, run in your environment

The logs stay with you.

  • You process your logs on infrastructure you control
  • nano never receives log content, so nano is not your processor for it
  • No transfer of log data to nano; you choose the region
  • Your record of processing describes your own install
SaaS SIEM

The vendor processes your logs.

  • The vendor processes your logs on your behalf: an Article 28 processor contract
  • Its sub-processors and support locations need checking too
  • If it is outside the EEA, Chapter V transfer rules apply
  • A breach at the vendor reaches you through Article 33(2) notice
Your environment

Your data center, your account with a cloud provider in the EU region you pick, or an air-gapped network

01 · Sources
  • identity provider
  • firewall
  • VPN
  • endpoint
  • web proxy
  • SaaS apps
02 · nano
  • Collect and parse
  • Detections and alerts
  • Search and cases
03 · Your storage
  • Disks you own
  • Optional object storage tier
  • Retention you set
Optional · AI pivt AI calls your model endpoint directly: any OpenAI-compatible API (including self-hosted models) or the Anthropic Messages API. Off by default; model calls never go through nano.
nano, the vendor

Never receives your logs.

Connected
  • Daily license check-in: deployment ID, install ID, version
  • Hourly content and enrichment-feed updates (no data sent; can be turned off)
  • One number per day: total GB ingested
  • Downloads: log-source catalog, detection rules and SOAR content, enrichment feeds, releases
Air-gapped
  • No connection to nano at all
  • Offline license file, renewed by hand
fig 01 · nano runs inside your environment. Log data is never sent to nano.
FAQ

Questions we get asked.

Are security logs personal data under the GDPR?

Usually, yes. Article 4(1) covers information that identifies a person directly or indirectly, including by "an online identifier", and Recital 30 names internet protocol addresses. In Breyer (C-582/14) the Court of Justice held that even a dynamic IP address can be personal data for a website operator that has legal means to identify the person through the internet service provider. Logs with user names, email addresses, device IDs or IP addresses are personal data.

Is security monitoring allowed under the GDPR?

For most organizations, yes. Recital 49 says processing personal data to the extent strictly necessary and proportionate for network and information security is a legitimate interest of the controller, a lawful basis under Article 6(1)(f). Public authorities are the exception: Article 6(1) says "Point (f) of the first subparagraph shall not apply to processing carried out by public authorities in the performance of their tasks", so they usually rely on a legal obligation (Article 6(1)(c)) or a task carried out in the public interest or in the exercise of official authority (Article 6(1)(e)). Whatever the basis, the processing has to be necessary and proportionate, and principles such as minimization and storage limitation still apply.

How long can security logs be kept under the GDPR?

The GDPR sets no number of days. Article 5(1)(e) says personal data must be kept no longer than necessary for the purpose, so set a period you can justify for security monitoring and investigation, record it (Article 30 asks for envisaged time limits for erasure where possible), and delete after it. Sector and national laws can require longer periods for some logs.

What is the GDPR breach notification deadline?

Article 33(1): notify the competent supervisory authority without undue delay and, where feasible, not later than 72 hours after becoming aware of a personal data breach, unless it is unlikely to result in a risk to people's rights and freedoms. Late notifications must give reasons for the delay. Article 34 adds notice to the people affected when the risk is high, and Article 33(5) requires every breach to be documented.

Is sending logs to a cloud SIEM a data transfer?

It can be. If the SIEM vendor, its sub-processors or its support staff are outside the EEA, sending them personal data in logs is a transfer under Chapter V and needs an adequacy decision, appropriate safeguards such as standard contractual clauses, or a listed derogation. A SIEM vendor that processes your logs is also your processor under Article 28.

Is nano a processor of our log data?

No. nano is software you install and operate in your own environment, and nano never receives your log content. For that data nano is neither your processor nor a transfer destination. nano's Data Processing Agreement covers only your users' account data on app.nano.rs and any support material you choose to send.

Does using nano make us GDPR compliant?

No. GDPR obligations sit with you as controller and cover far more than logs. nano gives you control over what is collected, who can see it, how long it is kept and where it lives, and the evidence to investigate and document a breach.

Primary sources

Read the rules yourself.

  1. Regulation (EU) 2016/679 (General Data Protection Regulation), EUR-Lex
  2. Court of Justice of the European Union, Case C-582/14 Breyer, judgment of 19 October 2016

Last reviewed 14 November 2026. Regulations and guidance change, so read the current version at the source.

Start with nano.

From US$149/month at 5 GB/day, US$279/month at 10 GB/day (list price, billed monthly; 10% off billed annually). Every feature in one license, and one license covers two installs.

Buy nano
Talk to sales