DM Studio
BlogPricing

Privacy Policy

DM Studio for Instagram — Last updated: 2026-09-08

Data stored on your device

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 all of it at any time via "Reset all data" in Settings.

Data sent to the developer

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 enumerated values are sent: which screen was opened, the outcome of a list build, how many recipients a run had, our own error category on failure, which limit was hit, whether a checkout page was opened, 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. Message text, recipient usernames, 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.

Optional Google sign-in

Signing in is optional. If you never sign in, nothing here applies.

If you choose Sign in with Google inside the extension, we receive your email address from Google and store it on our license server so that signing in on any browser gives you that account's license key, and to grant the one-day PRO trial. That address is the only personal identifier we hold. We never receive your Google password or any other Google data, and the extension does not keep a Google session.

Log out any time from the extension's Subscription menu. This browser then switches to a different anonymous UUID — newly issued the first time, reused afterwards — and the previous one stays linked to your account, so nothing is lost; when a new one is issued, the previous UUID is sent along with the request so that a log-out is not counted as a new install. To delete the account record, email contact@getdmstudio.com.

Marketing website analytics

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 data is not linked to any account, payment, license UUID, or Instagram identity.

Contact

Questions? Email contact@getdmstudio.com.
© 2026 DM StudioContact: contact@getdmstudio.com
PrivacyTermsRefund