Privacy Notice

1. Scope and roles

This notice distinguishes UxerProof account, workspace, support and security data from customer-submitted journey data. The final controller or processor characterisation depends on actual contracts and processing purpose and is reserved for legal review. A customer generally determines why and how its authorised journey testing is configured; Cyclotron Technologies also has independent duties for account security, fraud prevention and legal compliance.

2. Data categories

• Account profile, authentication state, workspace membership and legal-acceptance evidence.
• Projects, authorised environments, Circuits, Test Contracts and source configuration.
• Synthetic-run actions, redacted URLs and page metadata, findings, timings, accessibility results and explicitly enabled masked evidence.
• AI-provider request metadata, redacted analysis, model and provider versions, usage and Possibility Engine recommendations.
• Support communications, audit events, security signals, IP-derived abuse controls where configured, and operational logs.
• Billing and payment-processor data only if and when a verified billing integration is enabled.

3. Prohibited and high-risk data

UxerProof does not intentionally collect passwords, one-time passwords, authentication tokens, session cookies, authorization headers, API keys, private keys, payment-card data, bank credentials, government identifiers, private health information or secret fields through ordinary journey analysis. Browser traces are disabled. Screenshots and redacted page content are disabled by default and require an approved Test Contract purpose; form and content-editable values remain masked.

4. Purposes and customer instructions

Data is processed to authenticate users, operate isolated workspaces, verify authorised properties, execute approved journeys, produce evidence and analysis, secure and support the service, enforce limits, meet legal duties and respond to authorised privacy requests. UxerProof account acceptance is never treated as a visitor's tracking consent.

5. AI analysis

Authorised, minimised and redacted workspace context may be sent to a configured AI provider with provider storage disabled where supported. Provider identity, retention, training use and transfer terms must be verified before any stronger public commitment is made. AI output is an inference and is not used to infer sensitive traits.

6. Recipients, transfers and subprocessors

Infrastructure, authentication, communications, support, payment and AI recipients must be listed only after their production use and contracts are verified. International-transfer and data-residency statements remain unresolved. The draft subprocessor entry point does not assert that a named provider is currently a subprocessor.

7. Retention, deletion and backups

Retention is determined by enforceable workspace settings, Test Contracts, security needs, contracts and legal obligations; this draft does not invent one universal period. Deletion covers linked tenant records and derived analysis through controlled jobs. Security, legal and deletion receipts may be retained separately. Backup expiry and restoration behavior must be verified and disclosed before publication.

8. Rights and choices

Authorised people may request access, correction, export, deletion, restriction or objection as applicable, and may withdraw consent where processing relies on it. Requests are verified without revealing whether a visitor exists to an unauthorised requester. Customer account acceptance does not replace a visitor notice, consent, opt-out or withdrawal mechanism.

9. Security and incidents

Workspace boundaries, database policies, scoped functions, encrypted transport, redaction, audit evidence and incident procedures reduce risk. No security guarantee or certification is claimed. Incident and notification responsibilities depend on verified facts, applicable law and contract terms.

10. Contact

Until verified privacy contact details are configured, use the privacy and data-rights request page. Formal legal and privacy contact information must be supplied before this notice is published.

Publication blockers

This draft cannot be published until these facts are verified and approved:

• Final controller and processor characterisation
• Legal bases and international-transfer mechanism
• Verified subprocessor and data-residency details
• Privacy contact and retention criteria for every operational system

Change history

• 0.1.0-review — draft; not effective. Engineering-aligned draft; not published or effective.

Print this document · Privacy and data-rights requests