Skip to content

How we handle your data

This notice applies when you browse Anysola, create an account, buy a plan, send a support ticket, claim a gift, use our Discord server, or sign in to Anysola Desktop. We collect what we need to run the site and answer you; we do not sell personal data or use it for advertising.

Last updated 29 September 2026

Who we are

Anysola Limited, trading as Anysola, operates this website and is responsible for the personal data described here. Our business address is Wyoming, United States. Contact us at [email protected] for privacy requests.

What we collect

Visitors
Aggregate page-use information provided by Vercel Analytics. We do not build advertising profiles from it.
Account
Email, name, username, and avatar if you provide them, plus sign-in method and last sign-in information through Clerk.
Support tickets
Subject, messages and replies, optional company name, account email/name, the IP address of the ticket and of each reply sent from the website, content-rule acknowledgement time, operational status and priority, unread state, email-delivery identifiers, and any internal support note. A ticket is emailed only after its database write succeeds. Email replies are accepted only through a signed webhook and a per-ticket authenticated recipient address, then checked against the account email.
AI support assistant
When it's switched on, an AI assistant answers support tickets first and says that it is one. To answer, it reads your ticket and, from your own account only, your plan and billing status, credit balance and recent credit history, and how many desktop devices are signed in. It passes anything about payments, refunds, credits, security, legal matters or closing your account to a person, and you can ask for a person at any time. We keep a record of each time it handled a ticket — the outcome, which lookups it used, and its cost, but not your messages again — for 90 days.
Support administration
We keep a limited audit trail inside each ticket for status, priority, internal-note, and support-reply actions, including the administrator account and time, plus a record of when you removed a ticket from your own dashboard. The audit trail records that a note changed, not its contents.
Abuse prevention
Rate-limit counters by account and IP. The longest rate-limit window is one hour.
Launch updates
If you ask to hear when a new app is ready: your account identifier, verified account email, consent time, request IP, form source, and a hash of the random unsubscribe credential. We email the credential but do not store a usable copy. Joining requires a signed-in account, so nobody can add an address that isn't theirs.
Beta programs
Your account identifier, name and verified email, application answers, acknowledgement time, application status, private review notes, decision history, and personal access instructions. We also keep queued emails and delivery results. Beta announcement unsubscribe links are signed and tied to the subscription that received them.
Gifts
When you claim a gift: the gift code, claim time, and the reward issued. Anonymous claims are tied to a random visitor identifier kept in a signed cookie; signed-in claims to a keyed hash of your account identifier, not the identifier itself. Anonymous claims pass a Cloudflare Turnstile check, and claim attempts are rate-limited by IP.
Status notifications
If you subscribe to incident emails: your account identifier, account email, and when you subscribed or left.
Discord
If you link your Discord account: your Discord user ID and username, your site account identifier, and when you linked them. In our Discord server, our bot also records member joins and leaves, reactions, and messages — including message text — to run server features and moderation. Giveaway entries record your Discord ID and username, linked account, and entry time.
Anysola Desktop
When you sign in to the desktop app: your account identifier, when the session started and was last used, and a hash of the session token and one-time sign-in code. We never store usable copies of either.
Billing
If you buy a plan: Polar handles the purchase as merchant of record and holds your payment details, billing address, tax information, and invoices. We keep your account identifier, your Polar customer identifier, which plan you are on, whether it is a trial, when the current period ends, and whether it is set to cancel. If we give you a plan without payment, we record the plan, its end date, and why. Billing actions our staff take on your account — cancellations, refunds, granted plans — are logged with the staff member, time, and amount. We never see or store your card details.
Anysola credits
Your credit balance, and one record per movement of credits: which app spent them, how many, the short description the app gave, and when; refunds from an app; and credits our staff added or removed, with who did it and why. Closing your account deletes the balance and the history.
Teams
If you pay for a Team plan and invite people, or are invited to one: for a seat, your account identifier and the name and email you and the team's owner each had when you joined, and the date you joined; for an invite, the owner's account identifier, name and email, the invited email address — which may not belong to an account yet — and when it was sent and expires. The owner sees the names and emails of the people on their team, and each of them sees the owner's. We email the invited address once, naming the owner and giving their email address; replies go to the owner. A seat is not stored as active or inactive: it counts for as long as the owner's own plan is Team.

Why we use it

Gift, Discord, and desktop data lets us deliver the rewards, server features, and sign-ins you ask for, and keep them from being abused. Status emails are sent because you subscribed; you can stop them at any time.

Beta application data lets us review applications, select testers, provide personal invitations, and send application updates. Applying does not subscribe you to the launch list. Leaving the launch list stops launch announcements without withdrawing your applications.

We use account and support information to provide features you request and answer you; security and limited audit information for our legitimate interests in operating and protecting the service; and aggregate analytics to understand whether the site works.

Launch emails are sent on the consent you give in the launch-list form. You can withdraw it at any time. The support acknowledgement confirms content rules and is not consent to process the ticket.

Service providers

Clerk
Provides accounts, sign-in, and profile features.
Resend
Delivers ticket receipts, reply notifications, launch announcements, beta application updates, launch-update confirmations, incident emails, and team invitations and, when configured, authenticates inbound support-email webhooks.
MongoDB
Stores support-ticket copies, launch-update signups, beta programs and applications, gift claims, status subscriptions, Discord links and server events, desktop sessions, plan status, team seats and invitations, and email queues and delivery results.
Cloudflare
Runs the Turnstile bot check on anonymous gift claims and, through Clerk, on sign-in.
Polar
Sells our paid plans as merchant of record: it takes payment, calculates and remits sales tax and VAT, issues invoices, and runs the billing portal. Purchases are also handled under Polar's own terms and privacy policy.
AI model providers
The AI support assistant runs on a language model from Anthropic (Claude), reached directly or through a model gateway such as OpenRouter. Your ticket and the account details the assistant looks up are sent to that provider to write each answer, and are processed on our behalf under its API terms.
Discord
Hosts our community server. What you post there is also handled under Discord's own privacy policy.
Google
Stores backup copies of our database in Google Drive.
Vercel
Hosts the application and provides aggregate site-use measurements.

These providers handle information for the services described above under their own terms and data-processing arrangements. We do not sell personal data or share it for advertising.

International processing

Service providers may process information outside your country. The location and transfer mechanism depend on the provider and service. We use the provider agreements and legally required safeguards applicable to our role. Contact us for current location and safeguard details relevant to your request.

Cookies

Clerk uses cookies needed for sign-in and account features, and the dashboard stores your sidebar preference in a cookie. Claiming a gift sets a signed visitor cookie for up to a year so the same browser can find its reward again. We do not use advertising or cross-site marketing cookies. If we add optional cookies that require consent, we will ask before using them.

Retention and deletion

Clerk retains account data under its account settings and policies. A successfully recorded support ticket, including its messages and embedded audit trail, is automatically removed from our support database two years after it was created. Rate-limit windows last no longer than one hour.

Deleting your account deletes the support tickets recorded under it, removes it from the launch list, ends any status subscription, unlinks any Discord account, and immediately cancels any paid plan, asking Polar to delete and anonymise your customer record. Polar may keep anonymised order and tax records it is legally required to retain. Clerk notifies us when an account is removed, and that notification erases those tickets, their messages, and their audit trail from our support database. To request deletion or a copy of data we control without closing your account, email [email protected] and we will respond within the time required by applicable law.

A team seat is kept until you leave the team, its owner removes you, or either of you deletes your account. Deleting an owner’s account also removes every seat on their team and every invite they sent. An invite is removed when it is accepted, declined or cancelled, and otherwise expires after fourteen days; one sent to your address is not linked to your account, so deleting the account does not remove it earlier.

A launch-list entry is kept while you are subscribed. Leaving the list stops the emails immediately and keeps a record that you left for thirty days, so you cannot be re-added by mistake; after that the record is deleted too.

A status subscription is kept while you are subscribed; after you leave, the record is deleted after thirty days. Discord link codes expire after ten minutes, and server events we record, including message text, are deleted after ninety days. Desktop sign-in codes expire after five minutes, and a desktop session ends ninety days after it was last used. Gift claims are kept for as long as the gift exists; email us to have yours removed sooner.

Database backups are kept in Google Drive and replaced on a rolling basis, so deleted information can remain in a backup until that backup is rotated out.

Beta applications and review history remain available until you delete your account or request deletion. Withdrawing an application stops its review but retains its history. Beta email queue records, delivery results, and bounce or complaint suppression records expire after 180 days. Deleting your account also deletes your beta applications and these email records. Product access is managed by the product itself; contact support to revoke an existing invitation.

The Remove button in your dashboard hides a ticket from your dashboard and stops you replying to it there. It does not erase our support record of the conversation, and it does not recall an email already delivered to our support inbox — support keeps its copy until the two-year retention period ends, or sooner if you delete your account or ask us to delete it. We may retain limited information where the law permits or requires it, such as for an abuse report or legal claim.

When a ticket contains abuse or other conduct we may report to the authorities, we can place it under legal hold and export it as an evidence record. The export contains the conversation, the IP addresses above, and the account details our identity provider holds (including recent sign-in IP addresses and approximate location). A held ticket is not deleted when the account is deleted, and evidence records are kept until the matter they were created for is closed. We share them only with authorities, courts, or our legal advisers.

Your rights

Your rights depend on where you live and applicable law. They may include asking for access, correction, deletion, restriction, or an objection to certain processing, and withdrawing consent where we rely on it. We will verify and handle requests as applicable law requires.

You can edit your profile from the account menu. Tickets that were successfully saved to our database appear in your dashboard, and the Remove button hides one from your dashboard. Email us if you want our support copy deleted as well.

Every launch email carries an unsubscribe link, and inbox providers that support one-click unsubscribe can use it directly. You can also leave the list from your dashboard at any time.

Email [email protected] to make a request. You may also complain to the data-protection or consumer authority that applies where you live.

Children

The site and its account features are not intended for anyone under 18. We do not knowingly collect personal data from children.

Changes

If this page changes, the date at the top changes with it. We may also provide a notice in the service when a change materially affects how we handle personal data.