Archived analysis

This page is old. Persistent Systems was reviewed on 2026-04-29.

This is a historical, policy-only review. Policies, product behavior and source URLs may have changed since this analysis was published.

For current public evidence from website trackers, policy findings and proof samples, go to State of Privacy 2026.

IT Services & Software

Persistent Systems

Ready Score 78/100
Sushant Pasumarty
ANALYSIS SUPERVISED BY Sushant Pasumarty
📅 29 Apr 2026

Discuss this page with an LLM

Persistent Systems has made significant strides in aligning its global privacy framework with the DPDP Act 2023, notably by including the Right to Nominate. While its security posture is robust, the policy still relies on GDPR-style 'legitimate interests' for marketing which may not withstand the stricter consent requirements of the Indian Act. To achieve full compliance, they must decouple consent from service terms and specify escalation paths to the Data Protection Board.

How To Read This Analysis

This is an archived policy-only review of the company's public privacy policy. It is not a government certification and it is not legal advice.

For current public evidence from website trackers, policy findings and proof samples, see State of Privacy 2026.

We look for:

  • Notice and consent clarity
  • Purpose limitation
  • Data minimization
  • Retention and deletion language
  • Vendor and processor disclosures
  • Data Principal rights
  • Grievance redressal
  • Breach and security posture

Source Check

  • Source policy was reviewed for this archived analysis, but the old policy URL is not linked because public policy locations may have changed.
  • Date reviewed: 2026-04-29
  • Company: Persistent Systems
  • Readiness score: 78/100
  • Policies and product behavior may have changed since review
  • Whether the current source policy still matches this archived policy-only review
  • Whether app, web and product flows match the policy

What To Do With This

If your company has a similar data model, use this analysis as a warning map. Do not copy the score. Map your own data flow.

Ask internally:

  • Do we collect similar categories of personal data?
  • Do we share data with the same number or type of vendors?
  • Can users understand why their data is shared?
  • Can we prove deletion, retention and grievance workflows?
  • What evidence would we show if questioned?

If this analysis resembles your business model, the next step is not a better privacy-policy paragraph. It is a data map and gap analysis.

Book a DPDP readiness call

⚠️ Compliance Gaps

  • Grievance redressal mechanism lacks explicit escalation path to the Data Protection Board of India
  • Legitimate interest used as a legal basis for marketing, which may conflict with Section 7’s narrow definitions
  • Consent for data processing is often bundled with website usage terms rather than being 'unconditional' and 'itemized'
  • Data retention periods are described qualitatively ('as long as necessary') rather than providing specific timelines

✅ Strengths

  • Explicitly incorporates the 'Right to Nominate' under Section 14 — a unique DPDP requirement
  • Recognizes and uses 'Data Principal' and 'Data Fiduciary' terminology throughout the policy
  • Publishes contact details for a local Data Protection Officer (DPO) based in Pune, India
  • Adopts ISO 27701 (PIMS) and ISO 27018 standards, aligning with Section 8 security obligations

Overview

Persistent Systems is a global Tier-1 IT services provider headquartered in Pune, India. Unlike many Indian firms that still rely on the outdated IT Act 2000 framework, Persistent has proactively updated its privacy notice to include terminology specific to the Digital Personal Data Protection (DPDP) Act 2023. As a Data Fiduciary for its employees and a Data Processor for its global clients, its compliance level is critical for maintaining cross-border data flow trust.

DPDP Readiness: Section-by-Section Analysis

Persistent’s policy provides a detailed list of what data is collected (Name, Email, IP address, etc.), but it falls short of the “itemized” notice requirement.

What the policy says: “By providing personal information to us, you understand we will collect, hold, use, and disclose your personal information in accordance with this privacy policy.”

DPDP requirement: Consent must be free, specific, informed, unconditional, and unambiguous with an affirmative action.

Gap: The “notice” is not always presented in the same view as the consent request. Furthermore, the policy uses a single agreement for multiple purposes (service delivery, marketing, and recruitment), which violates the requirement for granular, purpose-specific consent.

Section 7 — Certain Legitimate Uses 🔴

Persistent claims “legitimate business interest” for marketing and promotional campaigns.

Gap: Under DPDP Section 7, “Legitimate Uses” are restricted to voluntary provision by the data principal for a specific purpose, state functions, or medical emergencies. “Legitimate Business Interest”—a staple of GDPR—is not a valid ground for processing under the DPDP Act for marketing purposes. This creates a significant regulatory risk.

Section 8 — Obligations of Data Fiduciary ✅

Persistent excels here, referencing its ISO 27701 and ISO 27018 certifications. It describes technical and organizational measures (TOMs) including encryption at rest and in motion, and periodic Data Protection Impact Assessments (DPIAs).

Strength: The policy explicitly mentions maintaining the accuracy of data, which is a core obligation under Section 8(3) of the Act.

Section 9 — Data Retention & Erasure ⚠️

The policy states: “Personal Data will not be retained for a period more than necessary to fulfil the purposes… unless a longer retention period is required by law.”

DPDP requirement: Section 9(1) requires the Data Fiduciary to erase personal data as soon as the purpose of processing is fulfilled or the Data Principal withdraws consent.

Gap: While the intent is clear, there are no defined “retention schedules” or automated deletion triggers mentioned. For a B2B service provider, the lack of a “deletion-by-default” timeline remains a compliance risk.

Section 11 & 14 — Rights of Data Principal ✅

This is Persistent’s strongest section. It explicitly lists:

  • Right to access and rectification
  • Right to withdraw consent
  • Right to Nominate: “You have the right to nominate any individual who shall, in the event of death or incapacity, exercise the rights on your behalf.”

Strength: Including the Right to Nominate demonstrates that Persistent has specifically audited its policy against the DPDP Act 2023, rather than just relying on its existing GDPR templates.

Section 12 — Right of Grievance Redressal ⚠️

The policy identifies the Data Protection Officer (DPO) in Pune, Maharashtra, with a dedicated email address (privacyofficer@persistent.com).

Gap: Section 12 of the DPDP Act requires the Data Principal to exhaust the fiduciary’s grievance process before approaching the Data Protection Board of India. Persistent’s policy does not name the Board or provide the specific escalation timeline (e.g., acknowledging that the Board is the ultimate statutory authority for disputes).

Section 16 — Cross-Border Data Transfer ✅

Persistent acknowledges it may transfer data outside the country of residence. Since the Indian government has not yet notified a “negative list” of restricted countries, Persistent’s current reliance on “reasonable security and contractual controls” is sufficient for the moment.

Risk Assessment

CategoryRisk LevelDPDP SectionAnalysis
Consent BasisHighSection 6Bundled consent and “implied” agreement from website usage are non-compliant.
Legal BasisHighSection 7Relying on “Legitimate Interest” for marketing is a major DPDP gap.
Principal RightsLowSection 11/14Excellent; one of the few firms to include Nomination rights.
GrievanceMediumSection 12Needs to mention the Data Protection Board as the final arbiter.
SecurityLowSection 8Best-in-class; ISO 27701 certification provides a strong defense.

Fix these compliance gaps today.

Book 1:1 Consultation >
Book clarity call