Secure authentication
Security and authentication mechanisms help maintain sessions, prevent abuse and route users to permitted areas.
Cookie policy
Essential by default. Optional by choice.
TaskQA uses secure session mechanisms and device-local preferences; optional analytics should remain consent-controlled.
DESIGNED FORPolicy draft
Managed by TaskQA
In detail
TaskQA aims to use browser storage sparingly. Essential session and security mechanisms support account access and protected workflows; preferences remember user choices; optional measurement should be introduced only with appropriate notice and consent.
What this includes01 02 03 04
Theme preference
Local preferences such as colour theme can be stored on the device to improve continuity.
Consent categories
Any optional analytics or marketing category should be disabled until the required consent has been obtained.
Retention transparency
Each category should have a documented purpose, provider and lifetime, with expired data removed or renewed appropriately.
What to expect
Clear scope. Useful detail.
Essential storage
Used where necessary for authentication, security, request routing, fraud prevention and core platform operation. Disabling it may prevent protected features from working.
Preference storage
Remembers choices such as theme or interface settings. These values should not be used to build advertising profiles.
Analytics and marketing
TaskQA does not need these categories for core operation. If introduced, they should be disclosed and controlled through a consent mechanism where required.
Managing choices
People can use browser controls to remove stored data and, where provided, update consent preferences. Removing essential storage may sign the user out.
The TaskQA difference
Software coordinates the work. People make the important decisions.
- 01Define the requirement
- 02TaskQA selects participants
- 03Evidence is reviewed
- 04Results and rewards are approved
Ready when your product is
Request a test