Who runs EkaanHub

EkaanHub is built and run by one person in India. It is part of GadgetCrisp, a registered sole proprietorship. There is no company behind it, no investors, and no team — which is worth knowing before you decide how much to trust it with.

Why it works the way it does

Every tool here runs inside your browser. Your file is opened, processed and saved back by your own device, and never sent to us. That is not a feature added for marketing — it is the decision the whole site is built around, and most of what looks unusual here follows from it.

There are no accounts, because there is nothing to attach one to. There are no daily limits, because your own computer does the work and that costs us nothing per file. And there is no server holding your documents, because there is no server in the path at all. You can check that yourself in about thirty seconds.

What it costs to run

Very little, and that is the point. Processing on your device means the bill does not grow when more people use the site, so there is no pressure to meter what you do, ask for an email, or find something to sell you. A site that has to pay for every file it touches eventually has to charge for it. This one does not.

How it is paid for

Today, it mostly is not — the running costs are small enough to absorb. The plan is advertising on the pages that can carry it and a paid tier for heavier work later on. What will not happen is the two things free tool sites usually do: selling what you upload, which is impossible here because nothing is uploaded, and requiring an account to use a basic tool.

Being straight about the limits

Running on your device is not free of trade-offs, and we would rather say so than have you find out. A very large or unusual file can be more than a phone’s browser can handle, where a server-based tool would manage it. Conversions between document formats are approximations, not photocopies. And text recognition on a poor scan is good rather than perfect.

Several tools carry a “what this tool cannot do” section saying exactly where they stop. That is there because a tool that hides its limits wastes your time in a way that is harder to recover from than one that states them.

The source

Most of this site’s code is not public, and we are not going to pretend otherwise. One part is: the redaction engine is published at github.com/pkaur1130/pdf-redact under AGPL-3.0. It is the same file that runs here, not a demonstration written for the occasion, and it is public because redaction is where the difference between doing the job properly and appearing to matters most.

Getting in touch

Write to the contact page. Problems with a tool, a tool you wish existed, or anything on this site that turns out not to be true — the last one especially.