Refund Policy

Last Updated: May 20, 2026

Effective Date: May 30, 2026

This Refund Policy (hereinafter referred to as “this Policy”) constitutes a valid and legally binding agreement between you (hereinafter referred to as the “User”) and the software operator (hereinafter referred to as the “Operator”) regarding your purchase of paid subscription plans or related online services for this software.

The Operator is committed to providing users with high-quality productivity tools and secure data synchronization services. To protect the legitimate consumer rights of users while maintaining a healthy operational order for the platform, please read this Policy carefully before purchasing any paid services.

1. Refund Eligibility Conditions

Subscription purchases are divided into two channels:

• Direct Channel: Paid plans purchased through the Operator’s official independent website.
• Third-Party Channels: Paid plans purchased through third-party app stores such as the Apple App Store, Google Play Store, Microsoft Store, etc., via In-App Purchases (IAP).

1.1 Official Channel

Users are entitled to an unconditional money-back guarantee within 15 days from the exact time of purchase (subject to the timestamp when the order payment was successfully completed).

Scope of Limitation: This unconditional money-back guarantee applies exclusively to the User’s initial purchase or first-time subscription upgrade.

1.2 Third-Party Channels

The User explicitly acknowledges and agrees that for purchases made through the Apple App Store, Google Play Store, Microsoft Store, or other third-party app stores via In-App Purchases (IAP), the transaction funds are collected directly by the respective third-party platform. The Operator has no direct technical or financial authority to intervene in, control, or initiate refunds within those platforms.

Refund Path: The User must submit refund applications directly to the respective third-party platform. The review standards, procedures, and final outcomes of such refunds will be governed entirely by that platform’s terms of service and refund rules. The Operator assumes no legal liability for refund disputes resulting from third-party platform policies.

2. Refund Application Process

If a User meets the aforementioned refund conditions and decides to apply for a refund, the application must be submitted through the designated official channels listed below to ensure that funds are returned to the original payment method:

• Support Ticket System: Log into the software client or web-based user center, navigate to “Technical Support / Help Center,” and submit a ticket under the “Billing and Refunds” category.
• Email Application: Send an application email to the official designated customer support email address (support@easchi.com). Note: Given that the registration mechanism of this software does not collect direct personal data, email applications may require the User’s cooperation in completing an ownership technical verification within the client application.

Required Submission Materials: You must provide your complete account username and a billing screenshot (which must clearly show the payment reference number, transaction ID, and the exact date of purchase).

The Operator will complete the internal review within 5 business days from the date of receiving a compliant refund application. Upon approval, the refund will be processed through third-party payment gateways (such as Creem, Paddle, Stripe, etc.) and returned via the original payment path to the User’s original payment method (e.g., credit card). The actual arrival time depends on the processing cycle of the relevant banks and financial institutions.

3. Billing, Exchange Rates, and Gateway Disclaimers

3.1 Payment Gateway Fees

The User explicitly acknowledges and agrees that refunds via the official channel are processed through compliant third-party payment gateways (such as Creem, Paddle, Stripe, etc.). Except as otherwise provided in this Policy, refunds will be returned in full or after deductions pursuant to this Policy via the original payment path. However, because the original cross-border processing fees charged by third-party payment gateways or specific transaction fees charged by financial institutions may constitute “non-refundable fees,” the actual refund amount issued by the Operator will be subject to the technical refund rules of the payment gateways.

3.2 Exchange Rate Fluctuation Disclaimer

All refunds are initiated based on the pricing currency and the exact amount at the time of the original transaction. The Operator assumes no legal liability for any discrepancies in the User’s actual local currency billing caused by exchange rate fluctuations or cross-border currency conversions during the foreign exchange settlement and clearing processes handled by intermediary banks, issuing banks, or payment gateways. The actual amount received by the User shall be governed by the final statement issued by their financial institution.

4. Anti-Fraud and Abuse Limitations

To prevent malicious abuse, the Operator will manually verify original transaction records upon receiving a User’s refund application. Strict restrictions and punitive measures will be enforced against conduct suspected of involving friendly fraud/reverse fraud, high-frequency malicious refunds, or intentional occupation or exploitation of server resources:

4.1 Single Account and Payment Method Restrictions

The same registered user account, or the same payment account (including but not limited to the same credit card or the same linked payment account), is entitled to only one refund via the official channel within any consecutive 12-month period. This limitation applies to Section 1.1, Section 5.3, and Section 5.4 on an aggregate basis. Once a payment method triggers any type of refund, any subsequent orders purchased using that same payment method within 12 months will automatically forfeit all rights to refund exceptions.

4.2 Malicious High-Frequency Claim Restrictions

Given that the registration mechanism of this software does not collect direct personal data, if the Operator detects that the same payment method (such as the same credit card) is frequently applying for account liquidation and refunds across multiple distinct accounts within a short period pursuant to Section 5.3 and Section 5.4 of this Policy, such behavior will be deemed malicious cash-out / fraud testing. The Operator reserves the right to reject all subsequent refund applications associated with that payment method and permanently block that payment method from any future purchases.

4.3 Storage Resource Exploitation Restrictions

When processing the account credential loss procedures described in Section 5 of this Policy, if it is discovered that the account uploaded abnormally high-frequency, massive amounts of encrypted data within an extremely short period after purchase, and immediately thereafter applied for a credential-loss refund:

• Upon downgrading the account to the free tier, if the volume of encrypted data already stored in the cloud exceeds the maximum quota of the free tier, the exceeding storage space will trigger an immediate circuit-breaker lock.
• The Operator reserves the right to suspend all read, write, and transfer functions of the cloud-synchronized data for that account, without accessing or touching the User’s actual data contents.

4.4 Disputes and Chargebacks

The User acknowledges and agrees that the Operator has provided comprehensive, legitimate customer support and refund application channels, including the support ticket system and specific verification emails. If the User bypasses the legitimate channels stipulated in this Policy to initiate an external dispute or chargeback, the paid contract corresponding to the order shall be deemed to be in a “pending/disputed status,” and the Operator reserves the right to suspend paid features such as cloud synchronization. If the chargeback is ultimately sustained, resulting in the Operator not receiving or being forced to return the relevant funds, it shall be deemed that the User has failed to fulfill their payment obligation from the outset. Consequently, the service contract shall automatically terminate, and the Operator will purge all cloud assets associated with that user.

5. Protection Policy for Lost Account Credentials

Given that the general registration mechanism of this software does not collect direct personal data, the Operator cannot verify the true identity of users through traditional real-name information (such as legal name, email address, or phone number). To protect the digital asset security of legitimate users and prevent man-in-the-middle (MITM) or malicious third parties from interception fraud (e.g., fraudulently claiming refunds and maliciously closing accounts), the following protection policy is established.

5.1 Sole Proof of Ownership

The User explicitly acknowledges and agrees that holding valid login credentials or the secure recovery key for the account is the sole legal basis for proving ownership of that account. Merely possessing third-party payment receipts (such as transaction serial numbers or bank statements from Creem, Paddle, Stripe, etc.) does not equate to ownership of the account or its cloud-encrypted assets.

5.2 Refusal of Application

To prevent malicious third parties from using stolen or misappropriated payment credentials to fraudulently apply for refunds and delete accounts—thereby destroying the digital assets of the legitimate user—the Operator reserves the right to outright reject the refund application for security reasons if the applicant cannot prove actual control over the account (such as an inability to log into the account to submit a support ticket or an inability to provide corresponding technical verification credentials).

5.3 Special Appeals under Extreme Circumstances

If a User loses their secure recovery key due to force majeure and urgently requires a refund, they must submit an appeal through the official channel to enter a long-term security verification procedure.

Core Rules for Security Verification:

1. Dormancy Determination: To ensure that the original account is truly abandoned, the account must show zero active records from any client application for 90 consecutive calendar days (including but not limited to logins, synchronization, handshakes, or API requests). If the paid service of the account expires during this period, and no active behavior is detected from the time the appeal was filed until the service expiration, an early refund may be processed.
2. Liquidation and Settlement Rules: Once the verification is passed, the Operator will terminate the account services and process the refund according to the following rules:
   • The remaining balance after deductions will be refunded via the original payment path;
   • To the maximum extent permitted by applicable law, the Operator reserves the right to deduct the lesser of 20% of the actual amount paid or $3 as administrative verification costs. If the refundable balance is insufficient to cover this cost, the actual refund amount shall be 0 (i.e., no refund shall be issued);
   • Upon completion of the refund, the Operator will legally and permanently purge all encrypted backup data belonging to that account from the cloud.

5.4 Liquidation Exception for New Users with Lost Credentials

For new users who experience a loss of their secure recovery key within 72 hours (3 calendar days) after purchasing a paid plan, and who are unable to submit an internal support ticket due to their inability to log into the client, the Operator provides an accommodating, case-by-case liquidation channel. To prevent hackers and malicious third parties from exploiting stolen credentials to commit cash-out fraud, this exception must strictly execute the following verification and security observation procedures:

1. Precise Invoice Verification: The applicant must submit a complete, unedited screenshot of the billing statement/receipt containing the original payment details from the payment institution (such as the Invoice ID / Charge ID from Creem, Paddle, Stripe, etc.). The statement must clearly display the precise transaction time down to the second, and must not bear any traces of cropping, masking, or post-modification.
2. Upon receiving a compliant appeal and initially verifying the invoice, the Operator will implement a differentiated observation period based on whether the target account has any history of activity: If the account possesses historical records of activity such as logins, synchronization, or API communications, a 14-calendar-day “Security Observation Period” will be initiated (to reserve a sufficiently long observation window so that a genuine original account owner can immediately trigger a circuit breaker if they become active); if the account has absolutely zero historical activity records, a 7-calendar-day “Security Observation Period” will be initiated.
3. Decision Rules:
   • If the account generates any client activity records, such as logins, synchronization, handshakes, or API requests, during the observation period, the system will determine the application to be an impersonation cash-out fraud. The Operator reserves the right to terminate the refund process immediately and trigger a circuit-breaker suspension of the data erasure procedure;
   • If the account remains completely devoid of any activity records during the observation period (proving that the key is indeed lost and the account is uncontrolled), the refund matter will be processed strictly in accordance with the “Liquidation and Settlement Rules” under Section 5.3 upon expiration of the observation period.

6. Regulatory Environment and Legal Changes

In the event of changes in the regulatory environment, emergency adjustments to cryptographic compliance, or technical force majeure as described in Section 7.3 and Section 8.3 of the Terms of Service, which compel the Operator to shut down or mandatorily switch service versions for specific countries/regions, any “pro-rata refund” obtained by affected users shall constitute a compliant termination settlement under statutory exemptions. Such refunds shall not be subject to the single-account frequency limitations outlined in Section 4 (“Anti-Fraud and Abuse Limitations”) of this Policy. These refunds will be calculated directly by the Operator or the relevant Merchant of Record (MoR) based on the remaining unused days verified in the backend, and will be processed within 30 business days after deducting the basic net regulatory fees for cross-border network settlement charged by financial channels.