Personal data processing and data subject rights
Maintain accountable processing records and support timely handling of data subject requests under the applicable verified jurisdictional rules.
Bundle → Layer → Finding → Questions Filled
3 bundles · 4 layers · 5 findings · 13 questions
Processing activity Processing records distinguish purpose, participants, legal basis and permitted downstream use.
Purpose and basis
Each activity records its purpose and the verified rules governing its processing.
Processing activity
An activity identifies its purpose, affected categories and participant roles.
- What purpose does this processing activity serve independently of its storage system?
- Which personal data categories and data subject categories does this activity involve?
- Which participants act as controller, processor or another applicable role for this activity?
- Which verified jurisdictional profile identifiers and versions govern this activity?
Legal basis
A basis record attributes the approved justification to the processing it covers.
- Which legal basis is recorded for this processing, and what approved justification supports its use?
Downstream use
Derived uses remain subject to the recorded purpose and data minimization limits.
Minimal projection
Each projection records whether its purpose and included data remain permitted.
- Does this projection remain within its permitted purpose and minimum necessary data?
Retention policy Retention records specify category-specific periods and their grounds.
Retention rules
Each rule identifies the data category and the conditions governing retention.
Retention rule
A retention rule records its duration, trigger and supporting ground.
- Which data category does this rule cover, and what retention period, trigger and ground does it specify?
Data subject requests Requests are handled according to the right invoked and the applicable verified rules.
Request records
Each request retains its scope, verification status, deadline, decision and outcome.
Data subject request
A request may concern access, correction, deletion, restriction, portability, objection or another applicable right.
- Which right or rights does this request invoke, and what data and processing fall within its scope?
- What identity or representative authority verification status is recorded for this request?
- Which verified jurisdictional profile identifiers and versions govern this request?
- When was this request received, and what response deadline and authorized extension apply?
- What decision and grounds are recorded for this request, including any partial refusal or lawful retention exception?
- What action fulfilled this request, and what evidence confirms its outcome and communication to the requester?
Classifiers Filled
- Family
- Enterprise profiles
- Category
- Enterprise subject
- Entry kind
- subject
- Domain
- EnterpriseLEG
- Industry
- Cross-industry
- Tags
- EM-LEG-06W2subjectProcessingActivityPurposeDataSubjectRequestProcessingBasisRetentionRule
What it is Filled
Processing purpose, data categories, participant roles, legal basis, retention periods and data subject requests. Jurisdictional rules are defined by verified profiles.
Why it exists Filled
Maintain accountable processing records and support timely handling of data subject requests under the applicable verified jurisdictional rules.
Distinguishing features Filled
- Purpose and legal basis are separate statements, and neither is the storage system.
- Deletion has a defined scope and a confirmation, and can coexist with lawful retention of other records.
- A derived projection may not widen the purpose for which the data was collected.
- Distinct from the dataset contour, which describes data structures rather than processing purposes.
What robots and AI may and may not do Filled
Must not
- Delete the entire accounting history unconditionally because consent was withdrawn.
- Use data for a purpose beyond the one recorded.
- Treat consent as the legal basis by default.
- Disclose personal data in response to a request without verifying the requester.
- Combine projections in a way that re-identifies individuals.
Only with a human decision
- Deciding the legal basis for a new processing activity.
- Refusing or partly refusing a data subject request.
- Responding to a supervisory authority.
May
- Map processing activities to systems and data categories.
- Locate data within the scope of a request and prepare a fulfilment plan.
- Flag projections that use more data than the purpose needs.
Moral aspects Filled
- Personal data processing directly affects individuals' privacy and autonomy.
- Over-deletion can destroy records others are entitled to rely on.
- Repurposing data without a basis erodes trust and breaks the law.
Who is affected
- Data subjects
- Controllers and processors
- Supervisory authorities
- Staff handling requests
Owners Filled
Steward
The data protection lead who answers for the record of processing and data subject requests.
Master systems
- Record of processing activities
- Request management system
- Consent management system
- Data catalog
Links to other meta-models Filled
neighbor
- EM-DAT-01
references
- WM-XCT-002 - conceptual-candidate
- WM-XCT-003 - conceptual-candidate
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- A processing activity is identified by its identifier in the processing register, and a request is identified by its request number and receipt date.
Direct properties not applicable Not applicable
Not applicable
Enterprise record contour: physical properties belong to referenced world models.
Recognition required Filled
- A processing record identifies a purpose, legal basis, data categories and participant roles.
- The processing activity is distinct from the system or database storing its data.
Capabilities and actions required Filled
- Requests can be fulfilled with a provable scope and lawful exceptions.
- Purpose limits can be checked for each downstream use.
Hazards and failure modes required Filled
- Request deadlines may be missed.
- Shadow copies may remain after deletion.
- Supposedly minimal projections may allow re-identification.
Standards and interfaces optional Filled
- The Data Privacy Vocabulary is a specification of the Data Privacy Vocabularies and Controls Community Group hosted by the World Wide Web Consortium and is not a World Wide Web Consortium Recommendation.
- ISO/IEC 29100 from the International Organization for Standardization and the International Electrotechnical Commission provides a privacy framework.
- ISO/IEC 27701 from the International Organization for Standardization and the International Electrotechnical Commission addresses privacy information management.
- A record subject to Regulation (EU) 2016/679 of the European Parliament and of the Council must reference the actual identifier and version of its applicable verified jurisdictional profile.
- An unavailable verified profile identifier or version remains an explicit gap rather than being replaced by a regulation citation.
Context of use required Filled
- The record applies wherever an organisation processes personal data of customers, staff or users.
- Jurisdictional rules are applied through verified profiles rather than assumed.
Sources Filled
- OASIS UBL/FIBO: agreements, parties and obligations
- ODRL: permission, prohibition, duty and constraint
- Primary legal sources of selected jurisdictions; subject-matter verification of applicability is mandatory
- OASIS Universal Business Language (UBL) 2.3 - Checked live (HTTP 200) on 2026-10-07.
- W3C ODRL Information Model 2.2 - Checked live (HTTP 200) on 2026-10-07.
Open questions
- How to distinguish a purpose from a storage system?
- When is consent a legal basis and when is it not?
- How to fulfill deletion when another fact must be retained?
- Установить границу и решение reuse/extend/new по действующим спецификациям.
- Подтвердить semantic crosswalk, права и source mastership.
- Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.
Machine files
Provenance
enterprise research programme · published-partial
Built from: enterprise/models/em-leg-06/brief.json, ver-cy/world-models/card-supplements/em-leg-06.json
Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.