Public beta application

Privacy and application terms

These are the versions referenced by the `20260724` Telegram application manifest. Acceptance is recorded only inside the application flow.

PSB_PUBLIC_PRIVACY_2026-07-24_V2

Privacy notice

Stage one collects a chosen alias, US residency and age-21-or-older attestations, up to three choices from the current versioned testing-category list, an availability band, a feedback-strength response, one testing scenario, and versioned acceptance timestamps. Choosing “Something else” may add one short explanation. It does not request a birth date or address. No other demographic, outreach, or public-account questions are part of this path.

Telegram supplies the bot a stable numeric user ID and public profile fields. Project ShadyBot derives a keyed identity index and encrypts the contact mapping with AES-256-GCM. Review queues, reviewer records, exports, admin notifications, and plaintext logs exclude raw Telegram user IDs, chat IDs, and public profile fields.

Application answers and beta feedback are not used as model-training data under these terms. If Project ShadyBot later proposes using submissions as model-training data, that use will require separate explicit consent before it begins.

One completed stage-one application is allowed per Telegram identity. Pending and waitlisted applications may be retained for review for up to 12 months. A waitlist position promises no invitation or timeline. Withdrawal, rejection, or final non-selection schedules encrypted contact and free-text deletion within 30 days; the current implementation deletes them immediately when the decision is recorded. A non-identifying audit tombstone may remain for up to 12 months.

Use `/status` to check the application and `/withdraw_application` to withdraw from the same Telegram identity.

PSB_PUBLIC_CONDUCT_2026-07-24_V1

Conduct rules

Applicants and testers must protect other participants' aliases and project-sensitive information, submit truthful testing evidence, avoid harassment and manipulation, follow safety instructions, and report privacy or security concerns through the official channel. Testing must not require unlawful conduct, credential sharing, financial transactions, or real-money activity.

PSB_PUBLIC_UNPAID_BETA_2026-07-24_V1

Unpaid beta terms

The application and beta are unpaid. The beta has no fixed public end date. Applying or participating does not create employment, compensation, equity, membership, appointment, continued access, a result, or a promise of future selection. Applications, invitations, or participation may be paused or ended under the approved conduct, privacy, safety, and capacity rules.

PSB_PUBLIC_APPLICATION_AGREEMENT_2026-07-24_V1

Stage-one application agreement

By replying `I ACCEPT` in stage one, the applicant confirms the eligibility attestations are truthful, the submitted material may be reviewed for beta selection, the privacy notice and conduct rules are accepted, the application is unpaid, and no membership, appointment, or access is created. Human scores prioritize review only and never appoint automatically.

PSB_PUBLIC_STAGE_TWO_AGREEMENT_2026-07-24_V1

Stage-two agreement

A shortlisted applicant has seven days to provide sanitized experience, generic device and platform categories, one lane-specific test plan, a cadence acknowledgement, and final acceptance. Stage-two selection produces `selected_pending_release` only. It sends no invitation; appointment remains a separate owner action behind signed live/access gates and the active-member cap.

Return to the application gateway