Subprocessor List

Last updated: August 26, 2026

This page lists the third parties Z3NTRA LLC ("Z3NTRA") uses to help run the Z3NTRA application, as referenced in our Privacy Policy. It's split into two different kinds of third party, because they work differently:

1. Infrastructure subprocessors

SubprocessorPurposeWhat it may process
Fly.io, Inc. Application hosting and the persistent database volume the Service runs on. All account and task data, as the underlying infrastructure the Service runs on.
Stripe, Inc. Payment processing, subscription billing, and the hosted billing portal. Billing contact details and payment information. Z3NTRA does not receive or store full card numbers.
Google LLC "Sign in with Google" authentication, and the optional Google Docs/Drive integration for creating a document from a task. Email address and basic profile info for sign-in; document content you choose to create, for the Docs integration only.
Email delivery provider Sending account email — verification, password reset, and task reminder notifications. Your email address and the content of transactional emails sent to you. This is an SMTP provider configured by a Z3NTRA administrator and can change over time; contact us for the current provider in use.

2. Connected systems (at your direction)

These are the external systems Z3NTRA currently supports connecting to your account. None of them receive your Z3NTRA account credentials — you authorize each one separately, with its own credentials, and can disconnect it at any time from Settings.

SystemProviderWhat flows through it
Azure DevOpsMicrosoft CorporationWork items you sync into Z3NTRA.
Monday.commonday.com Ltd.Board items you sync into Z3NTRA.
JiraAtlassian CorporationIssues you sync into Z3NTRA.
ZendeskZendesk, Inc.Tickets you sync into Z3NTRA.
ClickUpClickUp (Uber Berlin, Inc.)Tasks you sync into Z3NTRA.
LiveAgentQualityUnit, s.r.o.Tickets you sync into Z3NTRA.
SmartsheetSmartsheet Inc.Rows you sync into Z3NTRA.
Custom REST connectorWhichever API you configureWhatever data that API returns, entirely under your configuration.
Basecamp37signals, LLCNot currently available to connect (built and tested, but awaiting Basecamp OAuth credentials before it's enabled).

3. Changes to this list

If we add a new infrastructure subprocessor (Section 1) that will process customer data, we'll update this page and, where required, notify account holders in advance. We add or remove connected systems (Section 2) as we build support for new integrations — those are always opt-in, since you have to explicitly connect one with your own credentials before it's used.