# Priv Privacy Policy V0.9.2.2.1 **Document type:** Privacy / Public Policy Draft **Version:** 0.9.2 **Status:** Baseline Candidate / Legal Review Required **Language:** English **Product:** Chanora **Repo path:** `docs/privacy/privacy-policy.md` --- ## 1. Important Notice This is a draft privacy policy template for review. It must be reviewed by a qualified legal/privacy reviewer before public release or store submission. ## 2. Overview Chanora is a client application for connecting to compatible voice communication servers. Chanora is designed to operate primarily on the user's device. ## 3. Data Processed by the App Depending on how the user configures and uses the app, Chanora may process: - server address and port; - server password if provided by the user; - user nickname; - identity information needed for server connection; - channel names and server-provided names; - chat messages displayed in the app; - audio input and output during voice sessions; - local application settings; - audio device settings; - diagnostic information generated by the app. ## 4. Local Storage Chanora may store local settings, bookmarks, recent server information, audio preferences, and related configuration on the user's device. Sensitive secrets such as server passwords or identity secrets are intended to be stored using platform secure storage mechanisms where supported. ## 5. Diagnostics Chanora may allow the user to generate diagnostic bundles for troubleshooting. Diagnostic export is intended to be user-initiated. Diagnostic bundles should be redacted to avoid including passwords, identity secrets, and other sensitive information. Chanora should not automatically upload diagnostic bundles unless a future version explicitly introduces an opt-in upload feature and updates this policy. ## 6. Audio and Microphone Chanora uses microphone access to provide voice communication features. Audio is processed for voice communication and may include echo cancellation, automatic gain control, noise suppression, and high-pass filtering. Chanora should not record or persist voice audio unless a future feature explicitly states otherwise and receives user consent where required. ## 7. Permissions Chanora may request permissions required for voice communication, notifications, audio routing, local storage access, or platform-specific behavior. Permission requirements vary by platform. ## 8. Data Sharing This draft policy assumes: - Chanora does not sell user data. - Chanora does not automatically upload diagnostics. - Chanora does not include automatic telemetry unless later approved and documented. - User-initiated sharing of diagnostic bundles is controlled by the user. These assumptions must be confirmed before public release. ## 9. Third-Party Servers When the user connects to a compatible external server, the server may receive connection information, nickname, voice data, text messages, or other information necessary for communication. The operation of external servers is outside Chanora's control. ## 10. Third-Party Dependencies Chanora may use third-party software dependencies. The dependency and license list should be published or made available where required by applicable licenses. ## 11. Children's Privacy TBD by legal/privacy reviewer. ## 12. Regional Requirements TBD by legal/privacy reviewer. Public release may require region-specific privacy disclosures. ## 13. Contact TBD. ## 14. Change History | Version | Date | Description | |---|---|---| | 0.9.0 | 2026-05-14 | Initial privacy policy draft template; legal review required before public release. | ## Baseline Candidate 0.9.1 Update | Version | Date | Description | |---|---|---| | 0.9.1 | 2026-05-14 | Updated baseline after product decision closure: Apple App Store SDK gate uses Xcode 26+ and iOS 26 / iPadOS 26 SDK+ since 2026-04-28, platform baselines and decision traceability propagated across the document set. | ## Baseline Candidate 0.9.2 Update | Version | Date | Description | |---|---|---| | 0.9.2 | 2026-05-14 | Corrected Apple App Store Connect upload gate to 2026-04-28 and checked full-package naming, references, and coverage. | ## Desktop Push-to-Talk Privacy Addendum (Baseline Candidate 0.9.3) Per SysRS-302 / SRS-202 / DEC-027, the Chanora desktop PTT subsystem operates under the following privacy rule: - Chanora shall not log, persist, or transmit raw keyboard key codes, scan codes, virtual-key values, keysyms, or key-press timing sequences. - The user-initiated diagnostic export shall include only the detected PTT capability level (`L0Focused`, `L1GlobalShortcut`, `L2GlobalHoldToTalk`, `L3GlobalWithMouseButtons`, or the reserved `L4DeviceAware`), the active backend identifier (a fixed string per implementation, for example `"raw-input"`, `"event-tap"`, `"gnome-wayland-portal"`, `"focused"`), and the bound input class (`"keyboard"`, `"mouse-side-button"`). - The bound key value itself is never included in any diagnostic, even when the user invokes the export explicitly. - Whether Global PTT is available depends on the operating system, the user-granted permission set, the display server, and the available input backend. Where Global PTT cannot be honoured, Chanora falls back to Focused PTT and reports the fallback honestly through the UI capability badge. | Version | Date | Description | |---|---|---| | 0.9.3 | 2026-05-15 | Added desktop Push-to-Talk privacy addendum: raw key history is not recorded or exported; Global PTT is capability-dependent and the UI reflects actual runtime capability. |