Skip to content
Narzan
The appMessenger moduleConnectBetaFAQ

NARZAN · LAVAL LLC

Privacy Policy

MessagingOn your devicePermissionsSharingData removalContact

Last updated: October 28, 2026

Narzan is a messenger client distributed by Laval LLC. It connects to a compatible ProcessWire Messenger website that you choose. The website operator manages your account, message storage, permissions and retention. This policy describes the Narzan client; the connected website and its identity provider also have their own policies.

Information used to provide messaging

Narzan communicates with your chosen website over HTTPS. This includes your account identifier, username and display name; your site contact book and conversation requests; messages and sent/read timestamps; presence settings; and photos, voice recordings or files you explicitly send. Your device connection name is used to identify an authorized session. The website and identity provider receive network connection information such as your IP address and may retain access and security logs under their own policies.

Account sign-in takes place in the system browser. Narzan receives a limited session after your approval, rather than your website password. Narzan does not operate a separate central messaging service. Messages and attachments are stored by the connected website and delivered to the participants. HTTPS protects transmission; this is not end-to-end encryption.

Information on your device

Session credentials use platform-protected storage. The app stores language, appearance and notification preferences. A profile photo and custom wallpaper remain on the device unless you explicitly share a profile photo in a conversation. Profile-photo sharing sends a resized JPEG through the connected website; the exported copy does not include the original EXIF/GPS metadata. Received profile-photo copies may be retained locally for display.

Narzan can keep a private, account-scoped cache of API-confirmed message history on your device for up to seven days, limited to 30 conversations and 100 messages per conversation. Text and reply drafts use a separate encrypted, device-only store with a seven-day expiry. Pending text and selected photo/file/voice attachments use a separate encrypted outbox with a 24-hour expiry and bounded capacity; this is not the evictable cache. Restoring the app does not send them automatically. Optional automatic retry requires a separate per-connection choice and runs only while the app is in the foreground. You can remove pending sends separately in Data and Storage. Downloaded media and temporary files share the storage limit you choose in Settings → Data and Storage (50, 200, 500 or 1,024 MB; 200 MB by default). Old cache files are removed as space is needed. You can clear history, downloaded media and temporary files separately. Local call history and optional unsent ratings are limited to seven days and 200 entries. You can keep up to five separate website accounts on the device. Credentials, drafts, queued sends, history, AI settings and notifications are scoped to their account. Signing out or removing one connection clears its corresponding private stores; it does not delete another connection, your website account or messages stored on the website.

Permissions and optional external actions

Microphone access is used when you start a voice recording or participate in an audio call. A recording can continue while the app is backgrounded, with the Android microphone notification, for up to two minutes. You can stop, cancel or explicitly send it. Gallery and file selection use native pickers. Narzan does not upload your entire photo library or read your device address book.

On compatible websites, optional ordinary message notifications can use APNs or FCM while the app is closed, independently of experimental call notifications. Your connected website and its configured push provider process registration tokens, routing identifiers and the notification payload needed to deliver and display the notification. Availability and contents depend on the site configuration and your notification permissions and preferences. Foreground refresh remains available. If you enable experimental calls on a compatible website, Apple Push Notification service (APNs) or Firebase Cloud Messaging (FCM) can deliver incoming-call invitations while the app is closed. Push registration tokens, device/platform identifiers, call identifiers and the information needed to display an incoming caller are processed by your connected website and its configured push gateway/provider. Microphone use starts only when you place or accept a call; an active call can continue in the background. Call signaling is handled by your connected website. WebRTC audio travels between participants where possible and may pass through the website's configured TURN relay; participants, network providers and relay operators may receive connection information such as IP addresses. Narzan does not record call audio. Calls are experimental and may fail or be interrupted.

After a connected call, you may optionally rate it. Ratings remain local unless you explicitly agree to send them to the connected website. A submitted survey contains stars and selected issue categories, plus the call/session identifiers needed to associate it with that call; it contains no audio, message text or free-text diagnostics. Messenger's current feedback retention is 30 days; contact your website operator about its policy and data removal.

Opening a link or requesting its rich preview contacts that link's website, which receives normal network information. Rich previews are requested only after your action and do not include your Messenger credentials. Opening a file in another app shares that selected file at your request.

Optional AI assistant, translation and transcription

AI is optional. You can choose OpenRouter or an HTTPS OpenAI-compatible API service and enter your own key and separate models for chat, translation and transcription. The key is stored in platform-protected, account-scoped device storage and is sent only to the API endpoint you configure for authorized requests, not to your Messenger website. Changing the endpoint requires entering a key for that service. Your chosen API service and its selected model provider process the prompts and content you explicitly submit. This may include text you write to the assistant, selected chat messages for translation, or a selected voice-message file for transcription. No entire website history is sent automatically, and new messages are not automatically translated. Translation and transcription show a confirmation before transmitting the selected material; assistant messages are sent only when you press Send.

Your chosen API service and model provider have their own privacy, retention and pricing terms; check them before entering an endpoint or sending content. OpenRouter requests prefer providers that disallow data collection, but this preference does not guarantee zero retention or end-to-end encryption and does not apply to a custom API service. Requests may incur charges on your provider account. Cancelling a request, removing the key or deleting a website message cannot recall content already transmitted to the provider. AI results are untrusted and may be inaccurate; they do not automatically change your website messages. Local assistant history is bounded and clears on account change/sign-out or manual clearing. Remove the AI key in Settings to delete the saved credential. See OpenRouter privacy information.

Group conversations and shared activity

Where supported by your connected website, group membership, roles, group photos, messages, mentions, shared pins, polls and events are processed by that website and disclosed to the authorized group members according to its permissions. Joining an invitation requires your confirmation. Account sessions, blocks, deletion and retention remain subject to the site operator. These are not public broadcasts merely because the client supports group conversations.

Advertising, analytics and sharing

This build includes no advertising, advertising identifiers, cross-app tracking or third-party analytics SDK. Narzan does not sell personal data. Your chosen website processes messaging data and your recipients receive what you send. Google Play may process distribution, diagnostic and testing information under Google's policies. If you contact support, we receive the information you choose to send; do not send passwords, session tokens or private conversations that are not needed for your request.

Optional quality diagnostics

Starting with build 15, Narzan can send selected diagnostic metadata to your connected website when that website supports this feature. Automatic collection is enabled by default for a supported account. You can turn it off in Settings → Privacy and security → Send diagnostics.

Diagnostics include selected screen and button actions, delivery outcomes, call connection and reconnection states, and network-quality measurements such as latency, jitter and packet loss. Events can be associated with your account and internal chat or call identifiers so that the website operator can investigate related failures. These are account-associated metadata, not anonymous statistics. Collection does not include message text, typed input, attachment contents, microphone recordings, passwords, authentication tokens or screen recordings.

The data goes to your chosen website, not a central Narzan analytics service. Messenger diagnostics are encrypted at rest, bounded by quotas and subject to seven-day retention with scheduled cleanup. The device queue is encrypted, limited in size and expires after 24 hours. Disabling collection clears unsent data and cancels pending uploads; packets already accepted by the website remain subject to retention. Existing voluntary call-rating surveys retain their own explicit submission consent. The connected website operator is responsible for its configuration, access controls and privacy policy.

Retention, removal and your choices

You can clear temporary media, remove a local profile photo, change permissions and sign out. Available message deletion and auto-delete controls follow the connected website's policy. Copies downloaded by recipients and operator backups may remain after message deletion. For website account deletion, exports or server data removal, contact that website's operator. Narzan support can help identify the appropriate operator but cannot erase an independently operated website's database.

To request help with Narzan-related data removal, email messenger@narzan.com with the subject “Narzan data removal”, your connected website address and the account username. Do not include your password. Verification may be required before any account-related action. Support correspondence is retained only as needed to resolve the request and meet applicable legal obligations.

Contact and changes

For privacy questions contact Narzan support at messenger@narzan.com. Material changes will be reflected on this page with an updated date. The app's connected-website policy remains separately applicable.

Narzan

Your conversations.
A little closer.

Narzan

  • The app
  • Why Narzan
  • Connect your website
  • Beta invitations

For site owners

  • Messenger module
  • Integration guide
  • Discover ProcessWire

Help

  • Common questions
  • Contact support

Legal

  • Privacy policy
  • Terms of use
  • Account & data removal
Need a hand? messenger@narzan.com

Built for websites running ProcessWire Messenger.

© 2026 Narzan · Laval LLC

Made with love in Philadelphia.

Appearance
Back to top

Narzan is an independently developed messaging app. ProcessWire is a separate open-source CMS project.