Where the disks are.
Data stored in an EU region or an EU data center is resident in the EU. Residency says nothing about who operates the service or whose laws reach the operator.
nano is a SIEM you run in your own EU cloud account, your own data center or an air-gapped network. Your logs are collected, stored and analyzed there and never reach nano, so sovereignty does not depend on a vendor's hosting promise.
Three terms get used interchangeably. For a SIEM, which holds some of the most sensitive data you have, the difference matters.
Data stored in an EU region or an EU data center is resident in the EU. Residency says nothing about who operates the service or whose laws reach the operator.
Data is subject to the laws of the place it sits and of whoever holds it. If a provider headquartered outside the EU controls it, that provider's home law can apply too.
Running the technology you depend on where you decide, under your own control, with a realistic way to change supplier. It is the policy goal behind much recent EU regulation.
nano is software you install and operate. There is no nano-hosted copy of your data, and the Self-run Addendum says so: Customer Data stays in your environment and nano has no access to it.
Your account with an EU cloud provider, your own data center, or an air-gapped network
Never receives your logs.
Install on Linux with Docker Compose or on Kubernetes, in an account you hold with the provider you choose, including EU-headquartered ones. The provider relationship is yours, not nano's.
Run on your own servers, one node or three and more for high availability, with older data tiered to S3-compatible storage you own. Storage and retention
Included with every license, if your environment requires it: zero connectivity to nano, a signed offline image bundle, offline content you import by hand and an offline license renewed by hand. Air-gapped deployment
The US CLOUD Act is why “hosted in Frankfurt” does not settle the sovereignty question for a US provider. Here is what it says, and where nano sits.
18 U.S.C. § 2713 requires providers of electronic communication or remote computing services to preserve or disclose data in their possession, custody or control, “regardless of whether” it is located inside or outside the United States.
18 U.S.C. § 2713 ↗EU law recognizes a third-country court or authority order to disclose personal data only if it is based on an international agreement, such as a mutual legal assistance treaty. A provider caught between the two faces conflicting obligations.
Regulation (EU) 2016/679 ↗nano, LLC is a US company. Your logs are on infrastructure you operate and nano has no standing access to your install, so there is no log data at nano for a request to reach. What nano does hold: your account details and license metadata.
Self-run Addendum, section 10 →There is no nano-hosted AI. pivt, the AI investigation assistant, works only with a model provider you configure, and calls it directly from your install.
Point nano at a model you host on your own GPUs or in your own cloud account, using the OpenAI-compatible API format most self-hosted inference servers speak.
Use a provider that speaks the OpenAI-compatible or Claude API format, under your own agreement with it. That provider is your third party, not a sub-processor of nano.
Prompts may include excerpts of your logs, so your install sends them straight to your model, never through nano. With no model configured, AI features are simply off.
IP addresses, user names and device identifiers make most security logs personal data under the GDPR. That shapes what you collect, how long you keep it and who you send it to.
Security logs hold IP addresses, user names, device identifiers and locations. The Court of Justice held in Breyer (C-582/14) that even a dynamic IP address can be personal data.
| Ref | The requirement | In plain English | How nano helps |
|---|---|---|---|
| Recital 49 | Processing personal data to the extent strictly necessary and proportionate for 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. | You decide which sources to onboard; every install starts with zero log sources. |
| Art. 5(1)(c) | Personal data shall be adequate, relevant and limited to what is necessary (data minimization). EUR-Lex · GDPR | Collect the logs your detections need, not everything by default. | The collection pipeline runs in your environment, so you decide which sources and events are collected at all. |
| Art. 5(1)(e) | Kept in identifiable form no longer than necessary for the purposes (storage limitation). EUR-Lex · GDPR | Set a retention period you can justify and delete afterwards. | You set the event retention window (365 days by default), on storage you own. |
| Art. 32 · Art. 33 | Appropriate security of processing; notify a personal data breach to the supervisory authority within 72 hours where feasible. EUR-Lex · GDPR | Protect the logs, and use them to scope a breach fast. | Role-based access control and a platform audit log on the SIEM itself; search across sources to establish what was accessed and when. |
| Ch. V · Art. 44–49 | Transfers of personal data to a third country only under an adequacy decision, appropriate safeguards or a listed derogation. EUR-Lex · GDPR | Sending logs to a SIEM vendor outside the EU is a transfer that needs a basis. | nano never receives your log content, so using it creates no transfer of log data to nano. Where the install runs is your choice. |
| Art. 48 | A third-country court judgment or authority decision requiring disclosure of personal data is recognized or enforceable only if based on an international agreement, such as a mutual legal assistance treaty. EUR-Lex · GDPR | EU law does not, by itself, recognize a foreign order to hand over EU personal data. | nano does not hold your logs, so there is nothing at nano for such an order to reach. |
Many SIEMs send log data to a US company, relying on the EU–US Data Privacy Framework or standard contractual clauses. The Court of Justice struck down both of the Framework's predecessors, Safe Harbor and Privacy Shield, so its status is worth tracking.
The Commission adopts the EU–US Data Privacy Framework adequacy decision.
EUR-Lex · 2023/1795 ↗The General Court dismisses the annulment action in Latombe v Commission (T-553/23).
General Court · T-553/23 ↗An appeal is before the Court of Justice (C-703/25 P), with no judgment as of November 2026.
CJEU · C-703/25 P ↗nano runs the same way in every European country: in your data center or your own cloud account, with your logs staying there. The rules around it differ outside the EU.
The GDPR is part of the EEA Agreement, so the guidance on this page about security logs as personal data applies in the three EEA countries outside the EU. Run nano in a Nordic cloud region or your own data center.
EFTA · EEA-Lex ↗Where the Data Protection Ordinance requires logging (large-scale sensitive data or high-risk profiling), Art. 4 says log files must be kept for at least one year, separate from the system that processes the data. A SIEM you run yourself is that separate system. Critical infrastructure operators must report cyberattacks to BACS within 24 hours, and FINMA-supervised firms follow Circular 2023/1. Sending data abroad, logs included, falls under FADP Art. 16; with nano your logs stay in Switzerland if you run it there.
Fedlex · DPO Art. 4 ↗ BACS ↗ FINMA ↗No UK law requires security logs to stay in the UK. What regulators assess against is NCSC CAF objective C, security monitoring, and the Cyber Security and Resilience Bill will add incident-reporting clocks once it becomes law. Read the UK guide
Elsewhere in Europe, from the Balkans to Turkey, nano is sold and runs the same way. All regions
Plain-English guides to the EU rules that shape what a SIEM has to do, each with the primary sources.
The Annex 3.2 logging checklist, Article 23 reporting and national transposition status.
Read DORARTS 2024/1774 Article 12 line by line, the incident clock and concentration risk.
Read Cyber Resilience ActSIEMs are Class I important products. The timeline, SBOMs and what to ask your vendor.
Readnano is licensed by daily ingest, from US$149/month at 5 GB/day and US$279/month at 10 GB/day, list price. License, updates and business-hours support for the nano software. You run the infrastructure.
Invoiced in USD. Indicative EUR prices on request from sales@nano.rs.
You pay your cloud or hardware supplier directly, so the bill for your data stays with a supplier you chose.
The same product at every size. See all price points
Digital sovereignty is the ability of a country, an organization or a person to control their own data and technology: where it runs, whose laws reach it, and whether they can change supplier. Europe cares because much of its cloud and security software comes from companies headquartered elsewhere, so EU data can sit under foreign legal reach and EU organizations can depend on suppliers they cannot easily replace.
Data residency is where data is physically stored, for example an EU cloud region. Data sovereignty is whose laws and control apply to it. Data stored in Frankfurt by a provider headquartered outside the EU is resident in the EU, but the provider's home-country law may still reach it. Sovereignty depends on who holds and controls the data, not only on where the disks are.
The CLOUD Act is a 2018 US law. Its core provision, 18 U.S.C. § 2713, requires providers of electronic communication or remote computing services to preserve or disclose data within their possession, custody or control in response to US legal process, whether that data is stored inside or outside the United States. It applies to providers subject to US jurisdiction, which includes US-headquartered cloud and SaaS companies.
Not by itself. Section 2713 turns on possession, custody or control, not on location, so data a US provider controls in an EU region can still be in scope. What reduces that exposure is who holds the data. GDPR Article 48 adds that EU law recognizes a foreign disclosure order only if it is based on an international agreement, which leaves providers caught between conflicting obligations.
nano, LLC is a US company. With nano, your logs are collected, stored and analyzed on infrastructure you operate, and nano does not hold them or have access to them, so there is no log data in nano's possession, custody or control for a request to reach. A connected install exchanges only license, usage-total and content-download traffic with nano, and an air-gapped install exchanges nothing. If you run nano in an account with a US-headquartered cloud provider, that provider's position is a separate question to assess.
They change it. By how much depends on the offering and on who ultimately controls the operating company and the data. Read each provider's own terms and assess them with your counsel. With nano you can choose an EU-headquartered provider, your own data center or an air-gapped network, so the SIEM vendor is not part of that question.
GDPR applies to organizations established in the EU, and to organizations outside the EU that offer goods or services to people in the EU or monitor their behavior there (Article 3). So a US company processing EU personal data in those ways must comply. Transfers of personal data from the EU to the US need a basis under Chapter V, such as the EU–US Data Privacy Framework for certified US companies.
As of November 2026, yes. The Commission adopted the adequacy decision on 10 July 2023, and the General Court dismissed a challenge to it in Latombe v Commission on 3 September 2025. That judgment is under appeal at the Court of Justice in Case C-703/25 P, and the Court of Justice invalidated both earlier frameworks, Safe Harbor and Privacy Shield, so many organizations plan for the possibility that it changes.
Yes. Air-gapped operation is included with every license: the install runs with zero connectivity to nano, from a signed offline image bundle, signed offline content bundles you import by hand and an offline license file that you renew by hand. AI features, if you use them, point at a model you host inside the same network.
Last reviewed 13 November 2026. Regulations and guidance change, so read the current version at the source.
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.