bwoodruff
Joined 10 years ago
Joined 10 years ago
The point was if we'd had telemetry while prioritizing this work, we would've known it was something many people were actually using. The little data we had showed that was not likely the case. Had we known, we would've prioritized differently.
https://bucket.agilebits.com/ben/telemetry-consent-draft.png
https://bucket.agilebits.com/ben/telemetry-consent-draft.png
Here is a draft of what we're considering: https://bucket.agilebits.com/ben/telemetry-consent-draft.png
Does that help clarify what the experience will be?
-Ben, 1Password
-Ben, 1Password
-Ben, 1Password
tl;dr If we roll this out to customers, we'll be asking for consent, and won't be collecting telemetry data unless we have it.
-Ben, 1Password
tl;dr If we roll this out to customers, we'll be asking for consent, and won't be collecting telemetry data unless we have it.
-Ben, 1Password
tl;dr If we roll this out to customers, we'll be asking for consent, and won't be collecting telemetry data unless we have it.
-Ben, 1Password
tl;dr If we roll this out to customers, we'll be asking for consent, and won't be collecting telemetry data unless we have it.
-Ben, 1Password
tl;dr If we roll this out to customers, we'll be asking for consent, and won't be collecting telemetry data unless we have it.
-Ben, 1Password