Trust center

Trust resources for teams handling privacy requests

Privacy Requests is built for work that may involve personal data, identity checks, response files, and delivery records. This page links to the information customers usually want before they buy.

Report a concern

Contact us about a service problem or suspected vulnerability without sharing sensitive requester information.

Reporting guidance

Security safeguards

See how access, secure delivery, revocation, and history are handled.

Read security page

Privacy practices

Review how we handle visitor, account, and product data.

Read privacy page

Terms of service

Review the terms that cover use of the service, responsibilities, and support.

Read terms page

DSAR operations guide

Read practical guidance on intake, review, response delivery, and record keeping.

Read guide

How the product works

Review the complete path from requester intake through verification, response review, secure delivery, and closure.

Read product overview

Operating principle

Keep sensitive files and decisions together

Privacy requests can involve sensitive context. Privacy Requests helps teams keep files together, control delivery, and maintain a clear record of who did what and when.

  • Receive public requests while keeping your team’s workspace private.
  • Keep access limited to the people handling the request.
  • Let requesters check their progress without seeing internal notes or files.
  • Use controlled delivery links for sensitive response files.
  • Keep human review in the loop before sensitive materials are approved or sent.
  • Preserve important actions for later review.

Service facts and review materials

Hosting and data storage

What the current service is built on

We use Cloudflare to host the service, store case records and private request files, and process background tasks. This describes the services we use; it does not guarantee that data is processed in a particular country or region.

Access and workspace boundaries

Team members need an active workspace membership. Their role controls the actions they can perform, including task updates, verification decisions, and secure delivery. Case access is shared within the workspace; assignment does not make a case private.

Secure delivery controls

Staff can set an expiring delivery link, require a passcode, and revoke the link. Delivery access and file downloads are recorded in the case history.

Documents for your review

We do not currently publish a fixed hosting location, subprocessor list, approved data processing agreement (DPA), certification, penetration-test report, or backup and recovery commitment on this site. Contact us for the current status of any requested review materials.

Your evaluation

Bring the questions that matter to your team

Use the published information to understand the current service. Where your review requires contractual commitments or supporting documents, confirm their availability directly before relying on them.

  1. Define the data and people involved.List the kinds of records you expect to upload, the people who will handle them, and the internal approvals your organization requires.
  2. Review the workflow controls.Walk through membership, identity review, response approval, controlled delivery, and the case record. The product tour shows these steps with fictional data.
  3. Identify your required review materials.Tell us if you need a DPA, subprocessor information, data-location commitments, or assurance evidence. The service facts page explains what is currently published.
  4. Try the handoffs before using real data.Use fictional records to check that the owner, contributor, and reviewer can complete their parts of the process.

View the product tour · Use the setup checklist · Check review-material availability

Questions

Contact Privacy Requests

For security, privacy, or product questions, contact support@privacyrequests.co.