Effective date: April 3, 2026
The short version: ContentForge does not collect, store, or sell your personal information. The extension sends only the text you choose to score to our API, and that text is discarded immediately after processing.
This privacy policy describes how the ContentForge Chrome Extension ("the Extension") and the ContentForge API ("the API") handle your data. ContentForge is an open-source project (source code) licensed under AGPL-3.0.
When you use the Extension to score a post, the text content of that post is sent to the ContentForge API at https://contentforge-api-lpp9.onrender.com for analysis. That is the only data transmitted from the Extension.
We do not collect:
There are no user accounts, no login, and no authentication of any kind.
The text you submit is used for one purpose: to generate a content score and feedback. The API processes the text using deterministic heuristic scoring, returns the results to the Extension, and the text is not retained after the response is sent.
We do not use your text for training models, advertising, profiling, or any purpose beyond returning your score.
On the server: Nothing. The API does not persist submitted text. There is no database of user content. Text is processed in memory and discarded.
On your device: The Extension stores your most recent rewrite history (up to 12 entries) locally using chrome.storage.local. This data never leaves your browser. You can clear it at any time by removing the Extension or clearing its data through Chrome's extension settings.
The Extension communicates with exactly one external service: the ContentForge API hosted at https://contentforge-api-lpp9.onrender.com. This API runs on Render.
We do not embed any third-party scripts, analytics services, advertising networks, or tracking pixels. There are no SDKs from Google Analytics, Facebook, Mixpanel, or similar services.
Because we do not store your personal data, there is nothing to access, correct, or delete. If you stop using the Extension, no trace of your usage remains on our servers.
To remove locally stored rewrite history, you can:
chrome://extensions, find ContentForge, and click "Remove" or clear its site data.If this policy changes, the updated version will be posted at this URL (captainfredric.github.io/ContentForge/privacy.html) with a new effective date. Since there are no user accounts, we cannot send direct notifications of changes. We encourage you to review this page periodically.
If you have questions about this privacy policy or the Extension, contact:
Aden Cisneros
captainarmoreddude@gmail.com
github.com/CaptainFredric/ContentForge