Data Processing Agreement
Last updated:Definitions:
- We use any of the terms “we”, “us” and “our” to refer to Feedoptimise ®™, a trading name of 33Concept Ltd.
- We use any of the terms “User”, “you” and “your” as defined in the Terms of Use, to refer to the person or legal entity that registers for, accesses or uses the Feedoptimise Services. This DPA applies to all Users, including those using a free trial.
- We use the term “Content” as defined in the Terms of Use.
- We use the term “Content Personal Data” to refer to any Personal Data contained in Content that we process on your behalf in providing the Services.
- We use the term “Data Protection Laws” to refer to the UK GDPR, the Data Protection Act 2018, the EU General Data Protection Regulation 2016/679 (“EU GDPR”) where it applies, and any other data protection laws that apply to the processing of Content Personal Data under the Terms of Use.
- We use the terms “Controller”, “Processor”, “Data Subject”, “Personal Data”, “Processing” and “Supervisory Authority” as defined in the Data Protection Laws.
- We use the term “Personal Data Breach” to refer to a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, Content Personal Data.
- We use the term “Sub-processor” to refer to any third party we engage to process Content Personal Data on your behalf.
- We use the term “Restricted Transfer” to refer to a transfer of Content Personal Data to a country outside the UK or the European Economic Area that is not covered by an adequacy decision or adequacy regulations under the Data Protection Laws.
- Any other capitalised terms not defined in this DPA have the meaning given in the Terms of Use.
This Data Processing Agreement (“DPA”) constitutes a legally binding agreement between Feedoptimise ®™, a trading name of 33Concept Ltd, a Private Limited Company, with a registration number 07286718, registered in United Kingdom, and the User.
This DPA forms part of the Terms of Use and governs how we process Personal Data that Users submit to the platform as part of their Content. It applies automatically to all Feedoptimise accounts, without the need for a separate signature.
This DPA does not cover Personal Data that Feedoptimise processes as a Controller in its own right, such as your login email address, optional first and last name, billing details, access logs and cookie data. That processing is described in our Privacy Policy.
-
Scope and roles
- Content submitted to Feedoptimise consists of product, catalogue, inventory and campaign data and is not intended to contain Personal Data. This DPA applies only to the extent that Content does contain Personal Data.
- In relation to Content Personal Data, you are the Controller and Feedoptimise is your Processor. The details of the processing are set out in Annex 1.
- You are responsible for ensuring that you have a lawful basis for submitting Content Personal Data to the Services, that you have provided any notices required by the Data Protection Laws, and that your instructions to Feedoptimise comply with those laws.
- You must not submit to the Services any special category data, criminal offence data, government identification numbers, payment card data, or other sensitive Personal Data, unless agreed with Feedoptimise in writing.
- You should include in Content only the Personal Data that is necessary for your use of the Services, for example by excluding shopper, buyer or reviewer details from product feeds.
-
Processing instructions
- Feedoptimise will process Content Personal Data only on your documented instructions. Your instructions consist of the Terms of Use, this DPA, the configuration of your account (including your sources, feeds, rules, integrations and any AI features you enable), and any other written instructions you give us that are consistent with the Terms of Use.
- Feedoptimise may also process Content Personal Data where required to do so by UK law or the law of the European Union or a member state to which it is subject. In that case, we will inform you of that legal requirement before processing, unless the law prohibits this.
- We will tell you promptly if, in our opinion, an instruction infringes the Data Protection Laws.
- We will not use Content Personal Data for our own purposes, sell it, or use it to train, fine-tune or otherwise improve AI models, whether our own or those of third parties.
-
Confidentiality of personnel
Feedoptimise will ensure that everyone authorised to process Content Personal Data is bound by an appropriate duty of confidentiality, whether contractual or statutory. Access is limited to personnel who need it to provide, support or secure the Services.
-
Security
Feedoptimise will implement and maintain appropriate technical and organisational measures to protect Content Personal Data, as required by Article 32 of the UK GDPR and EU GDPR. The current measures are described in Annex 2. We may update these measures over time, provided the overall level of protection is not reduced.
-
Sub-processors
- You give Feedoptimise general authorisation to engage the Sub-processors listed in Annex 3, and further Sub-processors in line with this section.
- We will give you at least thirty (30) days notice before engaging a new Sub-processor, by updating Annex 3 and notifying account owners by email or within the platform.
- You may object to a new Sub-processor on reasonable data protection grounds by writing to privacy@feedoptimise.com within that notice period. We will discuss your concerns in good faith. If we cannot resolve them, you may stop using the Services at any time, without penalty, under clause 8.1 of the Terms of Use.
- Feedoptimise will impose data protection obligations on each Sub-processor by written contract that are no less protective than those in this DPA. We remain responsible to you for the performance of our Sub-processors.
-
The following are not Sub-processors, because you choose them and the data is sent to them on your instructions:
- destination channels and partner platforms you connect, such as Google Merchant Center, Meta or affiliate networks;
- AI providers you use with your own API key for AI modifiers, where your own agreement with that provider applies;
- AI assistants you connect through our MCP server.
-
International transfers
- The Feedoptimise platform is hosted on Google Cloud Platform in the United States, and some Sub-processors process data outside the UK and the European Economic Area. Content Personal Data may therefore be subject to a Restricted Transfer.
- Where a Restricted Transfer takes place, Feedoptimise will ensure it is covered by an appropriate safeguard under the Data Protection Laws, such as the recipient's certification under the EU-U.S. Data Privacy Framework and its UK Extension, the European Commission's Standard Contractual Clauses, or the UK International Data Transfer Agreement or UK Addendum.
- Content processed by our self-hosted AI models is processed on hardware we operate in the United Kingdom and is not transferred to any third-party AI provider.
-
Data subject requests
- If Feedoptimise receives a request from a Data Subject relating to Content Personal Data, we will pass it to you without undue delay and will not respond to it ourselves, other than to direct the Data Subject to you.
- You can access, correct and delete Content directly within the platform. Where you need further help to respond to a request, we will provide reasonable assistance, taking into account the nature of the processing and the information available to us.
-
Personal data breaches
- Feedoptimise will notify you without undue delay, and in any event within forty-eight (48) hours, after becoming aware of a Personal Data Breach affecting Content Personal Data. Notice will be sent to the account owner and any Incident Contacts nominated under the Service Level Agreement.
- The notice will include, as far as the information is available, the nature of the breach, the categories and approximate number of Data Subjects and records concerned, the likely consequences, and the measures taken or proposed. Where not all information is available at once, we will provide it in phases.
- We will take reasonable steps to contain and remedy the breach, and give you the help you reasonably need to meet your own notification obligations. Notifying you of a breach is not an admission of fault or liability.
-
Impact assessments and consultation
Feedoptimise will give you reasonable assistance with any data protection impact assessment, and any prior consultation with a Supervisory Authority, that you are required to carry out in relation to the Services. This assistance is limited to the processing of Content Personal Data and the information available to us.
-
Deletion and return
- You can export and delete your Content at any time while your account is active.
- After your account is closed, you can review and export your configuration data for thirty (30) days, as described in clause 8.5 of the Terms of Use. After that period, and subject to section 10.5, Feedoptimise will delete or anonymise Content Personal Data from its active systems.
- Copies held in backups will be deleted within fourteen (14) days in the normal backup cycle. Until then, they remain protected under this DPA and are not used for any other purpose.
- This section does not apply to data we must keep under applicable law, which remains protected under this DPA for as long as we hold it.
- Mapping settings and change history records, including any Content Personal Data they contain, are retained for twelve (12) months after your account is closed, and in any event no change history entry is kept for longer than two years from the date of the change. You instruct us to retain them for this period so that, if you return, your configuration can be restored automatically when you reconnect your sources, so that changes made within your account can be audited, and so that either Party can establish, exercise or defend legal claims relating to the Services. During that period they remain protected under this DPA and are not used for any other purpose. You can still view them through your login, as described in clause 8.5 of the Terms of Use, and our own access to them is restricted to authorised personnel. At the end of the period they are deleted or anonymised.
-
Information and audits
- Feedoptimise will make available to you the information reasonably necessary to demonstrate compliance with this DPA, including written answers to reasonable security and data protection questionnaires.
- Where that information is not enough to demonstrate compliance, or where a Supervisory Authority requires it, you may carry out an audit, either yourself or through an independent auditor bound by confidentiality. Audits are limited to once in any twelve (12) month period, unless following a Personal Data Breach or required by a Supervisory Authority.
- You must give at least thirty (30) days written notice of an audit. Audits take place during UK business hours, are limited to the systems and records relevant to Content Personal Data, must not unreasonably disrupt the Services or put other Users' data at risk, and are carried out at your cost.
-
General
- Liability. Each Party's liability under this DPA is subject to the limitation of liability in the Terms of Use.
- Duration. This DPA applies for as long as Feedoptimise processes Content Personal Data on your behalf, including after the Terms of Use end.
- Order of precedence. If there is any conflict between this DPA and the Terms of Use in relation to the processing of Content Personal Data, this DPA prevails. If there is any conflict between this DPA and any Standard Contractual Clauses or UK transfer terms that apply under section 6, those clauses prevail.
- Changes. We may update this DPA to reflect changes in the Data Protection Laws, guidance from a Supervisory Authority, or our Services. We will give at least thirty (30) days notice of any change that reduces your protection, and if you do not accept it you may stop using the Services under clause 8.1 of the Terms of Use.
- Governing law. This DPA is governed by the laws of England and Wales, and the courts of England and Wales have exclusive jurisdiction, except where the Data Protection Laws or transfer clauses under section 6 require otherwise.
- Contact. Questions about this DPA can be sent to privacy@feedoptimise.com.
Annex 1: Details of processing
| Item | Details |
|---|---|
| Subject matter | Provision of the Feedoptimise feed management platform and related services under the Terms of Use. |
| Duration | For as long as you use the Services, plus the deletion period in section 10. |
| Nature and purpose | Importing, storing, transforming, analysing and exporting Content to the channels and integrations you configure; AI processing of Content where you enable AI features; support and troubleshooting at your request. |
| Types of Personal Data | Any Personal Data you include in Content, for example names or contact details of suppliers, brand or store contacts, names appearing in product data, and images of individuals in product photography. |
| Categories of Data Subjects | Individuals who appear in or are referred to in your Content, such as models in product images, your staff, and your suppliers' or partners' contacts. |
| Special category data | None. Not permitted under section 1.4. |
| Frequency | Continuous, in line with the import and export schedules you configure. |
| Excluded data | Reporting Data and data received from Google APIs are retrieved at item and campaign level only, and do not include user-level identifiers, cookie or device identifiers, or IP addresses. |
Annex 2: Technical and organisational security measures
| Area | Measures |
|---|---|
| Hosting | Platform hosted on Google Cloud Platform infrastructure operated by Feedoptimise. Self-hosted AI models run on Feedoptimise-operated hardware in the United Kingdom. |
| Encryption in transit | All connections between browsers and the platform, and between the platform and our self-hosted AI infrastructure, are encrypted using TLS. |
| Encryption at rest | Data encrypted at rest using AES-256 at the infrastructure layer. Credentials for Users' systems and third-party services (such as FTP and SFTP passwords, API keys and access tokens) are additionally encrypted at the application layer using AES-256-CBC. |
| Authentication | Passwords hashed using current industry-standard algorithms. Two-factor authentication (TOTP) available to all Authorised Users. MCP connections use OAuth2 with scoped tokens and the Authorised User's existing permissions. |
| Access control | Access to systems holding Personal Data restricted to authorised personnel on a need-to-know basis, and logged for audit. |
| Monitoring | Access logs and authentication events monitored to detect unauthorised access, brute-force attempts and other suspicious activity. Rate limits and automated controls applied to the platform and APIs. |
| Change tracking | All changes within accounts recorded in the change history for two years from the date of each change, with the ability to revert while the account is active. After account closure, change history is retained for twelve (12) months, within that two-year limit, as described in section 10.5. |
| Availability | Continuous platform monitoring, rolling deployments designed for zero downtime, and on-call engineering for critical incidents, as described in the Service Level Agreement. |
| Backups | Full database snapshot taken daily, with continuous incremental backups of all changes between snapshots, allowing recovery to any point in time. Backups are encrypted at rest, stored in Google Cloud Platform in the United States and retained for 14 days. |
Annex 3: Sub-processors
| Sub-processor | Purpose | Location |
|---|---|---|
| Google Cloud Platform (Google LLC) | Platform hosting and infrastructure | United States |
| OpenAI | AI Feed Agent (opted-in Users only) and internal support | United States |
| Anthropic | AI Feed Agent (opted-in Users only) and internal support | United States |
| Google (Gemini API) | AI Feed Agent (opted-in Users only) and internal support | United States |
| Google Workspace (Gmail) | General enquiries, website contact form and the fallback support email address, which may contain Content | United States |
Payment processors are not listed because they handle billing data, for which Feedoptimise is the Controller under the Privacy Policy, not Content Personal Data.