Privacy Policy for X DM Assistant

X DM Assistant ("the extension") helps users manage user-initiated direct message workflows on X/Twitter. This policy explains what data is processed, why, and how it is handled.

Data We Process

• Installation identifier: a random install ID generated locally to associate usage/purchase records with one extension installation.
• User settings: saved post link, speed settings, filters, and UI preferences.
• Runtime state: queue state, processed conversation markers, activity log, and bot status.
• Usage/purchase metadata: remaining uses, run counters, order/payment status returned by backend APIs.
• Clipboard text (fallback only): used only when user-triggered message insertion fallback is needed.

Why We Process Data

• To run the user-requested workflow (open DM pages, process selected conversations, and update queue/status).
• To persist user settings between sessions.
• To validate premium/usage status and show account history.

Where Data Is Stored

• Local extension storage (chrome.storage.local) on the user’s browser profile.
• Backend service endpoints for usage/account features (premium checks, usage tracking, history, order creation).

Data Sharing

• We do not sell personal data.
• Data is shared only with backend infrastructure required to provide the extension’s account/usage functionality.

Data Retention

• Local data remains until the user clears extension data or uninstalls the extension.
• Backend records are retained only as needed for account history, billing/usage integrity, security, and legal compliance.

User Controls

• Users can stop/pause workflows at any time.
• Users can clear local activity logs from the extension UI.
• Users may request deletion of backend-linked records associated with their install ID by contacting support.

Security

• Requests are sent over HTTPS.
• Access is limited to required services and minimum data needed for features.

Third-Party Services

• X/Twitter pages are accessed only to perform user-initiated actions.
• Backend APIs are used for premium, usage, and history features.