Useful software, without the unnecessary complexity.

Why EditMyStuff exists

Who builds this

How AI is used

Tools that call an AI model

• PDF Form Filler: Filling runs locally and your PDF is never uploaded. For a flat or scanned PDF, AI field naming asks first; if you say yes, the page’s printed text and field labels are sent to an AI provider to name the fields — never your answers.
• Resume Builder: The resume builder runs locally. Optional AI buttons send only what each needs to our API — the job matcher sends the job description you paste, not your resume.
• AI Error Debugger: The error and code you paste are sent to our AI API for diagnosis.
• AI Answers as Handwritten Notes: Your questions are sent to our AI API; rendering to handwriting happens in your browser.
• Generate System Design: Your prompt is sent to our AI API; the diagram editor runs in your browser.
• Frontend Interview Prep: Practice content runs locally; the mock interviewer and code judge send your answers and code to our API.
• AWS Certification Prep: Lessons and practice run locally; the optional AI interviewer and AI answer explanations send your answer or the question to our API.
• AI Presentation Maker: Your topic and outline, or an imported deck’s slide summaries, are sent to our AI API; editing and export run in your browser.
• Daily Talk: Recording and transcription run in your browser; your audio is never uploaded. If you ask for AI feedback or a clean-up, the transcript text is sent to an AI provider.
• Reel Studio: Your idea and any image you attach go through our server to an AI video service (after an automatic safety check); the voiceover script goes to an AI voice service. The voice, captions and AI label are added to your download in your browser.

Tools that fetch a public address you give them

• GitHub Repo Doctor: Fetches public repository data from GitHub and npm; optional AI explanations send code snippets to our API.
• Web QA Playground: Our server fetches the URL you enter to run the checks.
• Website → Design System: Our server fetches the URL you enter; the optional AI Vision sends a screenshot you choose to an AI provider.

Tools that run only in your browser

• PDF Editor
• Sign PDF
• Image to PDF
• Merge PDF
• Image Editor
• ITR-1 Calculator
• Reverse Singing Challenge

What happens to what you send

• AI features send only the text or images that feature needs to our server, which passes it to an AI provider: Groq by default, and Google (Gemini), OpenAI or Anthropic if a provider fails. Our server doesn’t keep what you send or what the AI writes back: its logs and records hold only technical details, such as the tool, the provider and model that answered, timings and token counts. What you choose to save is the exception: a System Design you save (which can be one the AI drew) and, if you’re signed in, your own answers and code from Interview Prep mock interviews. The AI’s replies there aren’t saved. Resumes and handwritten notes are saved in your browser’s own storage, not on our server. Each tool says when it uses AI.
• You can add your own API key in AI settings. Requests your key pays for don’t use up your free allowance.
• AI can be wrong. Treat what it writes as a draft, and check anything that matters before you rely on it.
• Google Analytics runs only if you allow it in Cookie settings, and it never sees your files or what you type.
• The privacy policy goes tool by tool: what is sent, where it goes and what is kept.

The free limit

How tools are tested

• Automated tests run first: the tools’ logic, the rules for credits and refunds, and the privacy claims the site makes.
• The whole site is then built, every page is turned into static HTML, and route checks confirm each page has its own title, links and content. A separate check compares what each tool’s page says about your data with what that tool’s code really sends.
• Anything people use is tried in a real browser, on a desktop-sized window and a phone-sized one, including the paths where something goes wrong.
• Interview Prep’s coding drills are run, not assumed: each answer is produced by running the snippet in Node and in Chrome, and both have to agree.
• AWS and interview questions carry the page they were checked against. AWS questions and lessons link a page on AWS’s own documentation, and a test fails if one doesn’t; the newer frontend questions cite official documentation, MDN or a specification, and a test checks that too.
• Something that still gets through shows up in feedback. Tell Vikas and it gets fixed.

How EditMyStuff is paid for

• The file tools are free, with no trial, no watermark and no paywall.
• AI features come with free requests every day, shared by all the AI tools: 3 without an account and 15 once you sign in. After that, each AI request uses a credit. Credits come in one-time packs paid through Razorpay, and they don’t expire (refund policy).
• Ads from Google AdSense are planned for reading pages only (the blog, the FAQ and the guides), not inside the tools. None run yet; the privacy policy explains the cookies they’ll use and how to opt out.

How the guides and policies are written

• The blog explains how to use the tools and covers the topics behind them: PDFs and images, presentations and speaking, frontend and system design interviews, and AWS certification. Every post carries Vikas’s byline.
• The privacy policy, terms and refund policy are written from what the code actually does, and each shows the date it last changed.
• Common questions, from free AI requests to cookies and refunds, are answered in the FAQ.

What’s being built next

What it’s built with