Privacy Policy

Last updated: April 2, 2026

Local Deletion Workflow. Separate Purchase and License Data.

Tweet deletion runs locally on your Windows computer through your own authenticated browser session. No cloud service performs the deletions. Delete My Tweets does not store OAuth tokens for deletion. Delete My Tweets does not upload archive files, deletion logs, or in-app deletion history to our servers. Separately from that local workflow, Stripe handles checkout, we receive limited purchase and contact details to deliver and support the product, and we process license data for activation. We also use Google Analytics on the marketing site to measure page views, CTA clicks, and checkout performance. We also keep a customer-contact record on our Contabo mail stack so we can support the order and, if you explicitly opt in, send product updates.

1. Information We Do Not Receive From the Deletion Workflow

When you use Delete My Tweets to clean your account, the deletion workflow stays on your machine. That means we do not receive the core deletion inputs:

  • Your X content: We do not receive your tweets, retweets, replies, or other account content as part of the deletion workflow.
  • Your Twitter/X password: You sign into X in your own browser. We do not provide a Delete My Tweets login form for your X credentials.
  • Stored OAuth tokens for deletion: Delete My Tweets does not require or store OAuth tokens to delete tweets.
  • Archive files or account exports: No archive files are imported or uploaded as part of the deletion workflow.
  • Deletion progress or in-app history: Deletion progress, in-app history, and deletion logs stay on your device unless you choose to send us something in a support email.

2. Payment and Transaction Data

Checkout is handled by Stripe. We do not run our own card-payment form. When you buy the product, we receive limited order details needed to fulfill that purchase:

  • Purchase email address: The buyer email used at checkout is sent to us so we can deliver the app, send the license key, and help with refunds or support.
  • Transaction confirmation: We receive confirmation that the Stripe payment succeeded so we can unlock the download page and fulfill the order.
  • Purchase record: We may use the Stripe order or customer record tied to that transaction to answer purchase questions, handle refunds, and support the license. We also keep a minimal customer-contact record on Contabo for order support and follow-up delivery.

3. Customer Contact Details and Support

We use your purchase or support email address for straightforward support tasks:

  • License delivery: We use your purchase email to send your license key and download information.
  • Support replies: If you email us, we receive the information you include in that message so we can answer your question.
  • Refunds and device changes: We may use your purchase email to locate the order when helping with refunds, license resets, or device-transfer questions.
  • Customer updates: If you explicitly opt in to product updates, we may keep your contact in our customer list so we can send those updates. You can unsubscribe from those messages at any time.
  • No remote deletion logs: Because deletion runs locally, support requests do not automatically include your tweets, deletion history, or in-app progress unless you choose to send details yourself.

4. License and Activation Data

Delete My Tweets uses a license key to activate the Windows app. To make that work:

  • License creation: After a paid order is verified, we generate a license key for that purchase.
  • License record: We store the license key with the related purchase record in Stripe so the license can be validated and supported.
  • Activation checks: When the app checks a license key, we process the key and the related purchase record needed to confirm whether it is valid.
  • Separate from deletion: License checks do not send us your tweets, archive files, authenticated browser session, or deletion history.

5. How the App Works (Technical Details)

Delete My Tweets uses browser automation for tweet deletion:

  • Authentication: You log into Twitter/X in your browser like you normally would. The app uses your existing authenticated browser session. No API keys required for deletion. Delete My Tweets does not store OAuth tokens for deletion.
  • Tweet deletion: The app automates the same delete actions you would perform manually in the browser, just at scale and with filters.
  • Data flow: During deletion, your browser communicates directly with X. Delete My Tweets does not provide a cloud deletion service or backend that performs those deletions on your behalf.

6. No Twitter Archive Required or Used

Delete My Tweets does not import or process your Twitter archive. Unlike cloud tools that request OAuth account access to delete tweets on your behalf:

  • The app scrolls through your profile in your own browser to find tweets — no archive file needed
  • No data export, no CSV handling, no file upload of any kind
  • Everything happens live through your authenticated browser session

7. Third-Party Services

We use minimal third-party services:

  • Stripe: Checkout, payment processing, and the purchase record used for license delivery and validation.
  • Mailcow on Contabo: Transactional email delivery for license keys, download information, and refund-related emails.
  • Listmonk on Contabo: Customer-contact storage and optional customer-update subscriptions for people who explicitly opt in.
  • Google Analytics: Page views, CTA clicks, and checkout performance on the marketing site.
  • Website hosting: Contabo VPS and Coolify for site delivery.
  • Twitter/X: The app automates actions in your browser on x.com or twitter.com. This is different from granting a cloud tool special API-based deletion access.

8. Data Security

Our security model depends on keeping the deletion workflow local and limiting what our website services process:

  • Tweet deletion uses your existing browser session rather than a Delete My Tweets cloud relay
  • Delete My Tweets does not store OAuth tokens for deletion.
  • No archive files are imported or uploaded as part of the deletion workflow.
  • License checks use the license key and the related purchase record rather than your deletion data.
  • Purchase, licensing, and analytics data are limited to the separate website services described above

9. Questions and Requests

You can contact us to:

  • Ask what purchase, license, or support information we hold about your order
  • Request deletion of support or purchase email information that we control, where feasible
  • Ask questions about how the app works and what the website services process

10. Children's Privacy

Delete My Tweets is not intended for use by children under 13 (or the applicable age in your jurisdiction). We do not knowingly collect information from children.

11. Changes to This Policy

We may update this privacy policy occasionally. If we do, we will update the date on this page. Continued use of Delete My Tweets after those changes constitutes acceptance of the updated policy.

12. Contact Us

If you have questions about this privacy policy or our data practices:

This privacy policy is effective as of March 22, 2026. Delete My Tweets is operated by Matthew Christensen.