Love
Open webui over Tailscale
Works...but
Privacy policy says no analytics. Code does
PRIVACY_POLICY.md, last updated 17 Dec 2025, says Ronas IT does not collect usage analytics or telemetry, and does not collect crash reports. The public source at github.com/RonasIT/open-webui-react-native does both in production.
On launch, analyticsService.init() starts Amplitude (EU). Tracking options turn on IP address, device model, OS name and version, platform, language, and app version. After you log in, the app sets Amplitude’s user id to your Open WebUI profile id and stores your OWUI version as a user property. It then sends events: new_chat_created, message_sent (with modelId), generate_image_used, dictation_mode_used, follow_up_used, and new_folder_created.
Sentry.init is enabled whenever the build is not in DEV, so production sends crash reports too. I did not see chat text, prompts, or your server URL in those analytics events. That part of the policy looks right. The “we collect no analytics and no crash reports” part is not.
There is no in-app opt-out. The project is GPLv3, so anyone can open the repo and check. Until the listing and the policy match the binary, I would not install this on a phone I care about.
Response from developer
Thank you — this was a fair and very precise report, and you were right. The policy did not match the binary. Here is what changed, as of version 1.12.1: • Amplitude has been removed entirely. No analytics SDK ships in the app any more — no user id, no device or IP-level properties, no message_sent, new_chat_created, or any other event. The dependency is gone from the project, not just disabled. • Sentry crash reporting is still there, and the privacy policy now says so plainly instead of claiming otherwise. It sends crash and error messages with stack traces, plus diagnostics for failed requests to your Open WebUI server: HTTP status, method and request path. Your server's domain/host is stripped and never sent, request/response bodies are truncated, and fields that could carry conversation text (content, message, text, prompt) are redacted. Your user id is no longer attached to bug reports. • The privacy policy has been rewritten (last updated 11 Sep 2026). The "no analytics" claim is now accurate, and crash reporting is disclosed in its own section rather than denied. We still do not operate any backend: your chats go only to the Open WebUI server you configure. The commits are public in github.com/RonasIT/open-webui-react-native, so you can verify all of this rather than take our word for it. An in-app opt-out for crash reporting is on our list. If you have any further questions or spot anything else that doesn't line up, please write to us directly at openmobileui@ronasit.com — we'd genuinely like to hear from you. Thanks again for taking the time to read the source and write this up — it made the app better. — Ronas IT
Doesn’t work at all!
Response from developer
Sorry to hear that — we'd like to get you connected. The app talks to your server only through the Open WebUI API, so it needs the instance root URL with the scheme and no extra path — a local address works fine too (e.g. http://192.168.1.10:3000 or https://chat.example.com). Could you tell us which Open WebUI version your server runs? Send us the details via Settings → Report a bug in the app or by email to openmobileui@ronasit.com, and we'll help you sort it out.
