MagicTicket is in active beta. These documents are reviewed each release; we’ll notify all account holders by email if a substantive change requires re-acceptance. Current revision: v2026-04-20. Questions? Get in touch.
Subprocessors
Last updated: v2026-04-20
MagicTicket relies on a small set of vetted, industry-standard third-party services to operate the platform. Each is bound by its own privacy and security commitments.
TeamViewer is intentionally not a subprocessor — MagicTicket only links to TeamViewer’s public download page from the ticket interface; we do not see remote-session content.
Categories of providers
At a high level, MagicTicket uses providers in the following categories:
| Category | Purpose |
|---|---|
| Cloud infrastructure | Application hosting, database, authentication, and file storage |
| AI inference | MagicAI suggestions, auto-replies, and ticket summaries |
| Payment processing | Subscription billing and invoices |
| Transactional email | Invites, ticket notifications, and account emails |
| SMS notifications | Optional new-ticket alerts when a workspace enables SMS |
Detailed vendor list
The named vendor list is available to account holders.
We share the specific provider names, the data each one handles, and the processing region with anyone who has a MagicTicket account. Start a free trial or sign in to view the full table — it takes about 30 seconds and no card is required during the trial.
Questions about how a specific provider handles your data? See the contact page— we’ll answer directly.