Bu metnin Türkçe sürümü hazırlanıyor. O zamana kadar aşağıdaki İngilizce metin geçerlidir.
BigM Growth Engine
BigM Data Processing Addendum
This Data Processing Addendum ("DPA") forms part of the BigM Terms of Service between the customer ("Customer", controller) and BIGM INNOVATIVE SOLUTIONS - FZCO ("BigM", processor). It applies automatically when Customer accepts the Terms. Customer may request a countersigned copy at legal@bigm.live.
1. Definitions
"Data Protection Law" means all laws on personal data that apply to the processing, including the EU General Data Protection Regulation 2016/679 ("GDPR"), the UK GDPR and Data Protection Act 2018, UAE Federal Decree-Law No. 45 of 2021 ("PDPL") and Turkish Law No. 6698 ("KVKK"). "Customer Personal Data" means personal data that BigM processes on Customer's behalf under the Terms, as described in Annex 1. Terms such as "controller", "processor", "data subject", "personal data breach" and "processing" have the meaning given in the GDPR.
2. Roles and instructions
2.1 Customer is the controller and BigM the processor of Customer Personal Data. Where Customer acts as a processor for a third party, BigM is its sub-processor.
2.2 BigM processes Customer Personal Data only on Customer's documented instructions. The Terms, the Account Access Authorization, Customer's settings in the dashboard and Customer's approvals are Customer's complete instructions. BigM will tell Customer if it believes an instruction breaks Data Protection Law, and may then suspend that instruction.
2.3 Customer is responsible for the lawfulness of the instructions, for having a legal basis for the processing, including for engagement with public posts of third parties, and for giving any notices its own audience requires.
3. Confidentiality
BigM ensures that everyone authorised to process Customer Personal Data is bound by confidentiality and processes it only as needed to provide the Service.
4. Security
BigM implements the technical and organisational measures in Annex 2 and keeps them appropriate to the risk, as required by Article 32 GDPR.
5. Separation and no cross-customer use
5.1 BigM keeps Customer Personal Data logically separated from the data of other customers, including separate browser profiles, operating system users and network addresses for connected accounts, and row-level separation in databases.
5.2 BigM does not use Customer Personal Data, Customer's materials or Customer's performance data for its own purposes or for the purposes of any other customer, and does not use them to train machine learning models, except that BigM may use aggregated operational metrics that do not identify Customer or any individual (for example error rates and processing times) to maintain the Service.
6. Personal data breach
BigM will notify Customer without undue delay, and in any case within 48 hours, after becoming aware of a personal data breach affecting Customer Personal Data, with the information Customer reasonably needs to meet its own notification duties, and will take reasonable steps to contain it. A security event on a connected account that a platform initiates (for example a forced sign-out) is not by itself a personal data breach, but BigM will report it in the dashboard.
7. Sub-processors
7.1 Customer gives general authorisation for BigM to use the sub-processors listed at bigm.live/legal/subprocessors (Annex 3).
7.2 BigM will give at least 14 days' notice by email before adding or replacing a sub-processor. Customer may object on reasonable data protection grounds within that period. If the parties cannot resolve the objection, Customer may terminate the affected part of the Service and receive a pro rata refund of prepaid fees for it.
7.3 BigM imposes on each sub-processor written obligations no less protective than this DPA, including that it may process the data only to provide its service to BigM and not for its own purposes, and remains responsible for its sub-processors.
8. International transfers
8.1 BigM is established in the UAE and hosts the Service in Germany. Where Customer Personal Data is transferred from the EEA, the UK, Switzerland or Turkey to a country without an adequacy decision, the parties agree that:
- a) for EEA transfers, the Standard Contractual Clauses approved by Commission Implementing Decision (EU) 2021/914, Module Two (controller to processor) or Module Three (processor to processor) as applicable, are incorporated by reference, with clause 7 (docking) included, clause 9 option 2 (general authorisation, 14 days), clause 11 optional wording excluded, clause 17 governed by the law of Ireland, and clause 18 courts of Ireland; Annexes I to III are completed by Annexes 1 to 3 of this DPA;
- b) for UK transfers, the UK International Data Transfer Addendum to the SCCs applies;
- c) for Swiss transfers, the SCCs apply with references to the Swiss FADP;
- d) for Turkish transfers, the parties will sign the standard contract published by the Turkish Personal Data Protection Board without modification, and the data exporter will notify it to the Authority within five business days of signature;
- e) for transfers out of the UAE, BigM relies on the grounds permitted by the PDPL.
8.2 BigM will ensure that onward transfers to sub-processors outside those regions are covered by equivalent safeguards.
9. Assistance
9.1 BigM will assist Customer, by appropriate technical and organisational measures, to respond to data subject requests, and will forward to Customer without undue delay any request it receives about Customer Personal Data, including any notice received from a platform about a data subject's rights.
9.2 BigM will provide reasonable assistance with data protection impact assessments, prior consultations and breach notifications, taking into account the information available to it.
10. Deletion and return
10.1 When Customer disconnects an account, BigM deletes its browser profile and revokes its tokens within 24 hours.
10.2 On termination of the Terms, BigM makes Customer's materials and Deliverables available for export for 30 days and then deletes Customer Personal Data, including in backups within the backup rotation period in Annex 2, unless law requires BigM to keep it. BigM will confirm deletion in writing on request.
11. Audits and information
BigM will make available the information reasonably necessary to demonstrate compliance with this DPA. Customer may audit BigM, by itself or through an independent auditor bound by confidentiality, once a year on 30 days' notice, during business hours, at Customer's cost, unless a personal data breach or a regulator requires otherwise. BigM may first answer by written responses and documentation.
12. Liability and precedence
The limitations of liability in the Terms apply to this DPA, except where Data Protection Law does not allow it. If this DPA conflicts with the Terms, this DPA prevails for the processing of Customer Personal Data; if the SCCs conflict with this DPA, the SCCs prevail.
Annex 1: Description of processing
Subject matter and purpose: production, scheduling and publication of social media and web content for Customer; reading and reporting of performance of Customer's connected accounts; light engagement with public posts on Customer's behalf; where Customer connects a personal LinkedIn profile, connection requests without a note and company page follow invitations; operating and securing connected account sessions. Duration: for the term of the subscription and the deletion periods in section 10. Nature: collection, storage, structuring, adaptation, retrieval, use, publication, transmission to platforms, deletion. Categories of data subjects: Customer's staff and representatives; people appearing in Customer's materials; followers, commenters and viewers of Customer's accounts as shown in platform statistics and comments; publishers of public posts with which the Service engages; LinkedIn members to whom connection requests or company page invitations are sent. Categories of personal data: names, handles, account IDs, profile pictures, images, voice and video recordings, comment text, aggregated audience statistics, session cookies and tokens, IP addresses and audit logs. Special categories: none intended. Customer must not include them in materials. Frequency: continuous. Retention: as in section 10 and the Privacy Policy.
Annex 2: Technical and organisational measures
- 1. Isolation: one browser profile, one operating system user and one dedicated network address per workspace; network rules allow browser processes to reach only their assigned network address and private infrastructure.
- 2. Encryption: TLS in transit, including every backup transfer; tokens and passwords with per-record authenticated envelope encryption, keys held separately from the data. Browser profiles and database backups sit on access-restricted servers; full-disk encryption of those servers is being added and is not yet in place.
- 3. Access control: production access limited to named staff, multi-factor authentication, least privilege, quarterly access review; staff do not enter Customer browser sessions.
- 4. Database separation: row-level security enforced per workspace for all Growth Engine tables, with the application role unable to bypass it.
- 5. Logging: audit log of every action on a connected account and every administrative access, kept 12 months.
- 6. Account identity check before every action; automatic stop on mismatch.
- 7. Monitoring and alarms: session health checks, alarms when scheduled work is not done, when a network address changes, or when a session is lost.
- 8. Backups: the database is copied every night to a separate BigM server (Hetzner, Finland) and each copy is deleted after 14 days. Browser profiles are not backed up.
- 9. Secure development: code review, dependency updates, secrets never in code.
- 10. Incident response: documented procedure, 48-hour customer notification.
- 11. Personal data minimisation in AI calls: only the content needed for the task is sent to AI providers, under terms that prohibit training on it.
Annex 3: Sub-processors
As listed at bigm.live/legal/subprocessors on the date of processing (see Privacy Policy section 7 for the initial list).