Skip to main content
Early accessBeta, invite only since 1 Nov 2026. A person reads every application.Apply for an invite
Demystify OS

Workflow in Demystify Skills Hub

Consent request to record

From asking for consent to a dated record, with erasure handled by a person.

Provisioned on requestR2 Acts after approval. On request, as of 4 Nov 2026.

From asking for consent to a dated record, with erasure handled by a person. This workflow is in the Compliance category at risk tier R2, acts after approval. A person is designed to decide at step 4. It is on request as of 4 Nov 2026, with no measured run yet.

How it works

The steps

  1. 1

    Send the consent request in the person's language.

  2. 2

    Record the answer with its date and source.

  3. 3

    Show the record to the owner on request.

  4. 4

    A person handles any withdrawal or erasure request.Designed: a person decides here.

Detail

What it needs and where it stops

What it needs from you
  • Person's contact details
  • Purpose of use
What it needs connected
  • Email or WhatsApp
  • Customer records
Risk tier R2: Acts after approval
Designed to act only after a person approves that step. Where a person is designed to decide: A person handles any withdrawal or erasure request. These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.
Status and what is not claimed
It is on request as of 4 Nov 2026: a catalogue entry we set up with you. No run of it has been measured yet, and nothing here claims it installs, syncs or streams on its own today.
India

DPDP, WhatsApp, Hindi and regional.

Want this set up?

Apply for the invite-only beta. A person reads every application.

Apply for the beta