Version 1.0, 16/11/2026. This agreement is accepted when a store is created on Codeator Stores or a plan is subscribed to, and it is part of our Terms. A new version is announced as set out in section 13.
1. Parties
Controller: the merchant who runs a store on Codeator Stores, on any plan including the free plan (“you”).
Processor:
Abdullah Mahmood Abdulqadir Al-Imam, trading as Codeator
Kolonnenstr. 8, 10827 Berlin, Germany
Phone: +49 1522 3324433
Email: [email protected]
(“Codeator”, “we”).
2. Subject, duration, nature and purpose
Subject: Codeator hosts and runs your online store on the Codeator Stores platform: the storefront, the admin panel, the store’s mobile app where your plan includes it, the shop counter (point of sale), the messages the store sends, and support.
Nature of the processing: storing, organising, showing, changing, sending (for example to a courier you have connected), backing up and deleting data, and answering requests to the AI assistant in the panel and in the storefront’s chat.
Purpose: only to provide the store to you as the Terms and your settings describe.
Duration: for as long as your store exists on the platform, and after that until its data has been deleted or returned as section 11 says.
3. Types of data and data subjects
Your customers (shoppers) and guests of your store: name; phone number; email address if given; password (stored only as a hash); delivery addresses, including a location pin where the shopper sets one; orders, their amounts, the payment method (today cash on delivery) and their history; wallet entries; messages and pictures in the store’s chat; back-in-stock and price requests; sign-in sessions and logs of one-time codes; the store app’s installation and push notification tokens; browser push subscriptions; and, where analytics are on, a pseudonymous analytics ID.
Your staff, sales representatives and cashiers: name, phone number, email, user name, password (as a hash), role, last sign-in, the cashier’s PIN (as a hash), and the record of the changes they make in the panel.
Others whose data you enter: suppliers (name, phone number) and people named on counter debts (name, phone number).
The platform is not built for special categories of personal data (Art. 9 GDPR). Do not enter such data in your store.
4. Instructions
We process the data only on your documented instructions. Your instructions are this agreement, the Terms, the settings you make and the actions you take in your store’s panel, and anything further you write to us at [email protected]. If the law of the EU or of a member state requires us to process data otherwise, we tell you before we do, unless that law forbids it.
If we think an instruction breaks data protection law, we tell you at once, and we may hold it until you confirm or change it.
5. Confidentiality
Everyone at Codeator who can reach your store’s data is bound to confidentiality, by contract or by law, and sees it only as far as their work needs it.
6. Security of processing
We take the technical and organisational measures of Art. 32 GDPR described in Annex 1. We may improve them; we never lower the level of protection they give.
7. Sub-processors
You give us a general authorisation to use other processors. The ones we use today are listed in Annex 2. We bind each to the same data protection obligations as this agreement.
We tell you of any intended addition or replacement at least 30 days in advance, by email to your store’s account owner and on this page. You may object within that time for a reasonable reason relating to data protection. If we cannot meet your objection, either of us may end the subscription at the time the change takes effect, and we refund what you paid for the time after it.
8. Requests from data subjects
We help you answer people who use their rights under Chapter III of the GDPR. Your panel shows your customers’ and staff’s data, and your customers can delete their own account from your store. When an account is deleted, its addresses, sessions, linked sign-ins, push tokens and location pins are removed, its name, phone number, email and password are cleared, and its chat messages and pictures are blanked; orders keep their own copy of the name, phone number and address. If a request reaches us directly, we pass it to you without delay and do not answer it ourselves unless you instruct us to.
9. Other assistance
We help you, taking into account the nature of the processing and the information available to us, with security (Art. 32), notifying personal data breaches (Art. 33 and 34), data protection impact assessments and prior consultation (Art. 35 and 36).
10. Personal data breaches
If we become aware of a breach affecting your store’s data, we tell you without undue delay, and we aim to do so within 24 hours, by email to the store’s account owner. We tell you what we know of its nature, the categories and approximate number of people and records affected, the likely consequences and the measures taken or proposed, and we add what we learn later.
11. At the end: deletion or return
When a subscription ends, the store is paused and its data stays in place, so that you can come back to it as it was. At any time, and in any case when you no longer want the store, you choose by writing to us whether we delete its data, or first return it to you and then delete it. We then hand you a complete copy of the store’s data and files if you asked for it, and delete the store’s database and files, including the backup copies, within 30 days, and confirm the deletion to you in writing. Data we must keep by law is kept only as long as that law requires.
12. Proof and audits
We give you the information you need to show that this agreement is kept. You, or an auditor you mandate who is bound to confidentiality, may inspect our compliance after giving notice of at least 30 days, during business hours, without disturbing the operation of the platform, as a rule not more than once a year unless there has been a breach. Each party bears its own costs.
13. Transfers outside the EU, and changes
The stores, their databases and their files are kept in the European Union (Annex 2). Some sub-processors are based in, or may reach data from, countries outside the European Economic Area, as Annex 2 says. Codeator’s own team also works from Iraq: it can reach store data from there for support and operations, and the nightly backup copies of the databases are also kept on Codeator’s own computer there. For every such transfer we ensure a safeguard under Chapter V of the GDPR: an adequacy decision, the EU–US Data Privacy Framework where the recipient is certified under it, or the EU Standard Contractual Clauses.
Merchants outside the EU. If you are established outside the European Economic Area, the Standard Contractual Clauses adopted by Commission Implementing Decision (EU) 2021/914, Module Four (transfer from processor to controller), are incorporated into this agreement by reference, with you as data importer and Codeator as data exporter. Clause 7 (docking) and the option in Clause 11 do not apply; Clause 17 chooses the law of Germany and Clause 18 the courts of Berlin. Annex I of the Clauses is filled in by sections 1 to 3 of this agreement.
Changes. We announce a new version of this agreement by email to the account owner at least 30 days before it applies. If you do not accept it, you may end the subscription before then.
14. Final provisions
Where this agreement and the Terms differ on the protection of personal data, this agreement prevails. It is governed by German law. If one provision is invalid, the rest remains in force. Questions about data protection: [email protected].
Annex 1: Technical and organisational measures
These are the measures in place on the date of this version, as the platform’s code and its servers’ set-up show them.
Where the data is and who can reach the servers
- The platform, every store’s database and its cache run on a dedicated cloud server of Hetzner in Nuremberg, Germany. The database is not reachable from outside the server.
- Sign-in to the server is by SSH key only; passwords are switched off. The keys are held by Codeator’s owner, and the automation keys can each run only fixed commands.
- Two firewalls, the server’s own and Hetzner’s, let in only web traffic and SSH. Security updates install automatically, and the server is checked every minute, with alerts.
Separation of stores
- Every store has its own database. A request is bound to its store before anyone signs in, and a sign-in token of one store is refused by every other.
- All stores’ databases run on one database server under one application role; pictures are kept apart by a folder per store.
Access, passwords and sessions
- All traffic to the stores is encrypted with TLS.
- Passwords are kept only as salted hashes (PBKDF2 with SHA-512); the cashier’s PIN as a PBKDF2 hash; one-time codes, password links and session tokens as hashes.
- Keys and courier passwords you save in the panel are encrypted (AES-256-GCM).
- Staff roles decide who sees and changes what. Sign-ins and one-time codes are rate limited, and repeated failed sign-ins are slowed down.
- Every change your staff make in the panel is recorded with who and when; passwords and keys are never written into that record.
Logs and measurement
- The API’s log records the route of a request, never its full address. The storefront counts its visitors only as daily totals and does not keep their IP addresses.
- The web server in front of the stores logs IP addresses in its access log, which is limited in size and overwritten as it fills.
Availability and backups
- Every database is backed up every night; those copies are kept on the server for 14 days, readable only by its administrator, and the newest copy of each database is always kept. Every database is also backed up before each new version of the platform is installed.
- Every 30 minutes the newest copies are copied, with a checksum, to a drive on Codeator’s own computer.
Not in place yet
So that you can judge the protection yourself: the panel does not yet offer two-factor sign-in; personal data is not encrypted field by field in the database, and encryption of the disks and of the backup drive is not yet confirmed; logs, the change record, abandoned carts and code logs have no automatic deletion period yet; and the export and deletion at the end of a contract (section 11) are carried out by hand.
Annex 2: Sub-processors
Companies that process your store’s personal data on Codeator’s behalf, as of 16/11/2026.
| Sub-processor | What it does | Data | Where |
|---|---|---|---|
| Hetzner Online GmbH, Germany | Server for the platform, the databases and the cache | All of the store’s data | Nuremberg, Germany |
| Hostinger International Ltd., Cyprus | The platform’s server until 11/11/2026; it still holds a stopped copy of the platform’s databases as they were that day, until it is deleted | The store data of that day | Frankfurt, Germany |
| Cloudflare, Inc., USA | File storage (product and theme pictures, chat and payment pictures, app builds), the map of the delivery address, and the domain’s name service | Pictures; the IP address of whoever loads a file | Storage in Eastern Europe; Cloudflare’s worldwide network delivers the files |
| Microsoft (Microsoft 365) | Sends the store’s emails: codes, password links and notices | Email address, the letter’s content | Microsoft’s cloud; may include the USA |
| OTPIQ, Iraq | Sends verification codes by WhatsApp, Telegram or text message, when your store uses Codeator’s credit | Phone number, the code, the requester’s IP address | Iraq |
| OpenAI, USA, and Anthropic, USA | The AI assistant in the panel and in the storefront’s chat, called from Codeator’s own server | The messages written to the assistant, and the store data it reads to answer (for a shopper: their recent orders) | USA |
| Google (Firebase, Google Analytics, Google Fonts) | Push notifications and app checks for the store app; Codeator’s analytics where the plan includes them, only after consent where consent is required; the storefront’s font | Push tokens and the message; a pseudonymous analytics ID and events; the visitor’s IP address | Google’s cloud; may include the USA |
| Browser push services (Google, Mozilla, Microsoft, Apple) | Deliver browser notifications to a shopper who has allowed them | The notification address and its text | The browser maker’s cloud; may include the USA |
| OpenStreetMap Foundation, UK, and OpenFreeMap | Map tiles on the store’s contact page, and the fallback map | The visitor’s IP address | UK and Europe |
Services you choose yourself. Some services work under your own account and on your own decision, for example a courier you connect (such as Al-Waseet or AlBarq), your own OTPIQ key, your own Telegram bot for staff alerts, your own Meta or TikTok pixel or Google Analytics property, or an AI app a member of your staff connects to the store. They are your processors or recipients, not Codeator’s sub-processors, and your agreement with each of them applies.
Not a sub-processor for your customers’ data: Stripe takes only your own subscription payment to Codeator, as described in our privacy policy.