[Bug]: Anonymous analytics missing from cloud version

[fdev23408]

Preflight

• I searched existing issues and docs before opening this.
• I removed secrets, tokens, private keys, customer data, and private repository details from logs and screenshots.
• This report describes observed behavior, not a speculative AI-generated rewrite request.

Summary

privacy settings are missing from cloud version. The are present in self hosted version: "Privacy

Anonymous analytics

Share anonymous usage analytics with the Roomote team to help improve the product. Activity is identified only by random IDs that are never linked to your company, users, or repositories. No prompts, conversations or code is ever shared."

Affected surface

Web dashboard

Steps to reproduce

/settings/misc shows no privacy settings

Expected behavior

should include privacy settings to toggle on/off anaonymous analytics

Actual behavior

it is missing.

Roomote version

main-82eebfdc

Installation method

Other

Deployment context

Roomote cloud

Diagnostics output

Instance

Generated at: 2026-08-02T07:35:49.404Z
Roomote version: main-82eebfdc
Git commit: Unknown
Docker image tag: main-82eebfdc
Deployment mode: production

Runtime

Node version: v24.13.1
pnpm version: Unknown
OS: linux
Architecture: x64
Containerized: Unknown
Timezone: UTC

Services

Web reachable: Yes
API reachable: No
Controller heartbeat: Yes
Worker heartbeat: Yes
Preview proxy reachable: No
Database reachable: Yes
Redis reachable: Yes
Object storage reachable: Yes

Database

Provider: PostgreSQL
Migration status: Applied
Current migration: 34becbf8d22809969520807e513b6fa22e6c27ce979db50504e24ff86bcbb3bf
Pending migrations: Unknown
Database time: 2026-08-02 07:35:49.404793+00

Compute

Compute provider: roomote
Sandbox provider: roomote
Snapshot support: Unknown
Artifact storage writable: Yes

Integrations

Communications providers configured: slack
Source control providers enabled: gitea, github
MCP servers configured: 0

Configuration Warnings

Missing required env vars: None detected
Suspicious public URL/callback mismatch: Unknown
Webhook secret configured: No
Encryption key configured: Yes
Default credentials detected: Yes

Logs, screenshots, task IDs, or job IDs

Additional context

No response

[roomote-community]

I've analyzed this issue and here's my proposed implementation plan:

1. Remove the Roomote Cloud-only forced-enable behavior from isAnonymousAnalyticsEnabledFromMetadata in packages/feature-flags/src/index.ts, so the existing deployment metadata setting controls anonymous Roomote telemetry consistently in both cloud and self-hosted deployments.
2. Update apps/web/src/trpc/commands/misc-settings/index.ts so setAnonymousAnalyticsCommand persists the administrator's selected value in cloud mode instead of coercing it to true, while retaining the current opt-out default when no value has been stored.
3. Update apps/web/src/components/settings/MiscSettings.tsx to render the existing Privacy / Anonymous analytics switch for cloud deployments as well as self-hosted deployments. The switch should continue to control the anonymous Ping/page-view telemetry path; the separate consent-gated cloud PostHog/Intercom integration should remain outside this setting's scope.
4. Adjust the auth and telemetry call sites (apps/web/src/lib/server/auth-context.ts and packages/telemetry/src/server/index.ts) to use the unified metadata result, ensuring a cloud administrator's opt-out stops both browser page-view tracking and server-side anonymous event delivery.
5. Expand tests around the feature-flag evaluator and misc settings UI/command behavior to cover a cloud deployment loading the switch, persisting false, and returning analytics as disabled. Retain coverage that an absent setting defaults to enabled.

The missing section is currently intentional code behavior introduced with the cloud analytics work: cloud mode hides the UI, forces the evaluator to true, and ignores a submitted false. The recommended fix therefore requires the maintainers to approve changing that cloud policy, rather than only unhiding the switch. Keeping the existing switch scoped to anonymous Roomote telemetry avoids conflating it with the cloud cookie-consent flow.

Please tag @roomote if you'd like me to implement this, or reply with feedback on the plan.

[daniel-lxs]

@roomote do it

[roomote-community]

I saw the mention, but I need your GitHub account linked to Roomote before issue and PR comments can start work here. Link it from Settings -> Linked Accounts and then mention me again.

[fdev23408]

@daniel-lxs i dont think it worked. I checked today and do not see the toggle in the admin