Privacy Policy

1. Scope and contact

This policy covers the Avalon Cloud website, account services and any cloud synchronization features you choose to use. Avalon Labs LLC is responsible for the processing described here. Local Avalon features run on your device; account information is used for Cloud services. Contact [email protected] about this policy or your information; do not include verification codes, access tokens or proxy passwords in your message. Avalon Labs LLC is registered in New Mexico, United States.

• Contact Avalon Labs LLC

2. Account, device and support information

When you request a sign-in email or use an account, we process your email address, verification requests and results, account identifier, installation and device identifiers, device name, operating system, activity times and session records. Where an entitlement exists, we also process its source, plan, status and expiry to enforce access and device limits. Information you choose to send to support is used to handle your request. Your local Avalon master key stays on your device. Where Apple or Google sign-in is offered and you choose it, we verify the provider identifier, signed identity claims and any verified email or profile name supplied; matching email addresses do not automatically merge accounts. We protect temporary authorization state and recoverable login receipts with encryption. Apple credentials needed to revoke the authorization are also encrypted. Where purchasing is offered, we process the channel, product, purchase and transaction references, account binding, paid service intervals, renewal, cancellation, refund and verification status. Apple, Google or Stripe process the payment details under their own policies; Avalon does not store payment-card numbers.

3. Content you choose to synchronize

When a synchronization feature is available and you enable it, we process the content you select, including configurations, subscription URLs and request headers, proxy nodes and credentials, groups, chains, rules and selections, together with identifiers, versions and timestamps needed to synchronize them. This content can contain sensitive credentials or information about other people: upload only content you are entitled to use. Browsing history, traffic contents and local traffic statistics are excluded from Cloud synchronization. The synchronization server does not fetch the subscription URLs you store.

4. Website requests and security records

Network requests expose connection information such as an IP address to the server and its infrastructure. We use IP-based controls and protected, pseudonymous email and IP identifiers to limit abuse; these identifiers are not anonymous data. Application access logs record the request method, route, result, duration and request identifier without deliberately logging message bodies, verification codes, tokens or synchronized credentials. Hosting or network infrastructure may process additional connection and security information. The homepage and policy pages have no advertising or analytics scripts, do not set first-party cookies and do not persist sign-in tokens in browser storage. Optional browser authorization uses a temporary security cookie described in the Cookie Policy. Google Fonts requests are described below and in the Cookie Policy.

5. Purposes and grounds for processing

We process necessary account and synchronization information to provide the services you request and perform our agreement with you. We process limited security and operational information to protect accounts, prevent abuse, diagnose faults and maintain the service, relying on our legitimate interests where that ground is available and balancing it against your rights. We may also process information to meet applicable legal obligations. Where consent is required for an optional use, we will request it separately, and you can withdraw it for future processing. Reading this policy is not blanket consent to unrelated processing.

6. Service providers and disclosures

We use Resend to deliver verification emails. It receives the recipient email address, verification message, code and expiry, with a delivery request identifier; synchronized content is not sent to Resend. Hosting, database and network providers process information needed to run the service. Website fonts load from Google Fonts, so Google can receive your IP address, browser information and font request details. We do not sell personal information or share it for cross-context behavioral advertising. Other disclosures are limited to your instructions, service delivery, a valid legal requirement, or the protection of users and the service as permitted by law. If you choose their sign-in or payment flow, Apple, Google and Stripe receive the information needed to authenticate you or process, verify and manage the purchase. Their hosted pages may use their own cookies. Optional flows appear only where the relevant client and channel resources are available.

• Resend Privacy Policy
• Sign in with Apple privacy
• Google Privacy Policy
• Stripe Privacy Policy
• Google Fonts privacy information

7. International processing

The service is offered outside mainland China. Our infrastructure and providers may process information in countries other than your own, including the United States in the case of Resend. A provider's applicable terms govern its processing and retention; we do not promise a particular data residency from the service's domain name or your location. Where applicable law requires safeguards for international transfers, we will use the required safeguards. Contact us for information about the processing locations and arrangements relevant to your account.

8. Encryption and account access

Public service connections use HTTPS. Cloud content is encrypted in storage with keys managed by the service. Verified account recovery restores access to content encrypted with service-managed keys; authorized server processing can decrypt the content. This is not end-to-end encryption. Access to the email account used for sign-in is therefore important to account security. Verification codes and refresh tokens are stored as hashes. No transmission or storage system can guarantee absolute security.

9. Account and security retention

Account and device information is kept while needed to provide your account and handle its closure. Verification codes are valid for 10 minutes, access tokens for 15 minutes, and a rotated refresh token for up to 90 days, subject to earlier revocation. These validity periods do not mean that all associated database records are deleted at expiry. Verification results, revoked-session history, rate-limit information and other security records may remain for account protection, abuse prevention, dispute handling or legal obligations; we retain them only for the relevant purpose and applicable required period. Support correspondence is retained as needed to resolve the request and related obligations. You can contact us about retention or request deletion. Login attempts and recoverable receipts have a ten-minute absolute lifetime and are cleared after expiry and a bounded cleanup period. Provider revocation credentials remain protected while revocation is unresolved. Purchase ownership, verified transaction and unresolved billing records may remain after account deletion to prevent reassignment of old purchases, resolve refunds or disputes and safely restore the service. These records are distinct from synchronized content and its 30-day disaster-recovery copies. Contact us to review retention or request deletion subject to the continuing purpose and applicable requirements.

10. Subscription expiry and cloud content

For synchronization spaces explicitly covered by the newer 30-day lifecycle policy, expiry stops uploads and downloads immediately. The existing cloud content is retained for a 30-day window, measured as 30 consecutive 24-hour periods in UTC, so a qualifying renewal within that window can restore access. At the end of that window the old space is permanently retired and its online content is scheduled for removal; later renewal requires a new space rebuilt from an eligible device's local content. Existing accounts that have not adopted this policy keep their earlier retention commitments until a migration is explicitly communicated. Publishing this policy does not itself migrate an account or make an unavailable synchronization or purchase feature available.

11. Account deletion and backup limits

You can request verified deletion at getavalon.app/account/delete or contact us. Deletion removes the online account and associated cloud data and revokes its sessions; it does not erase local Avalon content or proxy credentials on your devices, and it does not cancel an app-store subscription. Under the newer backup policy, controlled disaster-recovery copies may remain for no more than 30 days from each copy's original UTC creation time. Copying or restoring a backup does not restart that period. During retention, backups can still be decrypted with the service's keys; we do not promise immediate or eventual cryptographic irrecoverability. Backups are restricted to disaster recovery, and restored systems must exclude deleted accounts and reapply retired-space restrictions before serving users. Minimal account-identifier deletion and retirement records may be kept longer to prevent old backups from reinstating deleted accounts or retired content. Earlier commitments for accounts not migrated to the new policy remain in effect.

• Delete your Cloud account

12. Your choices and rights

Local features run on your device. You choose whether to activate Cloud sync and can sign out, remove devices or request account deletion. Depending on applicable law, you may also request access, correction, a portable copy, deletion, restriction or objection to processing, withdraw consent, and complain to a competent data protection authority. Email [email protected] to make a request. We may ask for proportionate verification to protect your account and will respond within the time required by applicable law. Exercising a right does not result in discriminatory treatment; removing data necessary for a requested Cloud function can prevent that function from working.

13. Young users and policy changes

The Cloud service is not directed to children below the age at which they can lawfully use it independently. Where a guardian's authorization is required, it must be obtained before an account is created. Contact us if a child's information was submitted without the required authorization. We publish changes to this policy with an updated effective date and provide an appropriate advance notice of material changes affecting existing users. Changes do not retrospectively shorten an existing retention commitment without an explicit migration arrangement.