Consent and communication choices
Current scope: Laborbot.si does not run advertising analytics, conversion tracking, advertising cookies, an automated marketing sequence or an external messaging provider. This page documents controls that exist now; it does not claim that future paid-service or market-specific consent requirements are complete.
Last updated October 28, 2026.
Early-access consent and removal
The early-access form requires an unchecked consent box before submission. The server rejects a request unless consent is true and stores consent notice version 2026-10-24-v1 with a successful new signup. The form does not automatically send email or enrol the address in marketing.
Use the private code issued at signup on Manage signup to delete the stored signup. Removing the record is the current withdrawal route; duplicate submissions do not reveal or replace an existing code.
Contact-request consent and removal
The contact form requires an unchecked consent box before submission. The server rejects a request unless consent is true and stores consent notice version 2026-10-25-v1 with the request. Storing a request does not send an email, start live chat or subscribe the address to marketing.
Use the private code issued with the request on Manage contact request to delete that stored request.
Communication stops in the planning workspace
Workspace owners and administrators can record a reply, opt-out, complaint or human-takeover signal for a contact reference. Once stored, any of those signals blocks the application's automated message authorization for that contact. The current preview has no connected external messaging provider, so recording a stop does not send a confirmation or cancel a provider-side campaign.
Signed-in administrators can review these records in the planning workspace. A future messaging provider must honor the same stop before delivery can be enabled and must be tested separately.
Cookies and browser storage
The current public preview does not configure optional advertising, analytics or conversion-tracking cookies, so there is no optional-cookie preference banner to save. ChatGPT identity and the hosting platform may use their own necessary session or security mechanisms under their own controls. If Laborbot later adds optional cookies or tracking, applicable notice, prior-choice and withdrawal controls must be implemented and tested before activation.
Open approval gates
- Verified business identity, launch markets, legal bases and qualified review of applicable cookie, electronic-communication and marketing rules.
- Approved outbound channels, sender identity, subscription purpose, audience source, opt-in evidence, message content and unsubscribe behavior.
- Provider-side suppression, revocation and delivery testing after a messaging or marketing provider is selected.
- Approved consent-notice versioning, retention and change-notification process for a paid service.
See the privacy notice, provider disclosure and preview use rules for related boundaries.