VibeRevise: privacy policy
Last updated 17 October 2026.
VibeRevise is a browser extension and web app for fixing the words in an HTML document without disturbing its markup. This policy says what it does with your information. The short version: almost nothing. Your documents never leave your browser unless you turn on AI with your own key, and even then they only go to the AI service you chose, and only when you ask. If VibeRevise itself breaks, it sends us a short error report, which never includes your document.
What stays in your browser
- Your documents. VibeRevise reads the document you open and edits it in your browser. It never uploads it anywhere of ours: there is nowhere of ours. Saving writes the file back to your computer, or to the server the document came from if that server accepts it.
- Your name, if you type one. It is stored in your browser and written into the comments you add to documents you save. It is whatever you choose to type, and there is no account behind it.
- Whether comments are shown in the document. A single setting, on or off.
- Your editing session, so a reload does not lose it. From the moment you start editing a document, VibeRevise keeps a copy of it as you opened it (and as you last reviewed it), your unsaved changes and the list of changes in this browser's storage, under the document's address. That is what lets it put your work back after a reload, and show what another program changed in the file meanwhile. It is never sent anywhere. The newest eight are kept, for two weeks at most, and Start fresh forgets one straight away.
- The file, looked at again while you edit. To notice another program changing it, VibeRevise reads the file again every few seconds while you are editing it and the page is in view. It reads it the way it first did, from your own disk or your own server, and compares it in your browser. Nothing is sent anywhere.
- Your AI settings, if you add them: the provider, its address, the model and your API key. They are kept in this browser only and are not synced. In the extension they are read only by VibeRevise's own settings page and background worker, never by the pages you edit.
Clear any of these from VibeRevise's settings, or by removing the extension.
What leaves your browser
Your documents, nothing, except in two cases you choose yourself:
- Saving to your own server. If the document you are editing was served over your own network, saving sends it back to that same server, because that is where the file lives.
- AI suggestions, if you add an API key. AI is off until you add a key for a service you choose: Anthropic, OpenAI, OpenRouter, Google Gemini, or any compatible address, including a model on your own computer. When you press a button asking for a suggestion, VibeRevise sends that service the words of the paragraphs involved. A rewrite also sends a little of the text either side for context, asking for an explanation sends the words you selected or the paragraph you are in, with a little text either side, and asking about a comment thread also sends the thread. It never sends the whole file or its markup. The request goes from your browser straight to the service, with your key; it does not pass through anything of ours. What that service does with it is governed by your agreement with them. A model on your own computer keeps it on your machine.
And one thing that is not about your documents at all:
- Error reports. When something in VibeRevise goes wrong (a bug in the extension, the web app or this website), it sends us a short report so we can fix it. A report holds the error message and where in VibeRevise's own code it happened, which part of VibeRevise it was, the version, your browser's name and version (its user agent), and the time. In the web app and on this website it also holds the page's path on our site, such as
/app/. It never holds your document, any text from it, its address or file name, your name, your comments or your AI key: before a report leaves, any web address or file path that is not one of VibeRevise's own scripts, and anything shaped like a key, is blanked out. Reports are not linked to you or to each other, and no cookie or identifier goes with them. They are stored with Google Firebase (Cloud Firestore, in the United States), where only we can read them, and are deleted after 90 days.
Nothing else is sent anywhere: no analytics, no tracking, no advertising, no account, and no AI service of ours.
What we never do
We do not collect, sell, share or use your documents or anything in them. We do not run servers that receive them. Error reports are used only to find and fix bugs, and are never sold or shared. We do not use it to determine creditworthiness or for any purpose other than the feature you invoked.
Contact
Questions: codebertcreations@gmail.com
This website
This site sets no cookies and runs no analytics, and it loads nothing from anyone else: no web fonts, no trackers. If a page on it breaks, it sends the same short error report the app does, described above. Like any website, the service that hosts it may keep ordinary server logs, such as the addresses that requested pages.