Privacy Policy
Last updated: October 26, 2026. This translation is provided for convenience only. If it differs from the English version, the English version prevails.
This policy explains how PromoSift handles information through its website, browser extension, and account service. PromoSift helps you identify likely promotional content on X (Twitter), using local display controls and classification provided by Jev, operated by TypeSafe AI.
1. Passwordless account sign-in
We process your email address and a six-digit verification code to create or access your account. Codes expire after 10 minutes and can be used once. The production account service stores a cryptographic hash of the code rather than the code itself. Resend receives your email address and the code to deliver the sign-in email.
The service stores your account identifier, email, account status, credit balance, usage and check-in records, and session records. Sessions can remain valid for up to 300 days unless revoked earlier. The website uses an authentication cookie; the extension stores its session token, account snapshot, and most recently used successful sign-in email in Chrome’s local extension storage. The saved email remains after sign-out to prefill the next sign-in; verification codes are not saved. Server-side session tokens are stored as hashes. We also use hashed IP addresses and email addresses for request limits and abuse prevention.
If you follow a referral link, the website keeps the first valid referral code in a signed cookie for up to 30 days. The code is carried through website sign-in and recorded with that session. If the sign-in creates a new account, we link it to the inviter and record the related credit rewards; existing accounts are never linked later. A successful sign-in with a recorded source clears the referral cookie. Referral codes do not contain email addresses. Inviter lists show masked email addresses. These records help identify referral sources and remain subject to the account-record retention and data-request practices below.
For the share task, we retain your task referral link, opening and reward times, and the post link you submit. We send the submitted post ID to TwitterAPI.io to retrieve the public post and verify its author, content, and publication time. We retain the verified post ID, author ID and handle, publication time, and verification time alongside the reward record. The link cannot be edited after verification. These records follow the account-record retention and data-request practices below.
For referral cashback and withdrawals, we keep the related deposit, amount, recipient wallet address, request status, and review or refund-deduction records. Pending withdrawal requests are temporarily saved in your browser tab storage with their request identifier so a retry does not create another request. These records follow the account-record retention and data-request practices below.
If you choose Google sign-in, Google processes the authorization request. PromoSift receives your Google account identifier, email address, email verification status, and, where applicable, your Google Workspace domain. We store the Google identifier linked to your PromoSift account. Google access tokens are used transiently to verify your identity and are not stored. Temporary login state expires after 10 minutes; extension sign-in tickets expire after one minute and can be used only once. Expired temporary sign-in records, including verification codes and request-limit counters, are deleted automatically within a few minutes. Google sign-in does not grant consent to post analysis or access to Gmail, Drive, or your Google password.
2. Browser and server processing
While you are signed in to PromoSift and data processing is enabled in the extension, it reads your current X account menu and saves the displayed handle and name with your PromoSift account. If you switch X accounts, the latest observed account replaces those values. If X is signed out or the account menu is unavailable, the extension skips the update and keeps the previously saved values. This does not connect your X account through OAuth or verify ownership. If you choose to verify the follow task, we send the saved handle to TwitterAPI.io to check whether it follows @promosift and store only the time the follow was verified. These account-menu values are not sent to Jev and do not consume detection credits.
After you explicitly consent in the extension, while you are signed in and have available credits, the extension automatically sends post text near the visible area of X pages to the PromoSift service, together with the displayed author, quoted-post text, and existing X ad labels. The service forwards the post state and classification questions to Jev. When semantic keyword matching is enabled, your configured keyword topics are included in those questions. Optional AI-writing analysis uses the same post text. An existing X ad label does not bypass classification.
Literal keyword matching, labels, and folding run locally. Your explicit data-processing consent, display mode, keywords, sensitivity, AI-writing preference, and session counters are stored locally in the extension. Results may also remain in the current page’s memory for display and reuse. The website uses session storage to remember an in-progress payment request.
3. Scope of page access
The extension’s page scripts run on x.com and twitter.com. Automatic scanning targets rendered post containers, including posts and replies, rather than direct-message conversations or unpublished drafts. It does not read your browser history, passwords, or pages on unrelated sites.
If you explicitly use the right-click “Check selected text with PromoSift” action on X, the selected text is sent for classification. This can include private text you select; do not submit text you do not want processed by PromoSift and Jev. Text within a post may also contain personal information, even if the post is publicly visible.
4. Purchases and payment data
Where available, paid credits are added after a USDC payment on the Flare402 payment page (flare402.com), the payment service we use. To create a payment we send Flare402 your account number and the order number, not your email address. Flare402 assigns a personal deposit address to your account, verifies transfers on the supported blockchain networks, retains the transfer details it needs (such as sender address and block information), and notifies us when a payment is confirmed. We retain orders, amounts, network, transaction hashes, payment references, and credit records to reconcile payments and provide support. A payment stays open for 10 minutes; transfers recorded on-chain before the deadline may finish confirming afterward. Transfers outside a payment require support review. Blockchain RPC services used by Flare402 receive the address and transaction queries needed to verify transfers. The website does not ask for your wallet’s private key or recovery phrase, or for payment-card details.
Blockchain addresses and transfers are public on their networks. Deleting information held by PromoSift cannot remove public blockchain records.
5. Service providers and sharing
We use the following services to operate PromoSift:
- Cloudflare: hosts the website, API, database, and download infrastructure. It processes requests and associated network information, such as IP addresses, to deliver and protect the service. See Cloudflare’s privacy policy.
- Google: provides optional Google account sign-in. See Google’s privacy policy.
- Resend: delivers verification emails using the recipient address and email content. See Resend’s privacy policy.
- TypeSafe AI / Jev: processes submitted post or selected text and keyword questions to return classification results. Your PromoSift email and session token are not included in our Jev classification payload. See TypeSafe AI’s privacy policy.
Providers may retain service records under their applicable policies and service terms. Our cache period does not determine their retention periods. Payment verification also uses the blockchain RPC services described above.
6. Storage and retention
Classification results are cached in Cloudflare Workers KV under a SHA-256 fingerprint of the post content (and, for keyword matches, of the normalized keyword). Cache entries contain the result only; they do not contain your account identifier, email, session token, or the original post text. Completed results are reused across accounts for the same post for up to 24 hours, after which the cache entry expires automatically. Each successful server check consumes one credit, including a cache hit; a check that fails is not charged. Each check is recorded in your credit history.
The 24-hour window controls result reuse; it is not an automatic deletion deadline. Expired classification records may remain until replaced or removed. Account, credit, payment, security, and operational records do not currently have a fixed automatic deletion schedule. Expiry of a verification code or session prevents its use but does not necessarily remove every related record. Contact us about access, correction, or deletion as described below.
7. Limited use and security
PromoSift uses the data described here to provide classification, filtering, authentication, credit accounting, payments, support, and service security. Our use and transfer of data received through the extension is limited to these user-facing purposes in accordance with the Chrome Web Store User Data Policy, including its Limited Use requirements. We do not sell this data or use it for personalized advertising, creditworthiness, or lending decisions.
Production requests to the PromoSift API, email service, classification service, and blockchain RPC endpoints use HTTPS. Extension session storage is restricted to trusted extension contexts so the X page’s content script cannot read the login token.
8. Your controls and data requests
You can choose Label or Fold, expand folded posts, adjust keywords and sensitivity, and turn off optional AI-writing analysis. Signing out stops automatic account-based classification. Uninstalling the extension removes its local settings and session data; it does not delete your server-side account or payment records. Classification and AI-writing scores are estimates, not proof of a paid relationship or text authorship.
To request access to, correction of, or deletion of your account information, email hello@promosift.app. We may ask you to verify account ownership before processing a request. There is currently no self-service account deletion control. Some records may need to be retained for payment reconciliation, dispute resolution, security, or applicable legal obligations; public blockchain records cannot be deleted by us.
9. Policy changes
We will update this page and its date when these practices change. Material changes to extension data handling will also be disclosed in the product before they take effect.
Contact
Questions can be sent to hello@promosift.app.