RI-8038 [E2E] 7.2 Settings -> Privacy Settings

[pd-redis]

What

Add Playwright E2E tests for the Privacy Settings section (7.2) of the Settings page.

Tests verify that the privacy section expands correctly, the usage data switch is displayed, and the privacy policy link is visible with the correct target attribute.

Testing

Run: npx playwright test tests/main/settings/privacy-settings

---

Closes #RI-8038

Made with Cursor

---

Note

Low Risk
Low risk: changes are confined to Playwright E2E tests and test-plan documentation, with no production code impact. Main risk is potential test flakiness from network interception and timing around the settings PATCH /api/settings response.

Overview
Adds a new Playwright spec for Settings → Privacy that verifies the section renders correctly (usage data switch and privacy policy link) and that toggling usage data suppresses or enables telemetry requests as expected.

Extends the SettingsPage page object with helpers to toggle usage-data while waiting for the settings PATCH /api/settings, and to intercept **/analytics/send-* requests for assertions. Updates TEST_PLAN.md to mark the new Privacy/telemetry cases as implemented.

^{Written by Cursor Bugbot for commit 802d9a6. This will update automatically on new commits. Configure here.}

[jit-ci]

🛡️ Jit Security Scan Results

✅ No security findings were detected in this PR

---

^{Security scan by Jit}

to be re-reviewed once tests pass

[valkirilov]

Being in the context of an e2e test, does it make sense to actually verify whether we send (or don't) telemetry data, once we toggle the Usage data switch?

Like, a simple network interceptor, just to verify whether we emit send-page and send-event 🤔

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}