> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/user-guides/tips-and-tricks/stay-logged-in.md).
# Stay Logged In
This guide reviews how to enable the new Stay Logged In feature and extend your Logout Timer setting.
## Overview
By default, users are logged out of Keeper if their browser closes, or if their computer restarts. Keeper's "Stay Logged In" feature allows you to instead remain logged into for a configurable duration. Continue reading to learn how to enable **Stay Logged In** in the Keeper Web Vault, Desktop App and the KeeperFill Browser Extension.
## Web Vault & Desktop App
To enable Stay Logged in, click the **Account Dropdown Menu** **(your account email)** **>** **Settings > Security** and turn "Stay Logged In" on.
Keeper will then recommend that you turn on "Auto-Logout" in the Keeper Browser Extension to protect your account if you walk away from your device. Also known as the "Inactivity Logout Timer", this automatically logs you out of Keeper after a period of inactivity. You can set the timer to the duration you prefer and it will continue to count down if you close your browser.
If you've downloaded the KeeperFill Browser Extension, you can manage the Auto-Logout setting from the extension's security settings menu (more on this in the section below).
{% hint style="info" %}
To learn more about Auto Logout in the Keeper Browser Extension click [here](/user-guides/browser-extensions.md#stay-logged-in).
{% endhint %}
### Impossible Travel
Impossible Travel applies a distance limit to Keeper’s Stay Logged In feature. When you reopen Keeper after closing your browser or restarting your computer, Keeper calculates the distance from your current location to where your session was last active. If that distance is greater than the limit you set, you will be required to log in again. This helps protect against reuse of stolen or long-lived sessions, with no change for sign-ins from familiar locations.
Impossible Travel is available in the Web Vault and Desktop App. To set a distance limit, go to **Settings > Security** and enable "Stay Logged In". Under "Impossible Travel", enter a number, choose miles (mi) or kilometers (km) and select **Update**. The maximum allowed distance is 621 miles (1,000 km).
Impossible Travel Settings
{% hint style="info" %}
Business customers should note that your Keeper Administrator may disable or limit this feature based on the security requirements of your organization.
{% endhint %}
## Browser Extension
If you've downloaded the KeeperFill Browser Extension you can enable both the Stay Logged In and Logout Timer features from the extension's security menu.
Click **Settings > Security** and enable "Stay Logged In Between Sessions" and set a "Inactivity Logout Timer".
{% hint style="info" %}
For security reasons, we recommend setting a reasonable logout timer duration when Stay Logged In is enabled.
{% endhint %}
## Mobile
To enable Stay Logged In on your Android or iOS device, navigate to the **Settings** menu and toggle "Stay Logged In" on. Once enabled, the setting will apply to all of your devices.
Enable Stay Logged In
## Security
Keeper's Stay Logged In feature uses [Login API V3](/enterprise-guide/developer-tools/login-api.md). The user's Master Password is **NOT** stored on the device or computer when using the Stay Logged In feature. Keeper utilizes advanced encryption, session management tokens and device authorization capabilities to protect your vault.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.keeper.io/user-guides/tips-and-tricks/stay-logged-in.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
.png?alt=media&token=9240563f-c210-453e-b913-b7fc398ba6d5)