Data Requests & Retention

Request intake

Employees and contractors submit requests through their employer HR/payroll administrator or the in-app support channel. Customer administrators submit requests through their assigned Benmore/Measured support contact. Requests involving another person, another tenant, payroll corrections, tax records, bank data, or legal holds require administrator review before fulfillment.

Review and fulfillment

1. Verify requester identity, tenant, role, and authority.
2. Classify request as access, correction, export, deletion, retention exception, or legal hold review.
3. Search relevant employee, payroll, tax, benefits, document, support, audit, and treasury records.
4. Export or correct records when allowed by the customer organization and law.
5. Deny or defer deletion when payroll, tax, employment, benefits, litigation, or contract retention applies.
6. Record requester, reviewer, decision, affected records, retention rationale, completion date, and verification evidence.

Evidence record

Completed requests should retain the support ticket, administrator approval, export/deletion/correction summary, any denied-record rationale, audit-log references, and final requester communication. The SOC 2 evidence packet now includes a deletion-register template and dry-run record; a real completed customer record is still required before this control can be marked verified.