← Back to Diemsy

Privacy Policy

Last updated: November 17, 2026

1. What Diemsy is

Diemsy is a warm-outreach CRM for X (Twitter). It helps you find people who fit what you sell, tracks your own engagement with them, and suggests when and what to DM. This policy covers the Diemsy website, dashboard, and Chrome extension.

2. What we collect

  • Account data: your email address, via our authentication provider (Clerk).
  • Billing data: handled by Stripe. We store a Stripe customer/subscription ID, never your card number.
  • Your offer: the product, pitch, and audience description you enter in Settings, used to personalize briefings and DM drafts.
  • Lead data: public professional information about the X accounts you choose to track — handle, bio, company, publicly posted content, and a short AI-generated briefing (role, fit, and conversation openers). This comes from TrustMRR, public Google search results, or the Chrome extension reading the X page currently open in your browser.
  • Touches: a log of the engagement you perform (likes, replies, DMs sent, notes) and whether a lead engaged back, so we can tell you when they are ready for a DM.
  • Extension token: a random token that authenticates the Chrome extension to your account. We store only its hash, never the token itself.
  • Waitlist: if you join the pre-launch waitlist, we store the email address you provide.

3. What we deliberately do not collect

Lead briefings contain professional information only — no personal life, no family, no location beyond country, no emails, no phone numbers. The Chrome extension reads only the X page you currently have open; it never scrolls, clicks, likes, follows, or sends anything on your behalf.

4. Why we process this data

Your own account data is processed to provide the service you signed up for. The public professional data we process about the people you track (who are not Diemsy users) is processed on the basis of legitimate interest: B2B outreach using information those individuals have already made public in a professional context, balanced against their right to privacy. If someone asks us to stop processing their public data, we will honor that request (see section 7).

5. Who we share data with

We use the following subprocessors to run the service. None of them receive your data for their own marketing purposes.

  • Clerk — authentication
  • MongoDB Atlas — database
  • Vercel — hosting
  • Stripe — payments
  • Anthropic (Claude) — generates briefings and DM drafts from the lead data described above
  • DataForSEO — Google search results used to find intent posts on X
  • TrustMRR — public startup/founder data
  • Web3Forms — sends us an email when someone joins the waitlist

We do not sell data to anyone.

6. How long we keep data

Leads and touches are kept until you delete them or close your account. Clicking "Delete lead" removes that lead and its touches permanently and immediately. Closing your account deletes your data on request.

7. Your rights

You can access, correct, or delete your account data at any time from Settings, or by emailing us. If you are a third party whose public professional information appears in someone's Diemsy pipeline and you would like it removed, email us at the address below and we will delete it.

8. Cookies

We use a single session cookie set by Clerk to keep you signed in. We do not use third-party advertising or tracking cookies.

9. Children

Diemsy is a B2B tool and is not directed at children.

10. Changes

If this policy changes, we will update the date at the top of this page.

11. Contact

Questions or data requests: clim.stefan27@gmail.com