Privacy Policy
What we store
When you run an analysis on JSR, we save the following to our server:
- The full input. The text you pasted, the URL you submitted, or the text Claude extracted from your screenshot.
- The full analysis output. Score, rating, substance points, jargon glossary, red flags, plain-English summary.
- Metadata. Source type (article, video, text, screenshot), source URL/title, timestamp.
- A share ID. Every analysis gets a permalink like
jsrscore.com/a/k7x2mB3p.
We do not require an account. We do not link analyses to you personally. We use your IP only for rate limiting (20 analyses per hour) and do not store it with the analysis record.
Why we store it
- To improve the product. Real inputs help us catch edge cases and calibrate the scoring model.
- To build public case studies. Our /cases gallery shows striking examples of jargon and clarity. Cases come from two sources:
- Analyses of public URLs (articles, YouTube videos) — these default to public because the source is already public.
- Analyses of pasted text or screenshots — these stay private by default. They only appear in the gallery if you check the "Add to public gallery" box on your result page.
- Training data for a future clarity model. We may use the corpus to train our own internal model that scores clarity more cheaply. We will never sell the data to third parties.
How to delete
You can delete any analysis you created. On the result page or the permalink page, click "Delete this analysis". The share link stops working immediately and the record is soft-deleted on our server.
The delete button only appears on the device and browser you used to create the analysis. If you need to delete an analysis from a different device, or want to delete all your analyses, email [email protected] with the share IDs (the codes in the URLs like k7x2mB3p).
Third-party processors
Content you submit is processed by Anthropic's Claude API. Anthropic receives the text of what you submit in order to return an analysis. Per Anthropic's API terms, your submissions are not used to train their models.
Our infrastructure runs on Railway. YouTube transcripts are fetched through Supadata. Both receive standard request metadata but not the analysis record beyond what is in transit.
Chrome extension permissions
- activeTab & scripting: read text from the current tab only when you explicitly invoke JSR.
- contextMenus: adds "Analyze with JSR" to the right-click menu.
- sidePanel: displays results in Chrome's side panel.
- storage: caches recent analyses locally on your device and remembers the consent state.
- host_permissions (jsrscore.com): allows the extension to send analysis requests to our API.
Children's privacy
JSR is not directed at children under 13. We do not knowingly collect information from children.
Changes to this policy
If this policy changes materially, the "Last updated" date at the top will change. This page is the canonical version.
Contact
Questions, deletion requests, or concerns: [email protected]
← Back to JSR