AI Lead Qualifier for Salesforce: Privacy Policy
Last updated: 28 October 2026
This policy covers AI Lead Qualifier for Salesforce ("the app"), a Salesforce package published by NextMark, Dubai, United Arab Emirates ("NextMark", "we"). It explains what happens to data when your organisation installs and uses the app. It does not cover NextMark's other products or websites, which have their own policies.
1. The short version
- The app runs entirely inside your own Salesforce org. Your leads, form answers, scores and settings are stored there, under your Salesforce security, and nowhere else.
- NextMark does not receive your leads or your customers' personal data. There is no NextMark server between your org and the services the app connects to.
- The app only sends data to the services you connect (Meta, Google Ads, your AI provider, your spam-protection provider), using your own accounts and keys, and only for the purposes described below.
2. Who is responsible for the data
Your organisation decides which leads to collect and which services to connect, so it is the controller of that data. Because NextMark never receives or processes it, NextMark is not a processor of your leads' personal data. You are responsible for having a lawful basis and giving any notices required by the laws that apply to you, for example on your website forms.
3. What the app does with data, inside your org
| Data | Where it comes from | What the app does |
|---|---|---|
| Leads and form answers | Your website forms, Facebook and Instagram lead ads you choose to import, other tools you connect | Stores them as Salesforce Leads and Lead Answers |
| AI score, tier and reason | Your AI provider | Stores them on the Lead |
| Ad details (campaign, ad set, ad names, ad text and image) | Meta or Google Ads | Stores one copy per ad, so a Lead keeps showing the ad it came from |
| Conversion events | Lead status and score changes | Stores a record of each conversion sent |
| Connection tokens and keys | You, when connecting a service | Stored encrypted in Salesforce Named Credentials. Nobody can read them back, including admins and NextMark |
| Logs | The app's own activity | Stored in your org for troubleshooting. They never contain email addresses, phone numbers or tokens, and old lines are deleted automatically |
4. What the app sends to other services
The app contacts a service only when you connect it, and only with the data that service needs:
- Meta (Facebook and Instagram): conversion events (Conversions API), with email and phone hashed (SHA-256) before they leave Salesforce, plus the Meta lead ID; requests to fetch your lead-ad leads, your ad and ad-account details and ad spend. Meta's own terms and privacy policy apply.
- Google Ads: click conversions, with email and phone hashed (SHA-256), plus the Google click ID; requests for your accounts, conversion actions, ad details and spend. Google's terms and privacy policy apply.
- Your AI provider (Anthropic Claude, OpenAI, or an OpenAI-compatible service you choose), with your own API key: the lead's source and form answers, and any Lead fields you choose, to score the lead. The lead's name, email, phone number and address are never sent to the AI. Your agreement with that provider governs its use of the data, including where it is processed.
- Spam protection and phone verification on website forms, only if you turn them on (Cloudflare Turnstile, Google reCAPTCHA, hCaptcha, RingCaptcha): the verification token from the visitor's browser, and for RingCaptcha the phone number being verified.
5. Website visitors
The form your website shows is served by your Salesforce Site. The embed script reads advertising parameters
from the page address (such as utm_source and gclid) and the Meta and Google advertising cookies already on
your site (_fbc, _fbp, _gcl_aw), and sends them with the form to your org so conversions can be credited
correctly. It sets no cookies of its own and sends nothing to NextMark. Tell your visitors about this in your own
website's privacy notice and cookie banner where the law requires it.
6. The sign-in page on nextmark.ae
Connecting Google Ads (and Meta, where used) passes through one fixed page,
https://salesforce.nextmark.ae/oauth/callback.html, because the providers require a fixed return address. The
page runs only in your browser: it checks that the sign-in started from a Salesforce org and sends you straight
back there with the one-time code. It stores nothing, uses no cookies or analytics, and sends nothing to NextMark.
Like any website, its hosting provider may record that the page was visited. The one-time code in the address
expires within minutes and can only be used by your org.
7. What NextMark receives
When an organisation installs the app, Salesforce gives NextMark the installing organisation's name, Salesforce org ID, edition, and the name and email of the installing user, through Salesforce's License Management App. We use this only to manage the app (licences, compatibility, security notices) and to answer support requests. We don't sell it or use it for advertising.
If you contact us for support, we see what you choose to share with us. We never ask for your passwords, tokens or keys, and we only access your org if you grant us temporary access yourself, for a support case you opened.
8. Security
Tokens and keys are encrypted by Salesforce and can't be read back. The app follows Salesforce's sharing and field security, and it was built for, and submitted to, Salesforce's AppExchange security review. Report security issues to us at the address below.
9. Removing the app and your data
Uninstalling the app removes its data from your org, following Salesforce's uninstall process; Salesforce lets you export the data first. Data you sent to Meta, Google or your AI provider is governed by your agreement with them.
10. Changes
We may update this policy as the app changes. The date at the top shows the latest version. Significant changes are announced in the app's release notes.
11. Contact
NextMark, Dubai, United Arab Emirates. Email: hello@nextmark.ae