Privacy and service-provider transparency

Subprocessors

This page identifies material third-party providers used by Corenth Technologies and explains their role, the types of data they may process, why they are used, and relevant transfer considerations.

Corenth Technologies LLCPolicy review in progress · Previous revision: August 15, 2026

Platform capability notice: Certain features described on this website may be undergoing staged rollout, production configuration, or acceptance testing. Availability depends on your account, subscription, and enabled integrations. References to planned or in-development functionality do not guarantee current access. For confirmation of specific capabilities, contact cdean@corenthtech.com.

Production provider register

Provider transparency principles

Provider disclosures should follow actual production data flows.

Corenth Technologies maintains this register to provide customers with information about material providers supporting the production Service.

01

Providers are listed based on their actual role in the production Service rather than planned or hypothetical use.

02

Provider roles may vary by feature, contract, jurisdiction, customer configuration, and processing activity.

03

Data shared with providers should be limited to information reasonably necessary for the applicable service.

04

Corenth considers available provider privacy, security, contractual, retention, and transfer information as appropriate to the service.

05

This register may be updated when a material provider is added, removed, or materially changes its role.

06

Customer-selected third-party integrations may be governed by agreements directly between the customer and the selected provider.

01

Overview

Corenth Technologies LLC uses third-party service providers to support hosting, databases, authentication, payments, artificial intelligence, transactional email, scheduling, customer relationship management, and related platform operations.

A provider may process personal information or Customer Data on behalf of Corenth Technologies. Where a provider processes Customer Personal Data on Corenth's behalf, that provider may qualify as a subprocessor under an applicable customer agreement or data-protection law.

Not every provider receives every category of information, and not every provider acts as a subprocessor for every activity. Some providers may act as independent controllers or in another legal capacity for certain processing.

Scope of this register

This page is designed to identify material providers that may process information in connection with Corenth Technologies' production Service. It is not intended to list every utility, software package, professional adviser, financial institution, or other vendor that never receives Customer Personal Data.

02

What Is a Subprocessor?

A subprocessor is generally a third party engaged by a processor to process personal information on behalf of a business customer.

Whether a particular provider is legally considered a subprocessor depends on factors including:

  • The service the provider performs.
  • The information the provider receives.
  • The purpose for which the information is processed.
  • Whether Corenth or the customer determines the relevant processing instructions.
  • The applicable agreement and privacy or data-protection law.

Certain providers, particularly payment and identity providers, may act in multiple legal capacities for different activities.

03

Active Providers

The following material providers currently support Corenth Technologies' production Service.

Supabase

Backend, database, authentication, and application infrastructure

Active provider
Role
Cloud infrastructure provider and subprocessor for applicable customer-directed processing
Processing purpose
Supports account creation, authentication, password recovery, authenticated sessions, database storage, customer records, support tickets, platform functionality, and other backend operations.
Processing location
Processing locations depend on Corenth Technologies' Supabase project configuration, selected infrastructure region, backup systems, provider operations, and applicable service configuration.
Transfer safeguards
Applicable provider contractual protections and lawful international-transfer safeguards are used where required.

Data categories

  • Account and profile information
  • Email addresses and authentication records
  • Session and access information
  • Organization and membership information
  • Application records stored in the database
  • Contacts and CRM records
  • Leads and opportunity information
  • Workflow and automation records
  • Support-ticket information
  • Appointments and related application records
  • Technical, security, and operational information
Current status note

Supabase supports Corenth Technologies' production backend, database, authentication, application data, and dashboard functionality. Customer-support tickets handled through the Corenth dashboard are stored and processed through the applicable Corenth and Supabase infrastructure rather than through a separate external help-desk provider.

Stripe

Payment processing, checkout, and subscription billing

Active provider
Role
Payment processor, independent controller, service provider, or subprocessor depending on the particular processing activity
Processing purpose
Supports checkout, payment authorization, recurring subscription billing, invoices, receipts, subscription management, fraud prevention, payment security, and related financial operations.
Processing location
Processing locations depend on Stripe infrastructure, customer location, Stripe account configuration, and the specific Stripe services used.
Transfer safeguards
Stripe contractual terms and applicable international-transfer safeguards apply where required.

Data categories

  • Customer name and contact information
  • Billing information
  • Payment-method information submitted to Stripe
  • Subscription and plan information
  • Invoice and transaction information
  • Trial and renewal information
  • Payment status
  • Fraud-prevention information
  • Technical and device information where applicable
  • Tax-related information where applicable
Current status note

Stripe is used for Corenth Technologies' production payment and subscription functionality. Stripe may act in different legal capacities depending on the specific payment, fraud-prevention, compliance, or processing activity.

Render

Production application hosting and infrastructure

Active provider
Role
Hosting and infrastructure provider for the Corenth Technologies production application
Processing purpose
Hosts and delivers the Corenth Technologies production website, application, server-side functionality, and related production infrastructure.
Processing location
Processing locations depend on Corenth Technologies' Render service configuration, selected deployment region, provider infrastructure, support operations, and related services.
Transfer safeguards
Applicable provider contractual protections and lawful transfer safeguards are used where required.

Data categories

  • Website request information
  • IP addresses
  • Device and browser information
  • Application requests
  • Server-side request information
  • Application logs
  • Deployment and operational metadata
  • Customer information processed through hosted application routes
  • Technical and diagnostic information
Current status note

Render is the production hosting provider used by Corenth Technologies. Information passing through server-side application routes may be processed through Render infrastructure as necessary to provide the Service.

Google

Google OAuth, Google sign-in, and related Google Cloud services

Active provider
Role
Authentication, identity, and cloud service provider for applicable Corenth Technologies functionality
Processing purpose
Supports Google account sign-in and authentication and may support related Google Cloud functionality used by Corenth Technologies.
Processing location
Processing locations depend on Google infrastructure, Google account configuration, applicable services, and provider operations.
Transfer safeguards
Google contractual terms and applicable international-transfer safeguards apply where required.

Data categories

  • Google account identifiers
  • Name
  • Email address
  • Profile information made available through authorized OAuth scopes
  • Authentication tokens or related authorization information
  • Login and authentication metadata
  • Technical information associated with authentication requests
Current status note

Google OAuth is available as an authentication option. Corenth Technologies requests only the permissions necessary for the applicable sign-in or connected functionality.

OpenAI

Artificial intelligence model and API services

Active provider
Role
Artificial intelligence service provider and subprocessor for applicable AI-powered customer processing
Processing purpose
Supports AI assistants, chatbots, content generation, summaries, classifications, workflow actions, knowledge-based responses, automation features, and other artificial-intelligence functionality requested through the Service.
Processing location
Processing locations depend on the OpenAI services used, account configuration, provider infrastructure, contractual terms, and applicable service settings.
Transfer safeguards
Applicable provider data-processing terms and lawful international-transfer safeguards apply where required.

Data categories

  • Prompts and user instructions
  • Customer-provided text
  • Conversation context
  • Customer-approved business information
  • Files or content submitted to supported AI features
  • Generated responses
  • Generated summaries and classifications
  • Technical request and usage metadata
Current status note

OpenAI is used to provide production AI functionality. Corenth Technologies limits AI processing to information reasonably necessary for the feature or action requested by the user and does not use customer business content to train a Corenth general-purpose foundation model.

Resend

Transactional and service-related email delivery

Active provider
Role
Communications provider and subprocessor for applicable email delivery
Processing purpose
Supports account verification, password recovery, transactional messages, billing communications, security notifications, service updates, and other operational email delivery.
Processing location
Processing locations depend on Resend infrastructure, message routing, provider operations, account configuration, and applicable service terms.
Transfer safeguards
Applicable provider contractual protections and lawful international-transfer safeguards apply where required.

Data categories

  • Recipient names
  • Recipient email addresses
  • Account-verification messages
  • Password-reset communications
  • Security notices
  • Billing and subscription communications
  • Service notifications
  • Support-related communications
  • Email-delivery and bounce metadata
Current status note

Resend is used for production transactional and service-related email delivery. Corenth Technologies does not rely on Resend as a separate customer-support ticketing platform.

Calendly

Meeting, consultation, and discovery-call scheduling

Active provider
Role
Scheduling service provider for applicable meetings and appointment requests
Processing purpose
Supports discovery-call scheduling, consultations, business meetings, appointment coordination, and related scheduling activity.
Processing location
Processing locations depend on Calendly infrastructure, connected calendar services, provider operations, customer location, and applicable account configuration.
Transfer safeguards
Calendly contractual terms and applicable international-transfer safeguards apply where required.

Data categories

  • Name
  • Email address
  • Company information where provided
  • Meeting date and time
  • Scheduling preferences
  • Information submitted through scheduling forms
  • Calendar-related information necessary to coordinate a meeting
  • Technical and scheduling metadata
Current status note

Calendly is used for applicable scheduling and meeting-booking functionality. Information provided directly through Calendly may also be subject to Calendly's own privacy terms.

HubSpot

Customer relationship management and business relationship administration

Active provider
Role
CRM and business operations provider for applicable prospect and customer relationship information
Processing purpose
Supports customer relationship management, lead and prospect administration, sales activity, business inquiries, communications history, and related business-development operations.
Processing location
Processing locations depend on HubSpot infrastructure, account configuration, provider operations, enabled features, and applicable service settings.
Transfer safeguards
HubSpot contractual terms and applicable international-transfer safeguards apply where required.

Data categories

  • Names
  • Email addresses
  • Company information
  • Business contact information
  • Prospect and lead information
  • Customer relationship information
  • Sales activity
  • Business inquiries
  • Communications and interaction history
  • CRM notes and related business records
Current status note

HubSpot is used for Corenth Technologies' CRM and related business relationship management. The exact information processed depends on the CRM records and functionality used.

04

Customer Support Data

Corenth Technologies does not currently use a separate third-party help-desk or customer-support ticketing provider.

Support tickets submitted through the customer dashboard are handled through the Corenth Technologies application and stored through the applicable Corenth backend and Supabase infrastructure.

Support information may include the customer's name, account or organization information, email address, message, troubleshooting details, and other information the customer chooses to submit as part of a support request.

Corenth may also communicate with customers by email regarding support matters. Where transactional email is sent through Resend, the information required to deliver that communication may be processed by Resend.

05

Analytics and Tracking

Corenth Technologies does not currently identify Google Analytics as an active production provider.

Corenth may use technical logs, application records, provider dashboards, and operational information necessary to secure, operate, troubleshoot, and maintain the Service.

If Corenth later activates a material third-party analytics, advertising, behavioral-tracking, or external monitoring provider that processes Customer Personal Data or visitor information, Corenth will update the applicable privacy and cookie disclosures and this provider register as appropriate.

06

Provider Due Diligence

When evaluating a material provider that may receive Customer Personal Data, Corenth Technologies considers factors appropriate to the nature of the service, including:

  • The service performed and whether Customer Personal Data is necessary for that service.
  • The categories and sensitivity of information processed.
  • The provider's contractual privacy and security obligations.
  • Available security documentation and control descriptions.
  • Provider retention, deletion, and account-configuration options.
  • Provider treatment of customer information, including AI or product-improvement uses where relevant.
  • Processing regions, support locations, and international transfers.
  • Incident-notification and cooperation obligations.
  • Downstream provider or subprocessor transparency where available.
  • Configuration options that can reduce unnecessary data collection or processing.

The scope and depth of review may vary depending on the sensitivity of the information, nature of the processing, provider documentation available, contractual requirements, customer requirements, and the role of the provider.

No provider eliminates all risk

Provider review and contractual safeguards are intended to reduce risk but cannot guarantee that a third-party provider will never experience an outage, security incident, legal issue, service change, or other failure.

07

Provider Changes and Notifications

Corenth Technologies may add, replace, or remove providers as the Service, architecture, functionality, customer needs, legal requirements, and provider availability change.

When a material provider begins processing Customer Personal Data on Corenth's behalf, Corenth may, as appropriate:

  • Review the provider and applicable service.
  • Document the provider's role and processing purpose.
  • Review available privacy, security, contractual, retention, and international-transfer information.
  • Update this provider register within a reasonable period.
  • Provide advance or other notice when required by an applicable agreement or law.

Removal of a provider does not necessarily result in immediate deletion of all information from provider-managed backups, logs, billing records, security records, or legally required archives.

08

Customer Objections

If a binding Data Processing Addendum or other applicable customer agreement provides a right to object to a new subprocessor, the customer may submit a written objection in accordance with that agreement.

An objection should identify:

  • The affected customer and agreement.
  • The provider involved.
  • The specific data-protection concern and affected processing.
  • Any other information required by the applicable agreement.

Corenth Technologies and the customer may attempt to address a valid concern through additional information, configuration changes, reduced processing, additional safeguards, alternative services where reasonably available, or another remedy provided by the applicable agreement.

An objection does not automatically require Corenth Technologies to discontinue a provider where the applicable agreement does not require that result or where no commercially reasonable alternative is available.

09

International Transfers

Corenth Technologies is based in the United States, and its providers may process information in the United States and other countries where they, their affiliates, support teams, or infrastructure operate.

Where applicable data-protection law requires an international-transfer safeguard, Corenth Technologies and the applicable provider may rely on an appropriate lawful mechanism, which may include:

  • An applicable adequacy decision.
  • European Commission Standard Contractual Clauses where appropriate.
  • A United Kingdom International Data Transfer Agreement or applicable UK Addendum where appropriate.
  • Another legally recognized international-transfer mechanism.

A particular mechanism applies only where relevant to the processing activity and where the required contractual and legal conditions are satisfied.

Provider processing locations and transfer arrangements may change as providers modify infrastructure, support operations, corporate structure, contractual terms, or service architecture.

10

Customer-Selected Integrations

Customers may choose to connect Corenth Technologies with external CRM, scheduling, marketing, communications, storage, analytics, payment, automation, or other third-party services.

A customer-selected provider may not be a Corenth Technologies subprocessor when:

  • The customer independently selects the provider.
  • The customer authorizes the connection.
  • The customer's own agreement with the provider governs the relevant processing.
  • Corenth merely facilitates transmission or functionality at the customer's direction.

Customers are responsible for reviewing the privacy, security, legal, retention, and contractual terms of third-party services they independently use outside Corenth and enable.

Corenth Technologies may restrict, suspend, or disable an external service or customer configuration that creates a security, privacy, legal, operational, technical, or platform risk.

11

Customer Responsibilities

Customers remain responsible for:

  • Determining whether the Service and applicable providers are appropriate for their intended use.
  • Providing legally required privacy notices and obtaining required permissions or consent.
  • Submitting only information they are authorized to collect, use, and process.
  • Avoiding unsupported sensitive or regulated information.
  • Reviewing independently selected external services and provider terms.
  • Configuring account permissions, AI features, workflows, and data collection appropriately.
  • Contacting Corenth Technologies before beginning a use that requires customer-specific contractual, security, localization, or regulatory protections.

Customers with specific data-residency, localization, regulated-data, vendor, industry, or security requirements should raise those requirements before purchasing or enabling the affected functionality.

12

Contact Information

Questions about providers, subprocessors, international transfers, customer-data processing, or provider objections may be sent to:

Corenth Technologies LLCcdean@corenthtech.comMailing Address
350 Northern Blvd STE 324-1400
Albany, NY 12204-1000
United States

This is Corenth Technologies LLC's business mailing address and should not be interpreted as a public office, retail location, or walk-in customer-service center.

A provider-related request should identify the customer, organization, relevant provider, applicable agreement, and specific privacy or data-protection concern where applicable.

Related documentation

Provider transparency works together with Corenth's privacy, data-processing, and security terms.

Data Processing Addendum

Review contractual terms governing Customer Personal Data, subprocessors, security, deletion, data-subject requests, and international transfers.

Review the DPA

Privacy Policy

Review how Corenth Technologies collects, uses, shares, retains, and protects information.

Read the Privacy Policy

Security

Review Corenth Technologies' security practices, safeguards, responsibilities, and limitations.

Review Security

This page is a provider-transparency register and may be updated as Corenth Technologies' production architecture, providers, processing activities, contractual arrangements, and services evolve. Provider roles, processing locations, retention practices, and international-transfer safeguards may depend on the specific service, customer configuration, processing activity, and applicable agreement.