Insert My Comments

Legal and privacy

What IMC does with your files

This page describes how Insert My Comments works as far as your documents, your data and payment are concerned. It only states what the tool does today.

Who provides the service

Insert My Comments is a service developed and operated by Ernest Vidal. The contact for any matter related to this page, to a specific process or to your files is insertmycomments@gmail.com.

Which files are handled and what for

IMC works in the browser, without installing anything on your computer. To run a process you need to provide the files that journey requires —usually a PDF with comments and, depending on the case, the source document or another reference PDF—. Those files are uploaded over a secure connection (HTTPS) and processed on a server with a single purpose: producing the result of the process you asked for and letting you recover it later. They are not used for any purpose unrelated to the tool's operation.

How long they are kept

IMC does not promise that files are wiped as soon as processing ends, because that's not what happens: an editorial process lasts longer than a browser session and you must be able to come back to it.

  • A process with a real run is kept for 30 days, together with its configuration, its files and the results already produced.
  • The purpose of that retention is continuity: continuing a process later without repeating what's done, and recovering the results you are entitled to.
  • Inside the process itself you are shown the exact date until which it will be available.
  • After the deadline, the process is no longer recoverable: the link no longer opens anything.

Deletion

  • Whenever you want. From the process itself you can delete it right now, with all its files. Before doing so you are told in plain language what will disappear. It is irreversible and the link stops working.
  • When the deadline expires. When the 30 days are up, deletion runs anyway and covers the whole set: the process, its jobs, its reports and its stored files.
  • Access is cut by the date, not by the cleanup. After the deadline the process won't open again even if technical remnants remain to be removed.
  • Expiring and deleting are not the same. If you try to open a process that no longer exists, you are told which of the two happened.

No account, and what the link means

There's no need to sign up to use IMC and no account is created. When there is a real run, IMC gives you a recovery link: it's the way back to your process. Knowing the process identifier is not enough; access is granted by the credential that travels inside that link.

That means anyone with the link can open the process. Keep it where you'd keep a work document and don't publish it or share it through open channels.

Comment interpretation with artificial intelligence

Two operations interpret the comments' content: the one that reduces a wordy instruction to the specific correction and the one that adjusts the text to its insertion context. To do so they send to the OpenAI API the comment's text, the selected fragment and its immediate context. Neither the whole document nor the file is sent. The remaining operations don't use that service.

If you don't want your comments' content to pass through an external service, don't select those two operations: the rest of the journey doesn't depend on them.

Payment and delivery

  • Processing and, when the journey allows it, checking the result in your own environment can be free. What payment authorises is the delivery of the corresponding file.
  • Payment unlocks, it doesn't produce: the file was generated and sealed beforehand; paying doesn't re-run the process or write it again. A download link can expire and be issued again; the file's bytes don't change.
  • Not all journeys are the same. Each operation's price and what it includes are shown in the tool before running anything.
  • Charging is processed by Stripe, on its own payment page. IMC doesn't receive, see or store your card details. The receipt is issued by Stripe.

External services involved

  • Google Cloud / Firebase: site hosting, storage of the process's files, case database and process execution.
  • reCAPTCHA Enterprise (Google): protection of the tool's pages against automated use. This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
  • Stripe: payment processing and receipt issuing.
  • OpenAI: only in the two operations described above, and only with the text stated there.

Cookies and browser storage

IMC V4 uses no tracking or advertising cookies of its own. During payment, the browser temporarily stores —only while the session lasts— the minimum data needed to return you to your process when coming back from the gateway. The external services mentioned (Google and Stripe) may use their own mechanisms according to their policies.

Responsible use

Using this tool for illegal or abusive purposes is not allowed, nor to handle documents you have no right to handle, nor in ways that infringe third-party rights. You decide which documents you upload.

Service limits

  • IMC certifies what it can verify inside the files you hand it. The final test is yours, in your own installation, and it doesn't promise it will work in every version, installation or plugin.
  • Doubtful cases are flagged; the editorial decision remains human.
  • Always keep your originals. IMC works on copies, but the custody of the master document is yours.

Questions and exercising your rights

For any matter about this page, a specific process or your files, write to insertmycomments@gmail.com. If what you want is to delete a process, you can do it yourself from the process itself, without asking.

Last updated: August 2026.