This Cookie Policy explains how Welobadge, LLC ("Welo", "we", "us"), 131 Continental Dr, Suite 305, Newark, DE 19713, New Castle County, USA, uses cookies and similar storage when you browse welobadge.com, follow Welo links, register, use the client portal or interact with our services. Read it together with our Privacy Policy, which explains personal-data purposes, recipients, retention criteria, transfers and your rights.
Questions about this Policy or your choices can be sent to daniel@welobadge.com or support@welobadge.com. You can reopen the preference center through Manage cookies. A cookie choice is separate from accepting our Terms, acknowledging the Privacy Policy or subscribing to promotional emails.
A cookie is a small value saved by a website in your browser and sent with matching requests. First-party cookies are set for the service you visit; third-party technologies are associated with another provider. Some cookies identify a browser or session, while others simply remember a language or a choice. A cookie is not necessarily anonymous: an identifier can relate visits to a device, account, application or campaign.
We also use localStorage, which can remain until removed or cleared by the browser or service, and sessionStorage, which generally lasts for the current tab's browsing session. Pixels and scripts can send interaction data without relying on a traditional cookie. This Policy covers those technologies as well. A cookie's browser expiry is different from how long related server records are retained.
The preference center offers service storage, analytics and marketing categories. Session authentication, security, requested form continuation and remembering your choices support operation of the service. Optional analytics integrations start after analytics consent; external advertising integrations start after marketing consent. Google Tag Manager is enabled only when both optional categories are accepted because a container can include different kinds of tags.
Some first-party measurement and link markers currently operate separately from those optional categories, as expressly described below. Refusing analytics or marketing therefore does not mean that every first-party cookie or record is removed. This explanation describes actual behavior; it does not turn a measurement technology into an essential technology merely because it is first-party.
welo_named_link_seen and welo_named_link_engaged are per-link opening and interaction markers that may remain for up to 90 days, including when analytics and marketing are refused. They are not unique visitor IDs, are not used across sites and are not used to attribute sales. They help distinguish link opening from a qualifying interaction.
Welo's first-party campaign measurement can also save welo_ads_v, a signed browser identifier for up to one year, and welo_ads_s, a signed session identifier for up to 30 days. These cookies can be set even without marketing consent. Limited first-touch context can also be saved in welo_ads_first_touch in sessionStorage. The word "session" in an identifier does not mean that every related cookie necessarily disappears when you close a tab.
The related records can include landing page, referring page, campaign parameters, advertising campaign references, time, device or browser information, country where available and the recorded consent state. Identifiers present in the URL may form part of campaign context. External advertising tags and transmissions are separately controlled by marketing consent. These internal measurements are not described as anonymous or as automatically exempt from consent solely because they use Welo's domain.
After analytics consent, Welo can create welo_website_visitor in localStorage and welo_website_session in sessionStorage. These help relate visits or page requests to a browser and session. localStorage has no inherent cookie-style expiry; it can remain until the service, you or the browser removes it. The session value generally lasts for the tab session.
Analytics requests can include the path visited, selected UTM campaign parameters, referring page, device category and country where available. The enabled integrations include Google Analytics, Umami, Ahrefs Analytics and Welo's analytics service. Measurements can be aggregated for reporting, but the collection may use pseudonymous identifiers and must not be understood as invariably anonymous.
Providers may create their own cookies or storage when their integration is active. For example, Google Analytics can use cookie names beginning with _ga. The exact names and durations depend on the provider and current configuration; the first-party periods in this Policy do not establish a blanket two-year lifetime for all analytics technologies.
After marketing consent, the relevant pages can activate Google Ads, Meta Pixel, TikTok Pixel and Paved advertising measurement, together with Welo's optional attribution tools. These technologies can measure advertising results, connect a visit or eligible conversion to a campaign, prevent duplicate conversion reporting and support advertising personalization where enabled by the provider and your choices.
welo_attribution can preserve optional attribution context in a cookie for up to 30 days and in browser storage. Vendor integrations may use identifiers or cookie names such as _gcl*, _fbp, _fbc or _ttp. These are examples, not a promise that each cookie appears for every visitor. Transmission can include event names, campaign and event identifiers, page information and device or browser information; relevant account or conversion data may be handled as explained in the Privacy Policy.
The provider can recognize activity across services where its technology and applicable consent permit it. Merely using the label "marketing" does not mean that Welo sells your information. The purpose, recipients and applicable choices determine the processing. Refusing these integrations does not prevent you from submitting an application or contacting Welo.
On a first visit, optional integrations are off until a choice authorizes the relevant category. You can accept both optional categories, refuse analytics and marketing, or customize them separately. Use Manage cookies to reopen the controls, change the switches and save. A choice applies to the browser and storage context where it is recorded; it is not automatically synchronized with every device or browser you use.
When you withdraw an optional category, Welo stops the corresponding optional integrations, requests advertising consent revocation where supported, clears known optional analytics or advertising storage and reloads the page to unload previously loaded integrations. Some first-party storage described in sections 4 and 5 may remain. Welo cannot use a browser preference to erase data already received by another provider; applicable deletion requests and provider controls remain available.
Refusal does not remove ordinary access to the service, although blocking service cookies in the browser can prevent sign-in, form continuation or remembering your choices. Revoking cookies does not automatically unsubscribe you from email or close your account. Those are separate requests.
Most browsers let you inspect cookies and site data, remove selected data, block third-party cookies or clear all storage. Chrome, Safari, Firefox and Edge provide these controls in their privacy or site-data settings. The available names and effects vary by browser and version; use the help information provided by your browser.
Deleting cookies may sign you out, remove drafts or make the consent banner reappear. Blocking only cookies may leave localStorage or sessionStorage intact, and private browsing does not guarantee that no request data reaches the service. You may need to remove both cookies and other site data. On a shared device, sign out and consider clearing saved drafts and site data when you finish.
When an optional integration is enabled, its provider can receive data under the applicable service configuration. The providers named above publish their own privacy and technology notices, including Google, Meta, TikTok, Umami and Ahrefs. Their settings and notices supplement this Policy; they do not replace Welo's responsibility for its own processing.
Some providers may process information outside your country or the EEA. See the Privacy Policy and contact Welo for information about the relevant recipients, locations and transfer safeguards. Payment or support services may use additional service-related storage when you open those services; their own notices describe their processing.
The durations above describe the relevant first-party storage settings, not a guarantee that data survives for the whole period. A browser can delete it sooner; a new interaction or save can refresh a value; and signing out, expiry or a changed setting can replace it. Vendor storage depends on the enabled integration. Related server records follow the retention criteria in the Privacy Policy, including operational, legal, security and dispute needs.
We update this Policy when technologies, providers or purposes change. The update date appears at the top. Where a change requires a new optional choice, that choice must be collected rather than inferred solely from continued browsing. Contact Welo if you need clarification about a particular cookie or wish to exercise your privacy rights.