Sign in with TelegramMemberPilot is operated by ANVOG LLC. This page lists every third party that processes data on our behalf or that data reaches through normal use of the product. It is referenced by the Privacy Policy.
The list is short on purpose. Services that are planned, evaluated or half-built are not on it, because they are not processing anything.
Core infrastructure
| Provider | What it does | What it receives | Where |
|---|---|---|---|
| InstantDB (Instant Inc.) | Database, authentication, realtime sync, file storage for offer cover images | All application data: creator profiles, workspaces, communities, offers, customer records, subscriptions, entitlements, payment metadata, encrypted provider credentials, audit records | United States |
| Postmark (ActiveCampaign) | Sends the one-time sign-in code for email sign-in, through InstantDB | Email address and sign-in code | United States |
| netcup GmbH | Virtual server hosting the application container, managed by us through Coolify | Data in transit and in application memory during request processing | Nuremberg, Germany |
Telegram
| Provider | What it does | What it receives | Where |
|---|---|---|---|
| Telegram (Telegram FZ-LLC / Telegram Messenger Inc.) | Identity for sign-in, the MemberPilot bot, community access control, digital product delivery | Telegram user IDs and chat IDs, invite and removal instructions, the text of bot messages we send, and the messages a creator sends the bot to set up a digital product | International |
Telegram is not a subprocessor in the usual sense. It is the platform the product runs on, and it holds the creator's community and the buyer's account regardless of MemberPilot. Digital product files never leave Telegram: delivery is Telegram copying its own message from one chat to another.
Payment providers
Each of these is an independent controller of the payment data it collects, not a processor acting for us. Card numbers, bank details and wallet addresses go to them and never to us.
| Provider | What it does | What it receives | Where |
|---|---|---|---|
| Stripe, Inc. | Card checkout and subscriptions through the creator's own Stripe Connect account, and the card MemberPilot charges creators for accrued crypto service fees | Payment details entered by the buyer, the offer name and amount, and identifiers linking the payment back to a MemberPilot checkout session | United States, international |
| NOWPayments | Crypto checkout settling into the creator's own NOWPayments account | Invoice amount, currency, order identifier and callback URL | International |
| CCPayment | Crypto checkout settling into the creator's own CCPayment merchant account, and — on MemberPilot's own merchant account — the USDT invoices creators can use to settle service fees they owe us | Invoice amount, currency, order identifier and callback URL | International |
A creator connects only the providers they want. A provider that has never been connected to a workspace receives nothing about it.
On the marketing site only
| Provider | What it does | What it receives | Where |
|---|---|---|---|
| YouTube (Google LLC) | Embedded product walkthrough videos on public marketing pages, served from youtube-nocookie.com with thumbnails from i.ytimg.com | Your IP address and the page you were on, from your browser directly. We receive nothing back. | International |
These embeds appear only on public marketing pages. There is no YouTube embed anywhere in the signed-in product or on any checkout page.
What is not here
There is no analytics provider, no error monitoring service, no advertising network, no customer data platform, no CRM, no chat widget, no CDN beyond what our host provides, and no AI or media generation service in the request path. Fonts are served from our own domain rather than from a font CDN.
Changes
We will update this page when a subprocessor is added or removed, and update the date at the top. Creators who want advance notice of additions can ask at support@memberpilot.bot.