Effective Date: January 5th, 2026
This Cookie Policy explains how Revion Solutions, Inc. (“Revion,” “Revion.com,” “we,” or “us”) uses cookies and similar tracking technologies when you visit or interact with our websites, customer portals, and related online services (collectively, the “Sites”). This policy should be read together with our Privacy Policy.
Continuing to browse is not consent. Nothing beyond the consent cookie itself is loaded on this website until you choose it in the banner, and you can change that choice at any time from section 6.
1. What Are Cookies?
Cookies are small text files placed on your device when you visit a website. They may store information such as preferences, session identifiers, or analytics data, allowing websites to recognize your device or improve functionality.
2. Why We Use Cookies
This policy describes revion.com, the website you are reading. Our customer portal at secure.revion.com is a separate application with its own session cookies, described where you log in.
On this website there are three purposes, and only one of them happens without you asking for it.
The first is remembering the cookie choices you make in our banner, so that we do not ask you again on every page. The second is booking a meeting: our meeting request page carries a calendar provided by Cal.com, and that calendar loads for every visitor as soon as the page opens, before and regardless of any answer to the banner. The third is Google Analytics 4, which counts page views so that we can tell which pages are worth keeping and which ones nobody finds. Analytics is off until you switch it on, and while it is off it is not loaded at all.
We do not use cookies on this website for advertising or retargeting, for live chat, or for building a profile of you. There is no Google Tag Manager, no Plausible, no Fathom, no Hotjar and no Microsoft Clarity on this site, and no advertising or remarketing tag of any kind. Our web fonts are served from our own servers, so loading a page contacts no font network.
3. Categories We Use
The banner offers three categories, and all three describe something real. There is no advertising category, because there is nothing on this site to put in one.
- Essential. The consent cookie, the booking calendar on our meeting request page, and the disclosure of reCAPTCHA v3 in section 5. Always on. The consent cookie is here because without it we cannot remember what you chose; the calendar and reCAPTCHA are here because each is the only way one particular thing on this site works, and neither is a tracking product.
- Analytics. Google Analytics 4. Off until you turn it on.
- YouTube. Embedded video. Off until you turn it on.
There used to be a fourth, Functional, and it controlled one thing: the scheduling widget that used to be our booking calendar. That widget has been replaced by Cal.com, which is not gated, so the category had nothing left in it and has been removed rather than left on the banner controlling nothing. Because the set of categories has changed, the choice you made under the old set is no longer a choice about the current one, and the banner will ask you once more.
Analytics is a plain on or off switch and not a consent signal sent to Google. We do not load the tag in a restricted mode while you decide, and we do not send Google a cookieless or anonymized message about your visit. Until you turn the category on, the measurement tag is not in the page, so there is nothing that could send anything to anybody.
4. Third-Party Cookies
Three things on this website are served by other companies. Two of them wait for you to allow them. One of them does not, and it is listed first so that it is not buried.
- Cal.com, which provides the booking calendar on our meeting request page, and which is not behind a category. It loads as soon as that page opens, for every visitor, before you have answered the banner and whatever you answer. That page exists to book a meeting and does nothing else, so a calendar that waited for permission would leave it empty; we treat it as strictly necessary to that one page, the same as reCAPTCHA v3 on our forms, and disclose it here instead of putting a switch on it. It is on that page and on no other. Cal.com loads the calendar in a frame of its own, and that frame is Cal.com’s page rather than ours, so it carries Cal.com’s own suppliers. We measured exactly one: Sentry, which Cal.com uses to collect its own error reports. Sentry stores nothing on your device, which is why it has no row in section 5. No advertising company, no social network and no analytics product is contacted from inside that frame, and no Google host is contacted at all. The four cookies the calendar sets are in section 5; they are on cal.com and app.cal.com rather than on our domain. If you would rather not load it, simply do not open that page: every link to it is an ordinary link, and the page itself carries the booking address, our telephone number and our email address in plain text under the calendar.
- Google Analytics 4, which counts page views and records which site or search sent you here. The tag is served by Google from googletagmanager.com and writes the two measurement cookies in section 5. Once you allow the Analytics category it also sends a request to stats.g.doubleclick.net, a Google advertising domain, which is a part of Google Analytics 4 itself rather than an advertising tag we have added; nothing on this site uses it to advertise to you, and no such request is made while the category is off. While the Analytics category is off, no measurement cookie is written and nothing about your visit reaches Google from this site in any form. Declining is not anonymized measurement. It is no measurement.
- YouTube, through youtube-nocookie.com, which withholds view-based ad personalization but still sets cookies once a video is loaded. No page on this site embeds a video at present, so allowing this category currently loads nothing and sets nothing; it is kept because the category has to exist before a video can be added behind it. While the YouTube category is off, no video frame is created and no request is made to YouTube. Every video also carries a plain link to it on YouTube, so the content stays reachable whether or not you allow the category.
5. Cookies Used on This Website
One is ours, and it is written only once you answer the banner. Two are written by Google Analytics 4 if you allow the Analytics category. Four are written inside the booking calendar on our meeting request page, for every visitor and whatever you have chosen, because that calendar is not behind a category; three of those four come from Cal.com itself and one from Cloudflare, which serves Cal.com. Open no other page and none of the four is written. Every lifetime below is the lifetime we measured in a browser, which is not always the lifetime the vendor asks for:
| COOKIE | SET BY | LIFETIME | PURPOSE |
|---|---|---|---|
| revion_consent | revion.com, first party | 12 months | Records which cookie categories you allowed, together with the version of the cookie notice you were shown, so that we do not ask again until that notice changes. It holds a setting and nothing else: no visitor identifier, no profile, nothing that identifies you or follows you between visits. |
| _ga | Google Analytics 4, written on the revion.com domain by the tag we load | 400 days, which is about 13 months and is the longest a current browser will keep it | A randomly generated identifier for the browser, so that two page views from the same browser are counted as one visitor rather than two. Written only after you allow the Analytics category. |
| _ga_T94F03YGES | Google Analytics 4, written on the revion.com domain by the tag we load | 400 days, which is about 13 months and is the longest a current browser will keep it | Holds the state of the current session for our specific Analytics property, whose measurement identifier is the part after _ga_. Written only after you allow the Analytics category. |
| __cf_bm | Cloudflare, inside the Cal.com booking calendar, on the cal.com domain. Written on the meeting request page for every visitor, whatever you have chosen | 30 minutes, measured at 29 to 30 | Tells automated traffic apart from real visitors, so that the booking calendar stays available to people. It reads how a request was made, not who made it. |
| __Secure-next-auth.callback-url | Cal.com, on the cal.com domain. Written on the meeting request page for every visitor, whatever you have chosen | Until you close your browser | Part of the sign-in machinery of the Cal.com application the calendar page is built on. You are not signing in to anything and it holds no account of yours. |
| __Secure-next-auth.csrf-token | Cal.com, on the cal.com domain. Written on the meeting request page for every visitor, whatever you have chosen | Until you close your browser | A one-visit token that lets Cal.com tell a form you submitted apart from one another site submitted on your behalf. |
| uid | Cal.com, on the app.cal.com domain. Written only once you pick a time slot; opening the page does not write it | Until you close your browser | Holds the slot Cal.com has put on hold for you while you fill in the booking form, so that two people cannot be given the same time. |
Both Analytics cookies are deleted the moment you switch the Analytics category back off. See section 6.
reCAPTCHA v3 is not a cookie this site sets, but it is worth being exact about. Our contact and quote forms are checked by Google reCAPTCHA v3 so that the inbox they feed stays usable. It is requested from Google at the moment you press the send button, and at no other time. A visitor who reads a page and leaves without submitting a form never contacts Google, and no reCAPTCHA cookie is set. Because the protection is only useful if it is present when a form is actually submitted, reCAPTCHA is disclosed here rather than placed behind a consent toggle.
Earlier versions of this policy listed cookies belonging to the previous WordPress website, its consent plugin, its page builder and its form plugin. That platform has been replaced. None of those cookies are set any more, and the descriptions of them have been removed rather than left to look current.
6. Managing Cookies and Consent
You can change or withdraw your choices at any time, and doing so takes effect immediately. Withdrawing the Analytics category takes the measurement tag out of the page, stops it sending anything further, and deletes the _ga and _ga_T94F03YGES cookies it had set. Withdrawing the YouTube category removes any video frame on the page. The booking calendar is not one of the choices, so there is nothing there to withdraw; not opening the meeting request page is what stops it loading. The four cookies it sets are on Cal.com’s domains rather than ours, so we cannot delete them for you: three of the four are gone when you close your browser, the fourth expires in half an hour, and your browser settings can clear them sooner.
You can also delete the cookie in your browser, which returns the site to its starting state and asks you again on your next visit, or block cookies in your browser settings entirely. Blocking them means we cannot remember your answer, so the banner will appear on every visit and nothing in the Analytics, Functional or YouTube categories will load.
7. Do Not Track
Revion Sites do not currently respond to browser-based Do Not Track signals.
8. Links to Other Websites
Revion Sites may contain links to external websites or services that use their own cookies. Revion is not responsible for third-party cookie practices.
9. Updates to This Cookie Policy
Revion may update this Cookie Policy periodically. Updated versions will be posted to this page with a new effective date.
10. Contact
Questions or requests related to this Cookie Policy or cookie preferences may be submitted through our contact page at:
https://revion.com/company/contact/
Last Updated: January 5th, 2026