Vugola Cookie Policy

    Effective as of October 8, 2026 · Last Updated: October 8, 2026

    This Cookie Policy explains how Vugola, a product of Vugola LLC ("Vugola," "we," "our," or "us"), uses cookies and similar storage and tracking technologies when you visit or use our platform, websites, and other products and services ("Services"). It describes what these technologies are, the categories we use, who places them, how long they last, and the choices you have, including how to accept, reject, or opt out of analytics.

    This Cookie Policy is part of, and should be read together with, our Privacy Policy and our Terms of Service. Any terms we use here without defining them have the meaning given to them in those documents. Where this Cookie Policy describes how we handle personal data, the broader practices, your rights, and our legal bases are set out in the Privacy Policy.

    1. What Are Cookies and Similar Technologies

    Cookies are small text files that a website places on your device to store information. We also use related technologies that serve the same purpose, including browser local storage and session storage, software development kits, pixels, and similar identifiers. In this Cookie Policy we refer to all of these together as "cookies."

    Cookies can be "first-party" (set by Vugola) or "third-party" (set by a service provider we work with). They can also be "session" cookies, which are deleted when you close your browser, or "persistent" cookies, which stay on your device until they expire or you delete them. Some of the technologies we use, including the analytics tools described below, store information in your browser's local storage as well as, or instead of, a traditional cookie, but we treat them the same way as cookies.

    2. The Categories of Cookies We Use

    We group the cookies we use into four categories: strictly necessary, preference, affiliate referral, and analytics. We do not use cross-context behavioral advertising cookies or advertising pixels, and we do not run third-party ad networks on the Services.

    2.1 Strictly Necessary Cookies

    These cookies are required for the Services to work. They cannot be switched off through our consent controls, because without them core features such as signing in and keeping your session secure would not function. We rely on these on the basis that they are essential to deliver a service you have requested, so they are set without asking for consent. Strictly necessary cookies include:

    • Authentication and session cookies that keep you signed in, maintain your session, and protect against unauthorized access. These are set by our authentication and database provider.
    • Security cookies that help protect the Services against abuse and fraud.
    • Your analytics choice itself, which we store in your browser so that we remember whether you accepted, rejected, or opted out of analytics and do not have to ask you again on every visit. This is stored in your browser's local storage under the key "vugola_cookie_consent." If a rejection cannot be saved there, we keep it in session storage for the current tab. Selecting "OK" on our one-line analytics notice is saved the same way as "Accept." To keep the analytics tools off before you choose and after you reject, we also store two small "off" markers in local storage, one for each tool. While "Cookie settings" is open, a marker in session storage keeps it open if the page reloads.

    2.2 Preference Cookies

    These remember interface settings in your browser, such as whether the dashboard sidebar is open, your editor theme, and the sign-in method you last used. Vugola sets them, and we do not use them for analytics or advertising. "Cookie settings" does not control them; you can clear them in your browser.

    2.3 Affiliate Referral Cookies

    When you follow a creator's referral link, our affiliate tracking provider stores a first-party referral cookie, and Vugola stores its own first-party cookies and a copy in browser storage that hold the referral ID and the creator's code, each for up to 30 days. Its script loads on our website pages but sets no referral cookie unless you arrived from a referral link. If you create a new account, we associate that ID with your account to credit the creator for eligible subscription payments and renewals made through our payment processor. We do not use this tracking for iPhone App Store purchases.

    Creator campaign links work in a similar way in every region: we save the creator's campaign code in your browser's local storage so we can credit that creator if you sign up. A code from a current campaign link expires after 30 days. A code saved by one of our older campaign links has no fixed expiry and stays until it is used at sign-up or you clear your browser storage.

    Affiliate referral tracking applies in every region and starts when you arrive from a referral link, without a banner click. The cookie banner, "Cookie settings," and Global Privacy Control do not turn it off. If you do not want a referral recorded, do not follow a creator's referral link, or block or clear cookies in your browser.

    2.4 Analytics Cookies

    These optional tools help us understand how visitors use the Services. They are not required for the Services to function. Section 3 explains when they run, and Section 4 explains how to turn them off. We use:

    • Product analytics. We use a product analytics tool to understand how the Services are used, including pages viewed, features used, sign-ups, and usage patterns. Once analytics are allowed, it uses a random visitor ID that we create and store in a first-party cookie and in your browser's local storage. The ID stays the same across visits, so we can tell when the same browser comes back, until you sign out, turn analytics off, or clear your browser storage. When you are signed in, it also uses an internal account ID that stands in for your account. We do not send your name or email address to our product analytics provider. The same cookie and local storage entry also keep the address of the first page you opened and of the page that referred you, and your browser's session storage keeps the campaign tags and any advertising click ID from the link you followed. These stay in your browser; only the campaign tags and the referring domain are sent to our provider. We use this data to understand and improve the Services, not to build advertising profiles.
    • Session recordings. When you are signed in, the product analytics tool makes masked session recordings of how the product is used, so we can find bugs and points of friction. All on-screen text and everything you type are masked, and media (video, audio, and images) is not recorded. Recordings never run on our public marketing pages. They are on by default for signed-in users where analytics are on by default, and run only after "Accept" where we ask for your consent first. Rejecting analytics or turning them off in "Cookie settings" keeps recordings off too.
    • Website analytics. We use a website analytics tool to measure where visitors come from and which campaigns bring them. If you allow it and later subscribe, it links your visit to your payment record so we can see which pages and campaigns lead to purchases. If you do not allow it, our website analytics provider may still receive the amount, date, and a transaction reference for each payment, with no visitor or customer ID attached, so our revenue totals are complete. It runs by default wherever our product analytics run by default, and only after you choose "Accept" where we ask for your consent first.
    • Help video statistics. The embedded player for our help videos loads when you open a page or pop-up that shows one. It records viewing statistics wherever our analytics run: by default where analytics are on by default, and only after you choose "Accept" where we ask for your consent first. Turning analytics off in "Cookie settings" turns these statistics off.
    • Cookieless visit counts. Where we ask for your consent first, we count visits to our pages before you answer the banner, while you are signed out. This uses no cookie and stores nothing on your device, so it is not a cookie; we describe it here so you know about it. Our product analytics provider receives the page you opened, the campaign tags and referring domain described below, whether you are on a phone, tablet, or computer, and the user-agent text your browser sends. It counts visitors with a one-way code that it builds from your IP address, that user-agent text, and a secret value it replaces every day, and it does not store the IP address or the user-agent text with the visit. No visitor ID is stored on your device and the code changes every day, so a visit cannot be recognized on a later day or connected to an account. Choosing "Reject" turns the count off, and choosing "Accept" replaces it with the product analytics above.

    Our product analytics record where your visit came from: the campaign tags in the link you followed (source, medium, campaign, content, and term), the creator's referral code if you followed a creator's link, and the domain of the site that referred you, never that site's full address. They do not record advertising click IDs. They do not record your location today. If that changes, they will record nothing more precise than your country, which our provider would work out from your IP address when the data arrives. The tool is set not to store the IP address itself.

    Where it runs, the website analytics tool records how you reached our site, including the site that referred you and any campaign tags (such as utm_source or utm_campaign) or creator's referral code in the link you followed. It also records your approximate location, such as your country or city, which is worked out from your IP address when the data is collected. Some analytics requests may be routed through our own domain before they reach these providers.

    3. When Analytics Cookies Run, and When They Are Off

    How we treat analytics cookies depends on where you are and, in some regions, on a privacy signal your browser sends. Affiliate referral cookies follow Section 2.3 in every region.

    • Where local law requires prior consent (opt-in). This includes the European Union and the rest of the European Economic Area (including Norway, Iceland, and Liechtenstein) and other European countries outside the UK and Switzerland, Turkey, Nigeria, Vietnam, China, and Quebec in Canada where we can recognize it (a visitor in Quebec whose browser uses the Toronto time zone and a language other than French is treated as elsewhere in Canada), as well as any visit where we cannot determine your location. There, analytics cookies stay off until you affirmatively opt in. We show a consent banner with "Accept" and "Reject" options, and we do not treat continued use of the site as consent. Product analytics that use cookies, session recordings, and the website analytics tool are enabled only if you choose "Accept." If you choose "Reject," or take no action, they remain off. Until you answer, two things run without cookies: the cookieless visit count described in Section 2.4 and, once you have signed in, the events our servers record for your account, described in Section 2.4 of our Privacy Policy. Choosing "Reject" turns both off. If your browser or a browser extension sends a Global Privacy Control (GPC) signal, we treat it as a rejection and keep all of these off.
    • United Kingdom (on by default, with a right to object). We do not show a banner. On your first visit we show a one-line notice with an "OK" button, which works as described for other regions below. Our product analytics run by default to collect statistics that help us understand and improve the Services. The Privacy and Electronic Communications Regulations 2003, as amended by the Data (Use and Access) Act 2025, allow this without consent when we tell you about it and give you a simple way to object. Session recordings of signed-in use, described in Section 2.4, the website analytics tool, including connecting your visit to a later payment, help video statistics, and the record of which onboarding steps and features you open are also on by default. You can object at any time through "Cookie settings" in our website footer or in your dashboard account menu, which turns all of these off. If your browser or a browser extension sends a GPC signal, we treat it as an objection and keep them off.
    • Everywhere else, including the United States and Switzerland (opt-out). We do not show a banner. On your first visit we show the same one-line notice with an "OK" button. Product analytics, including the record of which onboarding steps and features you open, the website analytics tool, including connecting your visit to a later payment, help video statistics and session recordings of signed-in use run by default. Selecting "OK" dismisses the notice and is saved as "Accept." It does not change what runs. That notice and this Cookie Policy are our notice to you, and you can refuse or opt out at any time through "Cookie settings" in our website footer or in your dashboard account menu. Here, a GPC signal does not turn off these analytics, because they are our own first-party analytics and we do not sell your personal information or share it for cross-context behavioral advertising. If that ever changes, we will honor GPC as an opt-out of that selling or sharing.

    We do not use Do Not Track as an opt-out signal in any region.

    We estimate your region from your browser's time zone and, in eastern Canada, its language; we do not use your IP address for this. If we cannot determine it, we ask for your consent before any analytics cookies are set. While a page works out whether analytics may run, for example while it checks whether you are signed in, it holds a small number of analytics events and the campaign source of your visit in the page's memory only. They are sent only if analytics are allowed; otherwise they are discarded or disappear when you leave the page. The one exception is the cookieless visit count described in Section 2.4, which sends the page and the campaign source of that visit. If you clicked "Reject" or turned analytics off, including before October 8, 2026, that choice stays in place until you change it. Strictly necessary cookies are used in all regions because they are essential to the Services.

    4. How to Manage or Withdraw Your Choices

    You are in control of analytics cookies, and you can change your mind at any time. You have the following options:

    • Cookie settings. Use the "Cookie settings" link in our website footer or in your dashboard account menu to change your choice at any time. Opening it turns product analytics, session recordings, and website analytics off for that browser straight away and deletes the visitor ID. They stay off until you choose "Accept," including if you close the page without choosing. Where we asked for your consent, you can withdraw it just as easily as you gave it.
    • The analytics notice. Where we show the one-line notice, analytics already run; "OK" dismisses the notice, and "Cookie settings" in our site footer or your dashboard account menu opens your choices.
    • The consent banner. If you are in a region where the banner is shown, you can select "Reject" to keep analytics cookies off, or "Accept" to allow them. "Reject" also turns off the cookieless visit count in that browser and the events our servers record for your account. If you choose while signed out, the choice reaches your account the next time you sign in from that browser.
    • Global Privacy Control (GPC). If your browser or a browser extension sends a GPC signal, we treat it as an opt-out of analytics in the United Kingdom and wherever we ask for your consent first, and you do not need to do anything else. Everywhere else, GPC does not turn off our own first-party analytics; use "Cookie settings" instead. We do not sell your personal information or share it for cross-context behavioral advertising, and if that ever changes we will honor GPC as an opt-out of that selling or sharing.
    • Do Not Track. We do not use Do Not Track as an opt-out signal anywhere.
    • Browser controls. Most browsers let you block or delete cookies and clear local storage through their settings. If you block strictly necessary cookies, parts of the Services, including signing in, may not work. Clearing your browser storage will also clear your saved choice, so you may be asked to choose again.

    Your analytics choice is stored in your own browser, so clearing your browser data or using a different browser or device resets it there. When you are signed in, we also save your choice with your account: if you turned analytics off, that carries over to other browsers when you sign in, unless that browser has its own saved "OK" or "Accept." There, product analytics stop, and website analytics and help video statistics continue until you turn them off in that browser. In a team workspace, product analytics in the browser run only while every active member allows them, and the account events our servers record stop for the workspace when any active member turns analytics off.

    5. Cookies Set by Our Service Providers

    Some cookies described above are placed by the third-party providers we use to deliver the Services. These providers process data on our behalf or in line with their own policies. The providers relevant to cookies and on-site tracking cover authentication, session, and security; product analytics, including session recordings; website analytics; embedded video hosting for our help videos; and affiliate referral attribution. Each has its own privacy practices governing data they handle. A fuller description of the providers we work with, and the safeguards that apply, is in our Privacy Policy.

    Besides the affiliate script described in Section 2.3, two other providers load for every visitor in every region and are not controlled by "Cookie settings." An error monitoring tool receives technical details about errors in the Services, along with an internal account ID when you are signed in. A font delivery provider serves the fonts our pages use and receives your IP address when they load. Some error-monitoring requests may be routed through our own domain before they reach the provider.

    Our emails, including transactional and product emails, record whether they were delivered and opened and which links were clicked. Opens are detected with a small tracking pixel in the email. "Cookie settings" applies to our website and does not change this.

    6. How Long Cookies Last

    The lifespan of a cookie depends on its purpose. As a general guide:

    • Session and authentication cookies last for the length of your signed-in session and are refreshed or cleared when you sign out or when the session expires.
    • Your stored analytics choice persists in your browser's local storage until you change it through "Cookie settings," clear your browser storage, or, in the United Kingdom and where we ask for consent first, your browser sends a Global Privacy Control signal.
    • Preference cookies and local storage keep the sidebar setting for seven days and other interface settings until you clear your browser storage.
    • Analytics cookies and local storage set by our analytics tools are persistent and typically last from the end of your session up to around 12 months. For the product analytics visitor ID, those 12 months restart on each visit while analytics are on, and its local storage copy does not expire on its own, so the ID stays until you sign out, turn analytics off in "Cookie settings," or clear your browser storage.
    • Affiliate referral cookies and local storage retain a referral ID and the creator's code for up to 30 days after you arrive from a referral link. A creator campaign code is kept as described in Section 2.3. You can clear them through your browser. An attribution already attached to a paid subscription remains in billing records for commission accounting.

    Actual durations are controlled by each provider and may change. The retention of the underlying analytics data, as distinct from the cookies themselves, is described in the Data Retention section of our Privacy Policy.

    7. Relationship to the Privacy Policy

    This Cookie Policy is part of and incorporated into our Privacy Policy. The Privacy Policy explains, more broadly, the personal data we collect, how and why we use it, the legal bases we rely on, international transfers, your privacy rights (including under the GDPR and the CCPA/CPRA), and how to exercise them. If there is any conflict between this Cookie Policy and the Privacy Policy on a cookie-specific point, this Cookie Policy controls.

    8. Children

    The Services are intended for users who are 18 years of age or older. We do not knowingly use cookies to collect personal information from anyone under 18.

    9. Changes to This Cookie Policy

    We may update this Cookie Policy from time to time to reflect changes in the technologies we use or in applicable law. When we make material changes, we will update the effective date above and, where required, provide a more prominent notice. Your continued use of the Services after an update takes effect means you accept the revised Cookie Policy, subject to any consent we are required to obtain.

    10. Contact Us

    If you have questions about this Cookie Policy or our use of cookies, contact us at:

    Vugola LLC
    Email: hello@vugolaai.com
    Website: https://vugolaai.com