Terms of service

These are the terms on which Sift intends to be offered: what the service does, what it commits to, what it asks of you, and where its limits are. It is written to be read, so it says "we" and "you" and avoids clauses that exist only to look like clauses.

It is also unfinished. The parts that describe the software are accurate. The parts a contract normally leans on — liability, warranties, governing law, refunds — are not drafted, on purpose, and are listed at the end for the operator's lawyer to write.

You connect your X account. Sift reads the posts you have bookmarked, stores them, gives each one a category, a few tags and a one-line summary, and makes the result searchable. It emails you a digest of what you have saved, daily or weekly by your own choice, and you can export the library as a CSV file.

What it is not: a backup of your X account, a scraper, a way to reach content you cannot already see, or a substitute for X. It reads what X's API returns for your own bookmarks, and nothing else.

• Read-only, by construction. We request tweet.read, users.read, bookmark.read and offline.access. There is no write scope on the connection, so nothing we hold can post, reply, like, follow, unfollow or message as you — whatever our code might one day ask it to do.
• Yours to withdraw. You can revoke our access from your X account settings at any moment, and deleting your Sift account revokes it for you and purges your data.
• Your X account remains yours to keep in good standing. X's own terms still apply to you and to the content you saved. Using Sift does not change them, and does not give you rights over other people's posts that you did not already have.
• An independent product. Sift is not affiliated with, sponsored by or endorsed by X Corp.

There is one plan. These limits are not a marketing summary of the product; they are the numbers the software enforces, read from the same configuration the sync engine and the plan gate use. If a cap changes, this table changes with it.

The reason the import stops at 300 is cost: X bills per post returned, so importing a library is a real expense we pay before you pay anything. The reasoning is set out in full in the pricing section.

Every bookmark we read costs us money, so the plan carries a hard monthly ceiling on newly saved bookmarks: 300 a month. It is enforced before any billable call: the sync engine checks what you have already saved this month against the cap before it even asks X whether anything is new, so a month you have filled costs nothing further. Sync reports it plainly rather than silently doing nothing, and the count starts over the following month.

There is also a separate per-account monthly budget for X API spend, and a global daily kill switch, sitting behind the bookmark cap as a backstop against a bug in our own cost control rather than a limit you would ordinarily reach. In normal use you will never meet either.

• Pro is $7 per month, or $70 billed once a year — $14 less than paying monthly.
• Prices are in US dollars and exclude any sales tax, VAT or GST that applies where you are.
• There is no setup fee, no per-seat pricing and no usage surcharge. What we spend at X is ours to manage.
• There is one plan and no smaller tier to move down to. What happens to an account after a missed payment or a cancellation is not yet settled in the product — see "Subscription mechanics" below. What is settled today: only deleting your account, or a post disappearing from X, removes content you have already imported.
• Not yet drafted: renewal and cancellation mechanics, refunds, any trial, invoicing, and the statutory withdrawal rights that apply to consumers in some markets. Those are open items below rather than promises made here.

• The posts are not ours and not yours. They belong to the people who wrote them and remain subject to X's terms. We store copies so you can search what you saved, and every one links back to the original on x.com.
• The categories, tags and summaries are ours, generated from post text. You may use and export them freely as part of your own library. They are always shown separately from post content, because presenting generated text as part of a post would be altering that post.
• Your bookmark list is yours. We claim no ownership of it, do not sell it, and do not use it to train models of our own.
• Generated text can be wrong. A category or summary is a model's guess. Treat it as a filing aid, never as a statement about what a post says — the post itself is one click away, which is the point of the link.

Most of this section exists because X's Developer Policy binds us, and we can only keep those commitments if the service is not used to route around them.

• Do not redistribute exported post content onward — republishing it as a dataset, an API, or a public archive. The export exists so you can use your own library in your own tools.
• Do not work around the 300-posts-per-day export limit, with multiple accounts or by automating the download. That number is ours, set inside X's own 500-a-day ceiling, and we have to honour both.
• Do not use the service to build a competing dataset of X content, or resell access to what it stores.
• Do not attempt to reach another user's library, probe the app for vulnerabilities without asking first, or automate against it in a way that degrades it for others.
• Do not connect an account you are not entitled to use. One person, their own bookmarks.

Sift depends on X's API, and X states plainly that its pricing, rate limits and policy are subject to change. If X changes what it charges or what it permits, this product has to change too — including, in the worst case, a cap moving or a feature going away. We would rather tell you that now than describe an entitlement we cannot guarantee.

There is no uptime commitment yet. Syncing runs once a day per account and a missed run is picked up by the next one; a digest with nothing new in it is never sent at all. If a published cap changes, the change is published — the same numbers appear on the pricing section, in this document and in the code, so a quiet reduction is not something we can do without it being visible.

• You, at any time. Delete your account from Settings. We revoke our token at X and purge your data, as described in the privacy policy.
• Us, if we have to. We may suspend an account that breaches the acceptable use section above, that is using the service in a way we are contractually unable to support, or where payment fails and is not resolved. Where the reason is not a security matter, we will say what it is and give you a chance to export first.
• Either of us, if X withdraws access. Our exposure to a policy breach is not a fine, it is the API being switched off. If that happens the service cannot function, and we will say so rather than let it fail quietly.