Cookie Notice
Scope
This notice covers cookies and similar browser storage on the FriendlyCrm website and clinic application. The website, application and API may use different hostnames, so their first-party storage is separate. Payment-provider pages use their own technologies and notices.
Sign-in cookie
The clinic application uses vetcrm_refresh, an HttpOnly refresh-token cookie sent to the API, to restore an authenticated session. It is a persistent cookie, not a browser-session-only cookie. Its lifetime follows the sign-in configuration (30 days by default), is renewed on refresh, and it is cleared on sign-out. This cookie is needed for sign-in; blocking it can prevent session restoration.
Language and interface preferences
The website and application store vetcrm-ui-locale in a first-party cookie for one year and in local storage until cleared, to remember the interface language. The application also uses session storage for the selected office and sign-in notices, and local storage for dismissed service notices. Session storage lasts for the tab’s session; local storage remains until cleared. These preferences do not store payment card details or the access token.
Analytics preference storage
When optional analytics is enabled, friendlycrm_landing_analytics_consent stores your accepted or rejected choice in local storage until you change it or clear browser storage. This stores a preference, not an analytics tracking identifier. When analytics is disabled, its banner and preference controls are not shown.
Optional website analytics
The website can load Cloudflare Web Analytics only after you accept it. Cloudflare describes this beacon as cookieless: it does not use cookies or local storage to collect usage metrics or fingerprint visitors. It measures aggregate traffic and page performance. The clinic application does not deliberately load this optional website beacon or advertising trackers.
Changing your choice
Use Cookie settings in the website footer or on this page to accept or reject optional analytics. If you withdraw permission after the beacon has loaded, the page reloads to stop it; information already sent is not undone. You can also clear or block browser storage. Blocking sign-in storage can affect the clinic application, while clearing preference storage resets your choices.
Notice updates
We will revise this notice when our use of cookies or similar storage changes. The revision date appears at the top of the page.