Cookie Policy
Last updated: 23 September 2026
Arvo sets only the cookies needed to sign you in and keep the service secure. None of them are for advertising or cross-site tracking, and none follow you to other sites.
1. About cookies
Cookies are small files a site stores on your device. Some are essential to make it work, for example to keep you signed in. Others are used for analytics or advertising. This policy covers the ones Arvo uses.
2. Our approach
Every cookie below is strictly necessary. Because none of them are used for advertising or analytics, there is no consent banner to click and nothing to opt out of. Blocking the sign-in cookies will stop you signing in.
We do measure page views and page speed, but with Vercel Analytics and Speed Insights, which are cookieless and set no identifier that can follow you between sites. That is the reason we use them rather than a conventional analytics product.
3. Cookies we set
| Cookie | Purpose | Roughly how long | Type |
|---|---|---|---|
| __session, __session_<suffix> | Set by Clerk, our authentication provider, when you sign in. Holds a short-lived token showing you are signed in, which is renewed while you use Arvo | Not yet measured | Essential |
| __client | Set by Clerk on clerk.arvosystem.com, its sign-in domain, to link this browser to your sign-in. Set on every page, including before you sign in | About 400 days | Essential |
| __client_uat, __client_uat_<suffix> | Set by Clerk. Records when your sign-in last changed, so the site knows whether to refresh it. Set on every page, including before you sign in | About 400 days | Essential |
| __refresh_<suffix>, __clerk_handshake, __clerk_handshake_nonce | Set by Clerk only when needed, while your sign-in is renewed or handed over from clerk.arvosystem.com to arvosystem.com | Not yet measured | Essential |
| __clerk_redirect_count | Set by Clerk during that handover, to stop a sign-in getting stuck in a loop of redirects | 2 seconds | Essential |
| __cf_bm | Set by Cloudflare on Clerk’s behalf to tell real visitors from bots and protect the sign-in page | About 30 minutes | Essential |
| _cfuvid | Set by Cloudflare on Clerk’s behalf to apply rate limits fairly. Not used to profile you or follow you across sites | Session | Essential |
| arvo_share_<link> | Set by Arvo when a guest enters the passcode for a protected shared whiteboard, so the code is not asked for again on that link | 2 hours | Essential |
| arvo_oauth_nonce_<provider> | Set by Arvo while an administrator connects another service to their organisation, to check that the connection finishes in the same browser that started it | Up to 15 minutes | Essential |
| arvo_oauth_pkce_microsoft-personal-onedrive | Binds a personal OneDrive authorisation code to the browser that started connecting that account (PKCE). HttpOnly; cleared on the callback. | Up to 15 minutes | Essential |
| arvo_imp | Set only in the browser of an Arvo staff member who is viewing an account to give support | Up to 30 minutes | Essential |
4. Other storage in your browser
Some things are kept in your browser’s storage rather than in cookies. They are listed here so you can see everything Arvo keeps on your device. None of it is used for advertising or analytics.
- On every page, including before you sign in, Clerk keeps a copy of its sign-in settings in local storage, under __clerk_environment.
- Once you are signed in, Arvo keeps settings and recent activity in local storage, under names beginning “arvo”: display and layout choices, which introductions and announcements you have dismissed, the last project you opened in each organisation, your five most recent searches in each project, and your 20 most recent conversations with the Arvo assistant. They stay until you clear them. The assistant’s history can be cleared from the assistant itself.
- In session storage, Arvo keeps a whiteboard’s Ask conversation, and whether its chat panel is open, until you close the tab. It also keeps opaque references to unconfirmed reviewed requests, including reviewed Outlook emails, scoped to your signed-in account, organisation and project, so reopening a review does not repeat a request whose response was lost. These references contain no message or task contents, access tokens or other sign-in secrets. They are removed when an exact saved receipt confirms the request’s durable status, or when you close the tab. This includes reviewed Planner task updates and Outlook appointment creation.
- If you use Site mode, Arvo keeps site captures, including photos, in your browser’s database until they have uploaded, with the project and the person each was captured for, so nothing is lost when the signal drops. It also installs a service worker that stores the offline capture page and the app’s own files, but no project data, so that page can open with no signal. Signing out clears the stored pages and the captures that have already uploaded. Captures that have not uploaded stay on the device, waiting for the person who took them.
5. Third-party services
Sign-in is handled by Clerk, which uses Cloudflare to keep bots away from the login page. Between them they set every cookie in the table above except the ones beginning arvo_, which Arvo sets itself. Hosting and our cookie-free traffic measurement are provided by Vercel. The providers we use are listed in our Privacy Policy.
6. Managing cookies
You can control or delete cookies, and the storage described in section 4, in your browser settings. Blocking the sign-in cookies will stop you signing in to Arvo. On a phone used for Site mode, clearing the site’s data also deletes any captures that have not uploaded yet. Since we use no advertising or analytics cookies, there is nothing else to turn off.
7. Changes and contact
We will update this page if the cookies change, and the date at the top will change with it. Questions go to hello@arvosystem.com.