Data Subject Access Request (DSAR) Procedure
Operated by Tek Asia Sdn Bhd · SSM 202501011675 (1613089-U) · DPO [email protected]
Under the Personal Data Protection Act 2010 (as amended by Act A1709, 2024), every data subject has the right to obtain a copy of the personal data we hold about them, to have it corrected if wrong, and to have it erased in defined circumstances. This procedure tells the team how we fulfil those rights — within 21 days, every time.
1 · Who can ask for what
| Requester | Can request | Route |
|---|---|---|
| Tenant (the customer) | Full export of their workspace · deletion of workspace | /app/settings → Compliance card |
| End-customer of a tenant | Their own messages and profile data. We are the processor; the tenant is the controller, so the end-customer must contact the tenant first. If the tenant escalates to us we cooperate within the SLA below. | Via the tenant; or [email protected] |
| Tenant employee (data subject within the workspace) | Their own audit-log activity, profile, login history | Email [email protected] with identity proof |
2 · Statutory rights covered
- Access (DSAR): JSON export of all data we hold on the subject.
- Rectification: correction of inaccurate or incomplete data.
- Erasure: deletion of data that is no longer necessary for the purpose collected.
- Portability: the access export is machine-readable JSON suitable for migration to another provider.
- Withdraw consent: opting out of optional processing (e.g. analytics).
- Restrict / object: pause processing while a dispute is being resolved.
3 · The 21-day clock
The clock starts the moment a valid request is received at [email protected] or via the in-app self-serve button. “Valid” means we can identify the requester and confirm they are the data subject (or an authorised representative).
4 · How the export is built
- The on-call engineer runs the
dsar:exportjob, passing the tenant ID (and end-customer phone number, if applicable). - The job pulls everything under that tenant scope: conversations, messages, knowledge base entries, prompt versions, audit log entries, escalations, broadcasts, usage events.
- For an end-customer request, the export is filtered to only that customer's conversation graph.
- Output is JSON, structured per our public schema, with a companion
README.mdexplaining each field. - The DPO reviews the export to confirm no cross-tenant data has bled through (sanity check).
- Delivered via a short-lived signed download URL (24 hours TTL). The DPO records delivery in the DSAR ledger.
5 · Erasure
Tenant-initiated workspace deletion (Settings → Workspace → Delete workspace) triggers a 90-day soft-delete grace period during which the workspace can be restored. After 90 days, all rows are permanently cascade-deleted across Postgres + object storage + backups (backups are pruned at the next backup-cycle boundary, within 7 days).
For end-customer erasure requests, the tenant must initiate from within the inbox (Settings → Customer → Right to be forgotten), which removes the customer's conversations + messages + derived embeddings while preserving the audit log of the erasure event itself (PDPA s.9 record-keeping).
6 · Refusing or restricting a request
We may refuse only on narrow grounds: identity cannot be verified after reasonable effort; the request is manifestly unfounded or repetitive; or fulfilling it would adversely affect the rights of another person. Any refusal is communicated in writing with the reason and the route to escalate to the PDPC.
7 · DSAR ledger
Every request is logged in compliance/dsar-ledger with: request date, requester, scope, identity verification method, completion date, output checksum, delivery channel, DPO sign-off. Retained 6 years.
8 · Free of charge, except…
First request per year per subject is free. Repeated or manifestly excessive requests may attract a reasonable administrative fee per PDPA s.30(4), communicated in advance.
9 · Ownership
Owner: Data Protection Officer ([email protected]).
Review cadence: annually.