Workspace guide

How ScalePulse works

Configure each feature with confidence, understand what it proves, and know what remains in your systems.

Important boundary

ScalePulse is a consent management platform, not a registered Consent Manager and not a compliance certificate. It records evidence and routes requests; your organisation remains responsible for fulfilment, retention, security, and legal decisions.

Feature

Reviewed notice + widget

Why

Explain what visitors are agreeing to before collection.

Next action

Publish a reviewed notice, then install the generated tag wherever consent is collected.

<script async src="https://cdn.example/sp.js" data-key="sp_pk_example"></script>

Feature

Immutable consent ledger

Why

Keep a tenant-scoped, hash-chained record of every decision.

Next action

Open Explore ledger from a tenant card and export evidence when needed.

Feature

Rights and grievances

Why

Receive verified requests with an SLA clock.

Next action

Select a tenant, route or manually fulfil the request, then record evidence.

Feature

Signed webhooks

Why

Deliver request and escalation events without exposing requester email addresses.

Next action

Save an HTTPS endpoint, verify HMAC, and process events asynchronously.

Feature

Hosted privacy portal

Why

Give visitors a branded place to submit verified requests.

Next action

Set a subdomain, add the CNAME, and check DNS. The portal activates after verification.

Feature

Enterprise data map, findings, and cases

Why

Classify metadata and assign accountable remediation work.

Next action

Upload signed metadata, evaluate controls, and create cases. Row values never enter the control plane.

Webhook reference

Every supported payload

ScalePulse sends signed JSON events to your HTTPS endpoint. Configure once, verify every request, then hand work to your queue.

1ConfigureSave your HTTPS endpoint and copy the secret.

2VerifyCheck the timestamp and HMAC before parsing JSON.

3AcknowledgeDeduplicate by requestId, return 2xx, process async.

Signature reference

Headers

x-scalepulse-eventx-scalepulse-timestampx-scalepulse-signature: v1=<hex>

Sign this exact valuetimestamp + '.' + rawBody

Use HMAC-SHA256 with the signing secret. Verify the raw request body before JSON parsing.

dpdp.access.requested

A verified requester asked to access their personal data.

{
  "format": "scalepulse.webhook/v1",
  "requestId": "2b7d9f7d-0f0f-4bf0-8dc8-8d2e55f9d7f5",
  "event": "dpdp.access.requested",
  "occurredAt": "2026-08-25T06:00:00.000Z",
  "tenantId": "your-tenant",
  "type": "access",
  "dueAt": "2026-09-24T06:00:00.000Z",
  "publicKey": "sp_pk_example"
}

dpdp.correction.requested

A verified requester asked to correct their data.

{
  "format": "scalepulse.webhook/v1",
  "requestId": "8f0d4f51-87dd-46b9-91f6-6e3b3c4fdc52",
  "event": "dpdp.correction.requested",
  "occurredAt": "2026-08-25T06:00:00.000Z",
  "tenantId": "your-tenant",
  "type": "correction",
  "dueAt": "2026-09-24T06:00:00.000Z",
  "publicKey": "sp_pk_example"
}

dpdp.erasure.requested

A verified requester asked for erasure.

{
  "format": "scalepulse.webhook/v1",
  "requestId": "c9dffb4e-b8ed-46b1-8e2f-1c1d8f5b8d70",
  "event": "dpdp.erasure.requested",
  "occurredAt": "2026-08-25T06:00:00.000Z",
  "tenantId": "your-tenant",
  "type": "erasure",
  "dueAt": "2026-09-24T06:00:00.000Z",
  "publicKey": "sp_pk_example"
}

dpdp.grievance.requested

A verified requester opened a grievance.

{
  "format": "scalepulse.webhook/v1",
  "requestId": "6b4bf0df-68ae-47f0-bf7b-4ba4ef174e1c",
  "event": "dpdp.grievance.requested",
  "occurredAt": "2026-08-25T06:00:00.000Z",
  "tenantId": "your-tenant",
  "type": "grievance",
  "dueAt": "2026-09-24T06:00:00.000Z",
  "publicKey": "sp_pk_example"
}

dpdp.webhook.test

The dashboard test button verifies your endpoint and signature handling.

{
  "format": "scalepulse.webhook/v1",
  "requestId": "test_7f4c7e1c-6b3c-4b6f-a9c2-2b9c5d0dd9d2",
  "event": "dpdp.webhook.test",
  "occurredAt": "2026-08-25T06:00:00.000Z",
  "tenantId": "your-tenant",
  "publicKey": "sp_pk_example"
}

dpdp.case.sla_overdue

A case passed its configured due time and needs escalation.

{
  "type": "dpdp.case.sla_overdue",
  "caseId": "case_01J5EXAMPLE",
  "dueAt": "2026-08-24T06:00:00.000Z",
  "occurredAt": "2026-08-25T06:00:00.000Z"
}

Ready to configure?

Choose a tenant first; every notice, portal, webhook, and enterprise record is isolated to that tenant.

Open workspace