Conversation
Came up during the questdb.com privacy notice refresh. The telemetry page called telemetry anonymous and said we collect no personally-identifying information and share nothing with third parties. Telemetry is sent with the IP address it comes from, so those claims are not accurate. Replace them with statements that are, link the privacy notice, and fix the telemetry.hide.tables default, which is true in the server code. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
|
🚀 Build success! Latest successful preview: https://preview-567--questdb-documentation.netlify.app/docs/ Commit SHA: a4391c4
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What and why
This came up during the refresh of the questdb.com privacy notice. We're updating the telemetry docs page so it says the same thing as the new notice.
The page said telemetry is anonymous, that we collect no personally-identifying information, and that we share none of it with third parties. Telemetry is sent with the IP address it comes from, and that IP is looked up with an external service, so those three statements aren't accurate.
Why it isn't "anonymous": under GDPR, data only counts as anonymous if it can't reasonably be linked back to a person or organization. IP addresses count as personal data (GDPR Recital 30; the EU Court of Justice in Breyer, 2016). Our telemetry also carries a persistent instance ID and, if set, the instance name and description, and the IP lookup identifies the organization and approximate location. Together, that makes the data identifiable, even though some values (database size, table count) are sent as ranges.
Changes
configuration/telemetry.mdtelemetry.enableddescription.telemetry.hide.tablesdefault fromfalsetotrue, which matches the server code (PropServerConfiguration) and the shippedserver.conf. This one isn't privacy-related; it was just wrong.configuration/overview.md: "Anonymous usage telemetry" becomes "Usage telemetry" in the settings table.No behaviour changes. Docs text only.
🤖 Generated with Claude Code