Your Account
A server's account pages have four parts:
- Profile shows your picture, name, and email, and your account ID, which an administrator may ask for. Upload picture, beside your picture, takes a PNG, JPEG, WebP, or GIF image; drag and zoom it to choose what shows in the circle, and Remove, once you confirm, goes back to your initials. Change name opens a dialog for your new name. Signing in with Google uses your Google picture until you upload one. The server keeps every picture itself, so pages never load them from Google or anywhere else. Change email sends a link to the new address, and your email changes once you open it. The old address gets a note saying which address is taking over. If you signed in a while ago, the server asks for your password first.
- Sign-in and security links Google or Apple, changes your password, and sets up two-step sign-in with an authenticator app or passkeys. Recovery codes are shown once: copy or download them before you close the dialog.
- Sessions lists every browser and desktop app signed in to your account, with when each was last active, and your recent sign-ins. Sign out any session you don't recognize, or all of them except the one you're using.
- Access tokens lets scripts and CI read and save your documents as you, sending a token as
Authorization: Bearer <token>. New token asks what will use it and when it expires (30 days, 90 days, or a year), then shows the token once: copy it somewhere safe, such as a CI secret, before you close the dialog. The list shows each token's name, first characters, and when it was made, last used, and expires; Revoke stops anything using it at once. A token reaches your workspaces and documents, with their uploads, versions, and Trash, and documents shared with you; it can't change how you sign in, make other tokens, or reach administration.
The server emails you when your account is signed in from an address it has never been signed in from, and when an authenticator app or a passkey is added or removed.
Accept the Terms
A server can ask you to accept its terms. Signing up shows a line saying that continuing means agreeing to them, with links to the terms and, where the server has one, its privacy policy. When the server has a version you haven't accepted, on your first sign-in or after it changes its terms, its pages open on Accept the terms to continue before anything else:
- Accept and continue records which version you accepted and when, and takes you on.
- Decline and sign out signs you out. You're asked again the next time you sign in.
- Leave with your documents, under Don't want to accept?, lets you download your files and delete your account without accepting.
Until you accept, the editor can't open the server's documents, and Settings → Cloud says Accept this server's terms to keep using it, with Review terms to open that page.
Download Your Files and Delete Your Account
Delete account…, at the bottom of Profile, lists what goes before you confirm: the workspaces only you belong to, with their files; your membership in shared workspaces, whose files stay with the others; and your sign-in methods, sessions, and picture. It can't be undone, and if you signed in a while ago the server asks for your password first.
- Download all saves, in one zip, the files in the workspaces that go with your account and the ones you created in shared workspaces, and names any it couldn't download. It leaves out documents in Trash, so restore any you want first, which, like version history, needs the server's current terms accepted; documents an administrator blocked; and documents other people created and shared with you. It saves each document as it is now, without its version history: to keep an earlier version, open it from File → Show version history and Duplicate it before you delete your account, so the copy is included. Version history opens only once you have accepted the server's current terms; if you are leaving without accepting them, Download all is what you can take.
- If you are the only admin of a workspace other people still use, make one of them an admin first. The server's only administrator has to make someone else a server administrator first too.
On the hosted service, the Privacy Policy says how long deleted files are kept before they are removed for good. A self-hosted server's operator sets its own periods.