Understand what this portal processes.
Account & workspace records
We store your name, email, password hash, organization membership, projects, evaluation access, quote and support requests, usage counters and security audit events to operate the service.
Identity documents
Test Studio processes document images and extracted fields locally in your browser. Do not paste identity data into support requests. No third-party analytics or advertising trackers are installed in this release.
Email delivery
Office 365 SMTP is used for account confirmation, password recovery and requested transactional notifications. Passwords are never included in messages.
Your choices
Use Account & security to change your password and sign out. Contact CEBS through workspace Support for account access, correction or deletion requests. Retention and contractual data-processing terms must be agreed for a production deployment.
Purpose and access
| Record | Purpose and access |
|---|---|
| Account and membership | Provide sign-in, recovery and organization authorization. |
| Projects and evaluations | Record configuration and time-limited evaluation access. |
| Commercial and support records | Review requests within the organization and authorized CEBS administration. |
| Operational metadata | Protect service access, investigate technical failures and maintain reliable operation. |
Retention and account requests
Account and request records are retained for service operation and applicable contractual or legal needs. Expired session, action-token, invitation and rate-limit records are cleaned operationally. Database backups have a separate recovery lifecycle; removing a live record does not immediately remove every backup copy. Confirm the required retention and deletion terms with CEBS for a production agreement.
Exercise your choices
Change your password or sign out through Account and security. Use authenticated Support for account access, correction or deletion requests. Avoid including identity documents in ordinary support text. Production deployments require an agreed market-specific privacy and data-processing review.