## Access (right to know) request

When a Data Subject requests to access the personal information that your company maintains on them, they will submit an **Access (right to know)** request.

### Workflow Steps

1. **Request Submission**  
   - **Method**: Email, Phone, API, Intake Form, Queue  
   - **Requires Verification**: Yes / No  
     - If `No`: Intake Form / API
2. **Data Subject Verifies** (valid for 7 days)  
   - **Notifications**: Verification email, Verification Reminder
3. **Privacy Manager Reviews** the retrieved data.
   - **Notifications**: Request Status - Pending Action
4. **Download Link** is sent to Data Subject (valid for 7 days)  
   - If not downloaded, request moves to **Closed: Not Downloaded**.
5. **Closure States**:
   - **Closed: Downloaded** (Data Subject has downloaded their data)
   - **Closed: Not Downloaded** (Download link expired)
   - **Closed: Responded** (No data found)
   - **Closed: Unverified** (Data Subject failed to verify their email)

### Key Definitions

- **User Action Required**: Actions that must be performed by the Data Subject or Privacy Manager.
- **Automated Step**: Processes that are handled automatically without user intervention.

### Additional Notes

- Requests submitted via **API**, **Intake Form**, and **Request Queue** will enter `Active: Initializing` if automation is configured.  
- **Email Templates** used include: 
  - Access Request Results  
  - Access Request Results - No Data Found  
  - Privacy Request Confirmation  
  - Verification Rejected

### Help & Support

If you have questions, contact your Account Manager or reach out to [support@datagrail.io](mailto:support@datagrail.io).

***Disclaimer***: The information provided does not constitute legal advice.
