CHAT4U LEGAL
Data Export and Switching Schedule
Last updated: November 4, 2026
1. Scope and relationship to the Agreement
This Schedule forms part of the Terms of Service between Chat4U and the Customer. Its switching provisions apply to the extent the relevant Service and Customer fall within Chapter VI of Regulation (EU) 2023/2854 (the "Data Act"), including covered Services supplied to customers in the European Union. Section 8's protections under Article 32 apply within their own statutory scope, independently of eligibility for switching or an exception under Article 31. This Schedule does not limit switching, portability, return, deletion or other rights arising under another applicable law or the DPA. Capitalized terms not defined here have the meanings in the Terms.
A free plan is not excluded merely because no fee is paid. A special regime for a genuinely custom-built service, or an exclusion for a limited-period, non-production testing or evaluation service, applies only where its legal conditions are met and we have informed the Customer before contracting of the obligations that do not apply. A standard configured assistant, a preview label or the description of a live deployment as a pilot does not alone establish an exception.
This Schedule concerns the affected hosted service and data. Ordinary subscription cancellation, an individual privacy request and switching have distinct purposes and timelines. The initiation notice below does not delay ordinary cancellation, a required privacy response or an already-due refund. The Customer's or a visitor's nationality, a project's default country field or a missing billing-address field does not alone determine statutory eligibility.
You may also request interoperability for use of the Service alongside another data processing service through the contact route below. Where Article 34 applies, we facilitate that use with the applicable cooperation, continuity, security, data-category and interface protections, including sections 6 and 7 as relevant. A request solely for copying or parallel use does not terminate the existing Service or begin post-termination retrieval or erasure. We confirm which scope, if any, you intend to terminate separately. The existing Agreement and its ordinary service charges continue for retained services. Section 5 concerns switching charges; this Schedule introduces no parallel-use tariff or blanket waiver of ongoing parallel-use charges. Any such charge must have a lawful contractual basis and comply with applicable cost limits. Required open interfaces remain free of charge.
2. Request, authority and initiation notice
Send a switching request to support@chat4u.ai. Identify the account and affected project or Service and the requested scope. You may choose one or more of the following for the identified scopes: move to another provider, move to your own infrastructure, or end the affected service and erase its exportable data and digital assets. You may confirm those choices and provide necessary destination-provider details at the end of the initiation notice period, or earlier, as permitted by the Data Act. We will provide relevant information to support your exit strategy and explain known methods, limitations and continuity risks.
We verify identity, authority and any destination access proportionately, using existing account information where sufficient. An authorized destination provider may assist you. We will promptly identify missing information needed for safe performance; routine routing, clarification or verification does not restart a valid request's statutory clock. A particular form or legal phrase is not required. A limitation of the dashboard does not prevent a request through support.
The initiation notice is no more than two months from receipt of your switching request, subject to an earlier start agreed with you and any shorter applicable legal requirement. We may start sooner where practical. We will confirm the affected scope, initiation date, transition arrangements, known limitations and applicable retrieval dates. Ordinary contracted service continues during this notice as applicable, subject to lawful protective action that does not defeat mandatory switching or safe data-access rights.
3. Transition, assistance and extensions
The transition begins when the initiation notice ends or on an earlier agreed date. We will enable switching without undue delay and ordinarily within no more than 30 calendar days from that start. During the transition we will provide reasonable assistance to you and your authorized destination provider, act with due care to maintain business continuity, continue the contracted functions or services as applicable, inform you of known continuity risks and maintain the required level of security during transfer and retrieval.
If completing the transition within that period is technically unfeasible, we will notify you within 14 working days after the switching request, explain and justify the technical reasons, and identify an alternative transition period not exceeding seven months. The continuity and security duties continue during that alternative period. Administrative inconvenience alone is not a technical justification.
Separately, you may extend the transition period once for a period you consider more appropriate for your purposes, as provided by Article 25(5). The seven-month limit on our technically justified alternative does not automatically cap your separate statutory extension right. We will record the revised dates and explain the ordinary service charges, if any, applicable under the existing Agreement; an extension is not permission to impose an undisclosed new charge or to revive a stopped recharge authorization.
Both parties will cooperate in good faith. We will agree practical capture and transfer arrangements, including any necessary final update, so ongoing changes do not produce an incomplete or inconsistent handover. Preservation of a scoped copy must be lawful, necessary for the request and protected; it is not a general extension of all retention. You remain responsible for arranging and configuring your destination environment and for permissions needed for its receipt and use of data. We remain responsible for our own export and assistance duties. We do not guarantee that another provider will reproduce Chat4U's features or rebuild our Service in its environment.
4. Completion, termination and retrieval
Upon successful completion of switching, the Agreement for the affected Service is considered terminated and we will notify you. We will confirm the transition's end and the retrieval period; successful earlier completion is not postponed merely to use the maximum period. Passage of time, creation of an incomplete file or an unsuccessful download is not itself successful completion. If an attempt fails, we will identify the remaining work and cooperate on a lawful completion or alternative arrangement rather than falsely recording success. Separable unaffected services continue under their Agreement.
For a request to end the affected Service and erase its exportable data and digital assets without switching, the affected Agreement ends at the end of the initiation notice, or an earlier applicable or agreed date, and we will notify you of that termination. This confirms the end of the affected Agreement; completion of erasure is recorded separately. The erasure request is handled under the DPA and applicable law. No export or retrieval period is forced on a customer who lawfully requests deletion instead, and an earlier mandatory deletion deadline remains effective.
After the agreed transition ends, we provide 30 calendar days for secure retrieval of the covered exportable data and digital assets, subject to any longer period required by law or separately agreed. This is access to the covered data, not an additional free period of operating assistants. It remains available through secure interfaces or support after ordinary dashboard access ends. Short-lived download links can be reissued during that period; an expired link or replacement of an export file does not shorten the retrieval right. We will communicate the retrieval deadline and available means of access.
Where successful switching is followed by expiry of the retrieval period, or an agreed later retrieval period, we will fully erase the exportable data and digital assets generated directly by or relating directly to the Customer, subject only to applicable lawful retention requirements. The DPA governs personal data, including the limits on legally required retention. Required accounting or contract records are restricted to their separate lawful purpose and do not justify keeping unrelated service content. We address relevant derived, supplier and backup copies and distinguish incomplete cleanup from verified erasure.
Privacy and data-protection law prevail in an actual conflict. A valid earlier erasure obligation, withdrawal of necessary authority or binding integration condition is assessed for its precise scope and any applicable legal exception. We will explain a material restriction and cooperate on a lawful sequence or delivery method. We will not invoke a general provider policy or routine cleanup as a blanket excuse to defeat a mandatory retrieval right, or retain prohibited data merely to regenerate an export. Shopify-specific cleanup is addressed in DPA section 10 and Retention section 6.
5. Charges and refunds
We charge no separate switching fee for the standard export, legally necessary switching assistance, required interfaces or data transfer, or the required retrieval period under this Schedule. This applies from the Schedule's activation; we do not impose a temporary switching charge before the Data Act's 12 January 2027 prohibition takes effect.
Normal charges for contracted service actually provided before the applicable termination remain governed by the existing Agreement, subject to law and applicable remedies. We stop future billing and new recharge purchases for the terminated scope in accordance with the applicable termination; already submitted transactions and amounts properly due are reconciled separately. Switching does not itself create a new early-termination penalty, remaining-term charge, new fixed-term subscription commitment or forfeiture of an accrued refund. Any service continuation required during the transition is handled under the existing Agreement and mandatory duties, with its applicable ordinary charges explained; it is not authorization for an undisclosed new purchase.
The Refund Policy, applicable Order, provider transaction terms and mandatory rights determine any refund of unused prepayment or credits. This Schedule does not create an additional unconditional refund or override a refund otherwise due. A fee dispute does not justify withholding an export or assistance where the law requires it.
Optional work genuinely beyond our legal and existing contractual duties, such as building a bespoke destination connector or configuring another provider's product, may be separately scoped and priced with your prior agreement. Necessary standard assistance cannot be relabelled as optional custom work. Work needed to correct our failure to meet an existing obligation is not charged as a switching extra.
6. Exportable categories and protected exclusions
The following categories cover the Service's customer input, output and usage-generated metadata and the digital assets you have an independent right to use. The applicable subset depends on your enabled features and records lawfully held when the request is performed. A category is not excluded merely because it is generated, derived, non-personal, associated with a free plan or omitted from a dashboard export. A package identifies its scope, included categories and any specific omission or exclusion with its reason.
| Exportable category | Included records and relationships |
|---|---|
| Account, workspace and project configuration | Customer account/project identifiers, names, domains, relevant descriptions, preferences and configuration; authorized membership and role relationships needed to interpret or administer the Customer's data. No unrelated person's account or cross-customer records. |
| Assistants and customer configuration | Assistant identities, customer-supplied instructions and prompts, selected behavior and model settings, widget appearance, customer-defined forms, questions, handoff settings and source assignments; customer-owned persona material, images and other supplied assets. |
| Knowledge and content | Customer-supplied or authorized source files, text, pages and store-product records held in the Service; source identifiers and provenance, relevant extracted content, structure, chunks, metadata, customer-specific indexes and embeddings within the exportable scope. Specific third-party rights or protected internals are assessed under the exclusions below, rather than treating all processed knowledge as proprietary. |
| Conversations and communications | Retained production and demo conversations, customer/visitor and assistant messages, timestamps, channel and relationship metadata, relevant attachments and stored media, transcripts, descriptions and structured response components within the Customer's lawful scope. |
| Leads and human-help handling | Captured fields, recorded permission evidence, relevant request, routing, handoff, delivery and recovery status and customer-directed destination references. Transfer does not reveal unrelated recipients or create authority for new marketing. |
| Customer-specific analysis and outcomes | Retained summaries, classifications, scores, insight records, feedback, metrics and related metadata generated from the Customer's use, including relationships needed to interpret them. Shared cross-customer analysis is handled under the exclusions below. |
| Commerce and integration records | Lawfully retained customer-specific product mappings, connection/configuration metadata, cart/action results, consent/attribution and purchase/refund outcome evidence, relevant status and recovery references. Native merchant orders are exported only to the extent lawfully held and within scope; temporary private order answers or proofs already removed are not reconstructed. |
| Owner assistance and authorized tool activity | Retained customer instructions, conversations, results, customer-specific configuration and relevant action/approval metadata, subject to other people's rights and protection of credentials and internal security mechanisms. |
| Usage, entitlement and customer service records | Customer-specific usage and allowance history, customer-facing subscription/payment references, authorization evidence, service requests and correspondence within scope, excluding internal supplier finances or legally protected third-party material. Independent records and individual privacy rights retain their own lawful treatment. |
| Portable digital assets and supporting metadata | Other customer-supplied assets and customer-specific elements the Customer has an independent right to use; identifiers, relationships, schemas, timestamps, source references, applicable permissions and provenance needed to make included data usable. This category covers qualifying items not confined to a single enabled feature above. |
The following are protected exclusions to the extent legally applicable. We distinguish an excluded internal mechanism from the Customer's exportable records processed by it:
- Chat4U's proprietary source and object code, shared orchestration logic, shared internal prompt templates, platform configuration and implementation of ranking, routing, security or abuse-detection systems, where protected by our intellectual-property rights or trade secrets. Customer-authored instructions and exportable configuration do not become excluded merely because used with those systems.
- Proprietary provider model weights and third-party software or assets for which the Customer has no independent right of use. Open-source and other independent licences, including the official plugin's applicable licence, remain effective.
- Shared infrastructure topology, internal security rules, vulnerability details, secrets, passwords, tokens, signing/encryption keys and internal access-control mechanisms whose disclosure would compromise security or reveal protected internals. Necessary customer configuration or permission metadata is supplied in a safe form where required; access credentials are separately re-established through an authorized process.
- Cross-customer or another customer's records, other persons' data outside the Customer's lawful authority, and genuinely protected internal business, supplier-pricing, privileged or trade-secret material. Separability is assessed so a mixed record does not automatically exclude the Customer's otherwise exportable information.
We will identify and explain a relied-on exclusion sufficiently to permit it to be understood or challenged without disclosing the protected material. An internal trade-secret exclusion must not impede or delay switching contrary to Article 23. Legitimate security and rights checks remain proportionate. We are not required to disclose protected technology or compromise service integrity; nor may those protections be used to withhold exportable customer data categorically. Data lawfully erased before a preservation duty arose, never held by us or held solely in an independent destination are not represented as available Chat4U records. We will explain material availability limits.
7. Methods, structures, formats and interfaces
This section is the online register of the export structures and formats for the categories above. We keep it and the associated interface information current. The package uses structured, commonly used, machine-readable formats and includes the information needed to interpret the included records.
| Structure | Format and interpretation |
|---|---|
| Package manifest and schema description | UTF-8 JSON describing the covered projects, generation/capture time, categories, parts and assets, record counts, schema versions, integrity checks and any exclusion or availability limitation. Field descriptions identify types, units, relationships and relevant null or unavailable states. |
| Structured records and configuration | UTF-8 JSON, or newline-delimited JSON for large record sets. Records use stable identifiers within the export, explicit relationship references and ISO 8601 timestamps with timezone information. Supplied configuration and metadata are separated from credentials and protected internals. |
| Text and extracted knowledge | UTF-8 text or Markdown, together with JSON metadata linking content to its source, project, version and related records where retained. Customer-specific vectors within scope use numeric arrays with available model/dimension metadata; this does not supply a model licence or guarantee destination compatibility. |
| Files, images and other media | Original retained format where available, with a manifest mapping file references, media type and integrity information. Where only a processed version is lawfully retained, it is identified as such. Secure links are a delivery mechanism, not a substitute for the underlying file during the retrieval period. |
| Multi-part delivery | Numbered or identified parts with a manifest that permits completeness and integrity checks and continuation after an interrupted transfer. A single-file size cap does not silently truncate required scope. |
We make documented open interfaces available free of charge, to an equal extent, to covered customers and their authorized destination providers for portability and interoperability. Authentication and authorization restrict access to the proper scope. Interface information identifies supported requests, field/schema definitions, pagination or continuation, limits, errors, download and retrieval procedures sufficiently to develop software communicating with the Service for these purposes. Support arranges authorized access and assistance without granting internal operator privileges. Security controls must not create unjustified obstacles or reserve a required interface for a higher-priced plan.
Where applicable common specifications or harmonized interoperability standards are published in the relevant Union repository, we will comply within the legally applicable period, including Article 30(3)'s period following publication, and update the register accordingly. We do not claim an interoperability certification or guaranteed direct import into every destination. Before contracting, and as relevant service information changes, we provide the available switching/porting methods and known restrictions, including a service whose switching is highly complex or costly or cannot occur without significant interference in data, assets or architecture. We explain relevant transformations and necessary cooperation before the transfer step. Current knowledge ingestion supports authorized URLs/pages, files, supplied text and supported native connections as described in the Service documentation; this does not imply an importer for every other provider's complete application export. Format updates cannot silently remove a contractual or mandatory export right.
8. Infrastructure jurisdictions and governmental requests
Chat4U is operated by the Israeli entity identified in the Terms. The configured primary application database and file storage are in AWS's Frankfurt region in Germany, with the relevant AWS seller identified as Amazon Web Services EMEA SARL in Luxembourg. Enabled LangSmith tracing uses its US endpoint. These statements distinguish operational control, contractual entity and primary storage; they do not promise that every provider, support operation, website delivery or onward processing occurs in those locations alone.
The Subprocessors and Providers disclosure, particularly sections 2, 3 and 5, forms the linked service/provider register for the relevant infrastructure, processing and further-provider information. We keep service-specific infrastructure-jurisdiction information current, distinguishing physical processing locations from corporate establishment and applicable legal authority. Customer-selected merchant hosts, channels and destinations have their own arrangements. The Security Measures describes relevant access, encryption and operational safeguards.
For non-personal data held in the Union, we take adequate technical, organizational and legal measures, including relevant contractual protections, to prevent third-country governmental access or transfer that would conflict with Union or applicable Member State law. These include restricted access, appropriate encryption, review of the requesting authority, jurisdiction and legal basis, assessment of applicable international agreements or statutory conditions, proportionate challenge where legally required, minimization of any lawful disclosure and notification where legally required and permitted. We do not grant access solely because a foreign request is labelled compulsory or because a supplier can technically retrieve the data. Applicable personal-data and confidentiality protections apply separately. This is not a guarantee that no lawful authority can ever obtain data.
Where Article 32 applies, we inform the Customer of the existence of a third-country authority's request to access its data before complying with that request. The exception is where the request serves law-enforcement purposes, and only for as long as withholding notice is necessary to preserve the effectiveness of that law-enforcement activity. Administrative inconvenience does not excuse this required notice. This specific rule is distinct from other notification duties that may apply to personal data or other requests.
9. Priority, changes and contact
This Schedule prevails over an inconsistent ordinary export, access-cutoff, service-expiry or charge provision within its mandatory switching scope. The DPA and applicable data-protection law govern personal-data handling, with mandatory law controlling an actual conflict. Terms section 17 continues to govern contractual liability to the extent lawful; this Schedule creates no separate damages allowance or waiver of a non-excludable remedy.
Material changes to this Schedule follow Terms section 19 and applicable law. The accepted version remains reproducible with the Agreement. Updates to the format register explain changed formats and limitations without retroactively narrowing an accepted right. We preserve the necessary request, authority, scope, dates and completion evidence under their justified retention category, without keeping the exported content indefinitely as evidence.
Switching and service support: support@chat4u.ai. Individual privacy rights and data-protection questions: privacy@chat4u.ai. A request received through either relevant channel is routed appropriately without restarting its valid deadline.
English is the controlling language of this document. Version: 2026-11-consolidated-v1. Permanent link to this version. SHA-256: fca7a1cb47acbf1fb12f7e5c7055ac9914fec7321c7ae0a4e2d386c5124fb28f.