# Anti-detect browser subscription expired: your profiles > When an anti-detect browser subscription expires, where profiles live decides the cost: a cloud vendor holds your cookie jars; a local app leaves them on disk. Source: https://mosaicbrowser.com/blog/subscription-lapse-profiles ## What happens to your profiles when the subscription ends When an anti-detect browser subscription expires, where profiles live decides the cost: a cloud vendor holds your cookie jars; a local app leaves them on disk. ![Their server versus Your disk, each name in its own tile: Where the cookie jar lives decides what a lapse costs](https://mosaicbrowser.com/covers/subscription-lapse-profiles.webp) When an anti-detect browser subscription expires, what happens to the profiles depends on where they are stored. If the vendor keeps them on its servers, the cookie jars are in its hands and its retention terms decide how long they exist. If the profiles live on your computer, the files stay on your disk and the lapse changes only what the app allows. Find out which kind you have before the renewal date. ## Two places a profile can live A profile in this kind of browser is several things kept together: a cookie jar with your signed-in sessions, a fingerprint, a proxy and the browser's own storage. That bundle has to sit somewhere, and products split into two camps. In the first, the profile is stored with the vendor. That is what makes opening the same profile on a second computer, or handing it to a colleague, work: the copy that matters is on their side, and your machine downloads it to launch. In the second, the profile is a folder on your own disk, and the vendor never holds the cookie jar. Neither arrangement is a trick. They are different trade-offs, and the bill for each one arrives on a different day. With a cloud copy you pay in dependence: the day you stop paying, the cookie jars are on a server you no longer have a contract with. With a local copy you pay in custody: the vendor cannot lose your profiles, and it cannot restore them either. Mosaic is a desktop app Email yourself the link and open it on your computer. How it works: Bulk actions ## What a lapse costs with a cloud copy Here a lapsed subscription is a question about someone else's records. The usual pattern is a read-only or locked state for a period, and then deletion, but the length of that period, whether you can still export during it and whether a downgrade counts as a lapse are all in each vendor's own terms and help pages. Read them before you need them, and read the date on them, because they change. The part people tend to miss is that the expensive thing to lose is not the fingerprint. A fingerprint can be drawn again. The cookie jar cannot: it holds sessions that took sign-ins, two-factor codes and sometimes weeks of ordinary use to build. If the only copy is on a server that will delete it, the lapse costs every one of those sign-ins. ## What a lapse costs with a local copy When the profile is a folder on your disk, ending the subscription does not reach it. The files are still where they were the day before. What changes is the software's side: which plan you are on, how many profiles it will open, which features stay on. That is how Mosaic is built. Profiles, cookies and proxies stay on your computer, and Mosaic has no cloud copy of your profiles. If a Pro subscription ends, nothing in the library is deleted and the account is on the free plan. The free plan has every engine feature, and it is limited by how many profiles it holds and makes, and by the two automation surfaces, the REST API and MCP; the exact numbers are on the [pricing page](https://mosaicbrowser.com/pricing), which reads them from the same file the app enforces them from. Exporting is not a Pro feature, so cookie jars can be exported on either plan. Custody is the cost. The store and cookie jars are encrypted on disk, and Mosaic keeps daily backups of the library for 7 days by default, but those backups are on the same computer. A disk that fails takes them with it unless you copy them somewhere else. ## Before an anti-detect browser subscription expires, save the profiles Do these while the subscription is still active, because some of them may not be possible after: 1. Export each cookie jar in a format other software reads. In Mosaic, the Export current button on a profile's Cookies tab fills the box above it with the jar as JSON, ready to save to a file. While Pro is active, the same jar is also at `GET /profiles/:id/cookies` over the local API. 2. Write down which proxy each profile used. A session arriving from a new address is one of the things a site notices. 3. If you keep whole profiles, export them while they are stopped. Mosaic refuses to export a running profile, because a live browser has its databases open and the archive would catch a half-written session. 4. Store the exports like passwords. A cookie jar is a set of signed-in sessions, and anyone holding the file can use them. How much a profile should cost in the first place, and why so many products price by profile count, is in [why anti-detect browsers cost what they cost](https://mosaicbrowser.com/blog/why-anti-detect-browsers-cost-so-much). The same export-then-retire order for a client whose contract is ending is in [what to do with a client's browser profile when the contract ends](https://mosaicbrowser.com/blog/client-offboarding-browser-profiles), and pricing by open browsers rather than stored profiles is in [paying per open browser instead of per profile](https://mosaicbrowser.com/blog/concurrent-browser-pricing). ## Questions ### Do I lose my profiles if my anti-detect browser subscription expires? It depends on where the profiles are stored. If the vendor keeps them on its servers, you keep them for as long as its retention terms say. If they are stored on your computer, the files stay there; what the lapse changes is what the app will let you do with them. ### What should I export before cancelling an anti-detect browser? The cookie jars, in a format another browser can read, such as Netscape cookies.txt or a JSON array. Write down each profile's proxy too. A cookie jar is a set of signed-in sessions, so store the export like a password file. ### What happens to Mosaic profiles when Pro ends? Nothing in the library is deleted. Profiles, cookie jars and proxies are on your computer, and Mosaic has no cloud copy of them. The account moves to the free plan, and the plan's limits decide what opens. ### Can a cookie export carry an account to another browser? The sessions, yes, if the site still accepts them. The fingerprint and the exit are separate, so a site may see a known cookie arrive from a different machine and address, and ask you to sign in again. ## Related [Why anti-detect browsers cost what they cost](https://mosaicbrowser.com/blog/why-anti-detect-browsers-cost-so-much): Anti-detect browsers are expensive per profile when the vendor stores and syncs each one. A profile on your own disk costs the vendor nothing. [What to do with a client's browser profile when the contract ends](https://mosaicbrowser.com/blog/client-offboarding-browser-profiles): Agency client offboarding goes wrong when access is revoked before the client can sign in. Confirm the handover, export, then trash the profile by id. [Paying per open browser instead of per profile](https://mosaicbrowser.com/blog/concurrent-browser-pricing): Concurrent-browser pricing charges for how many profiles are open at once, not how many exist. Cheap for a big quiet library, costly when many run together. [Why free anti-detect plans are often cloud-only](https://mosaicbrowser.com/blog/cloud-only-free-plans): A free anti-detect browser with cloud profiles only keeps your first sign-ins as cookies on the vendor's servers. A cookie jar is a credential. [Unlimited local profiles, metered cloud ones](https://mosaicbrowser.com/blog/local-vs-cloud-profile-limits): A local profile is a folder on your disk and costs the vendor nothing; a cloud one is storage and transfer on every open. That is why only cloud gets counted.  [Cloud phones by the minute, and what the meter adds up to](https://mosaicbrowser.com/blog/cloud-phone-per-minute): A cloud phone priced per minute and left open eight hours a day runs 14,400 minutes a month. Multiply by the rate before you compare it with a flat plan. [Anti-detect inside your own browser: the extension model](https://mosaicbrowser.com/blog/extension-based-isolation): SessionBox keeps a cookie jar per session inside your own browser. Logins stay apart; the GPU, fonts and canvas a page reads are the same in all of them. ## Mosaic, on your own computer The browser this blog is about: its own Chromium, fingerprints from real machines and a proxy exit per profile. Free holds 3 profiles. Pro is $49 a month for any number. Mosaic is a desktop app Email yourself the link and open it on your computer.