Contact and corrections

In-Product Closed Beta feedback

Active invited candidates can use Closed Beta feedback for product and technical feedback, content/source corrections, accessibility barriers, and a minimal privacy, security, or safety observation. That channel creates a timestamped, owner-scoped receipt, shows Founder triage and responses. Operational visibility ends and the case becomes purge-due at 30 days; content and the owner link are redacted only when the Founder runs the due-case purge and receives its receipt.

It does not accept attachments, screenshots, query strings, referrers, user-agent data, active exploit details, another person's data, legal process, emergency reports, urgent-harm escalation, or statutory-rights requests.

Requests outside Beta feedback

This link opens a draft in your email application for a request that does not belong in the in-Product Beta feedback queue. Staff.Zone does not submit, store, timestamp, or acknowledge an email request from this page. There is no verified delivery receipt or cleared response-time commitment for this external channel.

Account and private-data requests

A currently signed-in, email-confirmed, nonanonymous user can open the private-data request workflow, even when Closed Beta admission is missing, scheduled, expired, suspended, or revoked. It records a bounded technical request receipt and later operational state or outcome. It is not proof of statutory acceptance, compliance, a lawful basis, or completion of a rights action.

Existing invited users should first use the owner-scoped controls in Candidate account:

• profile and search-preference JSON exports;
• mobility-profile deletion;
• work-right answer and evaluation-history deletion; and
• search-preference deletion.

For an access/export, correction, deletion, restriction, or objection request, use the technical request workflow. If you cannot authenticate, email preview-feedback@staff.zone with the subject shown by the link. Email still provides no verified in-Product delivery receipt.

Current limitation: there is no self-service deletion of the authentication identity or complete account bundle. Auth-user deletion requires separately authorized operator access and an identity-verification process outside this workflow. Submitting either path is not proof that an action was accepted or completed.

Content or source correction

Active Closed Beta candidates should normally submit a minimal content/source observation through the in-Product queue. Use email preview-feedback@staff.zone only when the report needs an external source link or a safer follow-up. Distinguish a content correction from a request about private account data.

A report does not silently rewrite historical evidence or create a legal finding. Review, supersession, withdrawal, and any affected-user action remain separate governed steps.

Accessibility or security concern

An invited candidate can record an ordinary accessibility barrier or a minimal non-sensitive security/safety observation in Closed Beta feedback. Email preview-feedback@staff.zone when a report needs a safer conversation. Do not include exploit details that expose another person's data; start with the minimum affected route, environment, and observed behavior.

Emergency, urgent harm, and legal process

Neither the in-Product queue nor this technical email draft is an emergency service, urgent-harm response line, law-enforcement channel, or accepted legal-service address. Use the appropriate local emergency service or separately cleared legal/statutory process. Do not wait for a Beta feedback response when immediate safety is at risk.

Send the minimum

• Use only an approved synthetic test-account email or stable Preview record identifier.
• Never send passwords, one-time codes, session links, secrets, passports, or immigration documents.
• Do not send another person's data.
• For a page issue, prefer the route and public record identifier over screenshots containing private context.

Review boundary

This contact draft does not replace a statutory-rights, complaint, urgent-harm, breach, fraud, takedown, or qualified legal process. Operational ownership, identity verification, escalation, retention, service levels, and jurisdiction-specific notices must be cleared before processing real-user requests.