XreviaTech AI Workforce data-deletion instructions

Last reviewed: 22 October 2026.

  1. Send a request to xreviatech@gmail.com with the subject “XreviaTech AI Workforce data request.” Describe the account or interaction concerned and whether you request access, correction, or deletion. Do not send passwords, access tokens, or government ID documents in the initial message.
  2. We will verify that the requester is entitled to the records before disclosing or changing them. We may ask for limited additional information through a secure channel if necessary.
  3. The operator will identify records that can be linked to the verified requester. If Instagram messaging is later connected, those may include an Instagram-scoped user ID; message-event times and IDs in a private local SQLite inbox; recipient IDs and delivery records in the main SQLite database; audit records; and encrypted Cloudflare queue entries. Message text and attachments are not designed to be stored by the proposed relay.
  4. The operator will review which identified current records can be deleted or corrected and which audit details must be retained for security, integrity, or applicable legal reasons. Deletion of current records would be performed through a controlled, logged procedure after verifying database integrity. Existing backups and provider recovery copies require a separate retention decision; deleting a current row does not erase those copies immediately.
  5. We will report the outcome to the requester using the agreed contact channel. Requests concerning data controlled by Meta or another service must also be directed to that service.

Current technical limits

The live Instagram webhook is not connected. The relay code assigns queued events a seven-day expiry, but production cleanup has not been verified. The source-only Mac inbox has no automatic deletion period or self-service deletion endpoint. Cloudflare queue payloads are encrypted and cannot currently be searched by sender ID; entries not already linked to a local event require a reviewed matching or deletion mechanism before live use. App-managed SQLite backups are separate files and may retain earlier records. We will not claim instant erasure of all backup or provider-managed copies, or promise a deletion deadline that the system cannot enforce. These procedures must be tested before accepting real inbound events.

Privacy Policy