Privacy policy

Last updated:

EditMyStuff (editmystuff.in) is run by Vikas Rajput, an individual based in Delhi, India. This page explains what each part of the site sends, where it goes and what is kept. Questions: contact@editmystuff.in.

The short version

  • The file tools (Edit PDF, Sign PDF, Merge PDF, Image to PDF, the PDF task pages, the Image Editor and the ITR-1 calculator) open and change your file in your browser; the file tools don’t upload it to us.
  • AI features send the text or images that feature needs to our server, which passes them to an AI provider. We don’t store what you send or what the AI writes back — except what you choose to save yourself (section 4: a System Design you save, and, signed in, your own mock-interview answers and code; the AI’s replies there aren’t saved) and in Reel Studio, which keeps what you ask it to make for 90 days (section 12).
  • Without an account, we keep a coded form of your network address to count your free AI uses. Signed in, we keep your account and what you choose to save.
  • Google Analytics runs only if you agree, and you can change your mind at any time in Cookie settings.
  • EditMyStuff doesn’t show ads yet. When it does, ads from Google AdSense will appear only on reading pages, and Google’s consent tool there asks visitors from the EEA, the UK and Switzerland before any advertising cookie is used (section 6).

1. Files you open in the file tools

The PDF tools, the Image Editor, Image to PDF and the ITR-1 calculator process your file in your browser. The file tools don’t send your file to our server or to anyone else.

Two parts of these tools download an engine the first time you use them: OCR (making scanned text selectable) comes from cdn.jsdelivr.net, and the Image Editor’s background removal comes from cdn.jsdelivr.net and storage.googleapis.com. Those sites receive an ordinary download request (your network address and browser details), not your file.

Some tools keep your work in your browser so it’s there next time: saved signatures, PDF Form Filler templates and the answers from fillable PDFs you download, resumes, notes, Daily Talk recordings and the practice editor’s files. That data stays in this browser until you delete it; clearing the site’s data in your browser removes it. Your AI Handwritten Notes stay in this browser even when you’re signed in: they aren’t saved to your account or our server.

2. AI features

These features use AI, and each sends only what it needs:

  • Reel Studio (not open to everyone yet): your idea and settings, and any photo you add, go to a third-party AI video service; a voiceover script goes to Google (Gemini text-to-speech). Section 12 has the details.
  • AI Error Debugger: the error and code you paste (the first 6,000 and 16,000 characters).
  • AI Handwritten Notes: your questions.
  • Resume Builder’s AI buttons: the resume fields and job description the button works on.
  • PDF Form Filler’s AI field names (optional; the tool asks for each document): up to 1,800 characters of each page’s printed text and the field labels, never the values you type.
  • Generate System Design: your description, and the architecture image if you add one.
  • Presentation Maker: your topic and options; for an imported deck, each slide’s title, a few short lines and counts of its images, tables and charts.
  • Website → Design System’s AI Vision: screenshots of the page you’re analysing.
  • Interview Prep’s mock interview: the company, role, question, your answer, code and transcript.
  • AWS Certification Prep’s AI scoring and explanations: your answer and the question.
  • Daily Talk (signed in): your talk’s transcript, never the audio.
  • GitHub Repo Doctor’s AI answers: short excerpts of the repository’s files, with likely secrets removed and key or environment files skipped.
  • Reel Studio (beta, signed in): your idea and settings, any image you attach and your voiceover script. It works differently from the features above — where they go and what is kept is in section 12.

Where it goes. To our server, which sends it to an AI provider: Groq by default, and Google (Gemini), OpenAI or Anthropic if a provider fails and that provider is set up. Each provider handles the request under its own terms.

What we keep. We don’t store your text, images or the AI’s answers, apart from what you choose to save yourself (section 4) and what Reel Studio keeps (section 12). Our server logs a technical record of each request: the task, which provider and model answered, how long it took and whether it worked; if a provider returns an error, the log keeps the kind of error and its status code, never the provider’s message. Signed in, we also record each request’s task, time, provider, model and size (in tokens), without your text, to count your free AI uses and credits.

Your own API key (optional). It is kept in your browser — for this tab only, unless you tick “remember” — sent to our server with each request, used for that request only and not stored by us.

3. Free AI uses without an account

To count your free AI uses without an account, our server turns your network address into a code using a secret, and stores that code with the tool and the time. We don’t store the address itself, and the code can’t be turned back into it without the secret. People sharing one internet connection share one count. These records aren’t deleted automatically at the moment; you can ask us to delete them (section 11).

If a request is refused because the free uses are spent, we count that refusal per day and per tool, with no address or code attached.

4. Signing in

Anyone can use the tools without an account. Signing in (creating an account) and buying credits require you to be 18 or older.

Sign-in is with Google only. Google tells us your name, email address and profile picture. Signed in, we keep:

  • your account, name and plan;
  • your Interview Prep progress and what you choose to connect: your target company, role and interview date; your GitHub and LeetCode usernames with the public figures we read from them (solved counts, recent submissions, public repositories, followers, languages); mock-interview answers (the AI’s feedback isn’t saved); and code you submit to the code judge;
  • System Design diagrams you save — a diagram you publish can be seen by anyone with its link;
  • your AI-use records (section 2), free-use counts, credit balance, credit history and orders (section 5), and Daily Talk’s daily AI-attempt records;
  • credit requests you send when your free AI uses run out: your message, the tool you were using, when you sent it, whether credits were granted and the owner’s private note. Besides you, only the site owner can read them, shown with your account’s email address;
  • feedback you send while signed in (section 8);
  • your Reel Studio requests (section 12).

This data is stored with Supabase, our database and sign-in provider.

Deleting your account. There’s no button for it yet. Email contact@editmystuff.in from your account’s address and we’ll delete your account and the data linked to it within 30 days. You can delete saved System Design diagrams and reset your Interview Prep cloud progress yourself in those tools.

5. Credits and payments

Credit packs are paid through Razorpay: Razorpay receives the order (pack and amount), a reference that includes part of your account id, and the payment details you enter in its checkout. We never see your card or UPI details. We keep the order, its status and Razorpay’s payment id, and your credit balance and history. See also the refund and cancellation policy.

6. Analytics, advertising and cookies

Google Analytics loads only after you choose “Accept all” or turn Analytics on in Cookie settings; before that, no analytics script, cookie or request is made. If your browser sends a Global Privacy Control signal, analytics stays off even if you said yes before. Analytics sees the pages you visit (without anything after “?” or “#” in the address) and events such as “tool opened” or “file downloaded” with the tool’s name; it never sees your files or the text you type. It sets the _ga cookies, which identify your browser to Google Analytics. To withdraw consent, use Cookie settings at the bottom of any page: analytics stops and its cookies are deleted.

Advertising (Google AdSense). EditMyStuff doesn’t show ads yet. We plan to show ads from Google AdSense on reading pages only: the blog and its posts, the FAQ, the AWS service guides and the Interview Prep topic pages. Ads won’t appear inside the tools, where you open files or type. Once ads run on those pages:

  • Third-party vendors, including Google, use cookies to serve ads based on your prior visits to this website or other websites.
  • Google’s use of advertising cookies enables it and its partners to serve ads to you based on your visits to this site and/or other sites on the internet.
  • You can opt out of personalised advertising in Google’s ad settings. You can also opt out of some other vendors’ use of cookies for personalised advertising at www.aboutads.info/choices or, in Europe, www.youronlinechoices.eu.
  • Ads that aren’t personalised still use cookies, for example to limit how often you see an ad, for aggregate reporting and to fight fraud.
  • How Google uses data when you use sites that use its services is explained on Google’s advertising page.

How this fits our cookie banner. The banner and Cookie settings control analytics only. Advertising cookies are never set by this site itself: if you visit from the EEA, the UK or Switzerland, Google’s consent tool (next paragraph) asks first, and until you agree, Google sets none. Visitors elsewhere aren’t asked by Google’s tool, so for them the opt-outs above are the way to turn personalised ads off. None of this applies until ads go live.

Consent for advertising cookies (EEA, UK and Switzerland). On the reading pages listed above, and only there, we load Google’s consent tool (Google Privacy & messaging, a Google-certified consent management platform, from fundingchoicesmessages.google.com) after the page has loaded. Google receives an ordinary request from your browser so it can tell which region you’re visiting from. If you’re in the EEA, the UK or Switzerland, it asks for your consent before any advertising cookie is used, and stores your answer in cookies it sets on this site. To change your answer, open Cookie settings on one of those pages and choose “Review ad choices”. Elsewhere it shows nothing.

Essential storage (always on, needed for the site to work): your sign-in session, your theme and consent choice, each tool’s drafts and settings (section 1), and the GitHub connection cookie ghrd_session, which lasts 8 hours (section 7).

7. GitHub Repo Doctor

For public repositories, your browser reads the repository from GitHub (api.github.com, raw.githubusercontent.com) and package versions from registry.npmjs.org. For private repositories, you connect our GitHub App with read-only access: GitHub’s sign-in token is used once to find your installation and isn’t stored; a cookie holds your installation, GitHub username and repository selection for 8 hours; and our server requests files from GitHub for you, logging which GitHub path was requested (including the owner and repository name).

8. Other tools that use our server, and feedback

  • Web QA Playground and Website → Design System: our server fetches the web address you enter, without your cookies.
  • Interview Prep: a LeetCode username you enter is looked up through our server at leetcode.com; a GitHub username is looked up by your browser at GitHub; code you run in the code judge is sent through our server to an external code-running service.
  • Feedback: the form sends your message, the page you were on (without anything after “?” or “#”), whether your screen is phone-, tablet- or desktop-sized, up to 3 screenshots (with location data removed) and, if you give one, your email address (signed in, it’s filled in with your account’s email; you can change or clear it). Only the site owner can read feedback.

9. Hosting

The site runs on Vercel, which keeps request logs, including the web address of each request. Vercel and Supabase may store data outside India.

10. How long we keep data

  • Files in the file tools, and what you send to AI features: not kept by us, except what you choose to save yourself (section 4) and Reel Studio (below).
  • Reel Studio: your idea and image links in each request, 90 days; the records of blocked requests and the counts that limit how often you can use it, 90 days; the rest of each request’s record stays with your credit history. Videos and images it makes, and photos you upload to it: deleted by the video service after 7 days.
  • Account data: until you delete your account (section 4).
  • Free-use codes, AI-use records, credit history, credit requests, orders and feedback: not deleted automatically at the moment; ask us and we’ll delete what isn’t needed for payment or tax records.
  • Data in your browser: until you clear it.

11. Your choices

You can use the file tools without an account, turn analytics off, change your advertising choice (section 6), turn off personalised ads in Google’s ad settings, and clear your browser’s site data. You can ask for a copy of your account data, or for it to be corrected or deleted, at contact@editmystuff.in. For a complaint about how your data is handled, write to the grievance officer, Vikas Rajput, at the same address.

12. Reel Studio

Reel Studio makes short AI videos and images from your idea. It’s in beta: anyone signed in can use it. It needs an account (section 4) and bought credits (section 5).

What it sends, and where.

  • Your idea and settings, and any image you attach, go to our server, which sends them to a third-party AI video service that makes the video or image. That service is outside India. The photos you upload and the videos and images it makes are stored by that service at unlisted links: anyone who has a link can open it. The service deletes them after 7 days.
  • Safety check: before anything is made or charged, our server sends your idea, any image you attach and your voiceover script to OpenAI’s moderation service, which checks them against Reel Studio’s content rules (terms). OpenAI handles them under its own terms.
  • The video service’s own terms (updated 26 July 2026) say that, unless an account is on an enterprise agreement, it may use what is sent to it, including photos, to train and improve its AI models, and that content already used for training can’t be taken back out. Only add a photo of someone you have permission to use, and don’t add anything you wouldn’t want a service like that to keep learning from.
  • Voiceover: your voiceover script goes to Google (Gemini text-to-speech) to make the voice. On the free tier we use now, Google may use what you send to improve its products. Don’t put personal or confidential details in a voiceover script.
  • The free price check sends the video service your settings with a placeholder text and image, never your idea or your image.

What we keep.

  • For each video or image you pay for: your account, the request sent to the video service (your idea as written into the prompt, your settings and any image link), its price, whether it worked and when. We keep it to make the video, to return your credits if it fails, to prevent abuse and to look into reports. After 90 days we clear your idea and the image links from it; the rest stays with your credit history (section 5), which we keep for payment and tax records. If a request is reported, or the law requires it, we keep it unchanged for as long as needed (180 days under India’s IT Rules).
  • When the safety check blocks a request, we record that it happened and when, not what you wrote, so that accounts whose requests keep being blocked can be paused. Our server’s log notes the kind of block (for example “violence”). These records, and the counts that limit how often you can use Reel Studio, are deleted after 90 days.
  • We don’t keep the videos, images or voiceovers themselves: the videos and images stay with the video service for 7 days, and a voiceover is sent straight back to your browser.
  • Besides you, only the site owner can see these records.

In your browser only. “Your reels” (each reel’s idea, settings, link and a small preview frame), a reel that’s still being made, your voiceovers and your timing edits are kept in this browser, not on our server; clearing the site’s data removes them. The downloadable reel — with the voice, the captions and the AI label — is made in your browser too.

The AI label. Every video you download from Reel Studio carries a visible “AI-generated” label and a note in its file details that it was made with AI, with the reel’s ID. Every image you download carries the same label, smaller, and a note in the file with its ID. A video’s label is larger for its first 2 seconds. The ID lets us find the account that made a reel if it’s reported.

13. Changes

When this policy changes, the date at the top changes, and a significant change is noted on this page.

20 October 2026: Reel Studio is in beta for anyone signed in (sections 2 and 12).

19 October 2026: section 12 covers Reel Studio: what it sends to the video service, the safety check and the voice service, what we keep and for how long, and the AI label.

19 October 2026: section 6 now covers advertising: the ads planned on reading pages, how to opt out of personalised ads, how that fits the cookie banner, a link to Google’s advertising page, and Google’s consent tool for visitors from the EEA, the UK and Switzerland. Ads aren’t shown yet.