Data Protection

Pure mathematical calculations. You input a number, you get a converted number. No data stored anywhere.

Conversion formulas are hardcoded in JavaScript and execute entirely within your browser. Even the conversion history shown on-screen exists only in browser memory and disappears when you close the tab.

No server calls, no API requests, no logging of any kind.

All tax calculations use client-side JavaScript formulas based on Indian Income Tax Act provisions for FY 2025–26.

Your salary figures, deductions, HRA details, and tax breakdowns are never transmitted anywhere. The calculated results exist only in your browser's active memory.

When you close the tab or navigate away, all entered data and results are gone - no trace remains on our servers because the data was never sent to them.

Images are processed using HTML5 Canvas API and Web APIs entirely within your browser:

• JPG to PNG conversion: Canvas.toBlob() - happens in browser memory
• Image compression: Canvas quality parameter adjustment - local only
• Image resizing: Canvas drawImage() - local only

No image is ever uploaded to any server. Original files on your device are NEVER modified. Processed results are generated as new in-memory blobs and offered for download.

You can verify this yourself: open your browser's DevTools → Network tab while using any image tool. You'll see zero upload requests.

All text analysis happens via JavaScript string operations in your browser:

• Word/character counting: Real-time regex-based counting - local only
• Text transformations: In-memory string manipulation - local only
• Readability analysis: Mathematical formulas applied to text metrics - local only

The only exception: Firebase anonymous counters track aggregate totals (e.g., "total words counted by all users globally"). This sends ONLY a number like {words: 150, characters: 800} - NEVER any actual text content.

This is the one data point we do transmit - here's full transparency:

What we send: Anonymous numerical deltas (e.g., "a user just counted 150 words")

What we DON'T send:

• The actual text you processed
• Your IP address or device information
• Any user identity or session identifier
• Timestamps tied to individual users

Why: To power the "Community Has Counted X Words" live counter - a fun global metric.

How it works: Numbers are pushed to Firebase Realtime Database, aggregated by a Cloud Function, and the original individual contribution is deleted immediately.

You can verify: Open browser DevTools → Network tab → Filter by "firebase" → You'll see only numbers being sent, never text.

Some tools optionally use your browser's localStorage:

• Online Notepad: Saves your notepad content locally so you don't lose work
• User preferences: Remembers your last-used settings

This data NEVER leaves your browser. It's stored in YOUR browser's local storage on YOUR device.

How to clear: Browser Settings → Clear browsing data → Select "Cached images and files" and "Cookies and site data". You can also use DevTools → Application → Local Storage to see and delete specific entries.