Privacy policy

What Opyt stores, and what it never collects.

The short version: a local install phones nobody. A hosted home stores what you chose to import, so it can serve it back to you. The sharing service counts what it serves in daily totals and publishes those totals. Nothing here is sold, mined across users, or used to train models.

Opyt is operated from the United States. Questions: hello@useopyt.com.

Local install

On your machine, everything stays on your machine.

The Opyt you install is a local MCP server that reads and writes files in ~/.opyt on your own disk. It has no telemetry, no analytics endpoint, and no reporting call of any kind. Install counts come from PyPI and GitHub download statistics, which are public and need no code on your machine.

The one exception is deliberate and yours to trigger: if you shared your knowledge base (see the sharing service below), your install re-uploads it when it has changed and somebody has read the served copy since your last upload. What goes up is the export itself and the token saying which knowledge base it replaces — nothing else, and nothing about you. An install that has never shared holds no token, so this never runs at all.

Hosted home

What a hosted home stores.

If you connect through the hosted connector at mcp.useopyt.com (from claude.ai, ChatGPT, or another connector-capable client such as Meta's Muse), Opyt runs your server for you. A hosted home stores, on Opyt's server:

• Your email address, received from Google when you sign in. It identifies your home so the same sign-in reaches the same knowledge base from any client. Opyt never sees your Google password.
• Your knowledge base — the content you chose to import: bookmarks, posts from people you follow, subscriptions, papers, pages. Imports run only with your consent, given during onboarding, and only from sources you picked.
• Your source sessions. X and Substack connect through a private browser desktop; the resulting signed-in browser session is kept so your imports can stay current. Opyt stores the session, not your passwords.

To index what you import (sorting, extracting, embedding), content is processed through OpenRouter — under access Opyt covers to start with, or under your own authorized OpenRouter account if you connect one. That processing exists to build your index and nothing else. Your AI client — where every question, answer, and all the reasoning happens — is governed by that client's own privacy policy, not this one.

Opyt does not read your knowledge base except as needed to operate the service or respond to abuse, does not analyze content across users, does not sell any of it, and does not use it to train models.

Sharing service

If you share, the service counts — in daily totals.

The sharing service is reached only if you shared your own knowledge base or accepted an invitation to somebody else's. If you have done neither, none of this applies to you. What it records, in full:

• Access tokens as hashes — the SHA-256, never the token, so the database holds no usable credential. Alongside each: which one knowledge base it can reach, its role, the label its owner chose for it, and a random per-install id linked to no account, email, or machine.
• Storage accounting — how many bytes each shared knowledge base occupies, under a routing key assigned at random.
• Daily read counts — per day (deliberately a day, not a timestamp), which reader used which tool how many times. Not which documents they read, and not what they searched for.

What is never collected: query text (searches are processed in memory and never written down; semantic queries are embedded on the reader's own machine, so only numbers cross the wire), IP addresses (deliberately not logged, and a test fails if they come back), per-document reading history, and per-request timestamps. Raw process logs record method, path, and status code only, and are deleted after 30 days.

The service's totals are public at api.useopyt.com/stats, so whoever runs the service holds no more information than anyone else does. The full schema, checked against the code by an automated test, is in TELEMETRY.md — including its one honest limit: if exactly one person holds a grant, that knowledge base's daily total is that person's activity, and the service says so before their first query.

This website

No analytics, no cookies.

useopyt.com runs no analytics and sets no cookies. The one thing it keeps in your browser is your light-or-dark theme choice, in local storage, read by nobody. Invitation codes on /invite live in the URL fragment, which a browser never sends to a server — no server ever sees a code.

Your data, your call

Retention and deletion.

• Local install: delete ~/.opyt and everything is gone. There is nothing server-side to ask about.
• Hosted home: the forget tool removes individual items. To delete your hosted home entirely — knowledge base, source sessions, and the email that keys it — email hello@useopyt.com from that address.
• Shared knowledge bases: unshare cuts off one reader, or every reader plus the hosted copy. Unpublishing removes the served export.

Opyt is not directed to children under 13, and we do not knowingly collect their data. If this policy changes, the new version is posted here; a change that expands what is collected will be called out, not slipped in.

Contact for anything on this page: hello@useopyt.com.