Privacy

How MaybeSend handles your data

Last updated 19 Sep 2026.

• What we process

  When you press Check or Humanize, we send your draft text to the MaybeSend API (api.maybesend.com). If you are replying or quoting, we may also send the parent or quoted post so the score is context-aware. On Reddit we may send that sub's public rules with the draft. We do not post for you. We do not collect browsing history.

• What we store

  Account email (if you sign up), waitlist email if you ask for the install link or another room, a random device id, plan, usage counters, and last verdict metadata (for example Send, Fix, or Don't and meter values). We do not persist the draft or reply/quote text after the request finishes. Brief in-memory caching of scores may keep hashed drafts for a short time to avoid double-billing the same Check.

• Third parties

  Drafts (and reply/quote context when present) are scored and may be rewritten by our subprocessors so we can run Check and Humanize. Those vendors process the text to provide the service and may retain logs under their own policies. Payments go through Stripe when subscriptions are enabled.

• Chrome extension

  The extension stores a device id, optional session token, and settings in chrome.storage.local on this browser (not Chrome sync). Content scripts load on X, LinkedIn, and Reddit so the panel can sit next to the box you are typing in. Extra sites are off until you turn on anywhere else in your signed-in account and grant access in Chrome. On X it attaches under compose. On LinkedIn it docks inside the share dialog. On other granted sites it floats beside the focused field. On Reddit it may fetch that sub's public rules so Check can judge promo and off-rule drafts. Payment and password fields never send. Drafts leave this browser only when you press Check or Humanize, and then only to api.maybesend.com. Provider API keys are not in the extension. We do not scan the rest of the page. Full feature list: maybesend.com/extension.

• Analytics

  Public pages load a cookieless Umami script from agentseal.org so we can count page views. It does not set advertising cookies and does not identify you.

• Rate limits

  Check and Humanize are capped per device (trial and Pro) and per IP, including daily ceilings that persist if the API restarts. This stops token burn from rotating device ids. Caps are enforced on the server, not only in the extension.

• Contact

  [email protected]