Skip to content

Add Anonymous Telemetry page#30

Open
bjorkert wants to merge 3 commits intomainfrom
add-telemetry-docs
Open

Add Anonymous Telemetry page#30
bjorkert wants to merge 3 commits intomainfrom
add-telemetry-docs

Conversation

@bjorkert
Copy link
Copy Markdown
Member

Summary

New page Privacy → Anonymous Telemetry documenting the optional weekly telemetry check-in that LoopFollow sends.

The page covers:

  • What is sent (table of fields with examples and notes)
  • What is NOT sent (health data, credentials, logs, IP)
  • Where reports go (https://lf.bjorkert.se, self-hosted, no third-party)
  • How to opt out (Settings → General Settings → Diagnostics)
  • How often the check runs and how failures are handled
  • A "for the curious" pointer to LoopFollow/Helpers/Telemetry.swift

Nav

A new top-level Privacy section is added between Build and FAQs, with a single page initially. Easy to grow later if more privacy topics arise.

Companion PR

Implementation: loopandlearn/LoopFollow#626

Documents the optional weekly telemetry check-in shipped with
LoopFollow: what gets sent, what doesn't, where it goes, how to opt
out, and how often the check runs. New top-level Privacy section in
the nav so users can find it without digging through FAQs.

Implementation: loopandlearn/LoopFollow#626
- Drop time-zone field. Replace hashed NS host / Dexcom username with
  usesNightscout / usesDexcom yes-no flags. Add followingApp and IDFV
  rows. Bucket field is now dayBucket (yyyy-MM-dd) instead of
  weekBucket.
- Cadence section reflects the new 24h TaskScheduler-driven flow.
clientId is no longer in the payload — IDFV + instance covers the same
"identify this install" purpose.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant