Service Providers & Sub-processors: We work with the following third-party processors, each acting only on our instructions and only for the stated purpose: Clerk (authentication and user identity, hosted in the US), Convex (our primary application database, hosted in the US), Stripe (payment processing), Twilio (telephony and WhatsApp messaging infrastructure), and our voice AI provider (voice AI processing, including call audio, for the AI voice receptionist).
Analytics, Advertising & AI Processors: Meta (the WhatsApp Business Platform for messaging with your customers, and the Meta Pixel plus Conversions API for advertising, both only with your marketing consent and with your email and phone hashed before sending), Google (Google Analytics and Google Ads, only with your consent, and Google Gemini AI for knowledge-base features), PostHog (product analytics including session recording, only with your consent, hosted in the United States), Sentry (error monitoring), Anthropic, OpenAI, and OpenRouter (AI language processing that powers our reception and quality-assurance features), Pinecone (knowledge-base search index, hosted in the US), Resend (email delivery), and Upstash (infrastructure, including rate-limiting and caching).
Dashboard Support Chat (Jev): When you type a message into the support assistant (Jev) in your dashboard, the message, together with excerpts of our published Help content, is sent to OpenRouter and its model provider TypeSafe so that the model can decide which published answer fits. Jev does not write new answers; it only chooses from published Help content. Chats that do not become a support ticket are deleted after 30 days. A chat that becomes a support ticket is kept with that ticket.
Google Calendar Access & Use: For business appointment mirroring, if you connect Google Calendar, Mawidi uses your authorized event permissions to mirror appointments to the configured calendar when synchronization is enabled. This includes creating an event, updating it when the appointment changes, removing it when cancelled, and reading the mirrored event to check synchronization. A calendar-access check requests no event content. Mirrored events can contain the service, customer name, appointment times, booking reference, and assigned staff name; customer phone numbers and email addresses are not copied into these events. Events are visible according to your Google Calendar sharing settings.
Google Calendar Storage & Control: We store encrypted OAuth access and refresh tokens, granted permissions, token expiry, and connection details in Convex. Booking-linked calendar and event identifiers and synchronization status let us maintain the connection and avoid duplicate events. We use Google Calendar data for the calendar integration, not for advertising or training general-purpose AI models, and do not sell it. For business appointment mirroring, you can disconnect Google Calendar in Calendar & CRM Integrations, revoke access in your Google Account, and request deletion through privacy@mawidi.com. Service providers process connection data only to operate the integration as described in this policy.
Staff Demo Calendar Access & Use: The authorized Mawidi demo pipeline owner can connect a chosen Google account in Staff > Demo Requests (/staff/dashboard/demos), select a booking calendar and choose calendars whose busy times block demo availability. This flow requests openid and email to verify the connected account, calendar.calendarlist.readonly to list calendar choices, calendar.events.freebusy to check busy times, and calendar.events to create, read, update and cancel demo events with Google Meet links.
Staff Demo Event Data & Control: Demo events include attendee name and email, phone number, meeting time and duration, and may include business name, website and special requirements supplied for the booking. Google receives the attendee email to send invitations and updates; event information is shared according to the selected calendar's sharing settings and invitations. We store the verified Google account identity, encrypted OAuth tokens and saved calendar choices in Convex. The owner can disconnect a selected account under Staff > Demo Requests, revoke access in their Google Account, or request deletion through privacy@mawidi.com. Disconnecting prevents further use of that account and does not delete events already saved in Google Calendar.
Full Subprocessor Register: For the complete list of every processor with its purpose, the categories of data it processes, its region, and the safeguard we rely on, see our Subprocessor Register at /en/legal/subprocessors (Arabic: /ar/legal/subprocessors).
Facebook & Instagram Data: If you connect a Facebook Page or Instagram professional account, we access, via Meta's Graph API and with your explicit authorization, the messages sent to your Page/account (message content and the sender's Meta-assigned ID), your Page IDs, and connection metadata, solely to help you read, reply to, and manage customer conversations from your Mawidi dashboard. We never post as you without your action and never sell this data. You can disconnect at any time, and either you or a customer can request deletion of this data; see “Your Rights & Choices” and our data deletion endpoint at /api/webhooks/social/meta/data-deletion.
Business Transfers: In the event of merger, acquisition, or sale of assets, your information may be transferred. You will be notified via email and prominent website notice.
Legal Requirements: We may disclose information to comply with court orders or legal processes, enforce our Terms of Service, protect rights and safety of Mawidi and users.
B2B Context: Mawidi is a B2B platform. Your business customers' data is processed on your behalf. You remain the data controller for your customer data.
We Never Sell Your Data: We do not and will never sell your personal information to third parties or share data for third-party marketing without your consent.