Privacy, cookies and ads
How tools.junyo.dev handles data, consent, analytics, cookies and ads.
Tool data
Inputs typed into tools are not sent to analytics. Passwords, hashes, text, code and sensitive results stay in the browser whenever the tool is client-side.
Some network tools may call APIs to provide their functionality. In those cases, the request is operational and should be limited to what is necessary to answer the user.
Consent and cookies
The site stores a first-party cookie/localStorage entry named `tools_consent_v1` to remember analytics and ads preferences for up to 180 days.
By default, analytics and ad storage start denied. You can accept, reject or adjust preferences from the footer at any time.
Analytics
When allowed, analytics records aggregate events such as page views, tool usage, copy actions, categorical errors and Web Vitals. User-entered content is not captured.
Ads
Ads are manual, labeled as advertisements and loaded only outside the widget. On desktop, eligible pages may reserve side banners outside the tool plus one in-content slot; quick lookups use a reduced format. `/embed` routes do not load ads.
When enabled, AdSense and/or Media.net may use cookies or local storage according to their policies and your consent preferences. Without that permission, ads may be contextual, limited or not shown.
Affiliate links
Some pages may show editorial cards for related resources, always identified as affiliate-link recommendations. If you click and purchase or subscribe, the site may earn a commission at no additional cost to you.
Planned networks include Awin, Hotmart, Amazon Associates Brazil, Hostinger and compatible direct programs. Links use UTM parameters and/or clickRef to measure CTR and conversion per tool, without capturing what you type into the widget.
Sensitive tools, especially child health, ideal weight, body-fat percentage and technical health lookups, may intentionally avoid editorial affiliates for regulatory and editorial safety.