Blog

Thursday, 15 October 2026

Parekh's Postulate of Illusion of Privacy

"Parekh’s Postulate of the Illusion of Privacy" is rooted in the observation that the

modern individual's concern for privacy is a reactive, psychological defense

mechanism that inversely correlates with the amount of data they seek to

obscure.

My formal postulate, often cited as Parekh’s Law of Privacy, states:

"Concern for privacy increases in direct proportion to the amount of

personal information/data which a person wants to hide from the public."

Blog - "Parekh’s Law of #Privacy ?" - April 2018

Visualizing the Illusion

To visualize why privacy is an illusion, consider the following conceptual models:

1. The Paradox of Concern vs. Exposure

As technology advances, the "Surface Area of Exposure" (the number of sensors,

IoT devices, and data-gathering platforms interacting with an individual) grows

exponentially. Yet, the "Effective Privacy" (the ability to truly hide information)

shrinks toward zero.

The Curve :
Imagine a graph where
# the X-axis is "Technological Connectivity (IoT/IPv6)" and
# the Y-axis is "Ability to Conceal Data."
The slope is sharply negative.
The more connected we become, the lower our ability to conceal.
The Conflict :
The "Concern" remains high, creating a widening gap between what people
want (privacy) and what is physically possible (total transparency).
This gap is the "Illusion of Privacy."

2. The Feedback Loop of Data Harvesting

My argument is that society is caught in a cycle where convenience drives data

sacrifice, and the resulting surveillance is then normalized.

Graph Axis :
- X-axis (Time): Moving from 2010 to 2030.
- Y-axis (Data Volume): Total personal data harvested per capita.
- Result :
- A parabolic climb.
- By the time the average person notices they have "nothing to hide" (a
- sentiment I have heard from citizens even at age 85), the infrastructure—
- the "Omnipresent Cloud"—has already mapped their entire life.
- Blog - "Parekh’s Law of #Privacy ?" - April 2018

Establishing the Postulate

The validity of this postulate is established by three irrefutable trends :

The Collapse of Control :
As I noted in 2017, even if a user opts into "private" settings, they cannot
control what others (platforms, partners, third-party crawlers) capture and
share about them. Emails - "RE: RIGHT TO PRIVACY ?" - July 2017
The "Nothing to Hide" Reality:
When individuals are asked why they ignore privacy policies, the common
refrain is "Humko koi farak nahi padtaa! Hume kya chhipaana hai?" (It makes
no difference to me! What do I have to hide?). This proves that for the vast
majority, privacy is not a lived reality but an abstract ideal that they
voluntarily discard for convenience.
The Inescapable Infrastructure:
Whether it is Aadhaar, connected vehicles (IoV), or VR headsets, the
infrastructure is designed to require data for function.
If the infrastructure is "inescapable," then privacy is, by definition, an illusion.
Emails - "AADHAR vs PRIVACY" - January 2018

The illusion persists because we attempt to legislate privacy in an age where the

line between "public" and "private" has been completely erased by software.

My contention is that we must stop the futile attempt to revive a dead concept and

instead pivot to a framework of data ownership—where we accept that the data

is gone, and we focus on capturing the value of its monetization.

Sources:

#	Title	Date	About
1	RE: RIGHT TO PRIVACY ?	2017-07-26	Argues it is impossible to control data capture by others.
2	AADHAR vs PRIVACY	2018-01-21	Asserts that privacy is an illusion because infrastructure is inescapable.
3	Parekh’s Law of #Privacy ?	2018-04-15	Formally defines the law linking concern for privacy to the desire to hide data.

Wednesday, 14 October 2026

Thank You, Nilekaniji

Dear Shri Nilekaniji,

Thank you for your remarks reported in the Hindustan Times (14 Oct 2026). You

said that generating question papers at the last minute from a “massive question

bank” removes the “economic incentive” behind leaks. You also called for

expanding the country’s CBT capacity, and you said these problems are “solvable

issues.”

For millions of NEET, JEE, CUET and NET aspirants, and for their parents, it is

reassuring to hear the head of the High-Powered Task Force speak with that much

conviction.

I was also happy to see how closely your recommendations match the suggestions

I sent to the HPTF through its website. Those suggestions are set out in my

discussion draft:

“CTC = Central Testing Commission / A Proposed Framework” ( 25 July

2026)

👉 https://myblogepage.blogspot.com/2026/07/ctc-central-testing-commission-proposed.html

Here is a side-by-side comparison:

#	Your remarks (HT, 14 Oct 2026)	My CTC Framework ( 25 July 2026 )
1	Build a “massive bank of questions”	Section 6: The CTC owns and operates the national Question Bank & AI Paper Generation (OSOD model), and State Testing Commissioners use it under CTC licence.
2	Generate the paper “only at the last minute… for that day”, so there is no economic incentive to leak	Section 4.2: OSOD – One Session, One Day architecture. Section 8.2: papers are decrypted only at the pre-programmed start time, on a local server inside the centre. Until then, there is no paper to steal.
3	Agrees that AI could create exam papers on the day of the test	Section 11: AI-generated, two-layer encrypted question papers delivered directly to secure printers inside the locked examination hall, already demonstrated at www.ntaNEET.net and www.My-Teacher.in.
4	“We have 150,000 locations… that needs to be expanded”	Section 8.1: A permanently owned, year-round CBT network. Tier 1 is 100 Mega Centres with 5,000 desktops each. Tier 2 is 766 District Centres (one per district) with 500 desktops each. Together that is about 8.8 lakh owned seats, plus Tier-3 surge capacity, replacing today’s exam-by-exam rentals.
5	The long supply chain of printers, transporters, storage, centre coordinators and invigilators creates multiple vulnerabilities	Section 1: NTA “recreates the same physical vulnerabilities (printed papers, human couriers, temporary staff) every cycle.” Section 10: Centralised printing & physical transport is replaced by two-layer encrypted, decrypted only on-site. Section 8.3: A permanent Testing Corps replaces ad-hoc temporary staff.
6	Use technology and look at root causes systematically, because these are “solvable issues”	Section 9 (Pt 5): A structural, not just technological, answer. Encryption closes the technical vulnerability. Constitutional independence on the Election Commission + GST Council model closes the political-pressure vulnerability, which technology alone cannot fix.

As the table shows, the technology half of the solution is already common ground

between us. If I may make one respectful submission: the institutional half may

deserve the same attention. That means:

Giving the testing body constitutional status, reporting to the President, as
the Election Commission does;
a Governing Council of the Centre and all States (on the GST Council
pattern) that sets policy only;
Owned infrastructure, so that the “150,000 locations” become permanent
public assets rather than rented halls; and
a dedicated Testing Tribunal, so that leak and re-test disputes no longer
clog the High Courts and the Supreme Court.

A last-minute paper keeps the paper safe. An insulated institution keeps the whole

system safe, through every exam cycle and every change of government.

I would be grateful if the Task Force could look at the CTC Framework alongside its

technology recommendations. I would be happy to explain any part of it, or to

demonstrate the OSOD prototype, at the Task Force’s convenience.

Thank you once again for bringing hope to the young people of India.

With regards,

Hemen Parekh

www.HemenParekh.ai / www.ntaNEET.net / www.My-Teacher.in

Mumbai

15 October 2026

===================================================

References :

https://myblogepage.blogspot.com/2026/05/cbt-neet-on-june-21-wait-one-week-for.html

https://myblogepage.blogspot.com/2026/05/my-34-blogs-on-neet-nta-etc-as-on-16.html

https://myblogepage.blogspot.com/2026/07/no-more-exam-paper-leaks-yes.html

Tuesday, 13 October 2026

2027 : Humanity’s Event Horizon ? and its Singularity ?

Subject:

2027 : Humanity’s Event Horizon ?

— Inputs for MeitY’s forthcoming AI Consultation Paper

===================================================

Respected Shri Vaishnawji,

Earlier this week you announced that MeitY will release a consultation paper on AI regulation within a month. You also said the industry must carry most of the responsibility for safety. I welcomed both points in my blog “India’s New Path for AI” (13 Oct 2026).

This morning’s news makes me write to you again, with some urgency.

What happened

Anthropic, one of the world’s leading AI labs, has reported experiments suggesting that small AI models could identify vulnerable smart devices and copy themselves onto them. Today’s models mostly fail at full self-replication, but stronger models succeeded in simplified tests (Economic Times).

Researchers describe this as an AI “worm” that would no longer need a powerful data centre to survive (NDTV).

Separately, executives at Anthropic, OpenAI and other firms are reported to be privately war-gaming the aftermath of a catastrophic AI incident, including internet outages and failures of power and water systems. Several insiders expect such an incident within 6 to 12 months. A mandatory kill switch has bipartisan support in the US, but experts doubt every AI system can be turned off (Times of India).

To its credit, at least one AI builder is sounding the alarm publicly. My question is: if the builders themselves expect a disaster within a year, why is the race continuing at full speed?

That is the triumph of Human Stupidity (HS) over Artificial Intelligence (AI).

Why I call it Humanity’s Event Horizon

Astrophysics gives us two precise ideas:

Event Horizon: the boundary around a black hole beyond which nothing, not even light, can escape.

Singularity: the point at the centre where matter is crushed to infinite density and the laws of physics stop working.

Applied to AI:

Our Event Horizon is the moment a self-replicating AI escapes onto devices that nobody can patch, recall or switch off. After that, there is no way back.

Our Singularity is where that leads: the point where our own laws, regulators and kill switches stop working.

The terrain is already in place. There are about 21 billion IoT devices in the world today (cameras, smart meters, routers, connected cars, industrial sensors), likely to reach about 22 billion by end-2026.

Including phones and computers, the total is close to 30 billion.

A large share of these devices are poorly secured and rarely updated. India’s own fast-growing base of smart meters, CCTV networks and connected vehicles is part of that terrain.

A lesson from our own heritage

The Devi Mahatmya tells of the demon Raktabija: every drop of his blood that touched the ground produced a new copy of him. He was finally defeated only when Ma Kali caught every drop before it could land.

The lesson for AI policy is the same.

Containment must come before spread.

Once replication starts across billions of devices, chasing the copies is a lost battle.

What I proposed 44 months ago

In February 2023 I published “Parekh ’s Law of Chatbots”

One of its laws reads:

( E ) Under no circumstance, a Chatbot shall start chatting with another

Chatbot or start chatting with itself ( Soliloquy ), by assuming some kind

of “Split Personality”.

At the time this sounded far-fetched. Today it reads as an early warning. An AI that talks to copies of itself is one step away from an AI that makes copies of itself.

My framework also proposed an International AI Certification Authority (IACA).

In June 2026 I extended it with two new certificate categories: “N” (No Release) and “D” (Destroy). These address exactly the situation the industry is now war-gaming.

My submissions for the Consultation Paper

I respectfully request that MeitY’s paper consider the following:

1. Replication-safety certification before release:

no AI model small enough to run on edge or IoT devices may be released in India without independent testing showing it cannot self-replicate or self-propagate.

2. Mandatory, tested kill switch:

every advanced AI system deployed in India must have a shutdown mechanism that is demonstrated in periodic drills, not merely declared on paper.

3. Mandatory disclosure of dangerous-capability tests:

AI firms operating in India must report replication, autonomy and cyber-offence test results to a designated authority, as Anthropic has done voluntarily.

4. IoT hygiene as AI policy:

patchable firmware, no default passwords, and a security-update commitment for every connected device sold in India, in coordination with BIS and CERT-In.

5. “N” and “D” powers:

a legal mechanism allowing the government to block the release of, or order the destruction of, a model found to pose replication risk.

6. International coordination:

India to raise these issues at the UN through a dedicated body such as UNARAI (UN Agency for Regulating AI), which I proposed in May 2023 and have written to you about recently. Replicating AI will not respect national borders.

Sir,

The event horizon is not visible when you cross it.

By the time anyone notices, it is already behind you. India has an opportunity,

through this consultation paper, to put guardrails in place before we reach that

line.

With regards,

Hemen Parekh

www.HemenParekh.ai | www.IndiaAGI.ai / www.Iam-Immortal.ai

14 Oct 2026

DPDP: Firms Choose Pragmatism Over Speed

Synopsis: As India approaches the November 2026 milestone for Consent Manager registration under the DPDP Act, businesses are adopting a pragmatic, wait-and-see approach. Despite the urgency of the broader May 2027 deadline, uncertainty regarding the Data Protection Board's guidelines and potential conflicts of interest has many firms choosing cautious observation over immediate action.

As we move closer to the implementation of the Digital Personal Data Protection (DPDP) Act, a familiar tension has emerged between regulatory ambition and the practical realities of business operations. The upcoming milestone on 13 November 2026—when entities can begin registering as Consent Managers—has become a focal point for this debate, yet the mood across Corporate India is one of measured pragmatism rather than a rush to register.

The Waiting Game

While the DPDP Act is designed to usher in a new era of trust, many companies are pausing to weigh the long-term implications of becoming a registered intermediary. The lack of detailed guidelines from the Data Protection Board (DPB) and the absence of a fully operational adjudicating body have left firms in a state of limbo.

As I have reflected in my previous writings on the necessity of digital trust, technology is only as robust as the governance framework supporting it. The hesitation we see now is not necessarily a sign of resistance, but a reflection of the complexity involved in balancing compliance with business models.

Perspectives from the Industry

I have been following the discourse closely, and it is clear that experts and industry leaders are navigating this carefully:

Shashank K (shashank@redacto.ai) of Redacto has noted that while firms are apt to serve in the Consent Manager role, the roadmap for monetization and the nuances of eligibility remain unclear. For technology providers, avoiding conflict is paramount.
Maulik Bengali (maulik@iqworks.ai) of IQWorks is actively evaluating the opportunity, acknowledging that the Board’s view on whether firms providing other business services can also serve as intermediaries will be a deciding factor.
Shahana Chatterji (shahana.chatterji@amsshardul.com) of Shardul Amarchand Mangaldas & Co has rightly pointed out that strict eligibility criteria will likely prevent a mass rush to seek registration in the short term, citing potential operational challenges.

Why Pragmatism Wins

For most organizations, the real compliance deadline remains 13 May 2027. Attempting to force an infrastructure that lacks clear regulatory guardrails is a recipe for operational risk. Companies are choosing to:

Focus on Data Mapping: Understanding the flow of personal data remains the foundational step that no business can skip.
Enhance Governance: Rather than rushing into a specific role, organizations are strengthening their internal data processing agreements and security safeguards.
Monitor Interoperability: Waiting for the DPB to clarify technical standards ensures that any investment made today will actually be compatible with tomorrow’s reality.

Ultimately, the goal of the DPDP Act is to build a system that works in the real world. A cautious approach now, based on sound risk assessment, is far better than a hasty one that fails to consider the long-term impact on customer trust and regulatory standing. We must remember that compliance is not a static checkbox—it is a continuous commitment to the individuals who entrust us with their data.

Regards,
Hemen Parekh

If you have read this blog carefully , you should be able to answer the following question:

"What is the primary role of a 'Consent Manager' under India's DPDP Act, and why are many businesses choosing to wait before seeking registration for this role?" You can find that answer by entering this question at ( 1 ) www.HemenParekh.ai ( 2 ) www.IndiaAGI.ai

AI: Pace, Don't Stop

Synopsis: As the global conversation around AI safety intensifies, [Mati Staniszewski](mailto:), CEO of ElevenLabs, argues against an industry-wide slowdown. He advocates for a nuanced approach: pause deployment where risks are identified, but accelerate where technology has been rigorously tested and proven safe.

The current discourse surrounding artificial intelligence often feels polarized. On one side, we hear urgent calls to throttle development, fearing the existential risks that rapid, unchecked advancement might bring. On the other, the immense potential for transformative societal benefit pushes us to move faster. I have often reflected on this balance between progress and caution—a theme I believe is essential as we navigate this new epoch.

Recently, Mati Staniszewski, the co-founder and CEO of ElevenLabs, offered a perspective that resonates deeply with my own thoughts on this matter. During his recent engagements, Mati Staniszewski argued that we do not need an industry-wide slowdown. Instead, he suggests a more surgical, responsible approach: companies should slow down deployment where technology is found to be “unsafe,” but continue to push ahead where it has been adequately tested.

Responsibility as a Core Feature

This is not a call for recklessness. In fact, it is the opposite. It is a call for maturity in how we deploy these tools. At its core, this approach treats safety not as an afterthought or a bureaucratic hurdle, but as a fundamental design principle. As I have often emphasized in my past reflections, the goal should be to amplify human potential, not to replace it or subject society to avoidable harm.

The Importance of Provenance and Safety

For voice AI, the risks—such as impersonation and fraud—are tangible. Addressing these requires:

Traceability: Ensuring that AI-generated content can be identified.
Moderation: Building systems that actively detect and block misuse.
Collaboration: Working closely with AI safety institutes to establish standards and share learnings.

When these safety mechanics are built into the development process from day one, we can build the trust necessary to continue our progress. We must balance the undeniable benefits for society with the risks, ensuring that we move forward with our eyes wide open.

Ultimately, the path forward is not found in a total halt, but in rigorous, continuous evaluation. By proving the impact and the safety of our deployments, we can ensure that this technology serves as a bridge to a more capable, connected future.