Kanverse Blink
Privacy Policy
Effective: 15 August 2026
Kanverse Blink is designed for temporary private communication without a mandatory user account. This policy explains what information is handled when you use the app and how the current Blink service is designed to minimize retention.
Information you choose to provide
Blink may process a temporary display name, chat messages, photos, files, voice messages, room invitations, and call signaling data when you choose to use those features. Camera and microphone access is requested only when a feature you initiate needs it.
Encrypted room content
Message and media content is encrypted on the client before it is relayed through the Blink service. The relay stores encrypted packets temporarily so participants can receive them. In the current service configuration, encrypted relay packets are designed to expire after approximately one hour. Room and presence records are also cleaned up after rooms are closed or remain empty.
Local device data
Blink stores room credentials, encrypted local vault data, preferences, drafts, and related app state in your browser or installed PWA storage so the app can function. Blink provides controls to leave rooms, forget local room data, run privacy checks, and erase Blink data from the device.
Calls and network information
Blink Direct Call uses WebRTC. Establishing a WebRTC connection can involve STUN or TURN infrastructure and may expose network information such as IP addresses to the networking providers required to establish or relay the connection. Blink does not use carrier-call encryption for calls opened through your device's normal telephone service.
Anonymous feedback
If you voluntarily use the feedback feature, your feedback message is submitted through Netlify Forms. You do not need to provide your name or email. If you explicitly opt in to include basic diagnostics, the report may include the Blink version, browser/PWA status, and device user-agent. The feedback feature is designed not to include chat messages, room IDs, or encryption keys.
Service providers
Blink uses Netlify infrastructure for hosting, serverless functions, temporary relay/storage functions, and optional feedback submission. WebRTC connectivity may use third-party STUN or TURN infrastructure when required to establish a call.
Accounts, advertising, and sale of data
Blink does not require a mandatory Blink account for normal room use. The current app does not contain behavioral advertising and Kanverse does not sell Blink chat content or personal data to advertisers.
Your controls
You can leave or close rooms, remove local room entries, clear the local vault, and erase Blink data stored on your device. A room creator controls who is admitted to a room and can remove participants.
Changes
This policy may be updated when Blink's features or infrastructure change. The effective date above identifies the current version.
Contact
For privacy questions, use the feedback/contact option provided inside Kanverse Blink or the support contact shown on the Microsoft Store listing.