Practice · Service · India, EU and the UAE

DPDP compliance for startups, with the GDPR and UAE PDPL legs run as one programme.

A DPDP compliance consultant takes a startup through the DPDP Rules 2025 dates: the consent-manager rule on 13 November 2026 and every operating obligation on 13 May 2027. Infinilex runs that programme with its counsel qualified in India, with the GDPR and UAE PDPL legs alongside. It publishes no fee; scope is fixed on the discovery call.

Advised on $100M+ of founder fundraising and $200M+ in deal value, with 10+ IPO and pre-IPO mandates. Figures are internal, as of 2026.

A DPDP compliance consultant in India builds the programme the Digital Personal Data Protection Act 2023 and the DPDP Rules 2025 require of a Data Fiduciary: the data map, the itemised consent notice, the security safeguards, the breach playbook, children’s consent, the rights process and the transfer position. Infinilex runs that programme for startups and SaaS exporters against the dates that matter, 13 November 2026 and 13 May 2027, and carries it into the GDPR and the UAE PDPL where your users sit there. On cost, Infinilex publishes no fee and fixes scope on the discovery call. A DPDP consultant engagement with Infinilex starts with the gap list against the two commencement dates set by Rule 1 of the Rules as published in the Gazette of India on 13 November 2025: 13 November 2026 for Rule 4, the consent-manager rule, and 13 May 2027 for Rules 3, 5 to 16, 22 and 23, every other operating duty. The dated, item-by-item version of that gap list, with the downloadable file, is the DPDP compliance checklist for startups.

DPDP appears elsewhere on this site inside the fractional general counsel retainer scope; this page is the programme itself. Infinilex’s own privacy policy is a DPDP-era notice.

Three dates, three phases

The DPDP Rules 2025 were notified by MeitY as G.S.R. 846(E) on 13 November 2025 under section 40 of the DPDP Act 2023 (Act 22 of 2023); Rule 1 phases them in. Section by section and rule by rule, the dated clause list is on the DPDP checklist, under its question on when the Act comes into force for startups.

Schedule A: DPDP Rules 2025 commencement phases, as at 27 October 2026
DateRules in forceWhat it means for a startupProgramme work
13 November 2025Rules 1, 2 and 17 to 21: the Data Protection BoardThe Board is a digital office (Rule 20); no operating duty on a Data Fiduciary yetData map, applicability, gap assessment
13 November 2026Rule 4: Consent Manager registrationAn Indian company with net worth of at least Rs 2 crore may register as a Consent ManagerConsent architecture, notice, processor contracts
13 May 2027Rules 3, 5 to 16, 22 and 23: notice, safeguards, breach intimation, retention, children, Significant Data Fiduciary duties, rights, transfers, appealsEvery operating obligation appliesRollout, breach drill, retainer upkeep

Dates are computed from Rule 1. The Schedule to the Act caps penalties at Rs 250 crore for failing to take reasonable security safeguards (section 8(5)) and Rs 200 crore for failing to notify a breach (section 8(6)) or under the children’s-data duties (section 9): statutory ceilings.

What DPDP compliance costs in India: what sets the scope

Infinilex does not publish fees. Scope is fixed on the discovery call, and the project or retainer choice is on how engagements work. Four things move the scope: the number of products and data flows, the processors and SDKs in the chain, whether anyone under eighteen uses the product, and whether users in the EU or the UAE bring the GDPR or the PDPL in alongside the DPDP Act. A company that may be notified as a Significant Data Fiduciary adds the section 10 duties on top.

“With their presence in both the US and India, Infinilex provides Indian founders with US-incorporated entities seamless guidance through the complex maze of compliance requirements.”

Gaurav Luhariwala · Founder & CEO, TejasAI

If your startup has no legal team yet

Most DPDP guidance assumes a legal team. A seed-stage startup does not need one to start: the founders can list what the product collects, where it is stored and which vendors touch it, then read sections 4 to 10 of the Act and Rules 3, 6, 7, 8 and 14 against that list. What needs drafting (the notice, the processor clauses, the breach playbook) and what needs judgment (applicability under sections 3 and 17, the transfer position, whether a vendor is a Data Processor or a Data Fiduciary in its own right) is where the consultancy comes in, as a fixed-scope stage. Section 17(3) also lets the Central Government exempt notified classes of Data Fiduciaries, startups included, from sections 5, 8(3), 8(7), 10 and 11; no such notification is assumed here, so build for the full Act.

What the DPDP compliance programme covers

  • The data map and the applicability call. Section 3(b) reaches processing outside India connected with offering goods or services to people in India. Section 17(1)(d) switches most of the Act off where data of people outside India is processed in India under a foreign contract, though sections 8(1) and 8(5) still apply. Section 17(3) lets the Central Government exempt notified classes, including startups.
  • The consent notice, rebuilt to Rule 3. Understandable on its own, in plain language, with an itemised description of the personal data and the purposes, and links to withdraw consent as easily as it was given, exercise rights and complain to the Board.
  • Security safeguards and processor contracts. Rule 6 sets the minimum: encryption, obfuscation, masking or virtual tokens; access controls; logs, monitoring and review; backups; one-year log retention; and contractual safeguards with every Data Processor, engaged only under a valid contract (section 8(2)).
  • The breach playbook. Rule 7 requires intimation of each affected Data Principal and of the Board without delay, with detailed facts, causes, mitigation and findings to the Board within seventy-two hours of becoming aware unless it allows longer.
  • Retention, erasure and children’s data. Section 8(7) requires erasure on withdrawal of consent or once the purpose is served, unless another law requires retention; the Third Schedule deems the purpose spent three years after last engagement for the largest e-commerce, social media and gaming intermediaries (Rule 8). A child is anyone under eighteen; Rule 10 requires verifiable parental consent.
  • Rights, grievance and Significant Data Fiduciary readiness. Section 8(9) and Rule 9 require a published contact for data questions; Rule 14 a rights route answered within ninety days. A company notified under section 10 must appoint a Data Protection Officer based in India and an independent data auditor, and run an impact assessment and audit every twelve months (Rule 13).
  • The cross-border transfer position. Rule 15 allows transfer outside India subject to requirements the Central Government may specify, with no adequacy list and no standard-clause mechanism; section 16 lets it restrict transfers to notified countries.

DPDP vs GDPR vs UAE PDPL: the four regimes compared

GDPR compliance does not satisfy the DPDP Act. India adds an itemised stand-alone notice, parental consent under eighteen, breach detail to the Board within seventy-two hours and a Data Protection Officer for a notified Significant Data Fiduciary. It also has no legitimate-interest ground: section 7 lists the legitimate uses and GDPR Article 6(1)(f) has no counterpart. The UAE PDPL is separate again.

An Indian startup with users in the EU or the UAE meets three or four regimes at once. The GDPR column states the obligations generally; the specifics are confirmed with EU local counsel on your facts.

Schedule B: obligations compared across four regimes, as at 25 September 2026
ObligationDPDP (India)GDPR (EU)UAE PDPL (federal)DIFC and ADGM
Instrument and reachDPDP Act 2023 and Rules 2025 (section 3)The EU GDPR, where it applies to youFederal Decree-Law No. 45 of 2021, in force 2 January 2022; free zones with their own data law carved out (Art. 2)DIFC Law No. 5 of 2020 (Art. 6(3)); ADGM Data Protection Regulations 2021 (s.3(1))
Consent and noticeItemised stand-alone notice (Rule 3); verifiable parental consent under eighteen (Rule 10); Consent Managers from 13 November 2026Lawful basis and consent for the personal data you collectNo processing without the data owner’s consent, save stated exceptionsDIFC controllers register their processing with the Commissioner (Art. 14(7)); ADGM controllers notify the Commissioner and pay the Data Protection Fee before or as soon as practicable after processing starts (s.24)
Breach notificationUsers and the Board without delay; detail to the Board within 72 hours (Rule 7)A breach-notification process that exists before there is a breachTo the Data Office immediately on becoming aware, per the Executive Regulations (Art. 9)DIFC: as soon as practicable (Art. 41); ADGM: where feasible within 72 hours (s.32(1))
DPO and impact assessmentOnly for a notified Significant Data Fiduciary: DPO based in India, annual DPIA and audit (section 10, Rule 13)Confirmed with EU local counsel on your factsDPO for high-risk, sensitive or large-volume processing, inside or outside the UAE (Art. 10); DPIA for high-risk processing (Art. 21)DIFC: for High Risk Processing (Arts. 16, 20); ADGM: s.35(1) and s.34
Cross-border transferSubject to requirements the Central Government may specify (Rule 15); no adequacy list or standard clausesCross-border transfer of user data handled lawfully between your entitiesTo Data Office-approved countries (Art. 22) or under a binding contract (Art. 23)DIFC: adequacy (Art. 26) or standard clauses (Art. 27); ADGM: adequacy decisions (s.41(1))

Sources: u.ae and uaelegislation.gov.ae for the PDPL; the DIFC law and the ADGM Regulations. DIFC fines run per Schedule 2 item (USD 50,000 for no DPO) plus a general fine (Art. 62); ADGM fines are capped at USD 28 million (s.55(1)). Mainland and commercial free-zone companies, DMCC and IFZA under DIEZ included, sit under the PDPL.

Where DPDP sits in a processing chain: a B2B tool, an app SDK and an LLM call

Developer questions about the Act come down to one sorting exercise: who determines the purpose and means of the processing (section 2(i)), and who processes on that party’s behalf (section 2(k)). The intermediary in these questions is an agent or a reseller in the ordinary sense, not the IT Act term. The rows below follow the chain.

Schedule C: roles in a processing chain under the DPDP Act, as at 6 October 2026
Party in the chainDPDP roleWhat followsSource
The insurer, bank or enterprise customer whose purposes drive the processingData FiduciaryNotice, consent or a section 7 legitimate use, safeguards, breach intimation, erasure; responsible for every processor it usesSections 2(i), 5, 6, 7, 8(1)
Your tool, acting on that customer’s instructionsData ProcessorA valid contract with the fiduciary carrying a safeguards clause; erase what you were given when told toSections 2(k), 8(2), 8(7)(b); Rule 6(1)(f)
Your tool, using the data for its own purposes (model training, cross-customer analytics)Data Fiduciary for that processingYour own notice and consent, and full section 8 responsibility for itSections 2(i), 5, 6, 8
The LLM API or cloud provider your tool callsData ProcessorContract chain back to the fiduciary; one-year logs; a Rule 15 transfer if hosted outside India; erasure cascades to itSections 8(1), 8(5), 8(7)(b); Rules 6(1)(e), 8(3), 15
An analytics or crash-reporting SDK in a React Native or native appData Processor if it works only for you; a Data Fiduciary in its own right if it sets its own purposesGate it behind the Rule 3 notice and the section 6 consent; verifiable parental consent where users may be under eighteenSections 2(i), 2(k), 6, 9; Rules 3, 10
A registered Consent ManagerThe platform through which a Data Principal may give, manage, review or withdraw consent, accountable to her and registered with the BoardAn optional channel for consent from 13 November 2026Sections 2(g), 6(7) to 6(9); Rule 4

The Act has no separate category of sensitive personal data: personal data is any data about an identifiable individual (section 2(t)), and sensitivity enters as a section 10(1) factor for notifying a Significant Data Fiduciary. Sector rules for insurers, lenders or health providers sit on top of the Act and are checked separately on the discovery call.

How a DPDP compliance engagement is staged

Fixed-scope stages, mapped on a free discovery call. Stage one is the data map and gap assessment, which stands on its own. Stage two is the build: notice and consent flow, control list, processor contracts, breach playbook, retention schedule, rights process and transfer memo, with the GDPR and UAE legs in the same pass. Stage three is the rollout ahead of 13 May 2027, with the consent-manager decision taken before 13 November 2026; the retainer then keeps it current. The project or retainer choice is on how engagements work.

Who signs what on DPDP compliance work

No statute names a signatory for a consent notice, a processor contract, a breach playbook or an impact assessment, so this is drafting and programme work. Infinilex counsel qualified in India draft and run the DPDP leg; Infinilex counsel qualified in the UAE draft and run the PDPL, DIFC and ADGM legs. Acts a statute puts on the company stay there: the Data Fiduciary gives the notice (section 5), intimates the Board (Rule 7) and appoints its Data Protection Officer and independent data auditor once notified (section 10). For the GDPR leg Infinilex scopes the work, builds the fact record and briefs the EU local counsel who advise on it; they are brought into the engagement explicitly and named to you before they act.

Frequently asked questions

Does GDPR compliance for an Indian SaaS company already satisfy the DPDP Act?

Not on its own. A GDPR programme gives you lawful basis and consent, a breach-notification process and a lawful transfer position, all reused. The DPDP Act and Rules 2025 add India-specific items: an itemised consent notice that stands on its own (Rule 3), verifiable parental consent under eighteen (Rule 10), detailed breach information to the Data Protection Board within seventy-two hours (Rule 7), a Data Protection Officer based in India for a notified Significant Data Fiduciary, registered Consent Managers, and a transfer rule with no adequacy list or standard clauses. Two differences cut the other way, so GDPR compliance is not enough for the DPDP Act on its own. The Act has no legitimate-interest ground: processing rests on consent under section 6 or on one of the legitimate uses listed in section 7, which cover data the person volunteered for a purpose, State functions and benefits, disclosures the law requires to the State, court orders, medical emergencies, epidemics, disasters and employment; GDPR Article 6(1)(f) has no counterpart, so marketing or analytics run on legitimate interests in the EU needs consent in India. And breach intimation runs to every affected Data Principal and to the Board whatever the level of risk (section 8(6), Rule 7), where GDPR Article 33 notifies the supervisory authority unless the breach is unlikely to result in a risk and Article 34 reaches data subjects only where the risk is high.

What must a startup do before 13 May 2027 under the DPDP Rules?

Rules 3, 5 to 16, 22 and 23 come into force on 13 May 2027, eighteen months after publication on 13 November 2025. By then a Data Fiduciary needs a plain-language consent notice with an itemised description of the data and purposes, the Rule 6 safeguards (encryption or masking, access controls, one-year logs, backups, processor contracts), a breach playbook that reaches users and the Board without delay, a published contact for data questions, a rights process answered within ninety days, and an erasure routine. The consent-manager rule starts on 13 November 2026.

Does the DPDP Act apply to an Indian SaaS company whose users are all outside India?

Only in part. Section 17(1)(d) switches off most of Chapters II and III and section 16 where personal data of people not in India is processed in India under a contract with a person outside India, the standard offshore SaaS arrangement. Sections 8(1) and 8(5), responsibility for compliance and reasonable security safeguards, still apply. Once the product is offered to users in India, the section 17(1)(d) carve-out no longer covers that data and the full Act applies under section 3, while the laws where your foreign users sit govern theirs.

Who can help my startup comply with the DPDP Act before November 2026 and May 2027, and what does it cost?

A DPDP compliance consultant (or DPDP Act consultant) runs the programme end to end. A startup without a legal team does not need one to begin. Infinilex does this work: the data map and the applicability call under sections 3 and 17, the Rule 3 notice and consent flow, the Rule 6 safeguards and processor contracts, the Rule 7 breach playbook, retention and erasure under section 8(7) and Rule 8, consent for children under Rule 10, the Rule 14 rights route and the Rule 15 transfer position. The work is staged against 13 November 2026 and 13 May 2027, with the GDPR and UAE PDPL legs in the same pass. No statute names a signatory for a consent notice, a processor contract or a breach playbook. Acts the statute puts on the company stay with it: the Data Fiduciary gives the notice, intimates the Board and appoints its Data Protection Officer once notified. Infinilex counsel qualified in India, the UAE and the US sign opinions for those jurisdictions; for the EU and any other jurisdiction Infinilex scopes and coordinates the local counsel who sign. Infinilex publishes no fee. Scope, and so cost, turns on the products and data flows, the processors in the chain, whether anyone under eighteen uses the product and how many regimes apply; it is fixed on the discovery call. Email is answered within one working day.

Do I need a Data Protection Officer under the DPDP Act if I already have a GDPR DPO?

Only a Data Fiduciary notified as a Significant Data Fiduciary must appoint a Data Protection Officer, and that officer must be based in India, be responsible to the board and be the point of contact for grievances (section 10(2)(a)); a DPO sitting in Dublin or Berlin does not fill the post. Every other Data Fiduciary must publish the business contact of a person able to answer questions about its processing (section 8(9), Rule 9; the consent request carries a contact too, under section 6(3)) and run a grievance route answered within ninety days (Rule 14(3)); an existing GDPR DPO can hold that role. Under GDPR Article 37(1) a DPO is mandatory for public authorities, where core activities require regular and systematic monitoring of people on a large scale, and for large-scale processing of special categories of data. Under the UAE PDPL Article 10 a DPO is required for high-risk, sensitive or large-volume processing, inside or outside the UAE.

What is a Significant Data Fiduciary, and could a startup be notified as one?

A Significant Data Fiduciary is any Data Fiduciary, or class of Data Fiduciaries, that the Central Government notifies under section 10 (section 2(z)). The factors are the volume and sensitivity of personal data processed, risk to the rights of Data Principals, potential impact on the sovereignty and integrity of India, risk to electoral democracy, security of the State and public order (section 10(1)). Once notified it must appoint a Data Protection Officer based in India and an independent data auditor, run a Data Protection Impact Assessment and an audit every twelve months and report the significant observations to the Board, verify that its algorithmic software poses no risk to the rights of Data Principals, and keep any personal data the Central Government specifies, with its traffic data, inside India (section 10(2), Rule 13). This page assumes no section 10 notification as at 6 October 2026; a startup holding large volumes of sensitive data should plan for the possibility. Section 17(3) runs the other way: the Central Government may exempt notified classes, startups included, from sections 5, 8(3), 8(7), 10 and 11.

Is the DPDP Act in force in India?

In stages. The Digital Personal Data Protection Act 2023 (Act 22 of 2023) received the assent of the President on 11 August 2023, and section 1(2) lets the Central Government bring different provisions into force on different dates by notification. The DPDP Rules 2025 were notified as G.S.R. 846(E) on 13 November 2025 and Rule 1 phases them: Rules 1, 2 and 17 to 21 on publication, Rule 4 on Consent Managers one year later (13 November 2026), and Rules 3, 5 to 16, 22 and 23, the operating duties, eighteen months later (13 May 2027). Which sections of the Act are in force on a given day depends on the commencement notifications issued under section 1(2); verify the current notification before relying on a date, and build to 13 May 2027.

Is GDPR compliance mandatory in India?

No Indian law makes GDPR compliance mandatory; the Indian statute is the DPDP Act 2023 with the DPDP Rules 2025. The GDPR reaches an Indian company only on its own terms: Article 3(1) where processing happens in the context of an establishment in the EU, and Article 3(2) where a company with no EU establishment offers goods or services to people in the EU or monitors their behaviour there, in which case Article 27(1) also requires a representative in the EU unless the Article 27(2) exemption for occasional, low-risk processing applies. An Indian startup with no EU entity and no EU users is outside it. An Indian SaaS exporter serving EU customers meets both regimes, and under section 17(1)(d) most of the DPDP Act switches off for data of people outside India processed in India under a foreign contract, while sections 8(1) and 8(5) still apply.

My tool processes customer data through an intermediary, such as an insurance agent or an enterprise customer. Whose consent do I need under the DPDP Act?

Start with roles, not consent. The Data Fiduciary is whoever determines the purpose and means of processing (section 2(i)); a Data Processor processes on its behalf (section 2(k)). A tool that only fills insurer forms or runs a workflow on instructions from the insurer or the agent is a Data Processor: the notice and consent duties (sections 5 and 6) sit with the fiduciary, which may engage you only under a valid contract (section 8(2)), stays responsible for your processing irrespective of any agreement to the contrary (section 8(1)) and must write reasonable security safeguards into that contract (Rule 6(1)(f)). A one-line consent the agent shows the customer is the notice the fiduciary has to get right; it does not replace the contract with you. The moment you use the data for your own purposes, training a model or analytics across customers, you become a Data Fiduciary for that processing and need your own notice and consent. The Act does not define a sub-processor, so the contract chain runs back to the fiduciary.

Can I send personal data to a third-party LLM API under the DPDP Act, and does sensitive insurance or health data change the answer?

Yes, as a Data Processor engagement with four conditions. The provider processes on your behalf, so it is a Data Processor engaged under a valid contract (section 8(2)) that provides for reasonable security safeguards (Rule 6(1)(f)); you remain responsible for the data in its hands (sections 8(1) and 8(5)); logs of the processing are kept for one year (Rule 6(1)(e), Rule 8(3)); and when the purpose ends you must cause the provider to erase what you sent (section 8(7)(b)). Consent limits the data too: section 6(1) confines it to the personal data necessary for the specified purpose, so an LLM call that sends the whole record where one field would do falls outside it. A provider hosted outside India is a transfer under Rule 15, allowed subject to requirements the Central Government may specify, and a Significant Data Fiduciary may be barred from exporting specified data (Rule 13(4)). The Act has no separate sensitive-data category, personal data being any data about an identifiable individual (section 2(t)); sensitivity matters as a section 10(1) factor for notification, and sector rules for insurers or health providers sit on top and are checked separately. In a React Native or any other app, gate every SDK and API call that carries personal data behind the Rule 3 notice and the section 6 consent, since processing needs consent or a section 7 legitimate use before it starts and the notice comes with or before the consent request (section 5(1)).

Does the DPDP Act require deleting personal data when the purpose ends?

Yes. Section 8(7) requires a Data Fiduciary to erase personal data when the Data Principal withdraws consent or as soon as it is reasonable to assume the specified purpose is no longer being served, whichever is earlier, and to cause its Data Processor to erase what it was given, unless retention is necessary to comply with another law. Rule 8 adds the mechanics from 13 May 2027: for e-commerce entities with two crore or more registered users in India, online gaming intermediaries with fifty lakh and social media intermediaries with two crore, the purpose is deemed spent three years after the user last approached the fiduciary or exercised a right, or from the commencement of the Rules, whichever is latest (Third Schedule); the user gets at least forty-eight hours of notice before erasure (Rule 8(2)); and every Data Fiduciary keeps the personal data, traffic data and logs of a processing for at least one year for the Seventh Schedule purposes, then erases them (Rule 8(3)). A delete-on-purpose-end routine, a one-year log floor and a legal-hold exception are all needed, and the erasure instruction must reach your processors.

A customer gives us the name, phone number and email of a third person to deliver a gift. Is the declaration by the customer a lawful basis under the DPDP Act?

Not by itself. Processing needs either the consent of the Data Principal, here the recipient, which must be free, specific, informed, unconditional and unambiguous with a clear affirmative action (section 6(1)), or one of the legitimate uses listed in section 7. Section 7(a) covers the specified purpose for which the Data Principal has voluntarily provided her personal data to the Data Fiduciary, and the recipient provided nothing. A declaration by the customer binds the customer; it is not a basis the Act lists. The workable route is a notice to the recipient at first contact, consent for anything beyond the delivery, and erasure once the gift is delivered (section 8(7)). Whether another section 7 use fits your exact flow is a question for counsel on the facts.

Next step

Tell us what the product collects and where the users sit.

Send the one-paragraph version: the data you hold, where your users are, which entity contracts with them, and whether anyone under eighteen uses the product. We will tell you which regimes reach you and what the gap list looks like.

Thirty minutes with Prashant Sharma, the founder, who does the work himself. You leave with next steps either way. Email is read by the founder and answered within one working day.

Further reading

The DPDP compliance checklist for startups · The Web3 legal-readiness checklist · The FY 2026-27 India compliance calendar · DMCC vs ADGM vs IFZA from India · Founder FAQ

Related services: Fractional general counsel retainer · Contracts and IP · India subsidiary setup · How engagements work

Sources for the sections and rules cited: the DPDP Act 2023 (MeitY text; sections 1(2), 2, 3, 5 to 10 and 17) and the DPDP Rules 2025 (G.S.R. 846(E) of 13 November 2025; Rules 1, 3, 6, 8, 9, 13, 14 and 15 and the Third Schedule), both re-read on 6 October 2026, with Rule 1 (commencement), Rules 7, 10 and 13 and sections 6, 7, 8(6), 9 and 10 re-read in the Gazette of India text on 27 October 2026; GDPR Articles 3, 27 and 37 (Regulation (EU) 2016/679 of 27 April 2016, OJ L 119 of 4 May 2016) from EUR-Lex, re-read on 6 October 2026, and Articles 6(1)(f), 33 and 34 read there on 27 October 2026.

Infinilex is a consultancy. This page is general information about the service, not legal advice for your specific business, and no outcome is guaranteed. DPDP Act and Rules provisions were re-read on 6 October 2026 and the commencement, legitimate-use and breach provisions again on 27 October 2026; PDPL, DIFC and ADGM provisions, dates and penalty ceilings are stated as at 25 September 2026 from the texts cited above; GDPR Articles 3, 27 and 37 read in the Official Journal text on 6 October 2026, other GDPR points at the level of this site’s live checklist; no notification under sections 10, 16 or 17(3) is assumed. Scope and the professionals involved are confirmed on the discovery call.