Privacy Policy

All data stays locally in your own browser via chrome.storage.local — your settings, send history, and license identifier (an anonymous UUID, no password; logging out switches this browser to a different one — newly issued the first time, reused afterwards — and keeps up to five previous ones locally so you can restore them). None of it is sent to the developer. You can erase your settings, send history and campaigns at any time via "Reset data" in Settings. The reset keeps your license identifier, the list of your own Instagram accounts used with the extension (handle and profile picture), and each account's daily send count and last Instagram-imposed limit time, so it does not end your subscription or reset the sending limits. Uninstalling the extension removes everything.

The only data the extension sends to our license server (hosted on Supabase) is an anonymous random UUID and a daily send counter, used solely to confirm your subscription tier — the only exception is your email address, and only if you choose to sign in with Google (see Optional Google sign-in below). Payment is processed entirely by Lemon Squeezy; their privacy policy applies to the checkout flow. The extension also sends a small, fixed set of usage events to PostHog so we can see where the product fails people, such as whether building a recipient list works at all. Only controlled values are sent: which screen was opened and how it was reached, the outcome of a list build and whether it was a followers or following list (never the target account), recipient preparation method and current valid-row count, our own reason code if a spreadsheet import failed, whether the trimmed message is non-empty, whether an explicit Send or Add to queue click passed or was blocked with our own reason code (and, when it passed, whether previously sent accounts were excluded, how many, and whether the message uses variables — yes or no, never the message), how many recipients a run had, whether a run was paused or resumed and why, our own error category on failure, which limit was hit with our own reason code, whether a checkout page was opened or the plan list failed to load, and — for the optional sign-in flow — whether the sign-in button was clicked, whether sign-in finished and a trial was granted, our own reason code if sign-in failed, whether a one-day PRO trial started, and whether log-out was clicked, finished, or failed with our own reason code. Message text, recipient usernames, file names, and recipient lists are never sent and cannot be: the extension carries an explicit whitelist of allowed events and properties and discards everything else before making a request, and a regression test fails the build if a call site tries otherwise. Events are attached to the same anonymous license UUID, and none are sent if no UUID exists on the device. See the full policy for the exact list.

This marketing website uses PostHog to understand visitor patterns — pages viewed, browser and device type, approximate location (city/country derived from IP, with the raw IP not stored), and an anonymous identifier stored in a first-party cookie. The extension reports to this same PostHog project, told apart by a source property; what it sends is listed above. This telemetry does not join website and extension identifiers, and is not linked to an account, payment, license UUID, or Instagram identity.

Questions? Email contact@getdmstudio.com.