Mango9 Privacy Policy
Effective date: July 26, 2026 | Last updated: November 16, 2026
Mango9, Inc. (“Mango9,” “we,” “us,” or “our”) provides software-building, application hosting, cloud communications, customer relationship management, messaging, provisioning, and related services. These Services include Mango9 Builder Studio, the Mango9 Builder iPhone and iPad applications, the EPhonix iOS and Android applications, Mango9 websites, Mango9 Marketing OS, the Mango9 Click to Call / Text Chrome extension, and associated cloud services. This Privacy Policy explains what information we collect, how we use and disclose it, how long we retain it, and the choices available to users.
This Privacy Policy applies to the Mango9 Builder mobile application, the Mango9 Marketing OS mobile application, the EPhonix iOS and Android applications, the Mango9 Click to Call / Text Chrome extension, Mango9 websites, Mango9 CRM services, and the communications services connected to them. When a business customer provides the Services to its employees, agents, clients, or other users, that business may control the applicable account and CRM data. In that situation, Mango9 processes the data on the business customer's behalf, and users should also review their organization's privacy notices and policies.
EPhonix mobile application data practices
These disclosures apply to EPhonix for iOS and Android. EPhonix connects your supported business account to calling, messaging, contacts, CRM, and optional Assistant AI features. Available features depend on your account, organization, and connected services. The other applicable provisions of this Privacy Policy continue to apply.
Account and connected workspace
We process the account information needed to sign you in and provide your connected services, including your name, email address, account and user identifiers, phone numbers or extension, and device or installation identifiers. EPhonix stores account credentials or access tokens, preferences, and cached workspace information on your device to support signed-in use and service recovery.
Your organization may control your business account and the CRM records available to it. Depending on the features you use, these records can include contact names, phone numbers, email and postal addresses, leads, appointments, events, tasks, notes, and conversation history. Your organization's authorized users may have access to shared business records under its permissions and policies.
Device contacts and permissions
With your permission, EPhonix reads the device contacts you allow so it can display names and photos and help you call or message people. It does not automatically upload your entire device address book into the CRM. Contact information is transmitted when needed for an action you choose, such as calling, messaging, sharing a contact, or saving information to your connected workspace.
The microphone is used for calls, voice features, and recordings you initiate. Camera access is used when you choose to capture a photo or video. Photos and file access allow you to select, send, or save media and documents. You can manage these permissions in your device settings; refusing a permission may prevent the associated feature from working.
Calls, messages, and recordings
To provide communications, we and your connected service providers process caller and recipient numbers, call identifiers, timing, duration and outcome, call audio, messages, and attachments as applicable. This includes supported SMS/MMS, team and group conversations, connected social conversations, and live chat.
Messages, attachments, voicemail, call history, and recordings may be stored by your connected business services and made available to authorized account users. Recording availability depends on your account and configuration. You are responsible for obtaining any required permission or consent before recording or sharing another person's communications.
Optional SIP logging saves technical call-signaling information on the device for troubleshooting. Such logs may contain phone numbers, account or network identifiers, timestamps, and signaling details. Exporting or sharing a log sends it to the destination you choose. Turning SIP logging off removes the app's stored SIP-log files; it does not recall copies you previously exported or shared.
Notifications
We register device notification identifiers with Mango9 and Apple Push Notification service or Google's Firebase Cloud Messaging, as applicable. Notifications may include caller information, message previews, conversation identifiers, voicemail or missed-call information, and details of CRM activity such as leads, appointments, events, and tasks. This information supports notification delivery and opening the relevant item when you tap it.
Notification previews may be visible on your lock screen or to other people who can see your device. You can control notification permission and preview visibility in device settings and use the notification options available in EPhonix.
Assistant AI, AI requests, and file uploads
When you choose to use Assistant AI, Mango9 or EPhonix sends your messages, attached files, conversation history and relevant account or CRM information to the AI service configured by your organization to answer requests and assist with CRM tasks. Depending on your configuration, this may use OpenRouter with OpenAI or DeepInfra (DeepSeek), or your own supported ChatGPT account through OpenAI Codex or Claude account through Anthropic Claude Code. For connected-computer replies, this information also passes through your authorized computer running the selected tool. Voice sessions share microphone audio, transcripts and conversation context with Google Gemini. Provider availability and account limits apply. The app asks for your consent before AI sharing, and you can revoke it in AI privacy settings. Requests already sent may still complete. Review AI replies and proposed changes before relying on or applying them.
Only the services needed for your configured route receive the information for that request; not every request is sent to every listed provider.
Files you select for Assistant AI are transferred to your account's services and connected storage, including Wasabi object storage where configured. Uploaded files, filenames, file types and sizes, previews, and conversation associations may be retained to make attachments available in your Assistant AI conversation and for later actions you request.
Uploading a large video or other file does not, by itself, publish it to social media or request AI analysis of its contents. A later request may use the uploaded file for a supported workflow, subject to that feature's permissions and confirmations. You can turn off AI sharing in AI privacy settings; this prevents new AI requests but does not automatically delete earlier conversations or uploads.
Reports and personal blocking
When you report a message or Assistant AI reply, we receive the content and context included in your report, your reason, and relevant account or conversation identifiers so our support team can investigate. Reports are routed for review at info@mango9.com. Do not include passwords or verification codes in a report.
Personal blocking applies to the signed-in user's experience and associated alerts. It does not delete shared CRM history or block a sender on behalf of coworkers. Your organization may retain the underlying business records.
Service providers and purposes
We use this information to provide account access, communications, notifications, CRM and Assistant AI features, storage, customer support, and service security and reliability. Depending on the selected features, information is processed by Mango9, your organization's authorized services and users, communications providers, hosting and storage providers, Apple or Google notification services, and the AI services described above. Recipients and destinations you select receive the communications or files you send to them.
EPhonix does not use its contacts, communications, or Assistant AI content to provide third-party advertising or cross-app advertising tracking. The service-wide disclosure and international-processing provisions in this Privacy Policy also apply.
Retention and account controls
Cached information and preferences may remain on your device to support the app. Server-side business records, messages, recordings, uploads, and reports are retained according to the applicable account configuration, service purpose, agreements, and legal obligations. There is no single retention period that applies to every organization's connected workspace.
Signing out, removing an account from EPhonix, or uninstalling the app does not automatically delete the underlying service account, your organization's CRM records, recipients' copies, or files you saved or shared elsewhere. Changing device permissions or turning off AI sharing also does not delete information already submitted.
Data access and deletion requests
To request access to or deletion of EPhonix-related personal data, email privacy@mango9.com with the subject “EPhonix data request.” Include the email address associated with your account, your organization or workspace, and whether you are requesting deletion of specific data or closure of your service account. Do not send your password, verification codes, or account tokens.
We may need to verify your identity and authority to make the request. For an organization-managed account, contact your administrator as well; Mango9 may need the organization's instructions before deleting records it controls.
Requests may cover account/profile information, messages and attachments, call records or recordings, Assistant AI conversations and uploads, and support reports associated with you. Deletion is subject to the applicable rights and obligations for those records. Some information may need to be retained for legal, accounting, security, fraud-prevention, or dispute-resolution purposes, or because it forms part of another party's authorized business records. Where information must be retained, we will explain the applicable reason and retention period in responding to the request. Copies held by recipients or other independent services are subject to their own controls and policies.
These disclosures apply to the Mango9 Chrome extension, version 2.2.0 and later. The extension lets you use your Mango9 account to call or text phone numbers on web pages. The service-wide sharing, retention, security, and privacy-rights provisions below also apply, as do your organization's policies for its communications and CRM records.
Account and sign-in
When you sign in, the extension sends your username or email, password or email code, and a browser installation identifier over HTTPS to Mango9 provisioning. Provisioning locates and authenticates your account on its home CRM. Central-linked accounts are verified through Mango9 Central. The extension does not save your password or email code.
Access and refresh tokens, your account label, CRM address, phone extension, and preferences are saved in this browser so you can stay signed in across browser restarts. Credential storage is restricted to trusted extension contexts. Page scripts are not given these credentials. The extension periodically renews its own session.
Phone numbers on web pages
The extension reads page text locally to recognize phone numbers and add call/text controls, including on authenticated websites and in frames. It does not upload entire pages, browsing history, or a list of detected numbers. Your excluded-site preferences are stored locally.
When you use a number's controls, the selected number is sent to your Mango9 account for the requested call, message, or contact/history lookup. The SMS panel displays relevant CRM contact details and recent messages within the page you are using. The panel is part of that page, so use it on websites appropriate for your business communications.
Calls, texts, and optional media
Calling sends the selected destination, caller ID, and call-control requests to your account's CRM and PBX. Your connected Mango9 app or IP phone carries the call. Call identifiers, numbers, timestamps, and state are kept locally for call controls and history and are processed by the communications service.
Texting sends your chosen sender number, recipient number, message, and any attachments you choose to your account's messaging service. File uploads use service-generated upload addresses. Voice-message and voicemail-recording features request microphone access when you start recording. Recordings and files are transmitted when you send or save them. Call recording, when selected and available for your account, is performed by your PBX.
Notifications and lookup links
The extension registers a push identifier with Google's Chrome push service and Mango9. Push messages can contain call state, caller numbers, or incoming SMS content so Chrome can display notifications. Notification context is held in browser session storage.
Using the optional lookup action opens the URL configured in Settings with the selected phone number. Its default is Google Search; you can change it to your CRM. That selected lookup provider receives the number when you use this action.
Who processes the information
Information needed for these actions is processed by Mango9 provisioning, authentication, your organization's CRM/PBX and authorized account users, and the communications and hosting providers used by your account, including Telnyx for applicable messaging services and Google for Chrome push notifications. Your chosen call/message recipients receive the communications you send. A configured lookup provider receives numbers you ask it to look up.
The extension contains no advertising, analytics, or data-sale integration. It uses information for sign-in, calling, messaging, notifications, and the related controls described here. It does not use information for advertising profiles, creditworthiness, or lending decisions. Service-level disclosures and legally required sharing are described elsewhere in this Privacy Policy.
Retention and controls
Signing out clears this browser's login credentials and call history and revokes its session when the service is reachable. It does not sign out your mobile app. Changing accounts clears local call/history state. Uninstalling removes the extension's local storage. A failed network connection can prevent server-side revocation until a token expires or the session is revoked by the service.
Signing out or uninstalling does not delete CRM messages, call records, or recordings held by your organization or its communications providers. Their retention follows your account configuration, applicable agreements, legal requirements, and this Privacy Policy. Contact your account administrator or Mango9 for access or deletion requests.
You can disable call/text detection, exclude websites, adjust incoming notifications, or change the lookup URL in extension Settings. Chrome also lets you restrict the extension's website access and manage microphone and notification permissions.
For privacy questions or requests, contact privacy@mango9.com. For extension support, contact support@mango9.com.
Last updated: November 16, 2026