Sub-Processor List

Last updated: March 22, 2026

Mataki Labs LLC (“Authpipe,” “we,” “us,” or “our”) uses the following third-party sub-processors to process personal data on behalf of our customers in connection with the Authpipe platform and related services. This list is maintained in accordance with the Data Processing Addendum.

Current Sub-Processors

Sub-ProcessorPurposeData ProcessedLocation
Google Cloud PlatformCloud infrastructure and hostingAll Customer Data (OAuth tokens, API keys, webhook secrets, connection metadata, account information, API request logs)United States (us-central1)
SandbarMarketing website hostingIP addresses, request metadataUnited States
ClerkUser authentication and identity managementName, email address, authentication credentials, session dataUnited States
StripePayment processing and billingName, email address, billing address, payment method details, transaction historyUnited States
ResendTransactional and operational email deliveryEmail address, name, email contentUnited States
Google Cloud BigQueryInternal analytics and reportingAggregated and anonymized usage dataUnited States (us-central1)

Sub-Processor Details

Google Cloud Platform (Google LLC) Google Cloud Platform provides the core infrastructure on which the Authpipe platform operates, including compute, storage, networking, and key management services. All Customer Data, including encrypted OAuth tokens, API keys, and webhook secrets, is stored and processed within the us-central1 region. Google Cloud maintains SOC 2, ISO 27001, and other industry-standard certifications.

Sandbar (Mataki Labs LLC) Sandbar hosts the Authpipe marketing website (authpipe.dev). Sandbar processes only IP addresses and HTTP request metadata associated with visitors to the marketing website. Sandbar does not have access to Customer Data stored within the Authpipe platform.

Clerk (Clerk, Inc.) Clerk provides authentication and user session management for the Authpipe console. Clerk processes user names, email addresses, authentication credentials (passwords and multi-factor authentication data), and session tokens for users who log into the Authpipe platform.

Stripe (Stripe, Inc.) Stripe processes payment transactions and manages billing for Authpipe subscriptions. Stripe receives and processes customer names, email addresses, billing addresses, payment method details, and transaction history. Authpipe does not store full payment card numbers on its own systems.

Resend (Resend, Inc.) Resend handles the delivery of transactional and operational emails sent by the Authpipe platform, including account verification emails, password reset emails, billing notifications, and product announcements. Resend processes recipient email addresses, names, and email content.

Google Cloud BigQuery (Google LLC) BigQuery is used for internal analytics and reporting on aggregated and anonymized platform usage data. Data processed in BigQuery is not linked to individual Data Subjects and is used solely for internal operational purposes such as capacity planning, performance optimization, and product improvement.

Change Notification

In accordance with Section 4 of the Data Processing Addendum, Authpipe will provide at least thirty (30) days’ prior written notice before a new sub-processor begins processing personal data. Notification will be provided by updating this page and by email to subscribed customers.

To subscribe to sub-processor change notifications, email dpa@authpipe.dev with the subject line “Sub-Processor Change Notifications.”

If you wish to object to a new sub-processor, you may do so in writing within fifteen (15) days of receiving notice, as described in Section 4.4 of the Data Processing Addendum.

Change Log

DateChange
March 22, 2026Initial sub-processor list published

Contact

For questions about this sub-processor list or Authpipe’s data processing practices, contact: