Say that the app records the screen, before the build that does it - #173
Merged
Merged
Conversation
The policy claimed the opposite in two places — section 2.4's "No session recording. Screen replay is switched off. Nobody watches a recording of you using the app, because none is made", and section 4's "No session recording, anywhere" — and both become false the moment a build carrying `@posthog/react-native-plugin` reaches a store. That plugin landed in the app on 11 September 2026; no build carries it yet, which is the only reason this is a correction made in time rather than a false claim already published. Section 2.4 gets a paragraph rather than a bullet, because what is recorded needs more than a line: every word and every image is masked on the device before a frame is sent, so the recording is a wireframe and not a picture of somebody's phone, and the log output and request URLs are excluded too. The list below it drops from three settings to two. Section 4 is "What We Do Not Collect", and the honest entry there is no longer "no session recording" but what is not *in* one. It keeps the website half of the old sentence, which is still true: the recorder is a native component and a browser has none. Section 8 names recordings among what PostHog receives, and 10.5 says the Share usage data switch stops the recording as well as the events — it does, without waiting for a restart, because the SDK passes the refusal down. The effective date moves to today. The blog post's September note about the analytics SDK said "no session recording" too; it gets a second note rather than an edit, the way the first one did. `disable_session_recording: true` on the website is unchanged and stays — only the comment that justified it by pointing at the app is now wrong. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Merged
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.
The privacy policy currently says, twice, that the app does not record your
screen:
watches a recording of you using the app, because none is made."
Both stop being true the moment a build carrying
@posthog/react-native-pluginreaches a store. That plugin landed in the app on 11 September 2026
(langx/langx#1324), and no build carries it yet — the 2.3 round is the first
one that will — so this is a correction made before the fact rather than after
it. langx/langx#1324's own commit message names it as one of the two things
outside that repo that have to follow.
What changed
src/lib/analytics.tsdisable_session_recording: trueis unchanged — the website is not recorded; the comment justified it by pointing at the app, which no longer gives that answer.Checks
npx vite buildis clean and the prerenderedbuild/privacy-policy.htmlcarries the new text with no occurrence of "No session recording" left.
🤖 Generated with Claude Code