Part of the Data Processing Agreement; see also Security and data protection and Security incident response.
The assistant cannot work without a language model. The whole product is the model. Conversation text, and for the merchant back office the shop data the assistant reads (customer name, email, phone, address, orders), is sent to the language-model provider to produce answers. There is no switch or opt-out for sending text to the model. A shopper who does not want this should not use the chat; the shop's own pages, checkout and support channels remain available. The merchant can switch the assistant off for its shop in its Codexta settings (Chat on your store).
What is hidden before it is sent. Nothing is removed from what reaches the language-model provider. Chat text is sent as the shopper wrote it. For the merchant's back-office assistant, the customer and order details it looks up (names, emails, phone numbers, addresses, orders, as listed in the
privacy policy) are sent as returned by the shop and are not masked. Codexta hides emails and phone-like numbers only in what its own staff see and in the stored record of unanswered questions.
Language-model providers
Conversation text that the assistant sends to the model is processed by the configured provider. The provider receives the conversation (the shopper's messages, the assistant's instructions, tool results such as product, order and customer data when a tool is used) to produce a reply. Only the two providers below receive conversation data. Both are engaged under their standard commercial contracts, under which, as Codexta understands them, the data is not used for training.
| Provider | Purpose | Data | Location | Masked first |
| DeepSeek (api.deepseek.com), the default model | Generate assistant replies | Conversation content including tool results | People's Republic of China, according to DeepSeek's published privacy policy. There is no adequacy decision for the People's Republic of China. DeepSeek's standard commercial terms apply; transfer safeguards beyond those terms are not claimed. | No |
| OpenAI (api.openai.com), the fallback model, used when the default is unavailable or slow | Generate assistant replies | Conversation content including tool results | OpenAI's Data Processing Addendum applies and covers transfers of European personal data. OpenAI may process data in the United States unless European data residency is configured. | No |
Hosting and infrastructure
| Provider | Purpose | Data | Location | Masked first |
| Amazon Web Services (AWS) | Runs the Codexta service: application, PostgreSQL database, file storage, and centralised logging with alerting. Proxy and application logs are kept for one month | All data Codexta holds for merchants | eu-central-1 (Frankfurt). AWS's standard data processing terms apply | Not applicable (stored in full, tenant-separated) |
| Amazon Web Services (AWS) | Backups of the production database | Copies of the above | AWS. Deleted data can remain in backups until they expire. Schedule, retention and encryption details are available on request to codexta@codecta.com | Not applicable |
Email delivery
| Provider | Purpose | Data | Location | Masked first |
| Microsoft (Microsoft 365 email), used for Codexta's own email sent from codexta@codecta.com (account, invitation and alert emails) | Send email from Codexta | Recipient address and message | Details available on request | No |
| The merchant's own mailbox provider (for example Gmail, Microsoft or any IMAP/SMTP server), only if the merchant connects a mailbox to the helpdesk | Read incoming mail as cases and send replies from the merchant's address | Mail content and addresses of the merchant's correspondents | Chosen by the merchant | No |
Apps the merchant chooses to connect
These receive data only after a merchant admin connects them in the support console. Each key is stored encrypted as that shop's secret and sent only to the app's own address.
| Service | Purpose | Data | Location | Masked first |
| Slack (slack.com) | Post new cases to a channel; replies in the thread return to the case | Case details and replies | Chosen by the merchant's Slack workspace | No |
| Linear (api.linear.app) | Create or link an issue from a case | Case details | Linear's regions | No |
| Stripe (api.stripe.com) | Show the customer's subscriptions and invoices beside a case (read-only key) | Reads Stripe customer data for the case's customer | Merchant's Stripe account | Not applicable (reading) |
| Notion | Re-sync imported Notion pages into the knowledge base (api.notion.com) | Title and text of the pages the merchant selects, read only | Merchant's Notion workspace | Not applicable (reading) |
| Instagram messaging (Meta), only if the merchant connects Instagram on a plan that includes it | Receive and answer the shop's Instagram messages | Message text and sender id | Meta's regions | No |
Platforms
| Platform | Role | Data | Notes |
| Shopify | The platform the merchant's shop runs on. Codexta calls Shopify's APIs with the merchant's installed app grant, and Shopify sends Codexta webhooks | Customer, order and product data under the app's granted access | Shopify processes this data under its own terms with the merchant, not as Codexta's subprocessor |
| WooCommerce / WordPress | The merchant's own site. Codexta calls the shop's REST API with keys the merchant provides | Customer, order and product data | The data stays on the merchant's server until read |
Changes
Codexta will update this page before adding or replacing a subprocessor that handles a merchant's personal data, and will notify merchants by email to the merchant's account contact 30 days before the change takes effect. A merchant may object to the change within that period. Last review: 14 November 2026.