Beta Privacy Notice

We collect beta access requests, account details, professional profile information, project facts, company reviewer email addresses, reviewer verification responses, public proof settings, reference request submissions, audit events, and operational logs needed to run and secure the service.

We use this data to review beta access, authenticate users, create project records, send verification links, show only approved public proof, route reference requests to the professional first, prevent abuse, and support beta operations.

Public profiles show only fields that a company reviewer approved for sharing and that the professional chose to publish. Raw project notes, reviewer contact details, OTP tokens, and private request metadata are not shown on public proof pages.

When a prospect submits a reference request, the request is stored for the professional to review. The company reviewer is not contacted directly by the public form, and reviewer contact details are not exposed to the requester.

During beta, JISSEKI may use infrastructure and email providers to host the product, store data, deliver transactional messages, and monitor reliability. We do not sell personal data.

Beta data is retained while the workspace is active and while it is needed for audit, security, or product operations. A participant may request deletion through the beta invitation channel, subject to legal, security, and audit constraints.

The beta uses authenticated workspaces, row-level access rules, scoped reviewer sessions, hashed verification tokens, audit events, and limited public fields. No beta system should be treated as a substitute for a signed contract, NDA, or formal reference agreement.