Policy

Privacy Policy

This policy explains how Global account, profile, job, application, message, order, and verification data is handled in the Global deployment.

Data separation

Global and China are independent deployments with separate databases, files, storage namespaces, logs, payment credentials, support rules, and admin accounts.
The active region is fixed at process startup and is not selected by host, headers, cookies, query strings, or user input.
Global production starts from its own baseline data and does not import China production business data.

Login identifiers, company membership details, profile fields, resumes, case studies, jobs, applications, messages, orders, verification materials, and support requests are collected when users create or use those flows.
Operational records such as audit events, review decisions, entitlement grants, safety reports, and admin actions support platform operation and risk handling.
Payment-related data is limited to what is needed for checkout, order tracking, entitlement grants, support, and reconciliation.

Login identifiers, company membership, jobs, applications, conversations, orders, and audit records support account access, hiring workflows, payments, safety, and support.
Builder profiles, resumes, case studies, and private details are shown according to visibility and access rules.
Company verification materials are used for workspace-level trust review and are not public profile content.

Data is retained as needed for hiring workflows, verification, payments, safety review, support, compliance, and dispute handling.
Resume details, contact information, company verification materials, order data, and account-security information are restricted by role and permission.
Access controls, login checks, audit records, and review workflows reduce unauthorized access risk, though necessary records may remain after account closure where rules require retention.

Public visitors can see public profile, company, job, and approved case-study information according to each page's visibility rules.
Verified company context and business relationship signals can unlock fuller Builder information such as resume or private profile details.
Sensitive data is not shared with unrelated third parties except where required for service delivery, risk handling, legal obligations, or user authorization.

Users can contact support to request correction, export, deletion, or account closure for relevant account data.
Requests should include the account email, role, related page links, and enough context for identity and ownership checks.
After verification, support handles the request where allowed; necessary compliance, safety, payment, or dispute records may be retained as required.

Continue only if you accept the rules. If unsure, contact support first.

If you accept the collection, use, visibility, and access rules, continue with registration or data submission.

If deletion, export, account closure, or data boundaries are unclear, contact support before submitting more data.

This policy explains how Global account, profile, job, application, message, order, and verification data is handled in the Global deployment.

Global and China are independent deployments with separate databases, files, storage namespaces, logs, payment credentials, support rules, and admin accounts.
The active region is fixed at process startup and is not selected by host, headers, cookies, query strings, or user input.
Global production starts from its own baseline data and does not import China production business data.

Login identifiers, company membership details, profile fields, resumes, case studies, jobs, applications, messages, orders, verification materials, and support requests are collected when users create or use those flows.
Operational records such as audit events, review decisions, entitlement grants, safety reports, and admin actions support platform operation and risk handling.
Payment-related data is limited to what is needed for checkout, order tracking, entitlement grants, support, and reconciliation.

Login identifiers, company membership, jobs, applications, conversations, orders, and audit records support account access, hiring workflows, payments, safety, and support.
Builder profiles, resumes, case studies, and private details are shown according to visibility and access rules.
Company verification materials are used for workspace-level trust review and are not public profile content.

Data is retained as needed for hiring workflows, verification, payments, safety review, support, compliance, and dispute handling.
Resume details, contact information, company verification materials, order data, and account-security information are restricted by role and permission.
Access controls, login checks, audit records, and review workflows reduce unauthorized access risk, though necessary records may remain after account closure where rules require retention.

Public visitors can see public profile, company, job, and approved case-study information according to each page's visibility rules.
Verified company context and business relationship signals can unlock fuller Builder information such as resume or private profile details.
Sensitive data is not shared with unrelated third parties except where required for service delivery, risk handling, legal obligations, or user authorization.

Users can contact support to request correction, export, deletion, or account closure for relevant account data.
Requests should include the account email, role, related page links, and enough context for identity and ownership checks.
After verification, support handles the request where allowed; necessary compliance, safety, payment, or dispute records may be retained as required.

Continue only if you accept the rules. If unsure, contact support first.

If you accept the collection, use, visibility, and access rules, continue with registration or data submission.

If deletion, export, account closure, or data boundaries are unclear, contact support before submitting more data.