UseBoldTools privacy: how tools, analytics, and cookies work

Overview

UseBoldTools is a collection of free, in-browser utilities for text, PDF, images, developers, and more. The product direction favors client-side execution where practical so you get fast results without uploading content to our application servers for that step.

At the same time, loading a website always involves networking: your browser retrieves HTML, scripts, and assets from hosting and may connect to analytics or ad providers as described below. Those flows are separate from whether a specific tool keeps your paste or file entirely on-device.

Text, files, and tool data (how processing works today)

Across the current tool set, conversion and transformation logic runs in your browser with JavaScript (and relevant open-source libraries where used). For typical tools—text utilities, JSON helpers, timestamps, PDF and image workflows shown on the site—your input is used in memory on your device to produce an output you can copy or download.

• No dedicated “tool API” for your content: the Angular app is served as static and server-rendered pages; there is no separate UseBoldTools endpoint you must call to upload a file so the site can “clean” or convert it on our servers as part of normal tool use.
• Session-like behavior: processed data persists only in your browser tab/session until you refresh or navigate away, unless your browser or extensions store it separately (for example local storage or clipboard history)—that is outside our control.
• Clipboard: copy buttons use the browser clipboard API when permitted; we do not receive the copied value on our servers.

Honest limitation: we cannot guarantee every future feature will remain purely client-side forever. If server-side components are introduced later, this policy and any in-product messaging should be updated to match, and we will avoid implying that uploads never occur if they do.

Analytics (Google)

UseBoldTools loads Google Analytics using the global site tag (gtag) when the measurement ID is configured in the deployed site. The implementation disables automatic initial page-view sends and instead records navigation through the app’s router.

Depending on your browser, consent settings, and Google’s configuration, analytics may process information such as page paths, page titles, general usage events, and technical metadata. Analytics on public websites typically does not include the full text of everything you paste into a tool unless a future, separately documented integration were added—today’s code paths send page-level and configured tool events (for example when a tool tracks a button action), not your raw file bytes as the payload of those requests.

On localhost during development, analytics calls are suppressed in code so local testing does not pollute production reports.

Information we may receive

Beyond analytics, we may receive limited technical data from ordinary hosting and CDN logs (for example IP addresses, user agents, and request metadata) as part of operating any public website.

If you contact us by email, we receive whatever you include in that message and use it to respond. Address: hello@useboldtools.com.

Cookies and similar technologies

Cookies and similar storage may be used for site functionality, measurement, and (if enabled) advertising. Third-party scripts loaded by analytics or ads may set their own cookies subject to their policies and your browser controls.

You can adjust cookie settings in your browser; blocking some categories may affect measurement or certain features.

Advertising

The platform may display advertising now or in the future, including through third-party partners. Ad delivery systems may use cookies or related identifiers. If ads are shown, they are subject to applicable platform policies and regional requirements.

Ad tech operates largely outside our direct control; review partner notices where they appear.

Third-party services

We rely on third parties for hosting, DNS, measurement (such as Google Analytics), and potentially ads or embedded content. Each provider handles data under its own terms.

External links (for example from tool help sections or the About page) are not controlled by UseBoldTools; review those sites’ policies before sharing information there.

Security

We aim to follow reasonable practices for a static/SSR web app, but no online service can be perfectly secure in every scenario.

Do not submit highly sensitive personal data, secrets, or regulated content through tools or email unless you accept the residual risk of working in a browser and over the public internet.

Children’s privacy

UseBoldTools is a general audience utility site and is not directed at children. If you believe a child has sent us personal information, contact hello@useboldtools.com.

Updates to this policy

We may update this page when tools, analytics, or legal expectations change. The effective date above reflects the latest published version.

Contact

Privacy questions, data concerns, or contract inquiries:

You can also use the contact form and topics on the site.

Related pages