AdeDX is built around browser-based tools, and that design choice affects privacy directly. Most pages work without uploading your raw input, which is a very different model from many server-heavy applications. At the same time, the site itself still operates like a modern website, which means hosting, analytics, security, and advertising can involve limited technical data and third-party services. This policy explains both sides clearly so users understand what stays local, what may be processed at the site level, and what choices are available.
This policy applies to the AdeDX website, including the homepage, tool pages, policy pages, contact forms, and related site features. It covers how personal data and technical data may be handled when you browse the site, interact with tools, submit a message, or view pages that contain analytics or advertising integrations. It does not govern the privacy practices of third-party websites you visit after leaving AdeDX.
Tool input includes the text, numbers, dates, lists, files, colors, measurements, code snippets, or other values you enter or load into an AdeDX page in order to get a result. Because much of the catalog is built for local browser processing, that input often remains on your device throughout the session. That distinction is central to the site and is one reason AdeDX can be useful for quick, low-friction tasks.
Site-level data includes routine technical information associated with loading and using the website itself, such as network requests, browser type, approximate region inferred from IP, page URLs visited, referrer information, and timestamps. This kind of data can exist even when a tool is processing your actual working content locally.
A major part of the AdeDX product model is that many tasks can be handled directly with browser-side code. That means the tool does not need to transmit your pasted text, uploaded image, or calculator input to a remote application server just to show output. When that local model is possible, it reduces exposure and keeps the interface fast.
Local processing is common on text transformers, counters, encoders, JSON and CSV helpers, math calculators, date utilities, many image adjustments, and color tools. In these cases, the page loads code into your browser and the work happens there. The result is displayed immediately on the page, and the underlying input generally stays on the same device session where you entered it.
This approach is particularly useful when the data is temporary, internal, or sensitive enough that users do not want to hand it to a third-party processor for a simple formatting or calculation task.
Some tools may need remote information, outside lookups, or third-party services to complete a specific feature. When that is the case, the page should make the behavior reasonably clear rather than implying that everything is purely local. Users should be able to tell whether they are using a fully local helper or a page that relies on a live external request.
If you want confirmation about a specific tool, use the contact page and mention the exact URL so the question can be answered with page-level context.
Like most websites, AdeDX may process limited technical and operational information when a page is requested. This is not the same as uploading tool input, but it can still count as data processing in a legal or policy sense. The purpose is typically site delivery, uptime, security, diagnostics, traffic measurement, and advertising support.
Web hosting layers may process IP address, request paths, response codes, timestamps, user agent strings, and referrer information so pages can be delivered, cached, protected, and debugged. This kind of information is common to normal website operation.
Operational systems may use technical information to detect broken pages, layout failures, script errors, or unusual traffic patterns. That helps maintain a large tool catalog where page integrity and uptime matter.
Request-level data may also be used to prevent abuse, bot floods, malicious scraping, denial-of-service behavior, or other activity that could damage availability for ordinary users.
AdeDX uses local storage for theme preferences and may use or allow third-party technologies that depend on cookies or similar identifiers for analytics, advertising, fraud prevention, or measurement. The presence of local processing on tool input does not eliminate the possibility of cookies at the site level.
The site stores the selected light or dark theme locally in your browser so pages can respect your visual preference. This preference is a convenience feature rather than a user account profile, and it typically stays within the browser where you set it unless your browser syncs local preferences across devices as part of its own settings.
Analytics or advertising services may use cookies or comparable identifiers to measure page activity, understand audience behavior in aggregate, serve advertising, limit fraud, or improve reporting quality. The exact behavior depends on the services active on the page and the settings configured for those services.
AdeDX may use analytics and Google AdSense or related advertising technologies. These systems can help keep the site sustainable and measurable, but they may also involve data collection or identifier use governed by their own terms, policies, and user controls.
Analytics can help identify which tools are useful, which pages underperform, where broken behavior appears, and how visitors move through the site. In practice, this may involve aggregated traffic information, device categories, pageview counts, and interaction patterns rather than the raw content users type into a local tool.
Analytics are meant to improve performance, usability, and maintenance decisions, not to resell your working data.
AdSense may use cookies or similar technologies to serve and measure advertising. Google provides its own explanations, controls, and policy framework for advertising data. If you want to understand how personalized or non-personalized advertising may work in your region, you should review Google's own policy and settings pages in addition to reading this policy.
AdeDX does not promise to control every third-party signal inside advertising systems beyond the configuration choices available to the site owner.
If you voluntarily submit a contact form or send email, that message is intentionally transmitted for communication purposes. In that case, your name, email address, message content, and related metadata may be processed so the question can be reviewed and answered. This is separate from the behavior of a local converter or calculator page.
Contact details are used to respond to support requests, tool suggestions, bug reports, privacy questions, or business inquiries. The message itself may also be used internally to diagnose a reported issue, reproduce a layout problem, or understand a requested feature.
Please avoid sharing unnecessary personal, financial, medical, legal, or other highly sensitive information in a contact message. If you need to report a tool issue, example data or masked samples are usually enough.
Applicable law can differ by country or region, so the exact legal basis for processing may depend on context. In general, AdeDX may rely on legitimate interests, consent where required, contractual communication context for inbound messages, or compliance obligations tied to site operation, security, and recordkeeping.
Site-level logs, analytics records, advertising reports, or contact communications may be retained only as long as reasonably necessary for operational, legal, reporting, support, or abuse-prevention purposes. Retention windows can vary by service provider and system role.
Depending on the law that applies to you, you may have rights related to access, correction, deletion, objection, restriction, portability, or consent withdrawal. Because most tool input is not uploaded in the first place, many requests may concern site-level data or contact communications instead.
If you want to raise a privacy request or question, use the contact page and clearly identify the issue as privacy-related. Mention the relevant page or service context so the request can be reviewed accurately.
AdeDX is a general utility site and is not designed specifically for children. If you believe a child has provided personal information through a contact channel in a way that raises concern, use the contact page so the matter can be reviewed. Also note that third-party services linked from AdeDX, or advertising and analytics partners shown on the site, may have their own policies and regional obligations that operate separately from this page.
No online service can promise absolute security, but AdeDX aims to limit risk by favoring local processing where possible, keeping page structures understandable, and using ordinary hosting and operational safeguards. This policy may be updated as the site, services, integrations, or legal expectations change. The date at the top of the page shows the current revision.
Not necessarily. Many tools are effectively local after the page loads, but some features can depend on external resources, fonts, scripts, or live data. The practical point is that most core tool input processing is browser-based, while the site itself still works as a normal website.
For most local tools, the text is handled in the browser for the purpose of generating the visible output on that page. If a tool does not need to upload the input, AdeDX is not collecting it as server-side form data just because you used the tool.
Because privacy is broader than the calculator itself. A site can avoid uploading tool input and still use analytics or advertising technologies for the page. This policy covers both realities.
Yes. Use the contact page, include the exact page URL, and ask about the specific behavior you want clarified. A page-level answer is often more useful than a generic one.
You can also use browser settings, privacy tools, consent choices where available, and provider controls such as Google's advertising settings. Those controls may affect how some third-party services behave on the site.
AdeDX does not treat your local tool input as something to upload and sell. However, third-party services used for hosting, analytics, or advertising may process technical data under their own legal frameworks and terms, which is why they are disclosed here.