Armidus Cookie Policy
Effective date: August 28, 2026
This Cookie Policy explains how Armidus, Inc. ("Armidus," "we," "us," or "our") uses cookies and similar technologies on armidus.com and in the Armidus clinic and owner applications.
This Policy should be read with our Privacy Policy at https://armidus.com/privacy. Terms not defined here have the meanings given in the Privacy Policy. Security information is available at https://armidus.com/security, and our provider list is available at https://armidus.com/subprocessors.
1. What cookies and similar technologies are
Cookies are small text files stored by a browser. They can allow a website to remember a browser, maintain a signed-in session, save a preference, protect a form, or measure how a site is used.
Similar technologies include local and session storage, pixels, software development kits, tags, scripts, and identifiers stored or read by a browser or application. We refer to all of these as "cookies" in this Policy unless a distinction matters.
Cookies may be:
- session cookies, which generally expire when the browser session ends;
- persistent cookies, which remain until their stated expiry or deletion;
- first-party cookies, set for an Armidus domain; or
- third-party cookies, set or read by a provider whose service appears on an Armidus page.
2. How we use cookies
Armidus uses cookies to:
- authenticate users and maintain secure sessions;
- protect accounts, forms, and the Service from abuse;
- route a returning user to the appropriate regional application;
- remember privacy, consent, and interface preferences;
- operate website forms and the HubSpot chat or messaging widget;
- measure marketing-site visits, sessions, referrals, and related analytics through HubSpot, subject to the visitor's consent choice where the banner is shown;
- attribute referred website visits to partners through FirstPromoter, identify visits made through an Armidus affiliate or referral link, associate an eligible Clinic subscription with the referring promoter, calculate referral commissions, and investigate disputed referrals, subject to the visitor's HubSpot analytics consent choice where the banner is shown;
- play an optional product video the visitor requests, which loads YouTube only after the visitor clicks play; and
- diagnose errors and maintain availability and performance.
We do not intentionally use Clinic Data for advertising. We do not currently intend to deploy third-party advertising pixels on the Site. If that changes, we will update this Policy and obtain any consent or provide any opt-out required by law before the change applies.
3. Cookie categories
3.1 Strictly necessary cookies
These cookies are needed to provide a feature you request, maintain security, authenticate an account, preserve a privacy choice, or route the Service. The Site or application may not work correctly if they are blocked.
Examples include authentication session cookies, security and bot-protection cookies, consent-choice cookies, and the optional Armidus region preference.
3.2 Functional cookies
These cookies remember choices or enable optional features, such as a messaging widget, an optional product video, or an interface preference. If they are disabled, the underlying Service may still work, but the optional feature may not.
3.3 Analytics cookies
These cookies help us understand visits, sessions, page views, referrals, and interactions so we can evaluate and improve the Site. They also allow us to determine whether an eligible Clinic subscription resulted from an Armidus affiliate or referral link and to credit the appropriate promoter. They are not required for the Site's basic operation and should be set only in accordance with the visitor's consent or other choice where required.
3.4 Advertising cookies
Advertising cookies can be used to build an interest profile, measure ads, or track activity across services. Armidus does not currently deploy advertising pixels or use advertising cookies for its own marketing. A generic ability in HubSpot or another provider does not mean Armidus has enabled that ability. If you play the optional product video, YouTube (Google) may set cookies under Google's policies, including cookies Google uses for measurement or advertising. Armidus does not control those cookies. See section 4.6.
4. Current cookie inventory
Cookie names and durations can change when a provider updates its service or when browser behavior differs. The following table describes cookies that are used or may be set by the current configuration.
4.1 Armidus and authentication cookies
| Cookie or storage | Provider | Category | Purpose | Typical duration |
|---|---|---|---|---|
armidus_region | Armidus | Strictly necessary or functional | Optional country code used to direct a returning user to the corresponding Armidus application. It is a convenience only and does not grant access or determine where records belong. The marketing site reads this cookie if an Armidus application has set it. | Persistent if set; retained until it expires, is replaced, or is deleted through browser controls |
__session | Clerk | Strictly necessary | Stores the short-lived session token used to authenticate a signed-in user on the relevant application domain. | Controlled by the configured Clerk session lifetime and browser behavior |
__client or Clerk client-state cookies | Clerk | Strictly necessary | Maintains Clerk client and sign-in state on the configured Clerk domain. | Controlled by Clerk and the configured session lifetime |
_cfuvid or equivalent security cookie | Clerk or its infrastructure provider | Strictly necessary | Supports rate limiting, security, or abuse prevention for authentication services. | Usually session based or provider controlled |
Clerk cookies are set when a user interacts with an Armidus application in a way that requires authentication, such as signing in or signing up. They are not marketing-site analytics cookies.
4.2 HubSpot on the marketing site
The marketing site loads HubSpot in two ways:
- Forms embed (
js-na2.hsforms.net/forms/embed/...) so visitors can submit inquiry and interest forms; and - Site tracking code (
js-na2.hs-scripts.com/245941208.js), which enables HubSpot website analytics, the cookie consent banner, and the live chat or messaging widget when those features are turned on in HubSpot.
Because tracking and chat are enabled:
- HubSpot may show a site cookie consent banner and a separate in-chat consent prompt before chat cookies are used;
- analytics cookies may be set after the visitor accepts non-essential cookies where the banner requires a choice;
- chat or messaging cookies may be set when the visitor agrees to chat cookies or otherwise interacts with the widget under the HubSpot chat settings; and
- form delivery and related security cookies may still be set when a HubSpot form is shown or submitted.
HubSpot advertising, enrichment, or third-party ad-pixel integrations are not described here unless Armidus separately enables and discloses them.
| Cookie or storage | Category | Purpose | Typical duration |
|---|---|---|---|
__hs_opt_out, __hs_initial_opt_in, __hs_cookie_cat_pref, or equivalent HubSpot consent cookies | Strictly necessary | Remember the visitor's HubSpot cookie banner choice so the banner is not repeatedly forced after a decision. | Typically about 6 months, subject to HubSpot configuration |
__cf_bm, __cfruid, __cfuvid | Strictly necessary | CDN security, bot protection, and rate limiting for HubSpot-delivered form, chat, or tracking resources. | Session to approximately 30 minutes, depending on the cookie |
| HubSpot form or captcha session storage | Strictly necessary | Supports loading, securing, and submitting an embedded HubSpot form. | Session or provider controlled |
messagesUtk | Functional | Identifies a chat visitor so HubSpot can maintain conversation continuity and quality for the messaging widget. | Typically about 6 months, subject to HubSpot chat and consent settings |
__hstc | Analytics | Primary HubSpot visitor tracking cookie (domain, visitor token, visit timestamps, and session count). | Typically about 6 months |
hubspotutk | Analytics | Opaque visitor identity used to associate browsing activity with form submissions and CRM records. | Typically about 6 months |
__hssc | Analytics | Tracks HubSpot session activity and page-view count for the current session. | Typically about 30 minutes |
__hssrc | Analytics | Determines whether the visitor restarted the browser for HubSpot session handling. | Session |
4.3 FirstPromoter affiliate attribution
The marketing site loads FirstPromoter's tracking script (cdn.firstpromoter.com/fpr.js) through Netlify snippet injection, not from the HTML files in this repository. The script is intended to run only after the visitor accepts HubSpot analytics cookies where the banner requires a choice.
Armidus uses FirstPromoter to operate its affiliate and referral program. When a visitor follows an Armidus referral link and permits the applicable non-essential cookie category, FirstPromoter may store referral identifiers on an Armidus domain. Those identifiers may be readable on regional application hosts on the same parent domain (for example sg.app.armidus.com or us.app.armidus.com) if the cookie is scoped to .armidus.com.
If the visitor later completes an eligible Stripe Checkout, Armidus may add the FirstPromoter transaction identifier to the Checkout Session as metadata.fp_tid so FirstPromoter can determine whether the transaction should be credited to a promoter. Armidus does not add the promoter identifier in _fprom_ref to Stripe subscription metadata.
These identifiers do not contain payment-card details, patient records, animal health information, or other Clinic Data. Armidus may retain the referral identifiers in restricted operational logs to investigate disputed or failed referral attribution.
FirstPromoter may also receive technical and interaction information needed to provide referral attribution, such as the referral URL or code, page and referrer information, IP address, browser or device information, and event timestamps. The precise information depends on the FirstPromoter script and account configuration.
FirstPromoter is provided by IGIL WEBS S.R.L. in Romania. More information is available in FirstPromoter's privacy documentation at https://firstpromoter.com/privacy.
If the visitor rejects non-essential cookies, FirstPromoter should not load and a referred visit may not be credited automatically.
| Cookie or storage | Provider | Category | Purpose | Typical duration |
|---|---|---|---|---|
_fprom_tid | FirstPromoter | Analytics | Opaque transaction or visitor identifier connecting the browser visit to a FirstPromoter referral. If the visitor completes an eligible Clinic Checkout, this identifier may be added to the Stripe Checkout Session as metadata.fp_tid. | Typically about 60 days, subject to FirstPromoter campaign settings |
_fprom_ref | FirstPromoter | Analytics | Identifies the promoter or referral associated with the visit. Armidus uses it for referral diagnostics and does not add it to Stripe subscription metadata. | Typically about 60 days, subject to FirstPromoter campaign settings |
4.4 Stripe-hosted pages
When a Clinic opens Stripe Checkout or the Stripe customer portal, the browser leaves an Armidus-hosted page and interacts with a Stripe-hosted surface. Stripe may use necessary cookies and other technologies for payment processing, fraud detection, security, preferences, and its own legal obligations. Stripe's cookie and privacy notices apply on those surfaces. Armidus does not control the name or duration of Stripe's cookies.
4.5 Netlify hosting
The marketing site is delivered through Netlify as static hosting and content delivery. Netlify processes request and technical information needed to host and secure the Site (for example IP address, user agent, and request path in server or edge logs). The Site does not currently rely on Netlify Identity, Netlify Forms, or Netlify analytics cookies for visitor measurement. If a Netlify feature later sets a browser identifier on armidus.com, we will add it to this inventory.
4.6 YouTube product video
The homepage can show an optional 45-second product walkthrough. Armidus hosts the poster image on armidus.com and does not load YouTube until the visitor clicks play.
Clicking play loads Google's YouTube player from www.youtube.com. YouTube may then set cookies and similar technologies under Google's terms and privacy notice, including cookies used for playback, preferences, security, and measurement. Google may also set cookies that Google uses for advertising or cross-site measurement. Armidus does not control the name or duration of YouTube's cookies and does not use the embed as an Armidus advertising pixel. Armidus does not send Clinic Data, patient records, or owner records to YouTube through this player.
If you do not click play, YouTube should not load and YouTube cookies should not be set by this feature.
| Cookie or storage | Provider | Category | Purpose | Typical duration |
|---|---|---|---|---|
| YouTube or Google cookies that may be set after play (names vary, including identifiers on youtube.com, youtube-nocookie.com, or google.com) | Google / YouTube | Functional for playback; Google may also treat some as advertising or analytics | Play the requested video, remember player preferences, provide security, and operate YouTube under Google's policies | Session to persistent, controlled by Google |
5. Your choices
5.1 Cookie settings on the Site
Where HubSpot shows a cookie consent banner on the Site, use that banner to accept, reject, or (where HubSpot offers it) manage non-essential cookie categories. Rejecting non-essential cookies should not prevent access to ordinary public-site content. Forms may still work; analytics association, partner-visit attribution, and optional chat features may be limited.
FirstPromoter must not load or create new referral cookies unless the visitor has permitted the HubSpot analytics cookie category to which Armidus assigns affiliate attribution. Rejecting that category prevents FirstPromoter from loading on the Site. Withdrawing consent prevents the Site from loading FirstPromoter on later page visits, but referral cookies created before withdrawal may remain until they expire or are deleted through browser controls. Withdrawal does not affect processing performed lawfully before withdrawal. Rejecting or withdrawing referral tracking does not prevent the visitor from using the public Site or purchasing an Armidus subscription.
The chat widget may show a separate HubSpot consent step for chat cookies. That choice is specific to chat continuity and does not replace the site banner choice for analytics cookies.
Playing the optional product video is a separate choice from the HubSpot banner. Rejecting HubSpot analytics cookies does not prevent you from watching the video. Clicking play still loads YouTube and may allow Google to set cookies as described in section 4.6. If you do not want YouTube cookies, do not click play.
Your choice is generally specific to the browser and domain. You may need to set it again if you clear storage, use another browser or device, visit another Armidus domain, or the preference cookie expires.
Strictly necessary cookies cannot be disabled through the preference tool because the requested feature or security function may not work without them.
5.2 Browser controls
Most browsers allow you to view, delete, or block cookies and clear local storage. Blocking all cookies may prevent authentication, forms, regional routing, and other Service features from working correctly.
5.3 Global Privacy Control
Where legally required, we will treat a valid Global Privacy Control signal as a request to opt out of sale or sharing for cross-context behavioral advertising. Armidus does not currently sell personal information for money or intend to share it for cross-context behavioral advertising.
5.4 Provider controls
Some providers offer their own privacy controls. A provider-level control may apply across sites using that provider. It does not replace choices that Armidus is required to provide on its own Site.
6. Do Not Track
Some browsers offer a Do Not Track setting, but there is no consistently accepted technical standard for responding to it. We do not currently respond to ordinary Do Not Track headers. This does not affect our response to a Global Privacy Control signal where applicable law requires one.
7. International processing
Cookie and website interaction information may be processed by HubSpot, FirstPromoter, Netlify, Clerk, Stripe, YouTube (Google), and their subprocessors in the United States, Romania, or other locations where they operate. Website visitors who play the optional product video may have technical information processed by YouTube in locations where Google operates. FirstPromoter is provided by IGIL WEBS S.R.L. in Romania. Information associated with Stripe transactions may also be exchanged between Stripe and FirstPromoter for affiliate attribution. Regional storage of core Clinic application records does not mean that all website, authentication, or payment information stays in the Clinic's country. See the Privacy Policy and Subprocessors and Service Providers page for more information.
8. Changes to this Policy
We may update this Policy when our technology, providers, legal obligations, or practices change. We will post the revised version with a new effective date. Where required, we will ask for a new choice before using a new non-essential cookie category.
9. Contact us
Use the Privacy option at https://armidus.com/submit-request if you have a question about cookies or this Policy. Do not include patient records, passwords, payment-card information, or claim links in the form.
You may also contact Armidus's Data Protection Officer at privacy@armidus.com.
You may also contact us by post:
Armidus, Inc. 1111B South Governors Avenue #49736 Dover, DE 19904 United States