Your account and updates

Your account at lusiesta.com is the second half of the product: it holds the license, payments, the installer and your support conversations. The desktop app duplicates none of that, it only uses what the account hands out. Let's go through what is stored where, how the app updates itself and what to do when you move to another machine.

One account for the web and for the app

Signing in to your web account and signing in to the app use the same credentials: email and password. The Sign in to your account window says exactly that: "Enter the email and password for your Lusiesta account". The Forgot password? link in that window opens the password recovery page on the site.

The session is cached on your computer in encrypted form, so on later launches the app does not ask for the password again, it quietly re-checks the stored token with the server. If that check fails (password changed, license disabled, session revoked), the sign-in window comes back.

What is in your account

• Home - an account summary: license status, the currently published build, hints on what to do next.
• Plans - package cards and invoice payment in USDT.
• Licenses - key cards: "Expires", "Channel" (stable or beta), "Last check" and a counter of occupied PC seats.
• Builds - the "Download build" button and the number of the current stable version.
• Referrals - your referral code, link and payout stats.
• Support - tickets split into "Payment, Renewal, Plans" and "Software, licenses, devices".
• Security - email, profile, password, 2FA, "Sessions and sign-ins" and recommendations.

The "Devices" tab in the account is marked as still in development: live phone statuses are for now only visible in the app, on the "Home" page.

Where to download the installer

1. Sign in to your account and open the Builds tab.
2. Click Download build. The number of the current stable version is printed next to the button.
3. Run the downloaded file. It installs into your user profile and needs no administrator rights.

The button stays inactive in two cases: an unconfirmed email ("Confirm your email to download the build.") and no active subscription ("Downloads require an active subscription. Choose a plan in your account."). The first is cured by the confirmation link in the email, the second by paying for a plan. What happens on first launch is covered in Installation and first launch.

How the app updates itself

New versions are announced by the server: the current build number arrives in the response to sign-in and to the background license re-check, and the client compares it with its own version. If the server version is newer, a modal window appears on top of the app with a version badge, the line A new version is available, the heading What's new in Lusiesta Studio?, a short list of changes (up to four items) and two buttons:

• Update - starts the update right away.
• Keep working - postpones it for later.

Once you click Update, an Updating Lusiesta Studio window opens with a "Downloading update…" bar. The client downloads the installer, verifies its checksum and the server's digital signature, silently installs the new version and restarts the app. That verification is mandatory: if the signature is missing or does not match, the installation is cancelled with the message "This update is not signed by the server - installation cancelled." or "The update signature is invalid - installation cancelled.". A tampered installer will not get through, even if someone slips it in by hand.

Do not put updates off for long. Automation scenarios come from the server and are built for the current client version, and the server has a minimum supported version. Once you drop below it, the update window appears without the "Keep working" button, and sign-in returns the error "Your app version is out of date - update to continue.".

If the update did not install

1. Check your internet connection and try again: the update prompt returns on the next launch or after the next background license check.
2. If the app was not started from an installed copy, auto-update is unavailable and you get the message "Auto-update is only available in the installed app.". In that case, download the installer from your account manually.
3. The manual route always works: your account, the "Builds" tab, the "Download build" button, then run the installer over the current version. Your data (tasks, proxies, device map) stays in place.
4. If the error repeats, write to support and include the exact text of the message from the update window.

Account security and sign-in history

The Security tab is assembled from the "Email", "Profile", "Password", "2FA", "Sessions and sign-ins" and "Recommendations" sections. The most useful one when you are chasing a problem is Sessions and sign-ins: it is split into the browser account (browser, system, IP, last sign-in) and the desktop client (license key, app version, last check, client IP), with the app's sign-in history below. It tells you which machine and which version the app is really running on, and that is the first thing worth checking whenever the license seems to behave oddly.

Moving to another computer

The app is bound to a machine by HWID, and the number of PC seats is capped by the license. The move goes like this:

1. On the new computer, download the installer from your account and install the app.
2. Sign in with the same email and password. If a PC seat is free, the sign-in goes through and the new machine takes that seat automatically.
3. If no seats are left, the sign-in window shows "Device limit for this license reached.". Write to support from your account, category "Software, licenses, devices", and ask to release the binding of the old computer.
4. Once the seat is free, sign in again on the new machine.

Keep in mind: local data cannot be carried over by copying a folder. The session, the tasks and the proxy list are encrypted by Windows and tied to the machine and the user account, so on someone else's computer those files are worthless. Proxies have to be added again (importing a txt file makes it quick), and phones get reconnected and renumbered. The phone and PC seat limits themselves are described in Plans and device limits.

Where to write with questions

Tickets are accepted through two doors: the Support page inside the app and the tab of the same name in your web account. The app is more convenient for day-to-day questions, since it keeps the conversation history and the menu item shows a badge with the number of unread replies. For payment questions, choose the "Payment, Renewal, Plans" category in your account.

If a specific task broke, do not retell it in words: the app captures a diagnostic bundle automatically at the moment of failure, and you can send it with a single button. How that works is described in One-click error report.