X / Twitter DM Auto Responder & Retweeter ("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 ID generated locally to associate records with your installation.
- User settings: Saved post links, speed settings, filters, and UI preferences.
- Runtime state: Queue state, processed conversation markers, activity log, and bot status.
- Metadata: Remaining uses, run counters, and payment status returned by backend APIs.
- Clipboard text: Used only as a fallback for user-triggered message insertion.
Why We Process Data
- To run user-requested workflows and update queue status.
- To persist settings between your sessions.
- To validate usage status and show account history.
Storage Location
- Local extension storage (chrome.storage.local) on your browser profile.
- Backend service endpoints for usage tracking and payment history.
Data Sharing & Retention
We do not sell personal data. Data is shared only with backend infrastructure required to provide the extension’s functionality. Local data remains until you clear extension data or uninstall. Backend records are kept only as needed for billing, security, and legal compliance.
User Controls
- Stop or pause workflows at any time via the UI.
- Clear local activity logs directly from the extension.
- Request deletion of backend records by contacting support.
Security
All requests are sent over secure HTTPS. Access is strictly limited to required services and minimum data needed for features.
Third-Parties
X/Twitter pages are accessed only to perform user-initiated actions. Backend APIs handle premium and usage tracking.