본문으로 건너뛰기

이 페이지는 아직 사용하시는 언어로 제공되지 않습니다. 영어 원문을 읽고 계십니다.

Knowledge base

Profiles are no longer in your account

The notice arrives after a check against the account, when some of your profiles were not found in it. Its text varies, and the difference is the main point: whether the data on this computer was erased or only the records moved to the bin.

Four texts and four outcomes

The profiles were deleted on another device and their cookies and logins were erased here: that is the ordinary outcome. The server returned an empty list: records in the bin, data untouched.

You signed out and in with another account: records in the bin, data untouched. Some data could not be erased: the names are listed, and the first words of the notice are the same in all four cases, so read it to the end.

An empty list is not a deletion

A server that returned not a single profile may have answered that way because of a fault. No data is erased on such an answer: the records wait in the bin, and you decide.

When data is erased

Erasing follows only a confirmed deletion: the profile is gone from the account, the account is the same and the list is not empty. A running window is closed first, or the browser would keep its files open.

A profile lying in the account bin does not count as deleted: the record moves to the local bin, the data stays.

Switching accounts

After signing out and in with another account, the previous account's profiles move to the bin with their data in place. Sign in with the previous account and they come back; Delete permanently in the bin removes them for good.

Profiles shared with you

A colleague withdrew your access, and the profile shared with you vanished from the list. The record is removed, while cookies and logins stay on disk: it is their work, and it must not be erased unasked.

Some could not be erased

The files of one profile were busy or the folder had no permissions, and the notice names such profiles. Their data is still on disk, and erasing can be repeated from the bin.

How to collect evidence

Note the names from the notice and the time, open the bin and see whether the records are there. If the server returned an empty list, repeat the check by signing out and in.

Write through Help → Write to support: the report that travels with the message carries the app's recent notifications.

The profile list and the Recycle bin in the left column of the app.
The Recycle bin stands in the left column, a few rows below Profiles.

What this article does not cover

  • Deleting profiles on this computer. There is an article about deleting a profile.
  • Sessions in the shared folder between machines. The account check does not touch them.
  • Profiles created without signing in. They have a notice of their own.

Where this is decided

Each claim above is one place in the code and one stand.

Deletion on another device erases data here only on confirmation
apps/desktop/test/sync-remote-delete.js
An empty server answer and an account switch move records to the bin without erasing
apps/desktop/src/main/main.js
The hold on an account switch survives a restart
apps/desktop/test/удержание-переживает-перезапуск.js
Delete permanently leaves neither the record nor the directory
apps/desktop/test/delete-leaves-nothing.js

Questions

Is the session erased?
Only on a confirmed deletion in the same account. An empty list and an account switch leave the data alone.
What about an open window?
It is closed before erasing. Erasing under a running browser would erase half.
Can the profile be brought back?
If it is in the account bin, yes. If the data was erased on a confirmed deletion, the record comes back from the bin empty.

Still stuck

Support answers with the cause, not with a checklist.