Privacy policy

Text and rules sent for filtering are not used to train AI.

OneFilter does not store text sent for filtering on its servers or in logs. We also request a setting that prevents the filtering provider from retaining it, but are still confirming whether this applies to the current processing route.

The extension sends only the text of posts and comments shown on your screen, the rules you write, and an anonymous ID for counting daily usage (account authentication when you are signed in) for filtering.

The extension does not send social media account names, browsing history, or URLs.

For X DMs, message request text is sent only when you enable “Filter message requests too” on the paid plan. Conversations in your inbox are not sent.

When you sign in, we store your email address and rules in your account. You can also use OneFilter without signing in.

When a problem reading posts is detected, we are notified only of which social media service it occurred on.

When you report a post hidden by mistake or missed by the filter, the contents of that report are also sent (post text is included only if you choose to include it).

AI training and text retention

Preventing text and rules sent for filtering from being used to train AI and preventing the filtering provider from storing them are separate matters. We request a no-retention setting, and the system is designed not to send data to destinations that do not meet that requirement. However, we are still confirming whether the setting is accepted on the current processing route, and have not yet confirmed that the filtering provider does not retain the data.

The statements about not storing text apply to text sent for filtering. The ID and counts used to enforce daily limits, rules saved when signed in, and reports where you choose to include post text are stored for separate purposes. The filtering provider also keeps records such as usage counts and costs.

Destinations and settings in detail

By default, text and rules are sent from OneFilter's filtering API through Vercel AI Gateway to TypeSafe AI's Jev. Vercel and TypeSafe AI state that they do not use the submitted content for training.

The Gateway itself does not retain text sent for filtering or the responses. Text retention by the provider is a separate matter and depends on the contracts and models covered by zero data retention (ZDR). Until we have confirmed that ZDR applies to the current Jev route, we do not guarantee that the provider does not store the data.

When you use your own key, this also depends on your Gateway plan, settings, and contract. Registering a provider's key with the Gateway (BYOK) is different from entering a Gateway key in the extension, and requires checking your contract with that provider.

Vercel's zero data retention terms · No-training terms · How TypeSafe AI handles data

How we use your information

OneFilter sends text shown on your screen to a filtering server to check whether posts match the rules you write. Information is sent only for this filtering and to detect and fix problems reading posts. It is not used for advertising or analytics.

Information we send

  • The text of posts and comments shown on your screen
  • The rules you write to check whether posts or comments match
  • Only when message request filtering is enabled: the text of X message requests (DMs from people you do not follow) shown on your screen (see “When filtering message requests” below)
  • When you are not signed in: an anonymous ID for counting daily usage (a string created when you install the extension that is not linked to your identity)
  • When you are signed in: account authentication instead of the anonymous ID. Daily usage is counted per account. Immediately after sign-in, the anonymous ID is also sent once to carry over your previous usage count
  • Only when a problem reading posts is detected: which social media service it occurred on (X / YouTube). This does not include post text, account names, URLs, or the anonymous ID (at most once per day for each service from the same device; not sent when you use your own key)
  • Only when you submit a report (available to signed-in users only): the report type, a brief message, and your account ID. Post text is included only if you choose to include it

Information we do not send

  • Social media account names, display names, and profiles
  • Browsing history and the URLs of pages you have opened
  • Conversations in your X DM inbox, and the names and usernames of the people you message
  • When you are not signed in, contact information such as your email address

List of destinations

  • Vercel Inc.

    Country: United States

    Purpose: Relaying filtering requests and recording daily usage

    Data retention: Does not retain text, rules, or responses sent for filtering. Usage records, such as request counts and costs, are stored separately

  • TypeSafe AI, Inc.

    Country: United States

    Purpose: Checking whether posts match your rules

    Data retention: Not used for training. We request a no-retention setting, but are still confirming whether it applies to the current processing route

  • Upstash, Inc.

    Country: United States

    Purpose: Recording daily usage

    Data retention: An anonymous ID (an account ID for signed-in users) and usage counts. For invitation recipients, their public X ID and invitation ID

  • Clerk, Inc.

    Country: United States

    Purpose: Sign-in and storage of account information (signed-in users only)

    Data retention: Stores your email address, rules, and subscription status until you delete your account. Post text is not sent

  • Stripe, Inc.

    Country: United States

    Purpose: Payments for the paid plan (people who subscribe to the paid plan only)

    Data retention: Stripe stores your email address and payment information. OneFilter does not receive your card details

  • X Corp.

    Country: United States

    Purpose: Early access invitations (only for people who follow OneFilter on X and repost the announcement)

    Data retention: Sends an invitation link by DM. Post text read by the extension and OneFilter account information are not sent

  • Functional Software, Inc.（Sentry）

    Country: United States

    Purpose: Recording errors and problems reading posts

    Data retention: Post text and IP addresses are not sent

  • feedbase (operated by OneFilter's developer; runs on Vercel Inc. and Neon, Inc.)

    Country: United States

    Purpose: Receiving reports of posts hidden by mistake or missed by the filter. Uses Google LLC's Gemini (Vertex AI) to screen for inappropriate submissions

    Data retention: Stores the report type, a brief message, and your account ID. Post text is stored only if you choose to include it

When filtering message requests

X DMs are conversations encrypted between the sender's and recipient's devices. The extension reads the text of message requests shown on your screen and sends it for filtering only when you are on the paid plan, enable “Filter message requests too” in settings, and give your consent for this. It is off by default.

  • Only the text previews in the message request list and the text of conversations you have not yet accepted are read (the other person's name is not sent). Your inbox (conversations with people you have accepted or follow) is not read
  • The other person's name, username, profile picture, and the conversation ID are not sent
  • The text and rules sent are not used to train AI. OneFilter does not store text sent for filtering on its servers. We also request a setting that prevents the filtering provider from retaining it, but are still confirming whether it applies (when you use your own key, this also depends on your Gateway plan, settings, and contract)
  • Sending stops as soon as you turn this off, your paid plan ends, or you change the destination (your own key). You will be asked for consent again when you turn it back on
  • The text of message requests for which you select “Show” or “This isn't right” cannot be included in reports of posts hidden by mistake or missed by the filter

Information we store when you sign in

Signing in is optional. It increases your daily limit and lets you use your rules on other computers. To provide this, we store the following information in your account.

  • Your email address (if you sign in with Google, the email address, name, and picture received from Google)
  • The rules you write (each line, filtering strength, and display mode). We do not store post text or a record of hidden posts
  • That you received an early access invitation (only if you used an invitation link)
  • Your subscription status (free or paid). Payments for the paid plan take place on Stripe's payment page, and OneFilter does not receive your card details

To delete your account, contact us through “Report incorrect filtering” in the extension's popup. We will delete the information we hold.

What we read for early access invitations

To distribute the early access benefit (the first 3 months of the paid plan free), we use X's official API once a day to read the list of people who reposted the announcement from OneFilter's X account and the list of its followers. These are the only two lists we read, regardless of whether you use the extension.

  • We read only the public IDs (the number assigned to each account) of people who reposted and followers. We do not read posts, profiles, or DM contents
  • People who have done both receive a single-use invitation link by X DM
  • To avoid sending duplicates, we store the IDs of people we sent invitations to, the invitation IDs, and the IDs of people we could not send invitations to. We do not link these to information sent by the extension (post text or usage counts)
  • When an invitation link is used, we store the recipient's X ID together with the OneFilter account ID that used it in that invitation's record (to make the link usable only once)

What this website records

The sections above describe information sent by the extension. On every page of this website (the introduction page, this page, pages for opening shared rules, sign-in pages, and paid plan pages), we collect the following records. Neither service receives the part of the page URL after #, and these records are not linked to information sent by the extension. Sign-in and paid plan pages use Clerk cookies to keep you signed in.

  • To count page views, we send the page URL, referrer, country and region, and browser, operating system, and device type to Vercel Web Analytics by Vercel Inc. No cookies are used, and the value used to distinguish visitors is deleted after 24 hours
  • To fix display problems, we send error details and display logs (including the page URL) to Functional Software, Inc. (Sentry). IP addresses are not sent

When you use your own key

If you enter a Vercel AI Gateway key in settings, filtering requests are sent directly from the extension to your Vercel AI Gateway. The key is stored only on your device. OneFilter's servers do not receive the text, rules, or key used for filtering, and do not record filtering usage. The text and rules sent are not used to train AI. We request a setting that prevents the filtering provider from retaining data, but are still confirming whether it applies. This also depends on your Gateway plan, settings, and contract. Rule syncing when signed in and reports you choose to submit are separate communications from filtering.

Chrome Web Store Limited Use statement

OneFilter's handling of the information it receives complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. We use the information only for the filtering described on this page and to detect and fix problems reading posts. We do not sell it to third parties or use it for advertising or credit assessments.

Contact

For privacy questions, contact us through “Report incorrect filtering” in the extension's popup (sign-in required). Post text is sent only if you choose to include it.

Revision history

Published; Revised (added sign-in, the paid plan, and information sent when problems reading posts are detected); Revised (added information read for early access invitations and information sent when filtering message requests); Revised (added text previews in the message request list to the information sent for filtering); Revised (separated AI training use from text retention, clarified that zero data retention is still being confirmed, and stated that the rules you write are also sent for filtering). We will update this page before changing how we handle information.