Privacy Policy

1. Introduction

ChamsDel Online LLC ("we," "our," or "us") operates the ReplyWisely Chrome extension and related website (collectively, the "Service"). This Privacy Policy explains how we collect, use, and protect your information when you use our Service.

ReplyWisely is a Chrome extension that runs on X.com (Twitter) and pro.x.com (TweetDeck). It helps you find posts worth replying to. It builds advanced X searches from your niche keywords, highlights posts in your feed that match those keywords, turns plain-English descriptions into X search queries, and finds posts from people describing a problem your product solves. It also marks posts you have already replied to and can draft replies in your voice. Keyword matching and highlighting of your feed happen on your device. The data we do receive is described below.

By using ReplyWisely, you agree to the collection and use of information in accordance with this policy.

2. Information We Collect

2.1 Account Information

When you create an account on our dashboard, we collect:

• Email address
• Account credentials (securely hashed), if you sign in with email
• If you sign in with X: your X user ID and handle, and the access tokens X issues to us. We would only ever use these tokens to read your own account's public information, and we do not currently use them to read anything. If you connect more than one X account to your ReplyWisely account, we store the same for each of them, and keep each account's voice samples, drafting rules, products and reply log separate.

2.2 Extension Data Collection

The ReplyWisely Chrome extension collects and processes the following data:

If your browser is signed in to more than one X account, the extension reads which account a tab is signed in as (the public X user ID that X stores in its own cookie) and sends that ID with reply-drafting, voice-learning, product, reply-log and usage requests, so each X account's data stays separate. It is a public identifier, not a credential.

2.2.1 Data Processed Locally

The following data is processed locally on your device and stored in your browser's local storage so the extension can work:

• Public post content in your X feed (text, engagement counts, author information), used to match posts against your niche keywords and highlight them. Your feed is not uploaded to our servers.
• Your keyword filters, niche keyword profiles, and extension preferences
• Cached author follower counts and relationship data
• IDs of posts you have replied to, so they can be marked with a checkmark
• Your queue of posts to reply to and recent replies

Some data is synced to our servers to provide features, as described below.

2.2.2 Data Synced to Backend

When the extension is activated and linked to your account, the following data is synced to our servers:

• Extension Settings: Your niche keyword profiles, Niche Targets, keyword filters, and other extension settings
• Follower/Following Data: Follower and following counts for X accounts (including your own) whose profiles you view or hover over while using the extension, cached so the extension can show them
• Relationship Data: Information about your follow relationships, including whether you follow specific users and whether they follow you
• Reply Activity Data: When you reply to a post using the extension, we collect:
  • The original post's ID and author information (handle, follower count, verification status)
  • The engagement counts visible on the original post at the time (likes, reposts, replies) and its age
  • Your reply's post ID (if detected) and timestamp
  • Engagement counts visible on your reply when the extension sees it (likes, reposts, replies)
• Search and Drafting Requests: When you use AI search, the plain-English description you type (and, for product search, the product you select) is sent to our servers to build an X search query. When you request a reply draft, the post you are replying to and your chosen tone are sent to our servers to generate the draft.
• Fit Check: Posts the extension collects from a search you run (an X search results page, including ReplyWisely's product, niche and description searches) are sent in batches, with their author handle, to our servers so AI can score how well each fits your product or niche. Posts from your own timeline or feed are not sent for the fit check: they are filtered only in your browser (a timeline post is sent only if you ask for a reply draft, as described above). We keep the score and a one-line reason in your browser; our servers keep only usage counts for billing, not the post text. This also runs for the one free search before you sign in, identified only by an anonymous install ID.
• Voice Training Data: If reply drafting is enabled, the text of replies you post with the extension and — once, when you sign in with X — up to 100 of your most recent posts read through the X API with the access you grant, are stored so drafts can match your writing style. If your free trial ends without a subscription, this voice data is kept for 30 days after the trial ends and then deleted. You can pause voice training (from the dashboard or the extension) or delete these examples from your dashboard
• Drafting Settings: Your “About You” bio, voice rules, and up to 3 product names and URLs. We fetch each product page server-side and store a short description of it.
• Usage Counts: Basic usage counts from the extension, such as active sessions, the number of drafts generated, and which drafting tones you use
• Feedback: Any bug reports or feedback you submit through the extension or dashboard

We sync this data to keep your settings across devices, mark posts you have already replied to, build searches, generate drafts, and improve the service. All data is encrypted in transit and stored securely.

2.3 Activation

When you activate the extension, we validate your extension's install ID or activation token against our server. This validation includes only that identifier and does not include any post content or browsing data. The extension may also read the X account you are logged into and link its ID and handle to your ReplyWisely account.

2.4 Analytics Data

We use PostHog to understand how people use ReplyWisely during their trial, so we can improve it. PostHog receives product events tied to your account ID: signing up, your trial starting and ending, the extension connecting to your account, drafts and searches being generated, products being added, and checkout and subscription changes. These events do not include the text of posts, replies, drafts, product descriptions, or your email address. On our website and dashboard, PostHog also records page views and session replays with all form inputs masked. We also use Google Analytics on our website.

2.5 Payment and Subscription Information

When you subscribe to ReplyWisely, we collect payment information through our payment processor (Stripe). We store:

• Stripe customer ID and subscription ID
• Subscription status and payment history
• Subscription start and end dates
• Payment method information (processed securely by Stripe, not stored by us)
• Cancellation information (if applicable)

3. How We Use Your Information

We use the information we collect to:

• Provide and maintain the Service
• Process your account registration and manage your subscription
• Validate your extension activation
• Sync your extension settings and keyword profiles across devices
• Build X search queries and reply drafts when you ask for them
• Show which posts you have already replied to
• Send important service-related communications
• Respond to customer support requests
• Improve and optimize the Service through data analysis

3.1 Data Usage for Service Improvement

We may use aggregated and anonymized data collected from all users to:

• Improve search and drafting quality
• Develop new features and functionality
• Understand usage trends and optimize service performance

When used for analytics, this data is processed in aggregated, anonymized form and does not identify individual users or their specific Twitter/X accounts. We do not use your personal account information (email, activation token) in these processes.

3.2 Data Displayed to You

We use your collected data to show you:

• Which posts you have already replied to, and when you last replied to an author
• Your saved niche profiles, drafting settings, and voice training status

4. Data Storage and Security

Account data and synced extension data are stored securely using industry-standard encryption both in transit and at rest. Extension preferences and caches are also stored locally in your browser using Chrome's local and sync storage APIs, which may sync across your devices if you're signed into Chrome.

We implement appropriate technical and organizational measures to protect your personal information against unauthorized access, alteration, disclosure, or destruction, including:

• Encryption of data in transit using TLS/SSL
• Encryption of sensitive data at rest
• Secure authentication and authorization mechanisms
• Regular security audits and updates
• Access controls limiting data access to authorized personnel only
• Row-level security policies in our database to ensure users can only access their own data

Your data is stored on secure servers provided by Supabase and other trusted cloud service providers. We retain your data for as long as your account is active or as needed to provide the Service, unless you request deletion or we are required to retain it for legal purposes.

5. Third-Party Services

We use the following third-party services:

• Supabase: For authentication, account management, and secure data storage
• Stripe: For payment processing and subscription management
• Anthropic: To generate reply drafts, build search queries from the text you send, and check whether collected posts fit your product or niche
• OpenAI: To create text embeddings for voice training, summarize the product pages you add, and check drafts for generic “AI-sounding” phrasing
• Resend: To send account and subscription emails
• Google Analytics: To understand how users interact with our website (not the extension)
• PostHog: Product analytics and website session replays, hosted in the United States (see 2.4)

These services have their own privacy policies governing their use of your data. We only share data with these services as necessary to provide the Service, and we ensure that appropriate data processing agreements are in place.

The ReplyWisely extension operates on X.com and pro.x.com (TweetDeck). We are not affiliated with, endorsed by, or sponsored by X Corp. Your use of X.com is governed by X Corp's own terms and privacy policies.

6. Data Sharing and Disclosure

We do not sell, trade, or otherwise transfer your personal information to third parties for marketing or commercial purposes. We may share information only in the following circumstances:

• With your explicit consent
• With service providers who assist us in operating the Service (e.g., Supabase, Stripe, Anthropic, OpenAI) under strict confidentiality agreements
• To comply with legal obligations, court orders, or government requests
• To protect our rights, privacy, safety, or property, or that of our users
• In connection with a business transfer (merger, acquisition, etc.), with notice to users

Aggregated and anonymized data may be used for research, analytics, or shared with partners for service improvement purposes, but this data cannot be used to identify individual users.

7. Your Rights

You have the right to:

• Access the personal data we hold about you
• Request correction of inaccurate data
• Request deletion of your account and associated data
• Export your data in a portable format
• Clear locally stored extension caches at any time via Chrome's extension storage

To exercise these rights, please contact us at support@chamsdel.online

8. Children's Privacy

Our Service is not intended for children under 13 years of age. We do not knowingly collect personal information from children under 13.

9. Changes to This Policy

We may update this Privacy Policy from time to time. We will notify you of any changes by posting the new policy on this page and updating the "Last updated" date.

10. Contact Us

If you have any questions about this Privacy Policy, please contact us: