# 2. Data Handling

User Type: **Super Administrator**
Source: *Mi Digital Academy - Education CRM Features Document*

---

## 2. Data Handling

### 2.1 Encrypted Data Storage (at Rest and in Transit)
**What it does:** Encrypts the data storage: the encryption of the data (the encryption, the data, the type, the date) is done at rest and in transit, so the data is protected (the encryption is the protection). The Super Administrator encrypts the data storage (the encryption, the data, the type, the date) so the encryption is structured and the protection is explicit.

**Sub-features:**
- Encryption: the encryption (the encryption, the data, the type, the date)
- Data: the data (the data, the type, the date)
- Encryption type: the type (the type of the encryption, e.g., the at-rest, the in-transit)
- Encryption status: the status (the encrypted, the unencrypted)
- Encryption count: the count (the count of the data by status)
- Encryption view: the view (the encryptions, the data, the types, the dates)
- Encryption export: the export (the encryptions, the format, the type)
- Audit logging of the data encryption

**Super Administrator User Journey:**
1. Super Admin encrypts the data storage: the encryption (the encryption, the data, the type, the date), the data (the data, the type, the date), and the type (the type of the encryption, e.g., the at-rest, the in-transit); the encryption is explicit.
2. Selects the data: the data (the data, the type, the date); the data is the subject.
3. Sets the encryption type: the type (the type of the encryption, e.g., the at-rest, the in-transit); the type is the mode.
4. Views the encryption status: the status (the encrypted, the unencrypted); the status is the state.
5. Views the encryption count: the count (the count of the data by status); the count is the measure.
6. Exports the encryptions: the export (the encryptions, the format, the type); the export is the record.
7. The data is protected: the encryptions, the data, the types, the dates, so the protection is complete.
8. The data encryption is audit-logged with the encryption, the type, and the timestamp.

**Rules & Edge Cases:**
- The encryption is the protection (the encryption, the data, the type, the date); the encryption is the shield.
- The data is the subject (the data, the type, the date); the data is the content.
- The encryption type is the mode (the type of the encryption, e.g., the at-rest, the in-transit); the type is the state.
- The encryption status is the state (the encrypted, the unencrypted); the status is the control.
- The data is protected (the encryptions, the data, the types, the dates); the protection is managed.
- Data encryption is audit-logged with the encryption, type, and timestamp.

### 2.2 Right to Access Personal Data
**What it does:** Provides the right to access the personal data: the access to the personal data (the access, the user, the data, the date) is provided, so the user can access their data (the access is the right). The Super Administrator provides the right to access the personal data (the access, the user, the data, the date) so the access is structured and the right is explicit.

**Sub-features:**
- Access: the access (the access, the user, the data, the date)
- User: the user (the user, the name, the access)
- Data: the data (the data of the user, the type, the date)
- Access request: the request (the request, the user, the date)
- Access status: the status (the requested, the granted, the denied)
- Access count: the count (the count of the accesses)
- Access view: the view (the accesses, the users, the data, the dates)
- Audit logging of the data access

**Super Administrator User Journey:**
1. Super Admin provides the right to access the personal data: the access (the access, the user, the data, the date), the user (the user, the name, the access), and the data (the data of the user, the type, the date); the access is explicit.
2. Selects the user: the user (the user, the name, the access); the user is the owner.
3. Selects the data: the data (the data of the user, the type, the date); the data is the personal data.
4. Views the access request: the request (the request, the user, the date); the request is the ask.
5. Views the access status: the status (the requested, the granted, the denied); the status is the state.
6. Views the access count: the count (the count of the accesses); the count is the measure.
7. The data is accessible: the accesses, the users, the data, the dates, so the right is complete.
8. The data access is audit-logged with the access, the user, and the timestamp.

**Rules & Edge Cases:**
- The access is the right (the access, the user, the data, the date); the access is the permission.
- The user is the owner (the user, the name, the access); the user is the subject.
- The data is the personal data (the data of the user, the type, the date); the data is the content.
- The access status is the state (the requested, the granted, the denied); the status is the control.
- The data is accessible (the accesses, the users, the data, the dates); the right is managed.
- Data access is audit-logged with the access, user, and timestamp.

### 2.3 Right to Deletion (Be Forgotten)
**What it does:** Provides the right to deletion: the deletion of the personal data (the deletion, the user, the data, the date) is done, so the user can be forgotten (the deletion is the right). The Super Administrator provides the right to deletion (the deletion, the user, the data, the date) so the deletion is structured and the right is explicit.

**Sub-features:**
- Deletion: the deletion (the deletion, the user, the data, the date)
- User: the user (the user, the name, the deletion)
- Data: the data (the data of the user, the type, the date)
- Deletion request: the request (the request, the user, the date)
- Deletion status: the status (the requested, the deleted, the pending)
- Deletion count: the count (the count of the deletions)
- Deletion view: the view (the deletions, the users, the data, the dates)
- Audit logging of the data deletion

**Super Administrator User Journey:**
1. Super Admin provides the right to deletion: the deletion (the deletion, the user, the data, the date), the user (the user, the name, the deletion), and the data (the data of the user, the type, the date); the deletion is explicit.
2. Selects the user: the user (the user, the name, the deletion); the user is the owner.
3. Selects the data: the data (the data of the user, the type, the date); the data is the personal data.
4. Views the deletion request: the request (the request, the user, the date); the request is the ask.
5. Views the deletion status: the status (the requested, the deleted, the pending); the status is the state.
6. Views the deletion count: the count (the count of the deletions); the count is the measure.
7. The data is deleted: the deletions, the users, the data, the dates, so the right is complete.
8. The data deletion is audit-logged with the deletion, the user, and the timestamp.

**Rules & Edge Cases:**
- The deletion is the right (the deletion, the user, the data, the date); the deletion is the erasure.
- The user is the owner (the user, the name, the deletion); the user is the subject.
- The data is the personal data (the data of the user, the type, the date); the data is the content.
- The deletion status is the state (the requested, the deleted, the pending); the status is the control.
- The data is deleted (the deletions, the users, the data, the dates); the right is managed.
- Data deletion is audit-logged with the deletion, user, and timestamp.

### 2.4 Data Portability
**What it does:** Provides the data portability: the portability of the data (the portability, the user, the data, the format) is provided, so the user can move their data (the portability is the transfer). The Super Administrator provides the data portability (the portability, the user, the data, the format) so the portability is structured and the transfer is explicit.

**Sub-features:**
- Portability: the portability (the portability, the user, the data, the format)
- User: the user (the user, the name, the portability)
- Data: the data (the data of the user, the type, the date)
- Format: the format (the format of the data, e.g., the JSON, the CSV)
- Portability status: the status (the requested, the exported, the completed)
- Portability count: the count (the count of the portabilities)
- Portability view: the view (the portabilities, the users, the data, the formats)
- Audit logging of the data portability

**Super Administrator User Journey:**
1. Super Admin provides the data portability: the portability (the portability, the user, the data, the format), the user (the user, the name, the portability), and the data (the data of the user, the type, the date); the portability is explicit.
2. Selects the user: the user (the user, the name, the portability); the user is the owner.
3. Selects the data: the data (the data of the user, the type, the date); the data is the personal data.
4. Sets the format: the format (the format of the data, e.g., the JSON, the CSV); the format is the structure.
5. Views the portability status: the status (the requested, the exported, the completed); the status is the state.
6. Views the portability count: the count (the count of the portabilities); the count is the measure.
7. The data is portable: the portabilities, the users, the data, the formats, so the transfer is complete.
8. The data portability is audit-logged with the portability, the user, and the timestamp.

**Rules & Edge Cases:**
- The portability is the transfer (the portability, the user, the data, the format); the portability is the move.
- The user is the owner (the user, the name, the portability); the user is the subject.
- The data is the personal data (the data of the user, the type, the date); the data is the content.
- The format is the structure (the format of the data, e.g., the JSON, the CSV); the format is the shape.
- The data is portable (the portabilities, the users, the data, the formats); the transfer is managed.
- Data portability is audit-logged with the portability, user, and timestamp.

### 2.5 Consent Management
**What it does:** Manages the consent: the consent of the users (the consent, the user, the scope, the date) is managed, so the consent is controlled (the management is the control). The Super Administrator manages the consent (the consent, the user, the scope, the date) so the management is structured and the control is explicit.

**Sub-features:**
- Consent: the consent (the consent, the user, the scope, the date)
- User: the user (the user, the name, the consent)
- Scope: the scope (the scope of the consent, e.g., the marketing, the analytics)
- Consent status: the status (the granted, the withdrawn, the pending)
- Consent count: the count (the count of the consents)
- Consent view: the view (the consents, the users, the scopes, the dates)
- Consent export: the export (the consents, the format, the scope)
- Audit logging of the consent management

**Super Administrator User Journey:**
1. Super Admin manages the consent: the consent (the consent, the user, the scope, the date), the user (the user, the name, the consent), and the scope (the scope of the consent, e.g., the marketing, the analytics); the management is explicit.
2. Selects the user: the user (the user, the name, the consent); the user is the owner.
3. Sets the scope: the scope (the scope of the consent, e.g., the marketing, the analytics); the scope is the category.
4. Views the consent status: the status (the granted, the withdrawn, the pending); the status is the state.
5. Views the consent count: the count (the count of the consents); the count is the measure.
6. Exports the consents: the export (the consents, the format, the scope); the export is the record.
7. The consent is managed: the consents, the users, the scopes, the dates, so the control is complete.
8. The consent management is audit-logged with the consent, the scope, and the timestamp.

**Rules & Edge Cases:**
- The consent is the permission (the consent, the user, the scope, the date); the consent is the agreement.
- The user is the owner (the user, the name, the consent); the user is the subject.
- The scope is the category (the scope of the consent, e.g., the marketing, the analytics); the scope is the segment.
- The consent status is the state (the granted, the withdrawn, the pending); the status is the control.
- The consent is managed (the consents, the users, the scopes, the dates); the control is managed.
- Consent management is audit-logged with the consent, scope, and timestamp.

### 2.6 Personal Data Anonymization
**What it does:** Anonymizes the personal data: the anonymization of the personal data (the anonymization, the data, the method, the date) is done, so the data is anonymized (the anonymization is the protection). The Super Administrator anonymizes the personal data (the anonymization, the data, the method, the date) so the anonymization is structured and the protection is explicit.

**Sub-features:**
- Anonymization: the anonymization (the anonymization, the data, the method, the date)
- Data: the data (the data, the type, the date)
- Method: the method (the method of the anonymization, e.g., the pseudonymization, the aggregation)
- Anonymization status: the status (the anonymized, the pending)
- Anonymization count: the count (the count of the anonymizations)
- Anonymization view: the view (the anonymizations, the data, the methods, the dates)
- Anonymization export: the export (the anonymizations, the format, the method)
- Audit logging of the data anonymization

**Super Administrator User Journey:**
1. Super Admin anonymizes the personal data: the anonymization (the anonymization, the data, the method, the date), the data (the data, the type, the date), and the method (the method of the anonymization, e.g., the pseudonymization, the aggregation); the anonymization is explicit.
2. Selects the data: the data (the data, the type, the date); the data is the subject.
3. Sets the method: the method (the method of the anonymization, e.g., the pseudonymization, the aggregation); the method is the technique.
4. Views the anonymization status: the status (the anonymized, the pending); the status is the state.
5. Views the anonymization count: the count (the count of the anonymizations); the count is the measure.
6. Exports the anonymizations: the export (the anonymizations, the format, the method); the export is the record.
7. The data is anonymized: the anonymizations, the data, the methods, the dates, so the protection is complete.
8. The data anonymization is audit-logged with the anonymization, the method, and the timestamp.

**Rules & Edge Cases:**
- The anonymization is the protection (the anonymization, the data, the method, the date); the anonymization is the masking.
- The data is the subject (the data, the type, the date); the data is the content.
- The method is the technique (the method of the anonymization, e.g., the pseudonymization, the aggregation); the method is the approach.
- The anonymization status is the state (the anonymized, the pending); the status is the control.
- The data is anonymized (the anonymizations, the data, the methods, the dates); the protection is managed.
- Data anonymization is audit-logged with the anonymization, method, and timestamp.