MESL Privacy Policy

Account and sign-in

• Account information — your email address, used to sign you in, identify your account, send verification codes, account notices (including plan expiry, data usage reminders and app update notices) and service-related product notices, and answer support requests. We keep only a one-way hash of your password. Your account also holds your plan, expiry date, balance and commission balance, referral relationships and commissions, notification settings, and notes that support, staff and our systems make while handling your requests or security issues (when our systems suspend an account for unauthorized access, the note records the time, the address accessed and the IP address).
• Third-party sign-in — with Sign in with Apple or Google sign-in, we keep that account's user identifier, the email address it provides (with Apple's Hide My Email, an address Apple forwards) and the last sign-in time. We do not keep your name or photo. If an account with the same email already exists and Apple or Google has verified that email, the sign-in method is linked to that account; otherwise an account is created with that email. With Sign in with Apple, if Apple provides an authorization token, we keep it encrypted so we can revoke the service's authorization when you delete your account.
• Passkeys — our servers keep the public key, the credential identifier, its name (by default the name of the device you added it on, which you can change), the authenticator type and technical parameters, and the time and IP address when it was added and last used, to verify your sign-in. The private key stays on your device or in your password manager; when a passkey is created, your account email is saved as its user name in your password manager.
• Device information — when you sign in to an app, it sends a randomly generated device identifier (kept on your device, not tied to hardware; our servers keep only a hash of it), the device type, the device name (on a Mac, the computer name), the system version and the app version. When you sign in on the website, your browser stores a random identifier cookie used only to recognize that browser; our servers again keep only its hash, and the device name is derived from the browser information. For each verified device or browser our servers keep this information, how it was verified, when it was first registered and last signed in, and the IP address of its last sign-in (the device list shows the approximate region derived from it). We use it to recognize sign-ins from new devices (which must be verified, for example with an email code or a two-factor code), list your devices, and send update notices to apps that need updating.
• Device records are kept until you remove the device or delete your account. After a password change, or when a device has not signed in for a long time, it no longer appears in the device list and must be verified again, but its record is kept until it signs in again or you delete your account. Up to 50 devices are kept per account; when there are more, the one that signed in least recently is deleted.
• Sign-in sessions — each sign-in records the IP address, client information and time, kept until the session expires and cleared at once when you change your password or delete your account.
• Two-factor authentication — when you turn it on, our servers keep the authenticator secret encrypted and hashes of your recovery codes, deleted when you turn it off or delete your account.
• Security records — security events such as repeated failed sign-ins, failed bot checks and two-factor lockouts, system errors, and staff actions on accounts are logged in our system logs. Entries include the IP address, the request address and parameters (passwords, codes, tokens and similar fields are masked), the account number, a masked form of the email, and a one-way identifier derived from the email that lets us match entries to an account. For staff actions, message text is recorded only as its length. System logs written before this policy took effect contain unmasked email addresses; they are deleted on the basis described under Retention.
• Credential change records — when your subscription link and connection credentials are reset (by you, by support, when handling account sharing, or when you delete your account), we record the old and new credentials, the time, where the reset came from and the IP address, to investigate leaked subscription links.
• Email change records — when your email address changes (including the change to an invalid address when you delete your account), we record the old and new address, the time, how the change was verified, the IP address and client information. These records are kept long term, including after account deletion, so support can find an account by a former email.
• Email records — for each email we send you, we record the recipient address, subject, email type and delivery result, to investigate delivery problems. Queued and failed email jobs contain the recipient address and the full email (which may include a verification code, an IP address, an approximate region and a device name) and are held temporarily so they can be sent, retried and investigated.

Plans, usage and purchases

• Data usage — our servers count the data (bytes) your account uploads and downloads each day, to apply your plan's allowance and show it to you. Usage counts do not include what you accessed.
• In-app purchases — when you subscribe through the App Store, we receive and keep Apple-signed transaction information: transaction identifiers, product, price and currency, App Store country or region, purchase, expiry and revocation dates, and a random identifier that links purchases to your account. We use it to activate and renew plans and to handle refunds. In-app purchases do not give us your Apple Account email or payment details.
• Website orders — for purchases on our website we keep the plan, amount, coupon, payment method, the payment provider's order number and time, and gift card redemptions. Payments are handled by payment providers; we do not store card numbers. Payment providers receive the order number and amount, and some payment methods also receive your email address.
• Referral rewards — if you signed up through an invitation, the person who invited you can see the order number, amount, commission and time of each of your orders that earns them a reward, but not your email address.
• Support tickets — the tickets you submit (including your replies to ticket notification emails) and the payout details you enter when requesting a commission withdrawal, used to handle your requests and pay commissions.

Connections

• Online records — while you are connected, our servers report your source IP address, the server and your connection times to our account servers, to enforce the device limit, detect account sharing, trace leaked subscription links and handle abuse complaints.
• Configuration downloads — when the app downloads its server configuration, we record the IP address, client information, time and count, to prevent abuse and identify apps that need updating.
• Online statistics — some of our servers regularly record the source IP address, server number, connection counts and upload and download traffic, for online-device and traffic statistics and for handling abuse.
• User access logs — for troubleshooting and handling abuse complaints, some of our servers keep user access logs with the time, protocol (TCP / UDP), server number, account number, source IP address, the domain or address accessed, destination IP address and port. They do not include traffic content.
• Account-sharing and security checks — we look up the approximate region of source IP addresses in a local database and compare them against a regularly updated list of abusive IP addresses; your IP address is not sent to third parties for this. Situations such as one account being used in several regions at once, or more devices online than the plan allows, are handled automatically: the subscription link and connection credentials are reset and you are notified by email; if it happens again, or the source IP is on the abuse list, the account is suspended. When our systems detect credential stuffing, unauthorized access or similar activity, they may also automatically restrict the IP addresses involved or suspend the account. Each action creates a case record (with the IP addresses involved); check logs contain the email and IP addresses. If you think an action was a mistake, email us to ask for a human review.
• DNS — when connected, domain lookups follow the configuration our servers provide. Sites and server addresses that are reached directly are resolved by the public encrypted DNS services of Tencent DNSPod and Alibaba Cloud, sent from your own network; to find the addresses of those encrypted DNS servers themselves, the app uses the plain DNS of Tencent, Alibaba and 114DNS. Other domains are resolved by the public encrypted DNS of Cloudflare and Google, normally sent through our servers according to the routing rules (on iPhone, iPad, Mac and Apple TV, "Prevent DNS Leaks" is on by default and does the same); in Direct mode all lookups are sent from your own network. On iPhone, iPad, Mac and Apple TV, with "Bypass LAN and Private Networks" on (the default), internal domains and reverse lookups of local addresses go to the DNS of the network you are on.
• Our DNS servers — the configuration for a small number of accounts uses our own DNS servers. When they query upstream DNS services, they include the network prefix of the requesting IP address so that nearby addresses are returned. Our DNS servers do not keep the domains of individual queries; they keep only aggregate statistics (the most-queried domains and the source IP addresses with the most requests, with counts), which cannot be linked to a user's individual lookups.
• Domain lists — the configuration our servers provide has the app regularly download a list of domains from the public CDN jsDelivr, used to choose a DNS service. The download is sent from your own network, so jsDelivr sees your IP address.

Network requests

When the app or website contacts our service, requests pass through the network of Cloudflare or through our access servers to our account and download servers. These servers keep access logs (IP address, time, request address and client information) for protection and troubleshooting. The app's access gateway does not log request parameters; the account servers' access logs and a few error logs may contain the full request address, including subscription links. When you download an app or check for updates, the download servers record the IP address, time and client information.

Website sign-in may require a bot check, part of which is provided by Cloudflare and processes your IP address and browser information. The website's sign-in and sign-up pages load Google's sign-in component, so Google receives your IP address and browser information when you open them, whether or not you use Google sign-in.

Sync to account (optional)

In apps that offer it, and only after you turn it on, your custom routing rules and similar settings are stored in your account so you can restore them on your other devices. Custom chain settings, which contain server addresses and passwords, are uploaded only if you also select that option. The settings are stored encrypted on our servers (server-side encryption, not end-to-end) and deleted when you clear them or delete your account.

Live support

Every page of our website, including before you sign in, loads a third-party support tool, Crisp. Crisp processes your IP address, browser information and the page you are on, and stores a session identifier in your browser. After you sign in, the website gives support your email, plan, expiry date, remaining data and balance so it can help you. Opening "Support" in an app opens Crisp's chat page with your account email filled in (on iPhone, iPad and Mac, in your browser).

Some replies are written by AI and sent automatically, shown as the assistant; when the AI cannot help or you ask for a person, the conversation is handed to our staff. The AI is provided by Anthropic and processes the messages in the conversation and the account information above; the program that runs it is hosted on Cloudflare and briefly caches that account information. What you share in the chat is also handled by Crisp under its privacy policy.

Cookies and local storage

The website uses your browser's local storage for your sign-in state, language and invite code, and cookies to remember verified browsers and completed bot checks; our homepage's download page stores a short-lived cookie after you pass its human check. The bot check, Google's sign-in component and the Crisp support widget loaded by the website may set their own cookies. We do not use advertising or analytics cookies of our own.

What we do not do

• We do not inspect or store the content you send through the service. The only records that link the sites you access to your account are the user access logs described above.
• We do not sell your data, and we do not use it for advertising, advertising profiles or cross-app tracking. Apart from the account-sharing and security checks above, we do not make automated assessments of you.
• The apps do not access your contacts, photos, location or advertising identifier, and contain no third-party advertising or analytics SDKs.

Data stored on your device

The apps keep your session token, device identifier, server configuration and settings on your device to sign you in and connect. Some apps offer on-device traffic statistics and logs, off by default; when turned on they stay on your device, are never uploaded and can be cleared at any time. Signing out clears the session token on the device. Each app explains the details for its platform.

Who we share data with

We do not sell your data, use it for any purpose other than providing this service, or disclose it to third parties for such purposes. To run the service, the providers below process the data they need. Hosting, network, email, support and payment providers process data on our behalf; we give them only what they need for their work and require them to protect it to the same or an equivalent standard as this policy. Apple's and Google's sign-in and purchase services, and public DNS services, process data under their own privacy policies.

• Hosting providers, for our servers.
• Cloudflare: network acceleration, protection and bot checks, forwarding mail sent to our support address, and running the support AI program.
• SendGrid: sending verification codes and notice emails, which involves the recipient address and the email content.
• Apple: Sign in with Apple and In-App Purchase.
• Google: Google sign-in; the website's sign-in and sign-up pages load Google's sign-in component.
• Public DNS: Tencent DNSPod and Alibaba Cloud resolve directly reached domains and server addresses; Cloudflare and Google resolve other domains; 114DNS is used only to find the addresses of the encrypted DNS servers.
• Upstream DNS services: when our DNS servers query them, the query includes the network prefix of the requesting IP address.
• jsDelivr: the app regularly downloads a domain list from it, so it sees your IP address.
• Our mailbox provider: storing email sent to our support address.
• Crisp: live support. Anthropic: writing automatic support replies.
• Payment providers: processing payments on our website.

We may disclose the data listed above, including user access logs, to law enforcement or regulators when the law requires it, for example under a valid court order. We provide only the data the request covers.

Where data is stored and data transfers

Account data, access logs, user access logs, online statistics and DNS aggregate statistics are stored on the servers we use, and requests also pass through the network of Cloudflare. The providers listed above may store and process data in other countries and regions. When you use the service, your data may be processed outside the country or region where you live, where data protection laws may differ from yours. We transfer only the data needed to provide the service.

Retention

• Account data (email, plan, settings and so on) is kept while your account exists.
• Security, connection and access records (system logs, sign-in sessions, online records, account-sharing check logs, configuration download records, online statistics and user access logs, DNS aggregate statistics, access logs, credential change records, failed email jobs and daily usage figures) are used only for the purposes described above and to keep the service secure, troubleshoot problems and handle abuse. They are kept only as long as those purposes need and then deleted automatically.
• Case records (date, action taken, regions involved and number of IP addresses) are kept long term to recognize repeated violations; the IP addresses in them are deleted on the basis above.
• Email change records and email sending records are kept long term.
• Orders, In-App Purchase, commission and gift card records are kept as required for financial and legal purposes; when our staff delete an account in the admin tools, its website orders are deleted with it.

What is deleted at once and what is kept when you delete your account is described in the next section.

Deleting your account

You can delete your account at any time: in the app under Account → Delete Account (app version 2.0.3 or later), or on the website in your account settings. You can also email support@meslcloud.com; we process email requests within 30 days, including when your account has been suspended and you cannot sign in. When you delete your account in the app or on the website:

• Deleted immediately: sign-in sessions, two-factor authentication, passkeys, linked third-party accounts, device records, synced settings, invite codes, support tickets, online records and configuration download records. If we hold an authorization token from Apple, we ask Apple to revoke Sign in with Apple authorization; you can also stop using Sign in with Apple for this app in your Apple Account settings.
• Account closed: the email is replaced with an invalid address, the password and subscription link are reset, and the balance and commission balance are cleared, so the account can no longer be used or restored. The account number, plan and usage, who invited you, registration date and similar account records are kept for financial reconciliation and commission settlement; the link between your account and the users you invited is removed, and existing commission records are kept. Support notes are cleared except for the deletion date.
• Kept: orders, In-App Purchase, commission and gift card records, kept as required for financial and legal purposes; email change records (with your former email, time, IP address and client information), kept long term so support can find the account by a former email; and case records (their IP addresses are deleted). In email sending records, the email address you had when you deleted the account is replaced with an invalid address, and that address is removed from bulk-mail lists; other addresses you used before remain in email sending records.
• Deleted later: system logs, check logs, credential change records, online statistics and user access logs, daily usage figures and failed email jobs from before the deletion are deleted automatically on the basis described under Retention.
• Accounts deleted by our staff: this includes accounts we remove for violating our terms and accounts our staff delete after an email request. This kind of deletion removes the account and its order records directly. Email sending records (with the original email), case records, online records, configuration download records, email change records, credential change records, In-App Purchase and commission records are kept for abuse review and reconciliation, and those that expire are deleted on the basis described under Retention. Apple authorization is not revoked automatically; you can stop using Sign in with Apple in your Apple Account settings.
• Data held by providers: payment records at payment providers, your Crisp chat history and the content sent to Anthropic to write support replies, the emails you sent to our support address and the email service's sending records are kept or processed under the providers' own rules; contact us to have them deleted. You can remove Google sign-in access in your Google Account settings.
• Your devices: delete the passkey from your device or password manager yourself.
• Backups: copies in database backups are deleted as the backups are rotated on schedule.

An App Store subscription must be cancelled in your Apple Account; deleting your account does not stop Apple billing.

Legal bases

If you are in the European Economic Area or the United Kingdom, we process your personal data on these bases:

• Contract: creating and managing your account, sign-in and device verification, providing connections, counting usage, enforcing your plan's device limit, handling purchases and refunds, answering support requests and sending account notices.
• Legitimate interests: keeping the service and accounts secure, detecting credential stuffing, account sharing and resale, troubleshooting, handling abuse complaints (including user access logs), and sending service-related product notices. Our legitimate interest is a secure, reliable service used in line with our terms. You can object as described under "Your rights".
• Legal obligations: keeping transaction records as financial and legal rules require, and responding to lawful requests.
• Consent: optional features such as Sync to account are used only after you turn them on, and you can turn them off at any time; on Apple devices you can also withdraw your consent to "Your Data & Privacy". Withdrawal does not affect processing before it.

An email address, or Sign in with Apple or Google sign-in, is required to create an account; without it you cannot use the service. Device information, online records and similar data are generated by the service and are necessary to provide connections and enforce the device limit. Optional features such as Sync to account are not required for the basic service.

Your rights

You can view and change most of your account information in the app or on the website, including your email, password, notification settings, devices, passkeys, orders and tickets, and you can delete your account at any time. Expiry and data usage reminders can be turned off in your account settings on the website; account notices such as verification codes and security alerts cannot.

You can also email support@meslcloud.com to: access the personal data we hold about you and get a copy; correct inaccurate data; delete data; restrict processing; receive the data you gave us in a common electronic format; object, on grounds relating to your situation, to processing based on our legitimate interests; stop receiving product notices; or ask for a human review of an automated action. To protect your account we first confirm that you are the account holder, and we reply within 30 days. Data we must keep by law, or must keep to handle abuse, may not be deletable; if so, our reply explains why.

If you believe our handling of your data breaks the law, you can contact us first, and you can also complain to the data protection authority where you live.

Security

The apps and website use encrypted connections to reach our account servers. We keep only one-way hashes of passwords, and two-factor secrets, Apple authorization tokens and synced settings are stored encrypted. Staff sign-in to our admin tools requires two-factor authentication. No system is perfectly secure; if a breach may affect your data, we will notify you and the relevant authorities as the law requires.

Children

The service is not directed to children under 13. If your country or region sets a higher age, you must be that age or have a parent's or guardian's consent. We do not knowingly collect children's personal information; if we find we have, we delete it. Parents can contact us by email.

US state residents

The categories of personal information we collect are identifiers (email, account number, IP address, device identifier), commercial information (plans and purchases), network activity information (sign-in, connection and access records, including the domains or addresses accessed in user access logs), and approximate region inferred from IP addresses. Sources, purposes, recipients and retention are described above. We do not sell your personal information or share it for cross-context behavioral advertising. You can ask to know, correct or delete your personal information as described under "Your rights", or have an authorized agent ask for you; we will not treat you differently for doing so. The website does not respond to browser "Do Not Track" signals.

Changes

When this policy changes, we update this page and the effective date. For changes that significantly affect your rights, we notify you in advance by email or a notice on the website.

Contact

For requests and questions about personal data, email support@meslcloud.com with "Personal data" in the subject.