Contents
1. Status and purpose
This V1 register is a draft disclosure framework. No provider entries have been verified for publication in this package. This does not mean that Tessen uses no providers or that no personal data is processed externally. The register must be populated from actual contracts and data flows before an organization relies on it for procurement or DPA approval.
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. Required register fields
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.
[COMPANY DETAIL REQUIRED: verified subprocessor inventory and completed entries, including model, execution, infrastructure, storage, authentication, support and other actual processing providers.] Do not populate this register with inferred vendors, suggested tooling or a vendor logo found in the interface.
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. [LEGAL REVIEW REQUIRED: authorization mechanism, advance-notice period, customer notification channel and objection/resolution terms.]
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. No deadline, refund or substitute capacity is promised by this draft. 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 ask for the current verified register, relevant change notices and the appropriate data-processing documentation through hello@tessen.ai. Do not transmit confidential customer datasets with the request. The final legal/privacy contact remains subject to entity confirmation.
This framework should be read with the DPA, Privacy Notice, Connect Terms and Developer Terms. It offers a substantive disclosure process while expressly leaving unverified vendor facts open for completion.