Abstract enquiry preparation file for data privacy and cybersecurity matters

Enquiry preparation · browser-only

Prepare the right high-level facts before opening a secure enquiry.

Organise a short, non-sensitive data and cyber briefing before opening the existing secure enquiry path. Nothing selected here is submitted, stored, or sent to a lawyer.

Prepare my enquiry → What not to share ↗

03 preparation stages 05 briefing prompts ER–DP preparation companion

01 Starting point

Keep the context you already built

Carry forward the useful context from the guide, directory, or city page before entering the secure enquiry.

This companion helps you organise a concise first conversation. It does not replace the existing intake, consent, conflict, privacy, or engagement process.

Starting point

Data privacy guide or counsel directory

Keep the substantive data guide and lawyer directory as the primary places for orientation and counsel discovery.

Briefing scope

Processing / transfer / incident context

Prepare only a high-level description of systems, roles and question type—without personal data, logs or confidential architecture diagrams.

Next step

Existing guided secure enquiry

The handoff opens the established enquiry experience with route context only. Your checklist selections do not transfer.

02 Prepare

Choose where you are in the process

Choose the high-level stage that best describes your situation. The prompts then show what can be prepared safely without entering a confidential matter history.

These choices help frame an initial professional conversation. They do not assess suitability, urgency, legal merits, or lawyer availability.

Current stage

Program design or assessment

Describe processing categories and goals in general terms—without uploading inventories that contain personal data.

✓ A high-level route frame is different from a legal conclusion or a document review.

03 Briefing checklist

Prepare only high-level context

Prepare the basic facts that can be stated safely at a high level.

Use the checklist as a private prompt for yourself. Your selections are not stored, submitted, or transmitted by this companion.

I can state the high-level organisational role. Handler, vendor/processor, employer/HR or product team is enough. I can identify whether this is program, transfer, security or incident-related. A matter label is enough; do not paste personal data or security logs. I can describe systems or vendors in non-sensitive terms. Product or HR platform categories are enough; do not provide credentials or raw exports. I can name any preferred city or operations location in general terms. City or “multi-city China operations” is enough. I can name the main question for a first conversation. For example: notice/consent design, transfer mechanism, vendor oversight, or incident response planning.

04 Privacy boundary

What not to enter here

Keep confidential material, identity data, documents, and detailed legal issues out of this browser-only preparation step.

Do not add

Document or evidence file

Keep agreements, drafts, correspondence, regulator notices, schedules, and other files for an appropriate secure process.

Do not add

Identifier or contact record

Do not use this companion for names, passports, company numbers, banking data, emails, telephone numbers, or employee information.

Do not add

Conclusion or case assessment

Do not treat the page as a way to establish access, solve a transaction question, judge a deadline, or obtain advice.

Personal data, employee files, customer lists, logs, credentials, or incident exports Confidential architecture diagrams, assessment packs, or privileged advice Regulator correspondence beyond a high-level notice type and timing

05 Secure handoff

Continue to the existing secure enquiry

When ready, open the existing guided enquiry with only the Data Privacy and Cybersecurity route context attached.

The existing intake should present its own consent, privacy, conflict, scope, and secure contact process. This companion does not bypass those controls.

Continue to secure enquiry ↗ Browse data & cyber lawyers →

What the handoff carries

Practice contextData Privacy and Cybersecurity

Operating stanceProgram design or assessment

Checklist progress0 / 5

✓ No selected fields, documents, contact details, or narrative are included in the route transfer.

06 Other useful routes

Need more context first?

Go back to the relevant guide, location page, or lawyer directory if you need more context.

Read the data privacy guide

Return to national PIPL/CSL/DSL, transfer and incident orientation.

Open employment context

Use the employment route when HR systems and workforce data sit beside the privacy question.

Browse data & cyber lawyers

Compare practice-side discovery records before entering a professional handoff.

07 Common questions

Before you continue

Common questions before moving into the secure enquiry process.

Does this readiness companion send my selections to China Legal Portal or a lawyer?

No. The controls operate in the current browser view only. The handoff link carries only its controlled route context, not selected fields, documents, contact details, or a narrative.

Can I paste personal data, security logs or incident reports here?

No. The companion is intentionally limited to high-level preparation. Do not upload personal or confidential security material until a secure channel and engagement scope are confirmed.

Does opening the guided enquiry create a lawyer-client relationship?

No. The existing enquiry route should present its own consent, conflict, scope, and engagement boundaries. A route selection or enquiry does not establish representation.