nano never processes your logs.
A SaaS SIEM stores and analyzes your logs for you. nano is software you run, so the personal data in your logs is processed by you, in your environment, and never reaches nano.
From 13 May 2027, the Digital Personal Data Protection Rules ask Data Fiduciaries to log and review access to personal data, keep those logs for a year and report breaches within 72 hours. Security logs are personal data too. Running nano yourself keeps them in your environment, and nano never processes them.
The DPDP Rules commence in stages. The rules on security safeguards, logs and breach reporting are in the stage that begins 18 months after publication.
The Digital Personal Data Protection Rules, 2025 are published as G.S.R. 846(E).
egazette.gov.in · DPDP Rules 2025 ↗Rule 4, on consent managers, commences.
egazette.gov.in · DPDP Rules 2025 ↗Rules 3, 5 to 16, 22 and 23 commence, 18 months after publication. That includes the security safeguards, breach reporting and one-year log retention.
egazette.gov.in · DPDP Rules 2025 ↗The Rules' own words, what they mean in practice, and where nano fits.
These rules bind Data Fiduciaries, including processing done on their behalf by Data Processors.
| Ref | What the Rules say | In plain English | How nano helps |
|---|---|---|---|
| Rule 6(1)(c) | Reasonable security safeguards include "visibility on the accessing of such personal data, through appropriate logs, monitoring and review". egazette.gov.in · DPDP Rules 2025 | Log who accesses personal data, watch those logs, and review them. | Collects access logs from the systems that hold personal data, searches them in one place and raises alerts on the access patterns you write detections for. |
| Rule 6(1)(e) | The Data Fiduciary must "retain such logs and personal data for a period of one year, unless compliance with any law for the time being in force requires otherwise". egazette.gov.in · DPDP Rules 2025 | Keep those access logs for a year, unless another law says differently. | Event retention defaults to 365 days on storage you own. Set what your policy needs, and tier older data to your own object storage. |
| Rule 8(3) | Retain "personal data, associated traffic data and other logs of the processing for a minimum period of one year". egazette.gov.in · DPDP Rules 2025 | A one-year floor on logs of the processing itself. | Retention is set on your own store, not by a vendor's plan, so a year of logs costs you storage, not a bigger license. |
| Rule 7(2) | On a personal data breach, inform the Board "without delay", and report to it within "seventy-two hours of becoming aware of the breach". egazette.gov.in · DPDP Rules 2025 | Two steps: tell the Data Protection Board straight away, then report within 72 hours. | Detections raise alerts as events arrive, and cases hold the evidence and timeline you report from. Reporting to the Board stays with you. |
| Rule 13(4) | The government may require Significant Data Fiduciaries to keep specified personal data "not transferred outside the territory of India". egazette.gov.in · DPDP Rules 2025 | For the largest fiduciaries, some data may have to stay in India. | If you run nano in an Indian cloud region or your own Indian data center, the logs it holds are already in India. |
The clock starts when you become aware of the breach. Knowing what happened, to whose data, depends on the logs you already keep.
A personal data breach, in your systems or a Data Processor's.
Without delay, to the Data Protection Board.
Within seventy-two hours of becoming aware of the breach.
Usernames, email addresses, IP addresses and device IDs fill security logs. Where those logs are processed, and by whom, is part of your DPDP picture.
Your account in an Indian cloud region, your data center, or an air-gapped network
Never receives your logs.
A SaaS SIEM stores and analyzes your logs for you. nano is software you run, so the personal data in your logs is processed by you, in your environment, and never reaches nano.
Event retention defaults to 365 days. Keep what your policy needs, and tier older events to your own object storage, where they stay searchable. Storage and retention
AI is off by default; when on, it calls your own model endpoint, never via nano (AI settings). Air-gapped installs send nano nothing (air-gapped deployment).
The Digital Personal Data Protection Rules, 2025 put the Digital Personal Data Protection Act, 2023 (the DPDP Act) into operation. They were notified on 13 November 2025 as G.S.R. 846(E), and set out, among other things, the security safeguards a Data Fiduciary must take, how personal data breaches are reported, and how long logs are kept.
In stages. Rule 4, on consent managers, commenced on 13 November 2026. Rules 3, 5 to 16, 22 and 23, which include the security safeguards, breach reporting and log retention, commence on 13 May 2027, 18 months after publication.
Rule 6(1)(c) makes "visibility on the accessing of such personal data, through appropriate logs, monitoring and review" part of reasonable security safeguards. In practice, that means logging access to systems that hold personal data, monitoring those logs, and reviewing them.
One year. Rule 6(1)(e) requires the Data Fiduciary to retain such logs and personal data for a period of one year unless another law requires otherwise, and Rule 8(3) sets a minimum of one year for personal data, associated traffic data and other logs of the processing. Both apply from 13 May 2027. Other rules can set their own periods, such as CERT-In's rolling 180 days.
Under Rule 7(2), the Data Fiduciary informs the Data Protection Board without delay, and then reports within seventy-two hours of becoming aware of the breach. This applies from 13 May 2027.
Often, yes. Security logs routinely contain usernames, email addresses, IP addresses and device identifiers that relate to identifiable people. That means the logs you keep to meet Rule 6 are themselves personal data to protect, and wherever they are processed is part of your DPDP picture.
No. nano is software you run in your own environment. Your logs are collected, stored and analyzed there, and nano never receives them, so nano does not process that personal data on your behalf. A connected install sends nano a daily license check-in and one usage number per day; air-gapped installs send nothing. AI is off by default, and when on it calls the model endpoint you configure, not nano.
Not as a general rule. The Act lets the government restrict transfers to countries it notifies, and Rule 13(4) lets it require Significant Data Fiduciaries to keep specified personal data in India. Sector rules can be stricter, such as CERT-In's Directions on logs. Running nano in your own Indian environment keeps the logs it holds in India either way.
No. No product makes a Data Fiduciary compliant, and nano, LLC holds no certification or approval. nano helps with the logging, monitoring, retention and incident evidence the Rules describe.
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.