Make a privacy rights request

Purpose and scope

Submit an identity-verifiable request for access, correction, restriction, portability or deletion of personal data.

Use this guide as orientation, then rely on the signed agreement, current policy or named support response where those sources set a more specific obligation.

Prepare the right information

• The right being exercised.
• Enough information to locate the relevant account.
• A secure route for identity verification.

Follow the controlled process

1. Frame the needState the desired outcome, affected product and accountable contact. For make a privacy rights request, avoid assumptions that have not been confirmed in writing.
2. Review and decideUse the current governed source, record material questions and obtain approval from the person who owns the decision.
3. Retain evidenceKeep the final reference, date, decision and any follow-up action together so a later reviewer can reconstruct what happened.

Expected record

• A logged privacy request.
• Identity verification where required.
• A response, action or lawful explanation.

Security and disclosure boundary

• Never send passwords, authentication codes, private keys or recovery codes to Obedience staff.
• Share the minimum customer, project and commercial information needed for the stated purpose.
• Public documentation explains controls and responsibilities without publishing exploitable topology, credentials or confidential implementation detail.