Privacy notice
Updated 17 November 2026
About this notice
SAVER Verifier is an independently operated project published as SAVER-SI. Contact rjp.saver@gmail.com for privacy, support or security questions. This notice covers the public website, verification API and SAVER Claude plugin.
Website analytics
The public website loads Microsoft Clarity (project ID zf3gwm6dui) to measure browser page visits and interaction patterns. The site sends Clarity a denied state for analytics and advertising storage; it does not grant cookie consent. Where Clarity Consent Mode applies, Microsoft says denied analytics storage uses cookieless, limited measurement and does not set Clarity cookies. Some features, including session continuity and recordings, may be limited. This browser analytics does not measure direct agent-to-API calls; API request activity is handled separately by the service's hosting logs. See Microsoft's privacy statement and Clarity consent documentation.
What you send
The verification API receives the factual claim you select and optional context, such as a source URL, date or definition. Send only the material needed for that check. Do not send wallet keys, seed phrases, API credentials, confidential information or unnecessary personal data. The Claude plugin is an instruction package; it does not bundle a wallet, background hook or SAVER MCP server.
How information is used
Claim and context are processed to research and assess the claim and return cited findings. The task is sent to OpenAI with web search; searches and retrieval can involve search providers and source websites. Railway hosts the API and optional recovery storage. The website is served through GitHub Pages. These providers may process network metadata such as IP addresses, timestamps and user agents. Their processing can occur outside your country. See OpenAI, Railway and GitHub for their privacy information.
Diagnostics and payments
Application diagnostics are designed to record request identifiers, response status, timing, validation categories and token/cost counts rather than claim text, payment signatures or recovery secrets. Hosting and provider logs have separate retention. Your wallet and the x402 facilitator process payment authorization and settlement information. Blockchain payments expose public wallet addresses, amounts and transaction records. SAVER does not require wallet private keys or seed phrases.
Retention and recovery
If you opt into result recovery, SAVER retains processing state and, when available, the result and settlement receipt for 24 hours from record creation. Expired records are not retrievable and scheduled cleanup removes expired files. Results can reveal the subject of your claim. This 24-hour period does not cover hosting logs, backups, email, your local client, third-party providers or public blockchain history. SAVER currently calls the OpenAI Responses API without disabling its default response storage. OpenAI documents response-state retention of at least 30 days under that default and standard abuse-monitoring retention of up to 30 days, subject to applicable exceptions and account controls. We have not verified any special reduced-retention approval for this project. See OpenAI API data controls. Railway documents plan-based log access windows (7 days on Hobby, 30 days on Pro); those access windows are not a guarantee of deletion from every backend or backup. See Railway log retention. We do not promise zero retention by these systems. Keep your recovery token private and send it only in the designated header, never a URL.
Contact and requests
Email rjp.saver@gmail.com to ask about processing or request access, correction, deletion, restriction or a copy of personal data, as applicable. Include only the minimum information needed to locate a request; never email wallet secrets or payment signatures. We may need proportionate verification before disclosing information. Some records, such as public blockchain history, cannot be erased by SAVER. You may also contact the relevant data protection authority where applicable. Do not post personal data, private claims or recovery tokens in public GitHub issues.
Changes
Updates will be published here with a revised date. Contact us before sending sensitive information if this notice does not answer your questions.