Codexta
PackagesCommerceService & knowledgeHow it worksSecurityPricingDocsCompareFAQStart a pilot ↗
CODEXTA / LEGAL

Data Processing Agreement

How Codexta processes personal data on behalf of the merchants who install it on their shop. Last updated 14 November 2026.

Contents
  1. Parties and roles
  2. Subject matter and purposes
  3. Data and data subjects
  4. Instructions and confidentiality
  5. Subprocessors
  6. International transfers
  7. Security measures
  8. Personal data breach
  9. Data subject requests
  10. Retention and deletion
  11. Return and deletion on termination
  12. Audit
  13. General terms
  14. Contact

1. Parties and roles

This agreement is between the merchant that installs Codexta on its shop (the Merchant) and Kodecta d.o.o., Vrbanja 1, 71000 Sarajevo, Bosnia and Herzegovina, company ID number 4202090890006, which operates Codexta (Codexta).

DataMerchantCodexta
Shopper and customer data in the shop and in chats with the assistant (including customer and order data the Merchant's own team asks the back-office assistant about)ControllerProcessor
The Merchant's own account: staff names, emails, roles, billing contactController of its own staff data as employerController for operating the account, as stated in the privacy policy

The Merchant's platform (Shopify or WooCommerce) holds the shop's customer and order records and sends them to Codexta only as described below. For data held in Shopify, Shopify processes it under its own terms with the Merchant; Shopify is not a subprocessor of Codexta for that data. For WooCommerce the shop's own server is the source of the data.

2. Subject matter and purposes

Codexta provides an AI chat assistant for shoppers, a back-office assistant for the Merchant's team, and a helpdesk (support console). Codexta processes personal data only to provide those services to the Merchant, namely to:

  • answer shoppers' questions and show them their own orders when they sign in;
  • answer the Merchant's team's questions about its customers, orders and products in the back-office assistant;
  • hand a chat to a person on the Merchant's team and keep tickets, return requests and mail in the helpdesk;
  • report to the Merchant how many chats, unanswered questions and orders followed a chat (counts and order id, total and time only);
  • operate, secure and troubleshoot the service.

Codexta does not sell personal data, does not use it for advertising and does not use it for a purpose of its own. Codexta does not use conversation text to train or tune models, and under its contracts its model providers do not use it for training either.

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).

3. Data and data subjects

Data subjects: the Merchant's shoppers and customers (signed-in and guest), and the Merchant's staff.

CategoryDetail
Chat contentMessages a shopper writes, the assistant's replies, and anything personal the shopper chooses to type.
Shopper identityFor a signed-in shopper, the shop's customer id and the shopper's own orders when they ask. A guest is not identified beyond an anonymous session.
Contact details given in a ticket or live chatName and email.
Customer data read for the Merchant's team (back-office assistant)Shopify: customer name, email, phone, default address, tags, note, order count and spend, recent orders; order lists with order number, date, status, total and customer name; for one order, the shipping address. WooCommerce: customer name, email, billing phone and address, note, order history; orders with billing name, email, billing and shipping address and the customer's note. The assistant can also run a read-only query against the shop's API for anything else the shop's access grant allows. These results are part of the conversation: they are sent to the language-model provider and stored in the conversation history.
Order attributionOrder id, total and time of orders that followed a chat. The webhook that carried the order, which names the buyer, is blanked after processing.
Merchant staffName, email and role in the shop.

Codexta does not ask for payment card details, passwords or government ids and the assistant is told not to collect them. The Merchant must not use Codexta to process special categories of data on purpose; if a shopper types such data into a chat, it is stored like any other chat content.

4. Instructions and confidentiality

Codexta processes personal data only on the Merchant's documented instructions, which are this agreement, the Merchant's use of Codexta's settings and the back-office assistant, and its written requests. Codexta will tell the Merchant if it believes an instruction breaks data protection law. Codexta staff access to a shop's conversations is limited and recorded (section 7). Everyone with access is bound by confidentiality.

The Merchant is responsible for its legal basis for processing, for telling its shoppers that an AI assistant is used (the chat window shows the notice "AI assistant. It can make mistakes, so check important information." with a Privacy link and it cannot be switched off), and for mentioning Codexta in its own shop privacy policy.

5. Subprocessors

The Merchant gives general authorisation for the subprocessors on the subprocessors page. Codexta will update that page before it adds or replaces one that handles the Merchant's personal data and will notify merchants by email to the Merchant's account contact 30 days before the change takes effect. The Merchant may object to the change within that period. Codexta imposes data protection terms on each subprocessor that are no less protective than these, and remains responsible for them. DeepSeek and OpenAI are engaged under their standard commercial contracts,, OpenAI's Data Processing Addendum applies to Codexta, and AWS's standard data processing terms apply to hosting.

6. International transfers

The production stack is hosted on Amazon Web Services (AWS) in the eu-central-1 region (Frankfurt). Conversation text that the assistant sends to the model is processed by the configured language-model provider, and the two providers named on the subprocessors page process data outside the EEA and the UK, or may do so:

  • DeepSeek. According to DeepSeek's published privacy policy, data sent to its service is processed and stored in the People's Republic of China. 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, and no standard contractual clauses are claimed with DeepSeek.
  • OpenAI. OpenAI's Data Processing Addendum applies to Codexta and covers transfers of European personal data. OpenAI may process data in the United States unless European data residency is configured.

7. Security measures

These are the measures that exist in the product today. Measures not listed here are not claimed. The fuller statement, with the Shopify requirement evidence table, is on the Security and data protection page.

  • Tenant separation. Every shop's conversations, notes and settings are stored under that shop's tenant id and every query is filtered by it. The production database is PostgreSQL on AWS. Row-level security is not claimed.
  • Encryption in transit. The public site is served over HTTPS with TLS 1.2 and 1.3 and an HSTS header; plain HTTP requests are redirected.
  • Secrets encrypted at rest. Platform access tokens and the shop's integration keys are stored encrypted (AES-256-CBC with an HMAC-SHA256 integrity check) with a key kept outside the database in database mode. Credentials are never logged or shown to the AI.
  • Webhook and install authentication. Shopify webhooks and installs are accepted only after their HMAC signature verifies. Processed webhook bodies are blanked.
  • Limits on Codexta staff. Staff see conversations with emails and phone-like numbers hidden by default. Showing the unmasked text is a separate action that writes an audit row before the text is returned. Acting inside a shop requires a written reason, lasts 60 minutes and is tied to one shop and one named staff member. The audit log is append-only (the database refuses updates and deletes) and the Merchant can see the entries for its shop in Settings › Team.
  • Roles on the Merchant side. Only owners and admins can change the assistant's settings. The back-office assistant is never offered to shoppers, and a change it proposes (a price, a customer note) is made only after the Merchant confirms that exact change.
  • Production separation. Test-only secrets and fake-shop switches are refused at startup in any environment except local Development. A test-mode conversation does not run tools against a real shop.
  • Backups and disk encryption. Production backups are kept on AWS. Deleted data can remain in backups until they expire. Schedule, retention and encryption details are available to merchants on request at codexta@codecta.com; encryption at rest of the database is not claimed here.
  • Incident response. Codexta keeps an incident response procedure, summarised on the Security incident response page. The incident lead is Amel Music and the deputy is Emir Causevic. The out-of-hours contact is Amel Music, amel.music@kodecta.com.
  • Customer data access log. Each time a member of the Merchant's team looks up a customer or an order through the back-office assistant, the lookup is recorded: which staff member, which customer or order, and when. The returned data is never recorded. Owners and admins can read the log in Settings › Team. It is kept for 12 months, and a monthly review is recommended.
What is not hidden from the language model. Codexta hides emails and phone-like numbers in staff views and in the record of unanswered questions. It does not remove personal data from what is sent to the language model: chat text, and customer and order details the back-office assistant reads for the Merchant's team, are sent as written.

8. Personal data breach

Codexta will notify the Merchant without undue delay after becoming aware of a personal data breach affecting the Merchant's data, and in any case within 72 hours of becoming aware. The notice will say what happened, which data and shops are affected as far as known, what Codexta is doing and who to contact. Codexta will help the Merchant meet its own duty to notify the supervisory authority and affected people, and will tell Shopify where Shopify's rules for apps with protected customer data require it. For the data where Codexta is itself the controller, the competent supervisory authority for Kodecta d.o.o. is the Agency for Personal Data Protection in Bosnia and Herzegovina (Agencija za zaštitu ličnih podataka u BiH), Dubrovačka 6, 71000 Sarajevo, www.azlp.ba. Bosnia and Herzegovina adopted a new Law on Personal Data Protection on 30 January 2025, in force since 8 March 2025; refer to the authority's site for the current text. A Merchant established in the EU also has its own supervisory authority.

9. Data subject requests

Codexta will help the Merchant answer requests for access, correction, erasure, restriction, portability and objection, taking into account the nature of the processing. If a shopper writes to Codexta, Codexta will pass the request to the Merchant unless it is about Codexta's own data.

  • Shopify. The customer erasure request that Shopify sends (customers/redact) is handled automatically: the person's conversations, tickets, preferences, uploads and order attributions in Codexta are deleted. The data request (customers/data_request) is received automatically; Codexta provides the Merchant with an export of that person's data held in Codexta. The export is a JSON file that the Merchant's owners and admins download in the Codexta admin under Settings, in the Data requests list. It is kept for 30 days and then deleted, and admins who have an email address on file get a mail notice when it is ready.
  • WooCommerce. Deleting a customer in WordPress deletes their conversations in Codexta.
  • Shopper control in the widget. The shopper can delete their own conversations with the Delete my chats option (the trash icon in the chat header, with a confirmation step). It deletes the shopper's own chats and keeps support tickets and return requests.
  • Other requests go to codexta@codecta.com and are answered within 30 days.

10. Retention and deletion

DataKept for
Conversations and their event recordsBy plan: 30 days (Lite), 60 days (Start), 90 days (Growth), 365 days (Scale), counted from the last activity in the conversation. A nightly job at 03:30 UTC deletes expired ones; a conversation still running is kept.
Parked helpdesk mail records (sender and subject)90 days, whatever the plan.
Stored webhook bodiesBlanked as soon as processed; the rows themselves are deleted after 30 days.
Files made available for download (chat attachments, report exports)14 days.
Daily statisticsCounts only, no text and no person; kept.
Order attributions (order id, total, time)Hold the order id, value and the link to the chat, with no name, email or address. Kept while the shop is active; deleted when the person is erased, when the order is deleted in the shop, and when the shop is purged after uninstall.
Shop uninstalledAll of the shop's data is deleted 48 hours after uninstall by the nightly job. The Shopify shop/redact request is handled automatically.
Staff audit logAppend-only; kept while the shop is active, with no expiry job.
BackupsBackups exist on AWS; deleted data may remain in backups until they expire. Retention details are available on request at codexta@codecta.com.

11. Return and deletion on termination

When the Merchant uninstalls Codexta, Codexta deletes the shop's data after the 48-hour period above (reinstalling within that period keeps it). Before that, or on request to codexta@codecta.com, Codexta will provide an export of the Merchant's data on request, within 30 days, as JSON. Codexta will confirm deletion on request. Data that law requires Codexta to keep stays, with a notice to the Merchant.

12. Audit

Codexta will give the Merchant the information needed to show compliance with this agreement, including the answers to a reasonable security questionnaire. The Merchant may audit Codexta, or appoint an independent auditor, once a year and after a personal data breach, on 30 days' written notice, in working hours and under confidentiality, at the Merchant's cost. Codexta holds no SOC 2 or ISO 27001 certificate.

13. General terms

This agreement applies for as long as Codexta processes the Merchant's personal data and forms part of the terms under which the Merchant uses Codexta. If the two conflict on data protection, this agreement prevails for the processing of personal data. Liability under this agreement is subject to the limitation of liability in the Codexta terms of service. This agreement is governed by the laws of Bosnia and Herzegovina, and the courts of Sarajevo have jurisdiction.

14. Contact

Data protection questions and requests: Amel Music, amel.music@kodecta.com, or codexta@codecta.com.

← Codexta overviewData Processing Agreement · Subprocessors · Incident response · Security · Privacy policyContact