PrivacyTermsCookiesDPAData deletion

MAJ Leads is operated by Majosphere FZE LLC, CWS-1V-229025, 26th Floor, Amber Gem Tower, Ajman, United Arab Emirates. hello@majleads.com

PrivacyTermsCookiesDPAData deletion

Data Processing Addendum

Last updated: 6 November 2026

This Data Processing Addendum (“DPA”) forms part of the agreement between Majosphere FZE LLC, which operates MAJ Leads (“Processor”), and each customer that uses MAJ Leads at app.majleads.com (“Controller”). It applies to personal data the Controller puts into, or collects through, the Service. Terms not defined here have the meanings in the Terms of Service and Privacy Policy.

This DPA is intended to meet the requirements of the UAE Personal Data Protection Law (Federal Decree-Law No. 45 of 2021, “UAE PDPL”) and, where the Controller processes data of people in the EU/EEA, the EU General Data Protection Regulation (“GDPR”).

1. Roles of the parties

  • Controller: the customer. It decides which leads and contacts to collect, how and when to contact them, and is responsible for having a lawful basis to do so.
  • Processor: Majosphere FZE LLC. It processes personal data only on the Controller’s documented instructions, which include the settings the Controller chooses in the Service.
  • Sub-processors: providers the Processor uses to deliver the Service, listed in section 6.

2. Processing scope

Subject-matterLead management: capturing leads from forms, ads, email, WhatsApp and connected tools; alerting the Controller’s team; follow-up tasks; messages and newsletters the Controller sends; reporting.
DurationFor the term of the subscription, and afterwards only as long as needed to export or delete the data under section 8.
Nature of processingCollection, storage, organisation, retrieval, transmission (including sending messages and newsletters the Controller sets up), reporting and deletion. If the Controller switches on Ask MAJ, this also includes sending the limited data described in section 6 to an AI model provider to answer questions and prepare changes that a user confirms. If the Controller’s users contact support, this also includes keeping their messages and, once the support assistant is switched on, sending the masked text to an AI model provider to answer and sort them, as described in section 6. The Controller should tell its users not to paste lead details into support messages.
PurposeProviding the Service to the Controller, keeping it secure and supporting the Controller when it asks for help.
Types of personal dataNames, phone numbers, email addresses, lead source and campaign details, messages, notes, follow-up history, newsletter consent and engagement records, and details of the Controller’s users.
Categories of data subjectsThe Controller’s leads, customers and newsletter subscribers, and the Controller’s staff who use the Service.

The Controller should not upload special categories of data (such as health, religious or biometric data) unless it is needed and lawful.

3. Processor obligations

The Processor will:

  • Process personal data only on the Controller’s documented instructions, unless the law requires otherwise (in which case it will tell the Controller first, unless the law forbids that).
  • Ensure everyone authorised to process the data is bound by confidentiality.
  • Apply the security measures in section 5.
  • Give notice before adding or replacing a sub-processor, as set out in section 6.
  • Help the Controller answer requests from data subjects (access, correction, deletion, portability, objection) within 30 days of the Controller passing them on.
  • Help the Controller with security, breach notification and impact assessments, as far as is reasonable.
  • Delete or return personal data at the end of the subscription, under section 8.
  • Make available the information reasonably needed to show compliance with this DPA, and allow an audit by the Controller or its auditor on 30 days’ written notice, no more than once a year, at the Controller’s cost.

4. Controller obligations

The Controller will:

  • Make sure its instructions, and its use of the Service, comply with applicable law.
  • Have a lawful basis, such as consent, for collecting each lead’s data and for contacting them by phone, WhatsApp, SMS or email.
  • Send newsletters only to people who agreed to receive them, and respect unsubscribes.
  • Follow Meta’s WhatsApp Business policies for messages sent from its connected number, and the UAE’s telemarketing rules (including the Do Not Call Registry) where they apply.
  • Tell the Processor promptly if it believes an instruction would breach the UAE PDPL or the GDPR.

5. Security measures

  • Encryption in transit: all traffic between users, the Service and sub-processors uses TLS 1.2 or higher.
  • Encryption at rest: the database and file storage are encrypted at rest by their providers.
  • Separation: database access rules keep each workspace’s data separate, and roles inside a workspace limit what each user can see and change.
  • Staff access: limited to authorised personnel who need it to run and support the Service.
  • Audit logging: important actions are logged with time and actor, and kept for 24 months.
  • Integrity: webhooks from connected services are verified by signature, and public forms are protected by bot checks.
  • Error monitoring: Sentry session replays mask all text and block all media, so personal data does not appear in them.
  • Updates: dependencies are reviewed regularly and critical security fixes are applied promptly.

6. Sub-processors

The Controller authorises the sub-processors below. The Processor will give at least 14 days’ notice before adding or replacing one, by updating this page and emailing workspace owners about material changes. The Controller may object in writing within those 14 days. If the objection cannot be resolved, the Controller may cancel and receive a refund of fees paid for the unused period. Each sub-processor is bound by data protection terms no less protective than this DPA, and the Processor remains responsible for them.

Sub-processorPurposeLocation
Supabase (PostgreSQL)Managed database and sign-in. Stores accounts, workspaces, leads, follow-ups, messages, newsletter contacts, audit logs and billing records.ap-south-1 (Mumbai, India) — AWS infrastructure
VercelHosts the MAJ Leads app and runs its server functions.Mumbai, India (server functions); global edge network for static files
Cloudflare (R2 and Turnstile)R2 stores images you upload for newsletters. Turnstile checks that sign-ups and public forms come from people, not bots.Cloudflare global network
ResendSends account emails (sign-up confirmation, password reset, alerts) and the newsletters you send, and receives leads you forward by email.United States
StripeTakes card payments for subscriptions. Card numbers go directly to Stripe and never reach MAJ Leads.United States and other Stripe locations
Google (Gemini API)AI model that sorts messages people send to MAJ Leads' own sales WhatsApp and drafts replies. Customer workspace leads are not sent to it.United States (Google infrastructure)
Anthropic (Claude API)Backup AI model for messages people send to MAJ Leads' own sales WhatsApp, used only when the primary model is unavailable. It is also the AI model behind Ask MAJ, the optional assistant that answers questions about your leads and prepares changes for you to confirm. Ask MAJ sends data to it only for workspaces whose owner has switched Ask MAJ on. Lead phone numbers, email addresses and full names are never sent. Once the support assistant and ticket sorting are switched on (after notice to customers), it is also the AI model behind them, reading the masked text of support messages from people who use Help or email support. Support never sends screenshots, workspace data or leads.United States (Anthropic infrastructure)
SentryApplication error and performance monitoring. Session replay is configured with all text masked and all media blocked.United States (Sentry infrastructure)
PostHog Inc. (EU cloud)Product analytics: which screens and actions are used, so we can fix what is slow or confusing. Nothing is stored on your device. Workspace owners' sign-up and onboarding screens and their first 7 days are also recorded with all text masked.Frankfurt, Germany (PostHog EU cloud)
Browser push services (Apple, Google, Mozilla)Deliver the lead alerts your team switches on as phone or desktop notifications.Depends on the device's browser vendor (mainly United States)
Green APIWhatsApp gateway MAJ Leads uses for its own service notices to customers, where no WhatsApp Business account is connected.Germany (Green API infrastructure)

Ask MAJ. Anthropic (Claude API) is listed above. It also processes the Controller’s personal data for Ask MAJ, the optional AI assistant, but only for a workspace whose owner has switched Ask MAJ on in Settings, Business. Switching it on is the Controller’s documented instruction for that processing, and switching it off stops it. The data sent is limited to the question typed (with emails, phone numbers, Emirates ID numbers and IBANs masked), first names with last initials, stage, source, timings and outcome codes, and, in lead summaries, intake answers and message text with personal identifiers masked. Phone numbers, email addresses and full names of leads are never sent. The Processor does not store the question or answer text; it keeps a usage log of metadata only. The Processor gives the notice described in this section for any later change to the data its sub-processors receive.

Support. Once the support assistant is switched on, Anthropic (Claude API) will also receive the masked text of support messages that the Controller’s users send through Help or by email, to answer how-to questions and to sort the message. The support assistant has no access to the Controller’s workspace, and the Processor does not intend support messages to contain lead data. If a user pastes some, emails, phone numbers, Emirates ID numbers and bank account numbers are masked and the rest is sent as typed. Screenshots are never sent to an AI model. The Processor keeps message text for 180 days after a report is closed and screenshots for 30 days, and Anthropic deletes its copy within 30 days of receipt unless the law or the enforcement of its usage policy requires longer. This paragraph is the notice described in this section for that change. The support assistant is switched on only after the Processor has emailed the Controller’s workspace owner about it and 14 days have passed. The Controller may object in writing within those 14 days, and the cancellation and refund terms above then apply.

Services the Controller connects itself (such as its WhatsApp Business account, Meta, Google Ads, Shopify or HubSpot) are not sub-processors. They act under the Controller’s own agreement with each provider, and data flows to them only on the Controller’s instruction.

7. International data transfers

  • India (Supabase database and Vercel server functions, Mumbai): the transfer relies on Supabase’s and Vercel’s data processing terms, which include Standard Contractual Clauses (SCCs).
  • United States and other countries (Resend, Stripe, Sentry, browser push services, Google and Anthropic for messages sent to MAJ Leads itself, Anthropic for Ask MAJ in workspaces that have switched it on, and, once the support assistant is switched on, Anthropic for support messages): each relies on the provider’s data processing terms and SCCs where available.
  • European Union (PostHog, product analytics, Frankfurt): no lead data is sent to PostHog. The EU is treated as providing adequate protection, and PostHog’s data processing terms apply.
  • For UAE PDPL purposes the Processor relies on these contractual safeguards as appropriate safeguards for transfers out of the UAE.

Copies of the relevant terms are available on request to hello@majleads.com.

8. Return and deletion

  • The Controller can delete leads and contacts in the Service at any time.
  • When a subscription ends, the workspace is paused and its data kept so the Controller can resume or export it. On written request, or when the workspace is closed, the Processor deletes the Controller’s personal data within 30 days, except records the law requires it to keep (such as invoices).
  • Support reports for the workspace are deleted with it, within the same 30 days.
  • The Processor will confirm deletion in writing on request.

9. Personal data breaches

The Processor will notify the Controller without undue delay, and in any event within 72 hours of becoming aware of a personal data breach affecting the Controller’s data. The notice will describe, as far as known at the time:

  • What happened, including the categories and approximate number of people and records affected.
  • A contact point for more information.
  • The likely consequences.
  • The steps taken or proposed to deal with the breach and reduce its effects.

The Controller remains responsible for notifying the UAE Data Office, any other regulator and affected people where the law requires it.

10. Governing law and precedence

This DPA is governed by the laws of the Emirate of Ajman and the federal laws of the United Arab Emirates. Where this DPA and the Terms of Service conflict on data protection, this DPA prevails.

11. Contact

Data protection questions and requests: hello@majleads.com · Majosphere FZE LLC, CWS-1V-229025, 26th Floor, Amber Gem Tower, Ajman, United Arab Emirates.