1. Your measurement choices
Google Analytics and Vercel performance measurement stay off until you allow analytics. Separately, Meta advertising measurement is on by default unless you decline it or your browser sends Global Privacy Control. Open Analytics preferences in the footer or use the button below to allow or decline analytics. The analytics controls stay within the page and open when requested.
Meta Pixel and server-side Conversions API measure page visits and confirmed inquiries by default to help us understand our Facebook and Instagram advertising, including the contact matching information described below. You can opt out at any time. Advertising preferences stay in the footer and open only when you choose to open them; no advertising-choice popup appears automatically. Allow and Decline are equally available. Advertising preferences are separate from analytics and permission to contact you; neither analytics permission nor an inquiry is recorded as an advertising opt-in. Use Advertising preferences in the footer or the button below. If your browser sends Global Privacy Control, advertising measurement stays off.
The controls are available on the live NMS.io website when the relevant measurement controls load. If you do not see them, those controls may be unavailable or blocked in your browser. Browser privacy settings can also block or clear cookies and site storage.
2. Cookies and browser storage
Cookies are small records stored by your browser and sent with matching requests. Local storage keeps records for a website in your browser. Session storage normally lasts for a browser-tab session, although browser session restoration can preserve it.
Our site uses these technologies for remembering your choice, understanding the source of an inquiry, and optional measurement. Website hosting and security also involve request processing that is separate from optional analytics.
3. What NMS.io stores
| Item | Purpose and duration |
|---|---|
Analytics preferencenms-analytics-consent-v1 | Local storage remembers allow or decline. The site honors a saved choice for 180 days. After it expires, optional analytics stays off until you choose again. A local-storage entry itself has no automatic browser expiry. |
Advertising preferencenms-advertising-consent-v3 | Advertising measurement is enabled by default, without storing a pretend opt-in or choice timestamp. An explicit Allow is remembered for 180 days; after that, the default policy applies unless an opt-out remains. A saved Decline, including an earlier-version opt-out, does not expire and keeps measurement off until you explicitly allow it again or clear the saved preference. An explicit new Allow replaces earlier saved declines. A later opt-out from another tab is respected. Global Privacy Control keeps advertising measurement off even if an earlier choice allowed it. |
Inquiry referralnms-attribution-v1 | Session storage holds the first landing page, referring page, and campaign parameters for the browser-tab session. This can accompany a submitted inquiry and operates independently of the analytics choice. |
Processing-review link contextnms-content-handoff-v1 | After an explicit processing-review link click, session storage carries the source page, link placement, and destination form. The record is valid for up to 15 minutes and cleared after a confirmed inquiry receipt or when it no longer matches the current handoff. It operates independently of optional analytics and accompanies your submitted inquiry; the resource topic is added from the page identifier. It does not keep a browsing history. Browser storage entries have no automatic expiry; the site checks the time limit when using them. |
Measurement deduplicationnms-analytics-receipts-v1 | With analytics allowed, local storage keeps up to 100 opaque receipt identifiers and timestamps to avoid counting a saved inquiry twice. Records are considered valid for 30 days and pruned during subsequent processing. They are not sent to Google Analytics and are cleared when analytics is declined or withdrawn. |
Advertising-event deduplicationnms-meta-receipts-v1 | While advertising measurement is enabled, local storage keeps up to 100 opaque inquiry receipt identifiers and timestamps, valid for 30 days and pruned during later processing. A confirmed inquiry’s identifier is sent to Meta as the Lead event identifier to avoid duplicate counts; it does not contain your form answers. The local record is cleared when advertising measurement is declined or withdrawn. |
Funnel association__Host-nms-funnel | While advertising measurement is enabled for a new saved lead, a Secure, HttpOnly, same-site cookie links the lead to a merchant application started in that browser. It contains an opaque signed reference, not contact details or application answers, and expires seven days after the lead was saved. Clearing or blocking this cookie can prevent funnel attribution. It does not give access to the lead or application. |
Meta Pixel cookies_fbp / _fbc | Unless you have opted out or your browser sends Global Privacy Control, Meta may use first-party browser and advertising-click identifiers to measure visits and inquiries. For an actual advertising click observed while measurement is enabled, NMS may also set _fbc for up to 90 days so its identifier remains available if you continue to another NMS inquiry page. An existing identifier for the same click keeps its original timestamp. Meta manages its own cookie lifetime and may also receive its own cookies; browser controls can block or shorten storage. We clear accessible matching first-party cookies when you decline advertising measurement. We cannot clear cookies on Meta’s own domains. |
Google Analytics cookiesnms_ga / nms_ga_* | Optional cookies distinguish browser visits for measurement. The site configures a 180-day lifetime without extending it on each visit. Browser settings can shorten or block this storage. |
These periods describe browser behavior and the site’s use of stored values. They are not automatic deletion deadlines for inquiry records held by NUMUS or its providers.
4. What optional measurement includes
Google Analytics measures page views, form starts and progress, successful inquiry saves, and general clicks on processing or contact links. The site removes query strings and fragments from measured page URLs and limits campaign information sent to approved values. Form answers and submission identifiers are not included in the site’s Google Analytics events.
Vercel Speed Insights measures page performance on supported pages after analytics is allowed. Our performance events omit form answers and remove URL query strings and fragments. The site’s Google tag disables Google signals and advertising-personalization features.
Separately, unless you opt out or your browser sends Global Privacy Control, Meta Pixel sends standard PageView and Lead events. Lead is triggered only after our server confirms an inquiry was saved, not when a submit button is clicked. Meta receives the page address and permitted campaign or advertising-click parameters, referring information, browser/device and network information such as IP address, cookie identifiers, and an opaque event identifier for a confirmed inquiry. Our browser event code does not add form answers or contact details as event parameters. Our server also sends a Lead event for an accepted inquiry through Meta’s Conversions API when advertising measurement was enabled for that inquiry, including under the default policy. It includes normalized, SHA-256-hashed email and phone details for matching, the inquiry’s opaque event identifier, receipt time, a public page address, IP address, browser information, and available browser and advertising-click identifiers. Hashing does not make matching information anonymous. Business names, industries, processing volumes, free-text answers, documents, and other business details are not sent. Browser and server events use the same identifier to avoid duplicate counts.
For the two-step form at NMS.io/lead, advertising measurement can also record successful business-detail completion, the start of a linked merchant application, and its accepted submission. These application milestones are sent by our server; the full application does not load the Meta Pixel. A secure, opaque first-party cookie links the saved inquiry to an application started in the same browser within seven days. Matching context, including hashed email and phone and available browser/click identifiers, is retained for up to seven days, subject to scheduled cleanup. IP address and browser information are supplied with the current request and are not kept in that longer-lived matching context. New milestone events require current advertising-preference evidence. A decline or Global Privacy Control received with a later funnel request suppresses further measurement for that linked funnel. Bank statements, identity documents, account numbers, income, application answers, processing volumes, and approval decisions are not sent to Meta. These funnel events use the site domain without URL paths or query strings, and do not include custom business parameters.
Meta may connect information from its business tools with information it otherwise holds for measurement and advertising under its policies. Conversions API is sent from our inquiry service; it does not export the CRM contact or opportunity record. See Meta’s Privacy Policy (opens in a new tab) and Meta’s Cookies Policy (opens in a new tab).
For Google’s explanation, see How Google uses information from sites or apps that use its services (opens in a new tab).
5. Changing or withdrawing your choice
Open Analytics preferences and select Decline analytics to stop subsequent optional analytics events from this site. The site also clears its accessible matching Google Analytics cookies and its locally stored measurement receipt records. This does not erase information already received by Google, Vercel, NUMUS, or the CRM.
Open Advertising preferences and choose Decline advertising measurement to stop subsequent Pixel events and advertising sharing for new inquiries from this site. We revoke Pixel consent, clear its pending events, remove our local advertising receipt cache, and clear accessible _fbp and _fbc cookies. A previously submitted inquiry retains the measurement state recorded with that request, and an already queued or in-flight event may complete. Withdrawal does not erase data already received by Meta or delete cookies on Meta’s domains. You can also manage your Meta account’s advertising and privacy settings. The site honors Global Privacy Control for this optional advertising measurement.
Declining analytics does not disable the separate session referral and processing-review link information described above, remove a submitted inquiry, or control a third-party website’s technologies. Clearing site storage in your browser removes locally saved choices. Analytics then stays off until you allow it. Advertising measurement returns to its default enabled state unless your browser sends Global Privacy Control; choose Decline again if you want to opt out after clearing site storage.
6. Embedded and linked services
The contact page’s CRM form is hosted at api.crm.accufy.net. Loading or using it connects to that provider independently of the NMS analytics choice, and it may use its own cookies or storage. The separate application on go.numuspayments.com and other linked websites have their own technologies and notices.
Review our Privacy Policy for inquiry handling and how to make a privacy request.
Have a question?
Contact the NUMUS team at support@nms.io or +1 305-290-4950.
Numus Payments LLCParamount Worldcenter
851 NE 1st Ave
Ste 3601
Miami, FL 33132, United States