Privacy Policy
Effective September 14, 2026
DynaFlow is a desktop app that connects your machine directly to your DynamoDB tables. We built it to stay out of the way, and that goes for your data too. Here's the short version of what we collect, what we don't, what you can turn off, and the two things you can't.
The most important part: your database contents never pass through our servers. DynaFlow talks to AWS directly using credentials stored on your machine. We never see, and never collect, your table names, queries, documents, cell values, or AWS credentials.
What we collect
- Account info. If you buy a license, we store your email address so your license works and we can reach you about it. Payments are handled by Stripe. We never see your full card details.
- License & device. A hashed device fingerprint, used only to tie your license to your machines. It can't be reversed into anything personally identifying.
- App opens. This one can't be switched off. Each time DynaFlow starts, it sends a single ping so we can count how many people use it, because there's no other way for us to know. It carries an install ID, an ID for that one run of the app, the app version, which operating system you're on, whether the install has a paid license, the time, a version number for the telemetry format itself, and whether usage sharing is on, off, or not yet answered. Nothing else from the app, and nothing from your databases. The install ID is a random number with no name or email attached, but it is the same every launch, so it does tell one install apart from another over time. That's what makes a count of people possible, and it's the reason we'd rather say so here than call it untraceable.
- Crash & bug reports. This one can't be switched off either. When something breaks, we collect the error type (like
TypeErrororpanic) and the source-code location where it happened: a file and line in our own code, or, when the crash is inside a third-party component we ship, that file's path on the machine we built DynaFlow on. Never error messages, never paths or files from your machine, never your data. It's sent whether or not usage sharing is on. Alongside those two details it carries the same identifying information as the app-open ping above: the install ID, the ID for that one run of the app, the app version, which operating system you're on, whether the install has a paid license, a version number for the telemetry format, and the time, so we can tell how many people a bug is actually hitting. A crash we can't see is a crash we can't fix, which is why this one isn't a choice. - Anonymous usage analytics. Everything beyond the app-open ping and crash reports: feature-usage counts tied to that same install ID, things like "the query editor was opened." On by default, and you're asked about it the first time you open DynaFlow, and again if this policy changes in a way that matters. Opt out any time in Settings → Preferences and all of it stops. Events already queued when you opt out may still be sent, because DynaFlow sends in batches, so that's a window of about 20 seconds.
Like any request over the internet, our server also sees the IP address it came from. We keep request logs for 30 days and don't join them to the ping or to anything else above.
What we never collect
Table names, queries, document contents, cell values, AWS credentials, file paths, or anything else from inside your databases. Our telemetry pipeline enforces an allowlist: anything not explicitly on it gets dropped before it's stored.
Who else is involved
We don't sell your data, and we don't use third-party advertising or analytics services. The only providers touching anything are Stripe (payments), AWS (our backend), and Cloudflare (delivery). Each only sees what it needs to do its job.
How long we keep things
Account and license data: as long as you have a license. Telemetry and crash data: only as long as it's useful for fixing bugs and improving the app, then it's gone.
Your choices
Anonymous usage analytics can be turned off in Settings → Preferences. The app-open ping and crash reports aren't toggles. They're sent either way, and they're the only two things on this page you can't turn off.
If you opt out, we may invite you back once after DynaFlow updates. Say no and that's the end of it until the next update. Want your account data corrected or deleted? Email us and we'll take care of it.
Changes
If we change this policy in a way that matters, we'll update the date above and note it in the app or on this site.
September 14, 2026: two changes, both described above. The app-open ping is now documented: it was always sent, but this page didn't say so. And crash reports can no longer be switched off; the setting that used to control them has been removed, and DynaFlow asks everyone about telemetry once more so nobody's earlier answer is quietly reinterpreted.
Contact
Questions or requests: privacy@dynaflow.dev