Contents
1. Status and purpose
This V1 register distinguishes providers evidenced in production configuration from contractual facts supported by applicable vendor agreements. The operational entries below do not represent that an unavailable contract has been verified or execute a customer's subprocessor authorization. A provider's brand, a configured endpoint or a cloud deployment region does not, by itself, establish the contracting legal entity, controller/processor role or complete processing and remote-access locations.
A subprocessor is a provider engaged by Tessen to process covered Customer Personal Data on its behalf. A model provider, hosting vendor, analytics service or support tool may have different roles depending on its actual terms and activity. Technical integration alone does not establish that role.
2. Evidenced providers and processing scope
Each approved entry should identify the provider’s exact legal name, processing function, applicable product(s), relevant data categories, storage and remote-access locations, role, contract status, transfer mechanism where required, and the date/version of approval. Trading names should not replace the contracting legal entity. Location information should address processing and access, not merely headquarters.
Google Cloud. Production Cloud Run hosts the observed Web, Auth and Gateway services, and Cloud SQL hosts the production database. Those observed workloads are configured in us-east1, a United States region. This verifies the configured workload region, not all provider support, administrative access or onward-processing locations. The applicable contracting legal entity and contractual processor/subprocessor role have not been substantiated by a Tessen-specific vendor agreement available for this register.
Cloudflare. Production configuration and existing observations identify edge delivery, R2 file storage and Web Analytics/RUM on public Web and Platform pages. These services can involve request metadata, stored files or usage telemetry according to the enabled service. The observed configuration does not establish the account's contracting legal entity, the contractual role for each service or the complete processing and remote-access locations. An edge point of presence or R2 setting is not an all-data residency guarantee.
Resend. The production Auth configuration includes a Resend credential, and the reviewed mail integration uses Resend's email API for transactional communications. This establishes the configured communications provider and purpose. Its applicable contracting legal entity, contractual processing role and processing/remote-access locations have not been substantiated by a Tessen-specific vendor agreement available for this register.
Modal. The production Gateway has a configured Modal inference endpoint. Feature availability and actual use remain subject to enabled routes, entitlements and release controls. The configured endpoint hostname identifies us-west; that label does not substantiate all processing countries, support access locations or contractual restrictions. The applicable vendor legal entity and processor/subprocessor allocation have not been substantiated by a Tessen-specific vendor agreement available for this register.
Stripe. Existing production billing records identify Stripe-hosted Checkout and payment transaction references for prepaid funding. Stripe is not automatically classified here as a Customer-data subprocessor: the applicable merchant and processing agreements determine its legal entity and controller/processor roles. Those agreements and their applicable processing/remote-access locations have not been substantiated in the records available for this register.
These entries identify evidenced service use or configuration and its limits. Each provider above is in the category “contractual role not verified from available account-specific records”; none is designated an authorized customer subprocessor or an independent controller on configuration evidence alone. They are not represented as a complete, contractually verified subprocessor authorization list. Actual applicable vendor agreements determine recipient roles and contractual location terms; public vendor documentation alone does not prove which agreement Tessen entered into. Completing those account-specific particulars is a legal follow-up to this disclosure, not a claim that they have already been verified. Any additional requirements of an executed customer DPA remain applicable to its covered processing.
3. Register completion workflow
The technical owner should map each external recipient to a real data flow and identify whether content, metadata, secrets or support records are transmitted. The procurement/legal owner should verify the provider contract, role, confidentiality, processing restrictions, security evidence and any onward-processing chain.
Entries should be approved only after the role and lawful access are established. The review record should explain product scope, limitations and any customer configuration that changes the recipient. A provider used only for Tessen’s independent controller activities should be described in the appropriate privacy disclosure rather than incorrectly listed as a customer subprocessor.
4. Customer authorization and notices
The executed DPA determines whether Customer provides specific or general subprocessor authorization. Proposed changes should be notified through the agreed channel with the information needed to assess them. Subprocessor changes are notified and resolved using the authorization and objection procedure in the executed DPA. A technical integration change is not authorization to bypass that process.
The final register should preserve previous versions and effective change dates. Updating a public page does not satisfy a promised direct notice by itself. Emergency replacement may require special handling, but that handling must be agreed and lawful rather than assumed.
5. Objections and alternatives
A Customer objection should identify a specific, legitimate data-protection concern and the affected processing. The parties should consider whether the risk can be addressed through additional safeguards, configuration, an alternative provider or suspension of the affected feature. An objection is not automatically a right to control unrelated Tessen suppliers.
If no lawful solution is available, the parties must follow the DPA’s agreed termination or restricted-use procedure for the affected service. This register does not add a deadline, refund or substitute-capacity commitment beyond the applicable agreement. Statutory obligations and required protection remain applicable while resolving the concern.
6. Independent connected services
A service selected and authorized directly by a user through Connect may be an independent recipient or customer-appointed provider rather than Tessen’s subprocessor. The distinction must be assessed, explained and reflected in the appropriate agreement. The user’s authorization does not excuse unnecessary access or permit unrelated data use.
Model-provider routing also requires role-specific analysis. Different modes, endpoints or contractual plans can carry different processing conditions. A broad statement that “all providers follow the same policy” should not be used without verification.
7. Due diligence and ongoing review
Review should be proportionate to data sensitivity, access scope and service criticality. It should cover provider security and incident processes, deletion/return, confidentiality, onward transfers, model-training uses where relevant and audit information. Certifications should be listed only with verified scope and current evidence.
Material changes in provider practices must be assessed against existing commitments. Remove obsolete entries with a documented record of cessation and data handling. Review the register when adding products or changing routing; do not assume an approval for one product applies to every future service.
8. Requests and related documents
Customers may request current provider disclosures, relevant change notices and the appropriate data-processing documentation through hello@tessen.ai. Do not transmit confidential customer datasets with the request. Tessen, Inc.'s correspondence details are provided in the Terms and Privacy Notice.
This register should be read with the DPA, Privacy Notice, Connect Terms and Developer Terms. Operational configuration evidence and contractual subprocessor authorization are distinct; this register does not supply missing contractual evidence.