Skip to content
Dynamic.ly
ProductHow it worksFor restaurantsTrustField NotesPilotAccess
Dynamic.lyDynamic.ly
Explore the productAbout us
OverviewPrivacyTermsCookies & storage

Provider disclosure preview

Dynamic.ly Subprocessors and Third-Party Services

A source-limited disclosure of verified providers and the information still required before publication.

Status
Non-final publication candidate
Verified website provider
Vercel
Processing region
Verification pending
Non-final previewFounder review is complete. Qualified counsel review is not complete. This document is not effective and does not authorize installation or connection of Clover. Unverified provider and contact details remain marked in the text.

On this page

  1. 01Current Verified Public-Website Provider
  2. 02Clover/Fiserv Platform Relationship
  3. 03Merchant-Data Infrastructure
  4. 04Questions
Back to top ↑

Status: Non-final publication candidate. The final page must contain only providers verified from current source, deployment, contracts, or authorized configuration.

Nomos Apex AI LLC uses a limited number of service providers to operate Dynamic.ly. This page is intended to identify the provider, purpose, relevant data category, and processing region where known. Material changes will be reflected here and communicated through an appropriate Merchant notice method where required.

Current Verified Public-Website Provider

ProviderPurposeData categoryProcessing region
VercelHosting and content delivery for the public Dynamic.ly website and legal/support pagesPublic webpage content and standard website request/technical metadataProvider infrastructure; exact configured region must be verified from the authorized Vercel project before publication

Clover/Fiserv Platform Relationship

Clover/Fiserv is the Merchant-authorized source platform for the Clover connector, not a Dynamic.ly subprocessor selected to replace Clover. Dynamic.ly exchanges authorized read-only source requests and OAuth-related communications with Clover/Fiserv to provide the integration.

Merchant-Data Infrastructure

The current H3/H4 legal pause did not prove a Production hosting, managed database, email, logging, or support provider for live Clover Merchant data. Before Production or live Merchant use, the H5/runtime audit must add every verified provider that processes Merchant Data, including:

  • backend/application hosting;
  • managed database or object storage;
  • security, logging, and monitoring;
  • email and support systems; and
  • any other infrastructure provider with access to Merchant Data.

No unverified provider may be added merely because it appears in historical planning material.

Questions

Privacy and subprocessor questions may be sent to privacy@dynamicly.app after that mailbox is created and verified.

Dynamic.ly

Clearer restaurant decisions.
Sources attached. The manager decides.

OverviewPrivacyTermsCookies & storageContact

© 2026 Dynamic.ly

Dynamic.ly

Restaurant cost changes, explained before they become blind decisions.

Discuss a pilot

Product

  • Product
  • How it works
  • For restaurants
  • Pilot

Evidence

  • Trust
  • How results are measured
  • Field Notes

Company

  • About
  • Philosophy
  • Happily
  • Contact

Legal and access

  • Privacy
  • Terms
  • Access

© 2026 Dynamic.ly

Sources. Limits. Manager decision.