Jewellink Service Provider and Subprocessor List

Last updated: 5/17/2026

This list identifies material service providers and subprocessors used or conditionally supported by Jewellink. Some providers may apply only when a retailer enables a feature, connects an integration, uses the mobile app, or participates in a migration.

Production and Core Providers

ProviderPurposePotential data categories

Google Cloud PlatformHosting, Cloud Run, build/deploy, runtime infrastructure, secret managementRetailer Data, account data, logs, operational data

PostgreSQL database providerPrimary application databaseCRM, user, customer, sales, training, messaging, settings, and integration data

TwilioSMS/MMS, OTP, messaging services, A2P 10DLC, webhooksphone numbers, message content, delivery metadata, brand/campaign data

StripeBilling, checkout, subscriptions, billing portal, payment webhooksbilling contacts, customer IDs, subscription metadata, payment processor tokens

PostmarkTransactional emailrecipient emails, system email content, delivery metadata

CloudinaryMedia storage, image/video/file upload, media migration, taggingimages, videos, files, product media, course media, metadata

OpenAIAI chat, reply suggestions, transcription, analysis, roleplay workflowsprompts, outputs, transcripts, CRM context, sales/training context

ElevenLabsVoice generation, text-to-speech, conversational roleplaytext, generated audio, voice/persona configuration, usage metadata

HeyGenAI avatar/video generationscripts, avatar/video settings, generated video metadata

UpstashRedis, rate limiting, OTP/session supportauth/security metadata, rate limit keys, temporary OTP/session signals

SCORM CloudLearning management, SCORM course launch and progresslearner names/emails, course IDs, registrations, progress, scores

BubbleLegacy data migration and legacy webhook forwardinghistoric CRM, customer, company, user, training, message, and file data

EDT / PlanetScale / sync.linkd.comRetail POS, customer, sales, transaction, inventory, wishlist, and media syncPOS data, customer data, sales data, inventory data, product images, wishlist data

Expo / EAS / Expo PushMobile app builds, mobile runtime services, push notificationsdevice tokens, mobile app metadata, push payload metadata

Retailer-Enabled Integrations

ProviderPurposePotential data categories

Google GmailConnected email sending, reading, and mailbox workflow featuresemail content, headers, recipients, mailbox metadata

Google CalendarConnected calendar featurescalendar events, attendee data, availability metadata

Google Business ProfileBusiness profile integrationbusiness account, profile, location, user info, OAuth token metadata

Microsoft Azure / Microsoft GraphOutlook email and calendar integrationemail content, calendar data, user profile, OAuth token metadata

FastmailJMAP email and calendar integrationemail content, calendar data, API token metadata

Meta / Facebook / InstagramMessenger and Instagram DM integrationpage data, IG account data, messages, participants, access token metadata

3CXCall, chat, and SMS webhook/transcription workflows where enabledcall metadata, phone numbers, chat/SMS transcript data, raw webhook payloads

Conditional or Future Providers

ProviderPurposeNotes

VercelScheduled cron configurationConfirm whether production cron jobs run through Vercel or another scheduler.

Apple App Store / APNsiOS app distribution and push notification deliveryApplies to production iOS mobile app distribution and push notifications.

Apple iCloud / CloudKitNative iOS shell has CloudKit entitlementsConfirm whether the native iOS shell is active. The Expo mobile app appears to be the active mobile product.

Google Fonts / Font delivery providersPublic web/mobile font loading where usedUsually low-risk, but include in cookie/privacy review if client-side calls occur.

​

Service Provider Change Process

Jewellink may update this list as providers change. Where required by an executed DPA or applicable law, Jewellink will provide notice of material subprocessor changes and an opportunity to object on reasonable data protection grounds.

Notes for Counsel

1. Confirm exact legal names and privacy/security URLs for each provider before publication.

2. Split "subprocessor" from "integration provider" if counsel prefers a narrower public list.

3. Mark providers as active, optional, or legacy before publishing.

4. Confirm whether OpenAI, ElevenLabs, HeyGen, and Cloudinary processing terms support the AI and media commitments in the Master Terms and AI Addendum.