How to request deletion of personal data

Submit a request

Send an email to the address confirmed by the owner vasif.quliyev00@gmail.com with the subject “Personal data deletion”.

Provide the minimum needed for a search

For WhatsApp, provide your number in international format and the approximate date of your last enquiry. These instructions do not cover searches by name, date, email or form data alone.

Do not send a password, payment details, a passport copy or other unnecessary information.

Identity verification and secure search

The draft internal procedure provides for registering the request under a random reference number containing no phone number or email, verifying identity through a separately agreed channel and conducting a preliminary search in safe mode only. Search results must show the set of storage locations found, without message content or exposed identifiers.

Current status: the applicant identification method and response time have not yet been approved or activated.

Determining the scope of deletion

Before physical deletion, the controller must check mandatory exceptions: an active contract, payment, claim, cargo damage, debt or mandatory archive. After review, a plan is drawn up specifying what to delete, anonymize or temporarily retain, with the grounds stated.

The command `STOP`, `СТОП` or `UNSUBSCRIBE` stops marketing messages but is not a request to delete previously stored data. A minimised opt-out record may be needed to prevent further mailings.

Separate confirmation and result verification

The retention preview v1 deployed on Hetzner performs only a read-only check each day. Applying changes requires a separate enable flag and an exact confirmation phrase. A separate apply operation must check confirmed WhatsApp data stores, queues and logs; backup lifecycles must first undergo a separate inventory review. CRM and forms are not part of the currently confirmed deletion scope. The outcome is sent to the applicant only after verification; the operation log must be retained without direct identifiers.

Preview is active on Hetzner. The schedule is enabled and verified; the last run made no changes to data. Actual execution is technically disabled and requires separate confirmation.

Locally implemented technical retention period

Retention v1 can replace the content of completed inbound records with a technical clearing marker after 30 days, preserving metadata and duplicate protection, and replace the text of completed replies after 7 days. `pending/failed` records, consent, STOP/suppression and the sender ledger are unchanged; no physical SQL DELETE is performed. A 30-day backup window remains a proposal: the current CRM setup does not separately back up WhatsApp storage, and the existence of external provider snapshots has not yet been confirmed.

Only the safe preview is active in production. Actual content replacement is disabled and is not run on a schedule.