# Permission Request Copy Review

Explain why a product requests access, what it enables, how information is used, what happens if the user declines, and where permission can change.

## Usage note

Request only access the feature needs, at the moment its purpose is understandable. Copy does not make unnecessary collection acceptable and must match actual platform and product behavior.

## How to use this template

1. Verify the permission's necessity, data scope, duration, product use, and narrower alternatives.
2. Choose a contextual trigger and define full, limited, denied, revoked, and restricted behavior.
3. Draft an accurate purpose explanation and consequences without coercion or unsupported privacy claims.
4. Obtain privacy, security, product, accessibility, and platform review and test every state.
5. Monitor task success and trust signals and reopen review when behavior or platform rules change.

## Blank template

### Permission facts

- **Feature and user task:** [Enter]
- **Platform permission:** [Exact name]
- **Data or capability accessed:** [Enter]
- **Purpose and necessity:** [Explain]
- **Scope and duration:** [Enter]
- **Processing/storage/sharing:** [Verified summary]
- **Narrower alternative considered:** [Enter]
- **Qualified owners:** [Product/privacy/security]

### Request moment and copy

- **Contextual trigger:** [User action]
- **Why the purpose is clear now:** [Explain]
- **Pre-prompt heading:** [Enter or None]
- **Explanation:** [What access enables]
- **Primary action:** [Enter]
- **Decline or not-now action:** [Enter]
- **Basic behavior after decline:** [State]
- **Privacy destination:** [Verified route]

### State map

- **Full permission:** [Product behavior]
- **Limited permission:** [Behavior where supported]
- **Denied or dismissed:** [Behavior]
- **Request again rule:** [Platform/policy]
- **Enable later path:** [Settings/help]
- **Revoked access:** [Detection and message]
- **Unavailable or restricted:** [Alternative]
- **Shared-device concern:** [Enter]

### Review and monitoring

- [ ] Copy matches actual data processing and platform terminology.
- [ ] The request appears only at a relevant moment.
- [ ] Decline remains visible and non-punitive.
- [ ] The flow works with keyboard and screen reader.
- [ ] Long localization and system-prompt sequence were tested.
- **Approvals and build:** [Enter]
- **Trust and task signals:** [Denial, completion, complaint, incident]
- **Update trigger:** [Platform, processing, feature, policy]