Automatic Session Refresh
When you log in, Omnivoo issues a pair of secure tokens:- Access token: Used for every request to Omnivoo’s servers. It lasts about 15 minutes.
- Refresh token: Used to obtain a new access token when the current one expires. It is longer-lived.
Token refresh is completely transparent. You do not need to take any action. Omnivoo’s server issues and sets all of your authentication cookies and is the single source of truth for whether you are signed in: the app running in your browser never sets these cookies itself, and it reads your signed-in state from your profile.
How Long a Session Lasts
Two limits can end a session. Which ones apply depends on the Keep me signed in on this device checkbox on the code-entry screen when you log in, which is ticked by default.
The maximum is counted from when you logged in and is never extended, however active you are.
With the box ticked, you stay signed in on that browser for up to 7 days, overnight and while your laptop sleeps included. With the box unticked, about 15 minutes away from Omnivoo ends the session, whether the tab sat untouched, the laptop slept or the tab was closed.
Signing in with Google, Apple, a passkey or SSO has no checkbox and counts as ticked.
Staying signed in does not cover everything. Before a payment, a bank change or a change to how you sign in, Omnivoo may ask you to confirm it’s you.
In the iPhone and Android app, a ticked sign-in ends after 8 hours away. You can instead unlock with Face ID or your fingerprint, which keeps the phone signed in for up to 90 days.
What counts as activity
The idle sign-out applies only when the box is unticked. Omnivoo watches for these interactions:- Mouse clicks anywhere in the app
- Keyboard input (typing in fields, using shortcuts)
- Scrolling through pages or lists
- Mouse movement across the screen
- Touch events on mobile or tablet devices
What happens when you time out
- After about 15 minutes with no detected activity, you are signed out and taken to the login page.
- The login page says you were signed out for inactivity.
- After logging in, you are returned to the page you were on before the timeout.
Tab Visibility Handling
With the box unticked, Omnivoo treats the idle timer differently depending on whether its tab is in the foreground or background:- Tab in foreground: The idle timer runs normally, and your interactions reset it.
- Tab moved to background: The idle timer is paused. Time you spend on other tabs or apps does not count toward the 15-minute idle sign-out, so a tab left in the background does not, by itself, sign you out.
- Tab returns to foreground: Omnivoo re-checks your session and the idle countdown resumes from the start. If your session is still valid, you continue where you left off. If it was already ended (for example, revoked or expired), you are prompted to log in.
Logging Out
Manual Logout
To log out of your current session:- Click your avatar at the bottom of the left sidebar and select Logout, or
- On a phone, open More and tap Logout. EOR employees tap Logout at the bottom of the Profile tab.
Active Sessions: Signing Out One Device
Omnivoo shows an Active Sessions list of every device currently logged into your account, so you can sign out one device without disturbing the others.1
Open your profile
Click your avatar, select Profile, then open Sign-in & security on the left. EOR employees open Profile in the sidebar instead.
2
Find the device
Each entry shows the browser, the country and IP address it signed in from, and Last active. The device you are using right now is tagged Current. The country comes from the IP address and is approximate, so a VPN or an office network can put a session in the wrong country.
3
Click Revoke
Click Revoke next to the device you want to sign out. Your current session has no Revoke button, so you cannot accidentally lock yourself out of the page you are on.
Logout from All Devices
To end every session at once (for example, if you suspect unauthorized access), click Log out of all devices at the top of the Active Sessions list and confirm in the dialog.Cookie-Based Authentication
Omnivoo stores authentication tokens in HTTP-only, Secure cookies. This design choice provides several security benefits:What this means for you
- No tokens in JavaScript: Your authentication tokens cannot be read or stolen by malicious scripts (protects against XSS attacks).
- Automatic inclusion: Cookies are sent with every request to Omnivoo automatically by your browser. You do not need to manage tokens manually.
- Secure flag: Cookies are only sent over HTTPS connections, preventing interception on insecure networks.
- SameSite protection: Cookies are scoped to Omnivoo’s domain, reducing exposure to cross-site attacks.
What this means for developers and integrations
If you are building integrations with Omnivoo, note that authentication is cookie-based, not header-based. API requests must include cookies (credentials: “include” in fetch calls).CSRF Protection
Cross-Site Request Forgery (CSRF) is an attack where a malicious website tricks your browser into making requests to Omnivoo on your behalf. Omnivoo protects against this by:- Validating the origin of incoming requests.
- Using SameSite cookie attributes to prevent cookies from being sent in cross-origin requests.
- Requiring specific headers on state-changing requests.