01
How to use this directory
The directory identifies recipients, triggers and necessary data, not unrestricted partner use. Linked notices identify entities, contacts, locations and rights channels. Request feature-specific information from [email protected] when needed. Listing does not itself complete statutory notice, transfer consent or processing safeguards. Model branding need not identify the contractual recipient; confirm routing or private integration requirements before submitting data.
02
Cloudflare: networking, security and R2
Pages and APIs using Cloudflare can involve IP, headers, connections and security events. R2-backed personal content and organisation assets involve uploaded content, object and access metadata. Processing can involve the United States and global infrastructure, without a single-country promise; product and customer terms determine roles and locations. Turnstile handles necessary security information when enabled.
03
Resend: email
Verification, reset, transaction, refund and support emails send recipient addresses, necessary message content and delivery state to Resend. Its notice identifies Plus Five Five, Inc.; processing can involve the US and service infrastructure. Avoid irrelevant secrets in email and distinguish marketing from necessary service notices.
04
Infobip: optional SMS verification and notices
Only when SMS is available and used, Infobip and necessary carriers receive numbers, codes or notice content, delivery and safety state. Locations depend on the contract and telecom route. Linking is not marketing consent and does not make the number a login or recovery credential.
05
Google: sign-in, fonts and optional analytics
Sign-in exchanges identity and email within scope; enabled drive connections separately transfer authorised files. Google Fonts requests carry connection information. Main-site Analytics loads only after optional acceptance and processes visits, devices and events, without granting advertising storage. Google entities and global facilities depend on the service and user region and can include the US.
06
GitHub: login, repositories and distribution
Login or repository operations can involve identity, authorisation identifiers, repository data, code and commits. Downloads send connection and download information. Processing follows GitHub services and US and other infrastructure. Login does not itself grant repository writes; review content and licences before public upload.
07
PayPal: payments and subscriptions
When used, PayPal processes orders, amounts, currencies, payer and transaction identifiers, subscriptions, refunds and disputes. It may directly collect payment instruments and identity. Entity and processing location follow the account region and payment documents. Use PayPal or relevant Laintas controls to manage renewal.
08
WeChat Pay: CNY payments
Payment involves orders, CNY amounts, transaction references, status and refunds, with Hubei Laintas Technology Co., Ltd. as the relevant merchant. WeChat directly processes its account and payment instruments. The payment confirmation identifies the actual institution and privacy terms. Refunds reconcile proportionately to the original amount.
09
Paddle: card merchant of record
For Paddle checkout, the identified merchant of record handles buyer, payment, tax, invoices, renewal and disputes and sends delivery-required order identifiers and state to Laintas. Its particular UK, US or other entity and rights follow purchase documents and its notice.
10
Creem: card merchant of record
Creem checkout involves buyer, payment, tax, order, subscription and refund state. Its public notice identifies Armitage Labs OÜ in Estonia. Check transaction documents for the entity and independent, joint or processing role; its suppliers may process elsewhere.
11
Dodo Payments: card merchant of record
This channel handles buyer, payment, tax, subscription, refund and fraud information; Laintas receives delivery and reconciliation data. The particular entity, region and contacts are identified by checkout, bills and provider notice rather than the brand alone.
12
NOWPayments: on-chain payments
Enabled on-chain payments involve assets, networks, amounts, addresses, hashes, status and necessary verification. Blockchain addresses and transfers are public, not automatically anonymous. NOWPayments identifies FD Transfers LLC; transaction documents govern the channel. On-chain refunds require your address and original proof, never seed phrases or private keys.
13
Serper and searched or fetched pages
Search and web tools can send queries, region and required URLs through configured paths, using Serper fallback or extraction when needed. Target websites and networks also process visits. Omission of query bodies from the console does not establish upstream non-retention.
14
Lium, Vast.ai and model download sources
Rental infrastructure receives deployment and necessary machine or connection information; runtime data is in the machine region and hosts may access underlying infrastructure. Model downloads may use Hugging Face, hf-mirror, ModelScope, GitHub or your source and involve downloads, tokens and connections. Actual suppliers and regions depend on order and choice. Laintas hosting and database infrastructure also process account and request data; request feature-specific information.
15
Models, own sources and Solvers
Cloud inference, media and summaries send content to the actual integrated service and downstream needed for the capability. Read model names with source labels, routing priority and chosen services, not as automatic processor identity. Own keys and selected Solvers are additional chosen sources; review upstream terms, regions and retention beforehand. Confirm actual arrangements with [email protected] before transmitting where strict recipients, no training or residency is required. This is not a guarantee about unspecified recipients, zero retention or fixed location and does not replace required notice and consent.
16
Routing changes and new recipients
Changing a model, Solver, own key, connector or location changes necessary recipients, and platform sourcing changes can affect content flows. New purposes, independent recipients, sensitive processing and transfers requiring renewed notice, separate consent or other procedures must complete those steps before processing, beyond adding a directory entry. Confirm a suitable route before submitting recipient- or location-restricted material; transmission cannot retrospectively become a different-region or zero-retention service.
17
Connection scope and revocation limits
When connecting identity, repositories, drives, MCP, devices or Solvers, check the provider, permissions and material sent. Read access does not authorise writing, publishing or deletion. Use separate, minimal credentials where possible. Revocation ordinarily blocks future access without reversing completed lawful transactions or automatically deleting recipient copies. Use recipient rights channels for their records, with Laintas assisting for its responsibilities; neither party can shift away its own legal duties.