DATA REQUESTS · VERIFIED PREVIEW ROUTES
Access, correction, export and deletion routes
Preview boundary: The routes below are available now for the records they name. Laborbot.si does not yet have an approved business privacy contact, launch-market rights matrix or statutory response deadline. The stored contact form is a review queue, not an email channel, and no response time is promised.
Last updated October 28, 2026. Do not place passwords, API keys, payment information, health data or other sensitive material in a request.
Current route and owner matrix
| Record | Available action | Current owner | Evidence and limit |
|---|---|---|---|
| Early-access signup | Delete | The submitter, using the private removal code issued at signup | Manage signup removes the exact stored record. The code is shown once; duplicate submissions do not reveal it. |
| Stored contact request | Delete | The submitter, using the private removal code issued with the request | Manage contact request removes the exact stored request. |
| Signed-in planning workspace | Export | A current workspace owner or administrator | The signed-in workspace export produces a private JSON snapshot and records administrative access. It does not export ChatGPT identity or separate provider logs. |
| Signed-in planning workspace | Delete | A current workspace owner | A separately confirmed deletion request pauses work, cancels queued or running checks, deletes Laborbot workspace records and leaves a minimal completion receipt. It does not delete ChatGPT identity or provider-held data. |
| Correction, access or other privacy question | Store a review request | No approved business privacy owner yet; product preview review only | Use the contact form and select “Data or privacy.” The request is stored for review and gets its own removal code. Submission does not prove identity, start a statutory clock or guarantee a response. |
Handling steps for a stored review request
- Keep the original request and submission time; do not claim receipt outside the stored form.
- Verify the requester and exact record scope before disclosing, changing or deleting data. The preview has no general identity-verification workflow, so unresolved identity is a blocker.
- Use self-service removal, signed-in export or owner-only workspace deletion when the request matches those implemented routes.
- Keep provider logs, backups, ChatGPT identity and any unconnected provider account out of the completion claim unless the relevant provider supplies separate evidence.
- Do not invent a legal basis, jurisdictional right, response deadline or completion record. Escalate those items to the future approved privacy owner and qualified adviser.
Open launch gates
- Verified business legal identity and privacy contact; launch markets and applicable rights.
- An approved request owner and backup, identity-verification procedure, statutory and internal deadlines, escalation path and evidence destination.
- Correction workflows for each record type, exception and refusal handling, provider coordination, backup/log scope and notification templates.
- Hosted end-to-end rehearsal with a real authorized requester and retained timestamps, decision, action and completion evidence.
See the privacy notice, workspace guide, consent and communication choices and provider disclosure.