XPEACH Unified Pass and Site Cluster Privacy Policy
Updated: October 31, 2026 Effective Date: October 31, 2026
XPEACH (including its core brand 🍑Code and client product XPeach Harness) is a unified identity authentication center, artificial intelligence model interface aggregation and forwarding, AI programming agent workbench and associated digital service cluster (hereinafter referred to as "this platform") independently operated by individuals. The core entrance includes XPEACH Unified Pass Center (https://sso.xpeach.codes), 🍑Code Main site and acceleration gateway (https://xpeach.codes, https://fast.xpeach.codes, https://ultrafast.xpeach.codes), XPeach Harness Agent Programming Workbench (xph) and via OpenID Connect (OIDC) / OAuth 2.0 Access the official subsites of the cluster.
This privacy policy aims to clearly and transparently explain to you: when you register or log in to the XPEACH unified pass, use web single sign-on or device flow (Device Flow) to authorize access to cluster subsites and XPeach Harness clients, configure multi-factor authentication (Passkey/TOTP), recharge or transfer peaches (🍑) and platform tokens, create APIs Key, how the platform operator (hereinafter referred to as "we") collects, uses, stores, synchronizes across sites, shares and protects your relevant information when using the agent tool chain to call the model interface or contact customer support, as well as the data storage and privacy boundaries of the XPeach Harness client on your local machine.
When you register for a pass, run XPeach Harness or use any site service on this platform, you are deemed to have read and understood this Privacy Policy.
1. Scope of application and regional restrictions
-
Scope of application: This privacy policy applies uniformly to the XPEACH unified pass center (
sso.xpeach.codes), 🍑Code main station and multi-line gateway (xpeach.codes/fast.xpeach.codes/ultrafast.xpeach.codes), XPeach Harness client (including Desktop desktop, Web workbench, Headless CLI and SDK), official sub-sites of the cluster, management console, API interface and customer support services. -
Third-party services and plug-in boundaries: This privacy policy does not apply to upstream artificial intelligence model service providers (such as OpenAI, Anthropic, Google, DeepSeek, etc.) independently operated by third parties, third-party payment institutions (such as Stripe, Aidenfa, etc.), third-party joint login platforms (such as GitHub, Google, LinuxDO, Discord, etc.), nor does it apply to third-party MCP (Model Context Protocol) servers and external websites that you install or connect to XPeach Harness. Such third parties will process information independently in accordance with their respective published privacy policies.
-
Service area restriction statement: This platform, the full cluster site and the XPeach Harness client do not provide services to the mainland of the People's Republic of China (excluding Hong Kong, Macao and Taiwan). Users located in mainland China should not register for a pass, download and run the client, submit any personal information or use the services of this platform.
2. Types of personal information we collect and process
Following the "minimum necessary" principle, we may collect and process the following categories of information based on the functions you actually enable, the client form you use, and the cluster sites you visit:
1. Unified pass core account information
When you register for or manage an XPEACH pass, we collect or generate:
- Universally Unique Identifier (UUID): A 16-bit immutable account primary key in the format of
****-****-****-****automatically generated by the system, used to uniquely identify you across sites and clients; - Basic account information: user name (converted to lowercase for standardized storage), display nickname, avatar URL;
- E-mail information: Bind email address, email verification status and verification completion timestamp;
- Password Hash: Password digest processed by a high-strength one-way cryptographic hashing algorithm and salted. This platform will never store or record your login password in clear text;
- Cross-site invitation relationship information: the unique cross-site invitation code (
aff_code) assigned to you by the system, the UUID of the superior user who invited you (inviter_user_id), the invitation source site short code (invited_from_site) and the binding time; - Account status record: account status (normal
active/ deactivateddisabled), number of consecutive failed logins, temporary lock expiration time, registration time and latest login time.
2. Multi-factor authentication (MFA) and passkey information
When you turn on advanced security for your pass, we handle:
- TOTP dynamic password data: TOTP shared key stored with AES-256-GCM symmetric encryption, activation time, highest used time step (
last_used_step) to prevent replay attacks, and one-time recovery code stored with one-way hash; - WebAuthn/Passkey pass key data: Credential unique identifier (
credential_id), asymmetric encryption public key (public_key), signature anti-clone counter (counter), transmission channel attribute (transports), device type tag (single device/multi-device synchronization) and your customized pass key name; - Biometric Privacy Commitment: When you use your device's fingerprint (Touch ID), face (Face ID) or Windows Hello to unlock Passkey, all biometric comparisons are strictly completed within the security hardware chip (Secure Enclave/TPM) of your local device. This platform will never collect, access, transmit or store any of your original biometric information.
3. Third-party federated identity binding information (Federated Identities)
When you actively choose to bind your XPEACH pass to or log in through an external identity provider such as GitHub, Google, LinuxDO, Discord, Cloudflare Access, etc., we will collect based on your authorization scope on the external platform:
- The name of the external platform (
provider) and your unique account identification on the platform (provider_account_id); - The email address and email verification status returned by the external platform;
- Summary of public basic information (such as nickname, avatar URL);
- Federated binding credentials stored with AES-256-GCM encryption, along with binding and recency times.
4. Single Sign-On (OIDC), OAuth 2.0 Device Flow and XPeach Harness Credential Bridging Information
When you use an XPEACH pass to log into a cluster subsite or authorize an XPeach Harness(client_id: xpeach-harness) client, the system handles:
- OIDC and device flow session records: interactive session identification, 8-digit device authorization code (User Code), device flow status (
DeviceFlowrecord stored via SHA-256 hash), access token (Access Token), refresh token (Refresh Token) and authorization scope (such asopenid,profile,email,offline_access,peachcode:credentials); - 🍑Code Credential Bridge Data (Harness Credential Bridge): When you confirm the authorization of XPeach Harness, SSO will automatically open or associate the 🍑Code site account for you, and bridge to generate or synchronize your site user ID and model group (such as
SWE,GPT|Standard,Claude|Standardetc.), total quota and used quota, system access token (Access Token) and exclusivesk-transit key metadata; - Cross-site user integration data (
user_site_data): Each sub-site business configuration, role membership, and sub-site synchronization keys or tokens stored with AES-256-GCM encryption bound to your UUID.
5. API call and model service usage information
When you call the artificial intelligence model interface on the 🍑Code main site, cluster subsite, or through XPeach Harness, we will record:
- API Key internal identification, call initiation time, selected gateway line (main station/high speed/express), interface path and request method;
- The name of the called model, the model group it belongs to, the input/output token consumption quantity, the number of requests, peach (🍑) or platform token deduction details;
- Request response status code, first word and total processing time, error code, client identifier (such as
XPeach Harness,PeachCode CLIor desktop browser type); - Rate Limit trigger records, content security risk control detection results, and upstream routing channel information.
6. Model interaction content submitted by users
- The prompts (Prompts), dialogue context, system rules (Rules), skill instructions (Skills), code snippets, file patches, multi-modal pictures/documents and tool call return results (Tool Outputs) that you actively send to the model gateway in the web page, API interface or XPeach Harness dialog box, as well as the response content generated by the model;
- In order to complete your inference request, the above content sent to the gateway will be forwarded to the corresponding upstream artificial intelligence model service provider via routing.
7. Transaction, billing and cross-site Peach (🍑) ledger information
When you recharge, daily check-in, CDK redemption, cross-site transfer or consumption, we will collect and record:
- Order and payment flow (
billing_transactions): payment source channel (such as Stripe, iPower, Cloud Cat, etc.), platform order number, payment channel event ID and transaction object identification, recharge amount, currency, settlement exchange rate, channel handling fee, platform peach (🍑)/token change quantity, package name and payment status; - Cross-site peach ledger flow (
site_peach_ledger): event unique key, source site and target site short codes, transaction direction (recharge/deduction/synchronization), event category (central recharge, CDK write-off, model consumption, subscription deduction, cross-site synchronization), quota balance before and after changes and timestamp; - Rejection, Refund and Dispute Records: Related records involving transaction disputes, malicious chargeback or accounting error correction;
- Payment Card Security Statement: Your complete bank card number, expiration date, CVV/CVC security code and payment password are collected and processed directly by a licensed third-party payment processor. Unless otherwise explicitly stated on a specific page, this platform will not collect or store your complete bank card number and security code.
8. Device, network and security audit logs
When you visit this platform's web page, console, or connect to the server through XPeach Harness, the system will automatically collect:
- Network and device parameters: IP address, operating system type and architecture (such as macOS arm64/x64, Windows x64, Linux x64, iOS, Android, HarmonyOS or CLI terminal), client version number, interface language preference and access time;
- Security audit log (
audit_logs): Pass key security operation records (such as login, device flow authorization, bridge issuing credentialspeachcode.credentials.issued, logging out of the device, changing passwords, binding/unbinding third-party identities, enabling/resetting MFA, registering Passkey), including operator UUID, action type, target object, IP address and User-Agent; - System delivery and synchronization log: System security notification email delivery status log (
mail_logs) and cross-site cloud synchronization execution log (cloud_sync_logs); - Anti-Fraud and Regional Compliance Signals: Approximate country/region information based on IP address resolution (used to enforce service restrictions in mainland China) and non-invasive human verification risk scores such as Cloudflare Turnstile. We do not actively request or collect your device’s precise GPS geographic coordinates.
9. Customer support and complaint communication information
When you contact us via email, GitHub Issues or other channels for technical support, accounting verification or risk control review, we will collect your contact email, problem description, screenshots provided, error logs, relevant request ID or order number, and communication records between the two parties.
3. XPeach Harness client local storage, tool calling and asset migration privacy instructions
In order to fully protect developers' control over local code and workspace data, XPeach Harness (xph) adopts a "local first, explicit transmission" privacy architecture design:
-
Local independent directory and
0600minimum privilege isolation (~/.xph):- XPeach Harness stores all running data independently in the
~/.xphdirectory under the user home directory of your local operating system, completely isolated from other tools on the machine; - Your local historical session records (
~/.xph/sessions/) and global configuration (~/.xph/settings.yaml) are saved on the local disk; - Sensitive credential files related to account security—including SSO session credentials (
xpeach.sso.json), site system access tokens (xpeach.admin), exclusive transit keys (xpeach.key), multi-key slot and token grouping metadata (xpeach.keys,xpeach.token), and three-line speed test status (xpeach.route.json)—are stored in~/.xph/profiles/xpeach/, and use process-level temporary files with0600permissions (only the current operating system user can read and write) atomic write to disk.
- XPeach Harness stores all running data independently in the
-
Execution boundaries between local code base and tool chain:
- When you use file reading and writing (
fs), terminal commands (shell), code diagnosis (lsp) or desktop/browser automation tools in XPeach Harness, the relevant operations are performed on your local machine; - Except for text/code snippets that you actively send or authorize the agent to read and send to the 🍑Code model gateway as a model inference context (Context) in the current dialogue task, XPeach Harness will never silently scan, package or upload irrelevant source code repositories, private files or system environment variables on your local hard disk to the XPEACH server in the background.
- When you use file reading and writing (
-
Local read-only import of third-party AI programming tool assets:
- When you use XPeach Harness's first startup wizard or the "one-click import of native assets" function in the settings center, the client will scan the local configuration directory of installed tools such as Claude Code, Codex, Gemini CLI, Antigravity, ChatGPT or DeepSeek Harness on the machine;
- The scanning and import process is completed in a read-only, one-way manner in your local computer memory. Only the historical conversations, Skills skill packs, Rules rules and MCP configurations you selected are copied and moved into the local
~/.xphdirectory. The original tool data will not be modified, and the imported historical records will not be automatically uploaded to the cloud server.
-
Three-line delay speed test and forced update check:
- In order to realize multi-line intelligent optimization, the client will send lightweight probing and speed measurement requests to the main station (
xpeach.codes), high-speed (fast.xpeach.codes) and express (ultrafast.xpeach.codes) nodes in the background, and save the delay statistics in the localxpeach.route.json; - During startup and operation, the desktop client will connect to the update service to check the version number and security mandatory update policy signature. This process only transmits the client version number, operating system platform architecture and basic connection status.
- In order to realize multi-line intelligent optimization, the client will send lightweight probing and speed measurement requests to the main station (
-
Controlled device logout and local credential erasure:
- When you click to log out on the client (supports "log out current device only" or "revoke all devices under one click and reset token"), or when the server returns an account ban (
403)/token invalidation (401) signal, the client will immediately clean up the sensitive token file under the local~/.xph/profiles/xpeach/and write it to.xpeach-signed-outSentinel flag to ensure that logged-out credentials are never automatically restored in the background.
- When you click to log out on the client (supports "log out current device only" or "revoke all devices under one click and reset token"), or when the server returns an account ban (
4. How we use information
We strictly use the server-side information collected for the following legitimate and clear purposes:
- Create, verify, maintain and manage your XPEACH unified pass and global UUID;
- Implement OIDC single sign-on, OAuth 2.0 device flow authorization and XPeach Harness credentials automatic bridging across cluster subsites;
- Provide password verification, Passkey passwordless authentication, TOTP dynamic password verification and third-party joint identity login services;
- Provide artificial intelligence model API interface access, multi-line intelligent routing, request forwarding and high-availability switching services;
- Create, verify, group switching, rotation, current limit and revoke API Key and client bridge credentials;
- Accurately calculate the Token usage when calling the model, process recharge orders, issue sign-in rewards, write off CDK, maintain cross-site peach (🍑) ledgers and perform cross-site quota synchronization;
- Identify and intercept credential stuffing attacks, credential stuffing, malicious crawlers, interface abuse, invitation cheating and abnormal concurrent requests;
- Investigate, defend and handle payment fraud, theft and malicious chargeback disputes;
- Enforce service area restrictions (identify and block illegal access and registration from mainland China);
- Run automated sensitive word filtering, content security review and violation risk control;
- Send email verification codes, password reset links, new device login reminders, account status changes and important system notification emails;
- Troubleshoot gateway routing failures, provide XPeach Harness desktop version update verification, check abnormal bills and optimize system response performance;
- Respond to your customer support inquiries, data rights requests and risk control manual review applications;
- Fulfill obligations stipulated by applicable laws such as financial accounting, tax declarations, and network security audits;
- Establish, exercise or defend the legitimate legal rights of this platform and users;
- Analyze cluster traffic and service quality based on de-identification, anonymization or summary statistics.
Special Commitment Regarding AI Model Training: The operator of this platform will never actively use the prompts (Prompts), local code snippets, documents or model response content you submit through web pages, APIs or XPeach Harness to train the operator's own general artificial intelligence basic model. As for whether the upstream third-party model supplier will retain the interface data for security audit or model improvement, it depends on the terms of service and privacy policy of the corresponding API interface of the upstream supplier.
5. Cross-site data transfer and cluster internal synchronization mechanism
Since XPEACH adopts the cluster architecture of "unified pass + multi-site gateway + client workbench", in order to achieve "one login for the entire cluster" and "peaches (🍑)/limits for cross-site use", your necessary information will be safely transferred within the cluster according to the following mechanism:
- Single Sign-On (SSO) with Device Streaming Standard Claims Delivery: When you are authenticated by XPEACH SSO at a cluster subsite or XPeach Harness client, SSO will pass your global
UUID(sub), username, display nickname, verified email, role permissions, cross-site invitation code (aff_code) and bridgedsk-to the target site/client through an encrypted token or internal bridge interface key. - Webhook and real-time ban awareness linkage: When you change your password, unbind your identity, change your email address, revoke your device in SSO, or when your account is disabled due to violations, XPEACH SSO will notify each cluster subsite and the online XPeach Harness client through the outbound Webhook and gateway status synchronization mechanism with HMAC-SHA256 encryption signature, and immediately revoke the associated session and API Key.
- Edge node and distributed database synchronization: In order to improve global access speed and cross-site authentication high availability, this platform may synchronize desensitized or encrypted pass snapshots, permission configurations and cross-site Taozi (🍑) ledger data to controlled edge storage nodes such as Cloudflare D1 / Workers KV.
6. Content security detection and risk control log review
- The gateway of this platform will conduct automatic security scanning of the request parameters, call frequency and content characteristics transmitted through the interface.
- When a high-risk sensitive word, illegal attack load, or anti-abuse rule is hit, the system will automatically record the risk event and perform operations such as interception, flow restriction, API Key suspension, or pass ban.
- Minimize manual review principle: In daily operations, we will not manually spy on users' normal conversations or code content one by one. The operator will review relevant request logs or ledger records to a minimum extent only under the following truly necessary circumstances:
- Users actively initiate work orders or emails, requesting troubleshooting interface errors, abnormal bill deductions, or review of incorrect application seals;
- The system triggers a serious security alarm (such as suspected crimes, hacker attacks, key leakage and abuse, or violations reported by upstream model vendors);
- In the event of a malicious chargeback or transaction fraud, evidence of the call must be extracted and submitted to the payment institution or judicial authority.
7. Legal basis for processing personal information
According to the applicable data protection laws in your jurisdiction, we process your personal information mainly based on one or more of the following legal bases:
- Necessary for the performance of the contract: To provide you with the XPEACH pass registration, single sign-on, XPeach Harness device flow credential bridging, model API forwarding, CDK redemption and cross-site peach (🍑) settlement services you have requested;
- Legitimate and legitimate interests: To ensure cluster system and network security, prevent fraud and malicious chargebacks, prevent interface abuse, enforce regional compliance restrictions and troubleshoot technical failures;
- Perform legal obligations: To comply with financial bookkeeping, tax compliance, anti-money laundering or respond to legal requirements from judicial and regulatory agencies with jurisdiction;
- Your explicit consent: Processing based on your active authorization when binding third-party joint identities, confirming device flow authorization, enabling specific security functions, or other scenarios where consent is required by applicable law (you may withdraw your consent at any time, but this will not affect the legality of processing based on consent before the withdrawal).
8. How we share and disclose information
We keep your personal information strictly confidential and never sell, rent or trade your personal information to any third party for their own commercial marketing purposes. We will share necessary information with relevant parties only when necessary to provide services or required by law:
- Upstream Artificial Intelligence Model Service Provider: In order to execute your API or XPeach Harness model call request, the prompt words, code context, multi-modal files and model parameters you submit will be forwarded to the upstream model provider you specify or route matches (these providers may be located in different countries or regions such as the United States, Europe, Singapore, Japan, etc.).
- Cloud and edge infrastructure service providers: We use trustworthy third-party infrastructure providers to host cluster operations, including cloud server hosts, PostgreSQL/MySQL database service providers, Cloudflare (CDN, Turnstile human-machine verification, D1/KV edge storage) and transactional email sending service providers (SMTP/Resend, only used to send verification codes and security notifications).
- Third-party payment and anti-fraud service providers: When you initiate a recharge or have a payment dispute, the relevant order number, amount, email, IP address and transaction verification information will be processed by payment service providers such as Stripe, Aipower, and Cloud Cat and their risk control systems. In the event of a malicious chargeback, we provide the necessary login, device flow authorization and call audit records to the payment channel to combat fraud.
- Third Party Federated Identity Provider: When you actively use GitHub, Google, LinuxDO, Discord, etc. for OAuth login, your browser will interact directly with the provider to complete identity verification.
- Statutory disclosure and security protection: When receiving a court summons, judicial ruling, or order from a law enforcement agency with competent jurisdiction, or to prevent ongoing cyber attacks, serious fraud, or violations of public security, we may disclose the minimum necessary information in accordance with the law on the premise of carefully verifying the validity of the legal document.
- Project migration or change of operating entity: If the XPEACH cluster undergoes technical architecture reorganization, service migration or operation rights transfer, your pass and account data may be transferred to the undertaking party to the extent necessary to ensure service continuity, and will continue to be subject to this privacy policy or equivalent protection standards.
9. Cross-border data transmission
- The server nodes, multi-line acceleration gateways, edge networks, databases, payment channels and upstream artificial intelligence model service providers of the XPEACH cluster are distributed in many different countries or regions around the world.
- When you access this platform, run XPeach Harness, or make an API request, your information may be transferred to jurisdictions outside your country or region for processing and storage.
- We will ensure data security during cross-border transmission through full-link HTTPS/TLS encrypted transmission, origin and redirection whitelist verification, AES-256-GCM encrypted storage of sensitive fields, and strict supplier screening mechanisms.
10. Information retention period and data cleaning
- We will only store your personal information on the server side for the period necessary to achieve the purposes stated in this privacy policy, or for the period required by applicable laws and regulations.
- The specific retention principles for various types of data are as follows:
- Pass core information, UUID, MFA credentials and cross-site binding data: will be continuously saved during the duration of your XPEACH pass until you actively cancel your account or the account is cleared according to law;
- Recharge orders, transaction bills and cross-site peach (🍑) ledger flow: In order to meet the requirements of financial accounting, chargeback defense, taxation and dispute resolution, after the transaction is completed, it will be retained in accordance with the business record retention period required by applicable laws;
- API call statistics and security audit logs (
audit_logs/mail_logs): Save within a reasonable period required to complete billing verification, troubleshooting, security backtracking and anti-fraud analysis, and automatically rotate and overwrite or archive and clean after expiration; - Short-term tokens, device flow challenges and verification data: Email verification tokens, password reset tokens, OAuth 2.0 device flow verification codes (
DeviceFlow) with a 10-minute validity period, WebAuthn challenge values, TOTP login challenges and expired sessions will be automatically cleared by the system after expiration or consumption; - Client local data (
~/.xph): Saved on the local disk of your personal computer, you can control the retention or physical deletion at any time.
- When server-related information exceeds the necessary retention period, we will physically delete it or make it irreversibly anonymized. Due to the limitations of the encrypted cold backup mechanism, deleted data may be retained in controlled offline backup archives for a short period of time until the backup cycle is naturally overwritten, during which it will not be used for any daily business processing.
11. Cookies, session tokens and local storage
- In order to ensure the normal operation of single sign-on and console on the web page, the web page of this platform uses strictly necessary cookies and browser local storage technology (LocalStorage). The main purposes include:
- Core Identity Session Persistence: Save XPEACH SSO login session cookies and OIDC interaction status cookies, so that you do not need to re-enter your password every time you jump to a page or authorize a subsite;
- Security Protection: Stores CSRF (Cross-site Request Forgery) defense token, WebAuthn session challenge ID and human-computer authentication status;
- Interface and Language Preference: Remember the interface language you selected (such as Simplified Chinese, Traditional Chinese, English, Japanese, etc.) and theme display preferences.
- In the XPeach Harness desktop and CLI, the login status and configuration are persisted through protected files (
0600permissions) in the local~/.xphdirectory. - This platform and client do not embed any third-party commercial advertising tracking cookies or advertising SDK, nor will they track your personal browsing habits through cross-site advertising alliances.
12. Information security protection measures
We attach great importance to the security of pass, client and cluster data, and have adopted multi-level technical and management protection measures:
- High-strength encryption of passwords and keys: User login passwords are stored using an irreversible salted hash algorithm; TOTP keys, third-party OAuth binding tokens, subsite synchronization keys, SMTP keys, and financially sensitive fields are all encrypted and stored using the AES-256-GCM algorithm; API Keys, session tokens, and device flow codes only store SHA-256 digest hashes in the database;
- Modern authentication and bridge protection: OIDC single sign-on is forced to enable the PKCE anti-authorization code hijacking mechanism by default; OAuth 2.0 device flow implements strict HTTPS / Loopback origin whitelist verification and rate limitation; cluster cross-site Webhook communication uses HMAC-SHA256 signature verification; supports anti-phishing FIDO2 / WebAuthn Passkey authentication;
- Client process sandbox and minimum permission placement: XPeach Harness enforces
0o600permission atomic replacement writing on local credential files, and provides cross-platform process sandbox support for tool execution; - User’s own security responsibility: The Internet and local software environment cannot guarantee 100% absolute security. Please be sure to use a strong and unique password, actively enable Passkey or TOTP two-step verification, properly protect the local
~/.xphdirectory permissions, carefully review commands proposed by the agent, and never expose your API Key in public repositories.
13. Users should avoid submitting sensitive information
To reduce your own data compliance and security risks, unless legally authorized and necessary, please do not include the following high-risk sensitive information in model prompts (prompts), conversation content, uploaded files, or workspaces authorized to be read by XPeach Harness:
- Your or other people’s clear text account password, undesensitized
.envproduction key, API Key, OAuth Token, Session Cookie; - Cryptocurrency wallet private key, mnemonic phrase (Seed Phrase) or hardware key seed;
- Complete bank card number, CVV/CVC security code, online banking password;
- Original or number of legal identity documents such as ID card, passport, driver's license, social security card;
- Personal biometric raw data, genetic data or detailed medical records;
- Undisclosed core business secrets, closed source code strictly bound by non-disclosure agreement (NDA);
- Any third-party personal privacy data without the legal authorization of the rights holder.
You are solely responsible for any data leakage or compliance risks caused by you actively submitting to the model interface or authorizing the agent to read the above information.
14. Your rights to personal information and how to exercise them
In accordance with applicable data protection laws, you have the following rights with respect to your personal information:
- Self-service query and management: You can log in to https://sso.xpeach.codes/portal personal pass center, each sub-site console or XPeach Harness setting center at any time to directly check your UUID, user name, bound email, cross-site invitation code (
aff_code), current active session, bound third-party identity, Passkey list, TOTP Status and peach (🍑)/token bill flow; - Self-service corrections, device revocation and security operations: You can self-modify display nicknames, change passwords, change verification emails, add or delete Passkeys, reset TOTP two-step verification, and unbind third-party platform accounts in the Pass Center. You can also revoke authorized devices, reset bridging tokens, or directly delete the local
~/.xphdirectory at any time in XPeach Harness with one click; - Application for access, export or processing restriction: For personal information query, copy export, restriction processing or consent withdrawal request that cannot be completed by yourself through the console, as well as manual review application for automated risk control interception results, you can submit an application by sending an email to xpeachcodes@gmail.com;
- Identity verification and response restrictions: In order to prevent others from impersonating or maliciously tampering with your data, we may ask you to verify your pass identity before processing your email request. We are legally unable to respond immediately to deletion requests for records that are involved in legal financial retention obligations, anti-fraud investigations, bad faith chargeback defenses, or open disputes.
15. Pass cancellation and full cluster account deletion
- You can apply to cancel your XPEACH unified pass by contacting the official email.
- Consequences of coordinated logout between the entire cluster and the client: Since the XPEACH pass (UUID) is your only underlying identity basis at all sites in the cluster and the XPeach Harness client, once you log out of the XPEACH pass, the effect will be synchronized to all sites and client instances in the entire cluster:
- You will permanently no longer be able to log in to XPEACH SSO, 🍑Code main site, any cluster subsite and XPeach Harness;
- The API Keys, OAuth tokens, device flow bridge credentials, Passkeys and third-party identity bindings you create on all subsites will all become invalid immediately;
- Your personally identifiable information on the server will be deleted or irreversibly anonymized (except for financial bills, tax vouchers, anti-chargeback evidence and security audit records that are required to be retained by laws and regulations).
- Non-refundable reminder: Actively applying to cancel the pass does not constitute any reason for recharge refund or credit discount. After the pass is cancelled, the unconsumed peaches (🍑), platform tokens, CDK quota and unexpired subscription rights in the account and each sub-site will be automatically voided and cleared, and will not be refunded or exchanged for cash (unless otherwise mandatory provisions of applicable laws).
16. Protection of minors
- This platform, full cluster service and XPeach Harness client are only open to adult users who are over 18 years old (or have reached the age of full civil capacity as stipulated by local laws).
- We will not knowingly and actively collect personal information from minors. If you are the guardian of a minor and find that your ward has registered for an XPEACH pass or submitted personal information without consent, please contact us immediately via xpeachcodes@gmail.com. After verification, we will promptly close the relevant account and clean up the relevant data.
17. Description of third-party websites and external services
This platform page, documentation or XPeach Harness extension center may contain links to third-party websites, MCP server repositories, upstream model official documentation, payment checkout or joint login pages. These external sites and third-party plug-ins are independently operated by the corresponding third parties and are not controlled by this platform. We are not responsible under any circumstances for the security of the content of third-party websites or plug-ins and their personal information processing activities.
18. Privacy Policy Updates and Notices
- With the expansion of XPEACH site cluster, iteration of XPeach Harness client functions, technical security upgrades or changes in data protection laws, we may revise this privacy policy from time to time.
- The updated privacy policy will be published on the
https://sso.xpeach.codes/privacy-policypage, and the "Updated Date" and "Effective Date" at the top of the page will be updated. - If the changes will lead to a substantial reduction in your core privacy rights, or a substantial expansion of the purpose of processing and sharing of personal information, we will notify you through prominent announcements on the site, client prompts, or sending notification emails to your bound email address.
19. Applicable Law
- On the premise that it does not violate any mandatory applicable laws, the interpretation and execution of this Privacy Policy shall be governed by the laws of the operator’s primary place of residence or the place where the actual services are provided.
- This Privacy Policy does not voluntarily select the laws of the mainland of the People's Republic of China as the governing law, except for mandatory provisions that must be applied in accordance with the law.
- If the data protection laws in your jurisdiction have the effect of mandatory application that cannot be excluded, then its provisions shall apply to the extent of mandatory application.
20. Contact us
- Platform and product brand: XPEACH / 🍑Code / XPeach Harness (
xph) - Unified Pass Center (SSO): https://sso.xpeach.codes
- 🍑Code main website address: https://xpeach.codes
- Operation method: Individual independent operation
- Privacy and Data Protection Contact Email: xpeachcodes@gmail.com
If you have any questions, comments or requests about this Privacy Policy, personal information processing, XPeach Harness local storage security, Passkey and multi-factor authentication, cross-site data synchronization or exercising data rights, please feel free to contact us at the above email address.
XPEACH SSO