Privacy Policy
Last updated: 26 June 2026
This policy covers the free scoring tool at score.seoryon.com, the /api/score backend that powers it, and the open-source oryon-score Python code on GitHub. All three are made by SEOryon. Short version: there is no account, no tracking, no analytics — but the scorer does have a small server-side component, and we want to be specific about what it sees.
What this site does, step by step
The score has a backend. We're naming it explicitly because most “100% local” privacy claims wouldn't apply here.
- You paste a URL on score.seoryon.com. Your browser calls our serverless endpoint at /api/score with that URL as a query parameter.
- The backend fetches that URL once, exactly as a browser would, and runs 27 rule-based checks on the HTML it receives. No LLMs, no third-party APIs, no enrichment services.
- The score, signal results, and fixes are returned to your browser as JSON and rendered on the page. The fetch and the result are not written to a database or kept on disk.
- There is no account, no login, no user profile, no usage quota, and no cookie set by score.seoryon.com.
The /api/score backend
The endpoint is a stateless Python function running on Vercel's serverless runtime. For each request it:
- Reads the URL you submitted from the query string.
- Performs HTTP GET requests to that URL (and to its /robots.txt and /llms.txt at the same host) with a labeled User-Agent containing “OryonAISearchScore”.
- Parses the HTML in memory, computes the score, and returns JSON.
- Does not store the submitted URL, the fetched HTML, the computed score, your IP, or any identifier in a database we operate.
Like any web host, our serverless provider (Vercel) keeps standard, short-lived request logs — including IP address, request time, the path called, and User-Agent — to run the service and protect it from abuse. We do not use those logs to track, profile, or contact you. A short-lived edge cache may also remember a recent score for the same URL to keep the tool fast.
A practical note: the URL you submit becomes part of a request that crosses the public internet. Don't paste URLs you consider confidential (e.g. preview links protected only by obscurity). The backend will then fetch that URL itself, which means the target site sees a request from our server identifying itself as OryonAISearchScore.
This website (score.seoryon.com)
This is a static page hosted on Vercel.
- We do not run Google Analytics, Tag Manager, Meta Pixel, or any third-party analytics or advertising script on this page. We do not set marketing or tracking cookies. We do not fingerprint visitors.
- Your language preference (English, German, French) is saved in your own browser's localStorage so the site remembers it between visits. This preference never leaves your device.
- The page loads Geist, Geist Mono, and Plus Jakarta Sans from Google Fonts. Google may receive standard request metadata (IP, browser) as part of serving those fonts; we do not control that and do not use it.
- Outbound links to app.seoryon.com, seoryon.com, and github.com take you to separate properties with their own privacy terms.
The open-source oryon-score code
The same scoring logic is open-source on GitHub under MIT. If you clone the repo and run it locally, the code fetches the URL you give it directly from your machine — nothing is sent to SEOryon, and we never see what you scored.
If you create a SEOryon account
This page covers the free score tool, its backend, and the open-source package only. The paid SEOryon platform at app.seoryon.com is a separate product with its own account, data handling, and privacy terms. Creating an account there is entirely optional and never required to use the score.
Your data & contact
Because the score backend stores nothing about you in a database we operate, there is no personal account data for us to hold, export, or delete. If you have any question about privacy — or anything you'd like clarified — reach out and we'll gladly help.
Contact: support@seoryon.com · seoryon.com
Changes to this policy
If anything here changes — for example, if we ever decide to add lightweight, privacy-respecting analytics, or to keep scoring results for product research — we will update this page and the “last updated” date above before the change goes live. The history is visible in the open-source repository.