Legal & trust
Subprocessors
BlueTier uses a small set of third-party providers to host, store, and operate the service. This page lists each provider in the current production environment, its role, and the categories of data it processes. It was verified against the production configuration on 2026-10-02.
- Effective and last updated
- Sections
- 13
- Reading time
- 4 min
On this page · 13 sections
- 01Vercel — web hosting and serverless functions
- 02Supabase — Postgres database and authentication
- 03Railway — always-on background worker
- 04Approved third-party connectivity provider — LinkedIn, WhatsApp, Instagram, Telegram and email connectivity
- 05Stripe — payment processing
- 06Calendly — meeting scheduling
- 07Cal.com — meeting scheduling
- 08OpenRouter — AI inference
- 09Google (Google Sheets) — operational lead-tracker mirror
- 10Sentry — error monitoring
- 11Resend — transactional email
- 12SMS delivery (not yet integrated)
- 13Keeping this list current
Vercel — web hosting and serverless functions
Role: hosts the public website, the BlueTier Dashboard, application APIs, and scheduled jobs. Data categories: request and connection data such as IP address, browser and device headers, timestamps, and routes requested, plus the content submitted through site forms in transit. Region: see provider documentation.
Supabase — Postgres database and authentication
Role: the platform’s primary data store and its authentication provider; the content-management system behind BlueTier Insights uses the same database. Data categories: account and sign-in records, organization, campaign, contact, conversation, and dashboard records, audit logs, and member-provided profile, ICP, and messaging context. Data at rest is encrypted by the provider. Region: see provider documentation.
Railway — always-on background worker
Role: runs the always-on worker that paces campaign activity, synchronizes connected-account conversations, and drains queued provider events. Data categories: the same campaign, connection, and conversation records the worker processes, in transit and in memory. Region: see provider documentation.
Approved third-party connectivity provider — LinkedIn, WhatsApp, Instagram, Telegram and email connectivity
Role: connects a member’s LinkedIn, WhatsApp, Instagram, Telegram, or Gmail/Outlook/IMAP email account to BlueTier so the member’s inbox and the campaigns or bulk messages they approved can run on that channel — LinkedIn is the only channel a campaign or sequence runs on; the others carry inbox replies and bulk messages. The same provider can also carry an experimental Messenger or X connection a member starts, though neither runs a BlueTier campaign. When a member chooses a connected Gmail or Outlook mailbox for scheduling, the same provider also gives BlueTier access to that mailbox’s Google Calendar or Outlook calendar: to see which times are busy, and to add each meeting booked through BlueTier, with its invitation and video-call link. Data categories: connected-account session data, profile and network information, the invitations, messages, and conversation threads involved in a member’s inbox, campaigns and bulk messages, and, for a calendar a member chooses, its busy times and the meetings BlueTier adds (the invitee’s name and email address). BlueTier never collects a connected account’s password; every connection is session-based. The provider is identified to members on request and in the Data Processing Addendum. Region: see provider documentation.
Stripe — payment processing
Role: processes membership payments and manages billing records. Data categories: cardholder and payment-method data (tokenized by Stripe; BlueTier’s servers do not receive or store card numbers), billing name, email and address, and subscription and invoice records. Region: see provider documentation.
Calendly — meeting scheduling
Role: where a member connects their own Calendly account with a personal access token, lets BlueTier check availability and book meetings on that member’s behalf. Not used unless a member connects it. Data categories: the member’s Calendly availability and event data, and the name, email, and scheduling responses of the invitee being booked. Region: see provider documentation.
Cal.com — meeting scheduling
Role: where a member connects their own Cal.com account with an API key, lets BlueTier read that member’s event types and bookings and send people to the member’s own Cal.com booking page. Not used unless a member connects it. Data categories: the member’s Cal.com account, event type and booking data, and the name and email of the invitees on those bookings. Region: see provider documentation.
OpenRouter — AI inference
Role: routes the language models used for AI-assisted drafts, conversation summaries, and message classification; Groq is retained as a fallback provider. Data categories: the profile, ICP, messaging, and conversation context sent in a prompt for a member’s own campaigns; member data is not used to train shared models unless separately disclosed. Region: see provider documentation.
Google (Google Sheets) — operational lead-tracker mirror
Role: an operational mirror of lead-tracking records used by the BlueTier team. Data categories: onboarding submissions, contact details, campaign configuration, and authorization records. Region: see provider documentation.
Sentry — error monitoring
Role: receives error reports and technical diagnostics from the website, dashboard, and worker so failures can be found and fixed. Data categories: error messages, stack traces, request metadata, and the technical context attached to an error. Region: see provider documentation.
Resend — transactional email
Role: sends email a person is waiting for — password resets, "your password was changed" notices, invitations, and booking confirmations (the link that confirms a meeting booked on a member’s BlueTier booking page). Data categories: the recipient’s email address, name where available, and the message content of the transactional email. Region: see provider documentation.
SMS delivery (not yet integrated)
BlueTier does not currently use an SMS delivery provider: no vendor sends text messages on BlueTier’s behalf today. Before the “BlueTier text alerts” program (see the SMS Terms & Conditions) sends its first message, the SMS delivery provider will be named here, with its role and data categories, the same way every other subprocessor on this page is.
Keeping this list current
This list is updated as vendors change. A Data Processing Addendum covering these subprocessors is available on request — email info@bluetier.ai — and the public template is published on the DPA page.
Questions or correction requests?
Use the contact form or email info@bluetier.ai. Never include an account password or verification code.
Contact