Last updated: August 15, 2026
This Cookie Policy explains how QuickConvertify uses cookies and similar browser-storage technologies in the current website build. It should be read together with the Privacy Policy.
What cookies and browser storage are
A cookie is a small value that a website can ask a browser to store and send back with later requests. Browsers also provide storage mechanisms such as sessionStorage and localStorage. These technologies work differently from cookies but can also remember information on a device.
QuickConvertify first-touch session storage
The built-in tool analytics code uses sessionStorage with the key ucs_first_touch_v1. It remembers limited first-touch attribution for the current browsing session so tool events can be attributed consistently. The stored information can include channel, source, medium, campaign, referring domain, landing path and the type of a recognized advertising click identifier. It does not contain converter file contents, filenames, search queries or advertising click values.
This item is session-scoped rather than intended as persistent long-term storage. Browser behavior determines exactly when a browsing session ends and when session storage is cleared.
WordPress cookies
WordPress can use cookies for essential platform functions. Depending on which parts of WordPress are used, these can include authentication cookies for logged-in administrators or registered users, a login test cookie and preference or language cookies. If commenting features are enabled on any part of the site, WordPress may also offer commenter cookies. The current QuickConvertify setup closes comments by default.
Converter functionality
The included browser-side conversion tools do not require an advertising cookie in order to process supported files locally. A selected file remains subject to the tool-specific private-processing notice and is not placed into a cookie.
Analytics and advertising services
The current Universal Tool Studio plugin includes its own first-party event analytics and does not require Google Analytics or an advertising platform for the converter engine to function. If the site operator later adds third-party analytics, advertising, embedded media, affiliate tracking or a consent-management platform, those services may use additional cookies, pixels or device storage. This policy should then be updated to identify the new purposes and controls.
Consent and non-essential technologies
Some jurisdictions require consent before non-essential cookies or similar storage/access technologies are used. If QuickConvertify introduces a technology that requires consent under applicable law, the site operator should provide an appropriate consent mechanism and respect the visitor’s choice before activating that technology.
How to control cookies and storage
You can review, block or delete cookies and site data through your browser settings. Most browsers also allow you to clear session or site storage. Blocking essential WordPress cookies can prevent login or account-related functionality, while clearing session storage can reset the first-touch attribution remembered for that browsing session.
Do Not Track and browser privacy signals
Browser privacy signals and legal opt-out requirements continue to evolve. The built-in QuickConvertify analytics do not include a feature that sells personal information or uses converter inputs for cross-context behavioral advertising. If data practices change in a way that makes a legally required opt-out signal applicable, the site operator should update both the technical implementation and this policy.
Changes to this policy
This policy should be updated whenever a new plugin, advertising service, analytics service, embedded feature or other technology materially changes how cookies or device storage are used. The revised date at the top of the page indicates the latest published version.
Questions
Use the Contact page if you have a question about a cookie or storage item you observe on QuickConvertify. Browser developer tools can be useful for identifying the cookie name, domain and storage type involved.