TaskSultan should collect the minimum evidence needed to build the automation.
- Obtain participant consent before recording or taking control.
- Keep credentials, tokens and passwords out of recordings, screenshots and generated artifacts.
- Allow customers to choose local transcription or an approved hosted provider.
- Encrypt integration secrets at rest and never return them to the browser.
- Keep tenant data separated and make deletion and retention visible.
- Show provenance for generated requirements and model output.
- Require human approval before a specification becomes a build input.
Security controls are deployment-specific. This document describes the v2 product contract, not a certification or legal guarantee.
#Customer responsibility
The customer decides what may be recorded, processed or retained and remains responsible for the applications and data in their environment.
#Model processing
The selected model provider and processing location should be visible before sensitive evidence is submitted.