How DevToolKit handles your data

DevToolKit aims to provide privacy-aware PDF, image, and developer tools with clear processing labels. This page explains, in plain language, how information and files may be handled when you use the website.

This page is not legal advice. If you need formal legal guidance, consult a qualified professional.

When you contact DevToolKit by email, we may receive your email address, message content, and details you choose to include such as bug reports, browser information, or use-case descriptions.

DevToolKit does not require an account for basic tools today.

Some tools accept files or text inputs to perform a task. You should only upload or paste content you own or have permission to process.

Developer tools may accept tokens, JSON, regex, or other sensitive text. Treat these inputs carefully and review each tool’s processing label first.

Where supported, tools run in your browser and may not require uploading files to DevToolKit servers for the core task.

Local processing is the preferred default for simple PDF utilities, image edits, and many developer tools.

Heavier tasks — such as background removal, advanced PDF editing, conversion, OCR, and large files — may use temporary server processing.

Files processed on servers are intended to be handled only for the job duration. Formal TTL deletion windows and stronger retention controls are still being built.

AI-assisted features, where available or planned, should require explicit user action and should not run hidden inside basic tools.

DevToolKit is designed so sensitive content is not silently sent to third-party AI services. Credit-based limits for AI actions may be added later.

DevToolKit may use privacy-friendly analytics and diagnostics to understand usage patterns, improve reliability, and fix bugs.

Analytics is intended to be metadata-focused and should not store uploaded file contents.

DevToolKit may display third-party advertisements through Google AdSense or similar programs to help support the free tools. Ads are not live on every page until explicitly enabled after program approval.

Google and its partners may use cookies or device identifiers to serve ads based on your visits to this site and other sites, subject to your settings and applicable law.

You can manage personalized advertising preferences at https://adssettings.google.com and review Google’s advertising policies at https://policies.google.com/technologies/ads.

DevToolKit does not sell your personal information. Ad partners receive limited technical data needed to deliver and measure ads, not the contents of files you upload to tools.

DevToolKit may use cookies, local storage, and similar browser technologies to remember preferences and support site functionality.

If advertising is enabled, Google AdSense and related partners may set cookies to limit repeat ads, measure performance, and detect fraud. You may see an “Advertisement” label near ad units.

You can control cookies through your browser settings. Blocking all cookies may affect some tool preferences or site features.

Support emails are kept only as long as reasonably necessary to respond and improve the service.

Server-processed files are handled temporarily. Retention windows will be documented more formally as infrastructure matures.

DevToolKit may rely on hosting, storage, analytics, advertising, or AI providers to operate parts of the service.

Where third-party services are used, DevToolKit aims to limit the data shared to what is needed for the selected task.

Do not upload files you do not own or have permission to process.

Review outputs before sharing, signing, submitting, or publishing them.

Avoid pasting production secrets into tools unless you understand the processing mode and trust the workflow.

For privacy questions, email DevToolKit at amanhirut32@gmail.com. Include enough detail for us to understand your question, but avoid sending confidential file contents unless necessary.