Masar Inbox · Masar Next Company
Privacy Masar Inbox
Updated 27 October 2026
Who we are
Masar Next Company in Saudi Arabia operates Masar Inbox, a business communications application. Our monitored privacy and deletion contact is info@masarnext.com.
Accounts and company workspaces
Each company has a workspace and users with defined permissions. Platform administrators create companies and login accounts, set user limits and subscription dates, and suspend subscriptions. Subscription administration alone does not grant membership in a customer workspace or access to its conversations. Each business chooses who may use its data and remains responsible for its authorized use of channels and customer communications.
Information and purposes
We handle account information such as names, email addresses and authentication information, company records, memberships, permissions, subscription dates, sign-in records and administrative changes. We use this information to provide the service, control access, protect accounts and handle support requests.
When an authorized channel is enabled, we may process contact information, account identifiers and phone numbers, message and file content, timestamps, and delivery or read events, depending on the channel and feature used. This supports conversation display, routing and authorized user actions. We do not ask for a Meta password in an Inbox form; supported account connections use Meta's own window. Provider-dependent channels and features remain subject to activation, permissions and required approvals.
Browser storage retains sign-in state and preferences. Operational logs can include network addresses, request times and outcomes to run the service, investigate failures and prevent abuse. No external AI service or advertising analytics is enabled in this version. Evidence from authorized tests may be supplied to Meta for App Review with the information shown minimized. Personal test conversations are not automatically imported into customer or reviewer workspaces.
Providers and access
The platform uses Render to host the application in Singapore and Supabase for authentication and the database in Mumbai, India. Meta handles authorization, channel data and review evidence under its own terms. Naming the hosting regions does not mean that all support, operations or content delivery processing occurs exclusively there; these services can process some information in other countries.
Authorized personnel and service providers can have technical access needed to operate and support the service. We do not claim stored records are end-to-end encrypted against service operators. A previous WhatsApp test used a temporary Cloudflare route for test notifications; that route and its subscription were closed after the test.
Protection and retention
The application uses server and database access controls, separation between company workspaces and protections for authorization credentials. Suspending or expiring a subscription restricts authorized access through service controls; it does not delete stored records. Information already downloaded cannot be recalled from a recipient's device.
Records are retained to provide the service and handle requests and operational needs. A comprehensive automatic deletion schedule for all messages, logs and backups is not yet established. Deletion requests are handled manually after checking identity, authority and scope. Limited security records may need to remain, and any remaining scope will be explained when a request is handled.
Your requests
To request access, correction or deletion, email info@masarnext.com with the relevant account or workspace and your request. Do not send passwords or access tokens. See our deletion instructions for the required information and limits. A business controlling your conversation independently may also need to handle a request about its records.