CLOCOT SUBPROCESSOR LIST
Effective Date: October 2, 2026 Last Updated: October 2, 2026
This page identifies core third-party providers that may process personal information to help LexLupi LLC provide Clocot. The exact provider involved in a particular request depends on the feature, deployment, region, customer configuration, and integrations selected.
This list should be read together with the Privacy Policy and Data Processing Addendum.
1. HOW TO READ THIS LIST
A provider is listed as a Subprocessor where it may process Customer Personal Data on behalf of LexLupi in providing Clocot.
Not every provider processes every customer's data.
Some third parties connected by a customer are not LexLupi Subprocessors because the customer contracts with them directly or directs Clocot to disclose data to them as an independent recipient.
2. VERCEL INC.
Service: Web application hosting, serverless execution, edge delivery, content delivery, deployment infrastructure, and related platform services.
Typical data: Request data, account and application data processed through the web application, technical logs, and content necessary to deliver the web service.
Processing location: United States and other infrastructure locations used by Vercel.
Role: Core infrastructure provider for the Clocot web application.
3. RENDER SERVICES, INC.
Service: Application, API, worker, background-service, or related cloud hosting where Clocot workloads are deployed on Render.
Typical data: Application requests, workflow data, logs, Customer Content processed by hosted services, and technical metadata.
Processing location: Depends on the deployed Render region.
Role: Infrastructure Subprocessor where the relevant Clocot service is hosted on Render.
4. NEON, INC.
Service: Managed PostgreSQL database infrastructure.
Typical data: Account records, tenant and workspace records, CRM information, configuration, workflow state, billing metadata, audit data, and other structured application records.
Processing location: Depends on the selected cloud and database region.
Role: Core database infrastructure provider where production PostgreSQL is hosted on Neon.
5. STRIPE, INC. AND STRIPE AFFILIATES
Service: Payment processing, subscription billing, checkout, invoices, refunds, dispute handling, fraud controls, and payment-related services.
Typical data: Billing contact information, transaction data, payment status, payment-method metadata, tax-related details, and payment-provider identifiers.
Processing location: Global Stripe infrastructure, depending on the transaction and Stripe entity involved.
Role: Payment provider. Stripe may act as an independent controller for certain payment and regulatory processing in addition to acting as a service provider for other functions.
6. GOOGLE LLC
Service: Google Analytics for public-site measurement where analytics consent is enabled; Google account or data integrations where configured; Google AI or cloud functionality only where enabled for the relevant feature.
Typical data: Website analytics data, technical identifiers, OAuth-authorized data, or AI input/output depending on the enabled Google service.
Processing location: Google's global infrastructure.
Role: Subprocessor or independent recipient depending on the specific Google service and customer configuration.
7. NAMECHEAP, INC. / PRIVATE EMAIL SERVICES
Service: Domain-related email hosting and email transport used for Clocot or LexLupi communications where Private Email infrastructure is used.
Typical data: Email addresses, email headers, message content, delivery metadata, and mailbox information.
Processing location: Provider infrastructure locations.
Role: Communications service provider where used.
8. OPTIONAL AI PROVIDERS
Clocot supports a provider architecture that may allow customers to select or connect third-party AI providers.
Depending on configuration, these may include providers of large language models, image generation, video generation, speech, voice, transcription, embeddings, search, coding, and model inference.
An optional AI provider processes Customer Personal Data only when a workflow routes data to that provider.
9. CUSTOMER-PROVIDED API KEYS
When a customer supplies its own AI Provider API key, the provider relationship may be directly between Customer and that provider.
In that case, the provider is generally not appointed by LexLupi as a Subprocessor for that direct account relationship, even though Clocot technically transmits data at Customer's instruction.
Customer should review the provider's terms, privacy policy, retention, model-improvement settings, and transfer locations.
10. CUSTOMER-CONNECTED INTEGRATIONS
Customer-connected services may include Google services, Meta services, LinkedIn, TikTok, email providers, CRM platforms, social networks, messaging services, analytics services, and other APIs.
These providers may act as independent controllers, processors engaged directly by Customer, or recipients instructed by Customer.
They are not automatically LexLupi Subprocessors merely because Clocot can connect to them.
11. PAYMENT DATA
Complete payment-card details are generally collected by the payment provider rather than stored directly by LexLupi.
Clocot may receive payment status, transaction identifiers, limited payment-method metadata, and billing information required to administer the transaction.
12. SUBPROCESSOR CONTRACTS
Where a provider acts as a Subprocessor, LexLupi seeks to impose appropriate contractual data-protection obligations consistent with the services provided and applicable law.
13. INTERNATIONAL TRANSFERS
Where a Subprocessor causes a restricted international transfer, LexLupi uses applicable transfer safeguards as described in the DPA and Privacy Policy.
14. CHANGES TO THIS LIST
The Clocot architecture will evolve and providers may be added, removed, or replaced.
Where applicable law or an enterprise agreement requires advance notice of a material new Subprocessor, LexLupi will provide notice through the Legal Center, email, account notification, or another appropriate channel.
15. CONTACT AND OBJECTIONS
Questions or legally valid objections concerning a Subprocessor may be sent to office@clocot.com.
The request should identify the specific provider and the concrete data-protection concern.
LexLupi LLC Privacy and Legal Contact: Tatjana Sindjelic