Pilot trust

Privacy notice, terms notice, consent and participation, data visibility, and security contact for the controlled pilot — explained honestly, including what is not available yet.

Privacy notice

What the controlled pilot collects, how it is used, and who can see it — stated honestly for the pilot as it exists today.

Data we collect

Your account basics (name, sign-in email, trade context), your consent choices, your saved learning progress, the structured evidence you choose to submit, and high-level service logs needed to run the pilot.

No payment information and no uploaded files are collected in this pilot.

How data is used

Pilot data is used to run your Learning Workspace, show your saved progress, review the structured evidence you submit, build your readiness snapshot, and keep the pilot working safely.

Optional telemetry and product-update consents are off by default and recorded only if you turn them on.

Who can see data

You see your own records in your Learning Workspace. A small founder-operated pilot team can view pilot records to review evidence, answer questions, and keep the pilot running.

Pilot data is not published, not shared with employers, and not used for verification by anyone outside the pilot.

Terms notice

Pilot participation boundaries: what this pilot is, and what taking part does and does not mean.

Controlled pilot scope

BezaLink is running a controlled pilot for invited participants. The pilot exists to validate the learning experience with real people before any wider release.

This pilot does not create a credential, certification, public proof, or employer verification, and it is not a commercial launch.

Evidence and readiness boundaries

Structured evidence you submit is reviewed by the pilot team, and you can track its status at any time. Your readiness snapshot explains where you stand with reasons.

Evidence review and the readiness snapshot are pilot guidance only — never a credential, certification, public proof, or employer verification.

View readiness snapshot

Consent and participation

Joining the pilot records your acceptance of the privacy notice, with a recorded policy version. Optional consents are separate, off by default, and recorded only when you choose them.

Participation is for the controlled pilot only.
You submit structured evidence voluntarily.
Your readiness snapshot is pilot guidance — not a credential, certification, public proof, or employer verification.
Pilot support is founder-operated and handled manually.
Learning content is under review before pilot use.
File uploads and document scanning are not available in this pilot.
Export and deletion automation are not available in this pilot.
Optional consents are off by default and recorded only if you turn them on.

Data visibility

Who can see which pilot data, what it is used for, and what it is never used for.

Data	You can see it	Pilot team can see it	Used for	Not used for	How it is handled in the pilot
Account profile basics	Yes	Yes	Signing you in and showing your account status.	Marketing without your optional consent.	Stored with your pilot account; visible to you in your Learning Workspace.
Pilot access and role status	Yes	Yes	Deciding which pilot surfaces your account can open.	Employer verification or any public listing.	Checked on the server every time a protected page loads.
Learning Workspace activity	Yes	Yes	Showing your saved progress and your next step.	Automated scoring or credential decisions — no score is calculated in this pilot.	Saved to your learning record; shown back to you on your dashboard.
Evidence details and review status	Yes	Yes	Reviewing the structured evidence you chose to submit and showing you its status and feedback.	Public proof, employer verification, or anything outside the pilot.	You see only your own evidence; reviewers see submissions to review them.
Readiness snapshot factors	Yes	Yes	Explaining where you stand and what to do next — pilot guidance only.	A credential, certification, score, or any decision about you.	Built from your own account, progress, and evidence state when you open the page.
Support and help interactions	No	No	Nothing is stored in-app: structured support intake is not available yet in this pilot.	No in-app support records exist to use.	Support runs through the founder-operated invitation channel and is read manually.
Service and security logs (high level)	No	Yes	Keeping the pilot running and protecting accounts.	Profiling, marketing, or any decision about your learning.	Standard service logs reviewed manually by the pilot team when something needs attention.

Retention windows and self-serve data tools are part of the GA trust work; this pilot states only what is true today.

Security contact

To raise a security or privacy concern, use the pilot support path. It is founder-operated and handled manually.

Never include passwords, secret keys, or sign-in codes in a message. This is not emergency support.

This pilot does not include guaranteed response times, and there is no formal security reward program or formal incident-response commitment in this pilot.

Get pilot support

Privacy requests

To ask a privacy question or make a request about your data, use the pilot support path. Requests are read manually during the controlled pilot.

Export and deletion automation are not available in this pilot. This pilot does not include guaranteed response times.

Requests are handled manually by the founder-operated pilot team.

Get pilot support

What is not available yet

Full trust center automation is planned for GA. That includes self-serve data export, automated account deletion, automated privacy request handling, and a public status page.

A public status page is not part of this pilot, and learning content is under review before pilot use.

This page is a pilot notice for the controlled pilot. It explains the current posture honestly; it is not legal advice.

Return to your Learning Workspace Get pilot support