Data Processing Agreement (Appendix 3)
Version: 1.1 · Effective date: 17 November 2026
This Data Processing Agreement (the "DPA") is Appendix 3 to the Teachfluence Platform Service Agreement (the "Main Agreement") and forms part of it. In this Appendix, "DPA" means this Data Processing Agreement and "Main Agreement" means the Platform Service Agreement; in the other documents of the Main Agreement, "Agreement" means the Platform Service Agreement.
1. Parties and Conclusion
1.1. The parties are:
- Processor: Pi Education Teknoloji Anonim Şirketi ("Teachfluence"), İnkılap Mah. Sokullu Cad. No:5, 34768 Ümraniye / İstanbul, kvkk@teachfluence.com.
- Controller: the natural or legal person who opens an organization (online school, academy, store, etc.) on Teachfluence and accepts the Main Agreement (the "Customer").
1.2. This DPA is concluded, without a separate signature, when the Customer accepts the Main Agreement. For Customers who accepted the Main Agreement before this DPA's effective date, it takes effect through the notice described in Clause 13.2. Where the parties have signed written special terms, this DPA is concluded as an annex to those terms on the date they are signed.
1.3. A Customer who wants a signed copy can write to kvkk@teachfluence.com. The signed copy is identical to this text, with the Customer's name, address and signature added.
1.4. This DPA is published in Turkish and English. If the versions differ, the English version prevails for Customers established outside Türkiye; otherwise the Turkish version prevails.
2. Definitions
Terms not defined here have the meaning given in Turkish Law No. 6698 on the Protection of Personal Data ("KVKK") and, where it applies, Regulation (EU) 2016/679 ("GDPR"); "Data Protection Law" means whichever of them applies.
- Customer Data: personal data that the Customer uploads to, collects through or creates on the Teachfluence platform (the "Platform") and for which the Customer is the controller, such as data about the Customer's students, buyers, subscribers and team members.
- Data Subject: the natural person to whom personal data relates.
- Sub-processor: a third party that Teachfluence engages to carry out part of the processing of Customer Data.
- Personal Data Breach: a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, Customer Data.
3. Scope
3.1. This DPA applies only to Customer Data. The subject matter, nature, purpose and duration of the processing, the types of personal data and the categories of Data Subjects are described in Annex A.
3.2. Data that Teachfluence processes for its own relationship with the Customer (the Teachfluence accounts of the Customer's owners and team members, subscription and commission records, billing, Platform security and service improvement) is outside the scope of this DPA. Teachfluence is the controller of that data, and the KVKK Privacy Notice at https://teachfluence.com/yasal/kvkk-aydinlatma-metni (in Turkish) applies to it. The End User data (data of the Customer's students, buyers, members and subscribers) for which Teachfluence is the controller is limited to the authentication data of the user account that can be used across several organizations (email address, password hash, sign-in records). Teachfluence informs End Users about that data with its own privacy notice when they register. End Users' organization-specific data is not used by Teachfluence for any purpose of its own, including service improvement; only anonymised aggregate statistics may be produced.
3.3. If this DPA conflicts with the Main Agreement or any other document on the protection of personal data, this DPA prevails. If this DPA conflicts with the Standard Contractual Clauses in the GDPR Annex, the Standard Contractual Clauses prevail.
4. The Customer's Instructions
4.1. Teachfluence processes Customer Data only on the Customer's documented instructions and only to provide the Platform, including with regard to transfers to third countries. The Main Agreement, this DPA and the Customer's settings and use of the Platform are the Customer's documented instructions.
4.2. Teachfluence does not use Customer Data for its own purposes, does not sell or rent it, and does not share it with third parties except on the Customer's instructions.
4.3. If the law requires Teachfluence to process Customer Data other than on the Customer's instructions, Teachfluence informs the Customer before processing, unless the law prohibits it.
4.4. If Teachfluence believes that an instruction infringes Data Protection Law, it informs the Customer in writing without delay and may suspend that instruction until the Customer confirms or changes it in writing.
4.5. Instructions that go beyond the Platform's standard functions may be charged separately. Before carrying out such an instruction, Teachfluence tells the Customer the expected cost and waits for confirmation. Instructions to stop processing, or to delete or return Customer Data, are never charged.
4.6. The Customer is responsible for collecting Customer Data lawfully, for informing Data Subjects, for obtaining consent where it is required, and for complying with the rules on commercial electronic messages.
5. Personnel and Confidentiality
5.1. Teachfluence binds its employees and other authorised persons who can access Customer Data to a contractual or statutory duty of confidentiality, which continues after their engagement ends.
5.2. Access to Customer Data is limited to the people, and the extent, that their role requires.
6. Security
6.1. Teachfluence implements technical and organisational measures appropriate to the risk, as required by Article 12 KVKK and Article 32 GDPR. The measures are described in Annex B.
6.2. Teachfluence may update the measures as technology develops, provided that the overall level of security does not fall below the level described in Annex B.
6.3. Teachfluence assists the Customer, taking into account the nature of the processing and the information available to it, with the Customer's obligations on security and breach notification, and provides reasonable information and assistance for the Customer's technical and organisational measures under Article 12 KVKK, its risk assessments, and its notifications and applications to the Personal Data Protection Authority (for Customers subject to the GDPR, including data protection impact assessments and prior consultation under Articles 32 to 36 GDPR).
7. Sub-processors
7.1. The Customer gives Teachfluence general authorisation to engage Sub-processors. The current list is in Annex C (https://teachfluence.com/yasal/subprocessors). The Sub-processors on that list are authorised when this DPA is concluded.
7.2. Sub-processors marked "optional" in Annex C process Customer Data only if the Customer enables the related feature or integration. Enabling the feature authorises that Sub-processor.
7.3. Teachfluence updates Annex C and notifies the Customer's organization owners by email at least 14 days before a new Sub-processor starts processing Customer Data. The Customer may object in writing on reasonable data protection grounds within that period. If the objection cannot be resolved in good faith, Teachfluence will, at its choice, either continue to provide the service without that Sub-processor, or the Customer may terminate the part of the service that depends on it, or the Main Agreement, without penalty and with effect before the Sub-processor starts processing. In that case the prepaid fees for the unused period are refunded to the Customer.
7.4. Teachfluence imposes on each Sub-processor, by written contract, data protection obligations that are substantially the same as those in this DPA, and remains liable to the Customer for each Sub-processor's performance.
7.5. Tools chosen by the Customer are not Sub-processors. The Platform lets the Customer add third-party tools of its own choice to its own site and pages (for example Google Analytics, Google Tag Manager, Meta Pixel, TikTok Pixel, Microsoft Clarity, Hotjar, PostHog, live-chat widgets and custom HTML embeds), and send data to services the Customer connects with its own account (for example the Customer's own Stripe account, or webhook addresses the Customer defines). These tools and services act on the Customer's instructions and on its behalf. They are not Teachfluence's Sub-processors and are not listed in Annex C. The legal basis, cookie consent, transparency and the contract with the provider are the Customer's responsibility.
8. International Transfers
8.1. Platform data is hosted in Amazon Web Services eu-central-1 (Frankfurt, Germany). Teachfluence itself is established in Türkiye, and some Sub-processors are located outside Türkiye and the EEA, as shown in Annex C.
8.2. For transfers under KVKK, Teachfluence signs, with each Sub-processor shown in Annex C as located outside Türkiye, the unaltered "processor-to-processor" standard contract published by the KVKK Board under Article 9(4) KVKK, and notifies it to the Personal Data Protection Authority as data exporter within five business days of the last signature. These steps are completed by 31 March 2027; Teachfluence shows the signature and notification date for each Sub-processor in Annex C and shares the notification records with Customer on request. Data Subjects' explicit consent is not relied on for these systematic transfers; explicit consent may only be used for incidental transfers under Article 9(6) KVKK.
8.3. Where Customer Data originates from the EEA, Switzerland or the United Kingdom, the GDPR Annex below also applies.
9. Data Subject Requests
9.1. Taking into account the nature of the processing, Teachfluence assists the Customer, through the Platform's tools and reasonable additional support, in responding to requests from Data Subjects to exercise their rights (access, rectification, erasure, restriction, portability, objection). The Customer can view, correct, export and delete student and contact records in the Platform.
9.2. If a Data Subject sends a request directly to Teachfluence, Teachfluence does not answer it on the merits. It forwards the request to the Customer without delay and tells the Data Subject that the request has been passed to the controller.
10. Personal Data Breaches
10.1. Teachfluence notifies the Customer without undue delay, and in any event within 48 hours, after becoming aware of a Personal Data Breach affecting Customer Data. The notice contains, as far as then known, the information requested in the Personal Data Protection Board's data breach notification form.
10.2. The notice describes, as far as then known, 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. Information that is not available at once is provided in phases.
10.3. Teachfluence takes the necessary and reasonable steps to contain the breach and mitigate its effects without delay, and documents the facts of the breach.
10.4. Notifying the supervisory authority and Data Subjects is the Customer's obligation as controller. Teachfluence assists with the information available to it.
11. Information and Audits
11.1. On request, Teachfluence makes available to the Customer the information reasonably necessary to demonstrate compliance with this DPA and Article 28 GDPR, and assists the Customer with enquiries and inspections by competent authorities.
11.2. The Customer may audit Teachfluence's compliance with this DPA, itself or through an independent auditor bound by confidentiality, once per year (and additionally if a competent authority requires it or after a confirmed Personal Data Breach). Audits require at least 30 days' written notice, take place during business hours and must not unreasonably disrupt Teachfluence's operations. Teachfluence may first answer with written information and documents. The Customer bears the cost of the audit. Teachfluence may reject an auditor who is its competitor or on other reasonable grounds.
12. Termination, Return and Deletion
12.1. This DPA remains in force for the term of the Main Agreement and, after the Main Agreement ends, for as long as Teachfluence continues to process or store Customer Data, until the deletion under Clauses 12.2 to 12.4 has been completed.
12.2. When the Main Agreement ends, the Customer can retrieve Customer Data for 30 days after termination with the Platform's export tools or on request (Main Agreement Section 13.4). Teachfluence deletes Customer Data earlier on the Customer's request, or at the latest within 90 days after termination.
12.3. Deletion applies to live systems. Copies in backups expire on their own within the backup cycle (at most 30 days) and remain subject to this DPA's security and confidentiality terms until then. Deleted data is not selectively restored from backups.
12.4. Apart from the periods in Clauses 12.2 and 12.3, Teachfluence does not keep Customer Data on the Customer's behalf after termination. The records Teachfluence keeps under its own legal obligations are: the invoices it issues and its commercial books (Tax Procedure Law Art. 253, Turkish Commercial Code Art. 82); the transaction records it must keep as an intermediary service provider or electronic commerce intermediary service provider (Distance Contracts Regulation Art. 20/2; where relevant, Electronic Commerce Intermediary Service Providers Regulation Art. 33/6); hosting provider traffic data (Law No. 5651 Art. 5/3); and commercial electronic message records (Regulation on Commercial Communication and Commercial Electronic Messages Art. 13). Teachfluence keeps these records as controller, only for the relevant obligation and for the prescribed period, and deletes them at the end of that period. On the Customer's request, Teachfluence confirms deletion in writing.
13. Changes
13.1. Teachfluence may update this DPA because of changes in the law, decisions of competent authorities or changes to the service. Updates to Annex C follow Clause 7.3 instead.
13.2. Teachfluence notifies the Customer's organization owners by email at least 30 days before a change to the Customer's detriment takes effect. Under Main Agreement Section 15.2, such a change applies to the Customer only with the Customer's express acceptance; for a Customer who does not accept it, the current version continues to apply until the end of the paid period, and either party may terminate the Main Agreement as of that date. Changes to the Sub-processors in Annex C follow Clause 7.3.
14. Liability
Each party is liable for damage caused by its own breach of this DPA or of Data Protection Law. Otherwise the liability provisions of the Main Agreement apply, and liability arising from a breach of this DPA is subject to the cap in Main Agreement Section 10.3. Mandatory liability under Data Protection Law (including Article 82 GDPR) is not affected.
15. Governing Law and Jurisdiction
This DPA is governed by Turkish law. Section 16.1 of the Main Agreement applies to disputes. The Standard Contractual Clauses in the GDPR Annex are governed by their own law and jurisdiction clauses.
GDPR Annex — Transfers from the EEA, Switzerland and the United Kingdom
G.1. When it applies. This Annex applies where the Customer is subject to the GDPR, the UK GDPR or the Swiss Federal Act on Data Protection ("FADP") for Customer Data, and Teachfluence's processing involves a transfer of that data to Türkiye or another country without an adequacy decision.
G.2. Standard Contractual Clauses. The standard contractual clauses approved by Commission Implementing Decision (EU) 2021/914 (the "SCCs") are incorporated into this DPA by reference, with the Customer as data exporter and Teachfluence as data importer, as follows:
- Module Two (controller to processor) applies where the Customer is a controller; Module Three (processor to processor) applies where the Customer is itself a processor for a third party.
- Clause 7 (docking clause) applies.
- Clause 9(a): Option 2 (general written authorisation), with the notice period in Clause 7.3 of this DPA.
- Clause 11(a): the optional redress wording does not apply.
- Clause 13: the competent supervisory authority is the one determined under Clause 13(a) for the data exporter.
- Clause 17: Option 2 — the law of the EU Member State in which the data exporter is established; where that law does not allow third-party beneficiary rights, the law of Ireland.
- Clause 18(b): the courts of the EU Member State whose law governs under Clause 17.
- Annex I.A (parties): the parties in Clause 1.1 of this DPA. Annex I.B (description of the transfer): Annex A of this DPA; transfers are continuous for the duration of the Main Agreement. Annex I.C: as under Clause 13. Annex II (security measures): Annex B of this DPA. Annex III (sub-processors): Annex C of this DPA.
G.3. United Kingdom. For transfers subject to the UK GDPR, the International Data Transfer Addendum to the EU Commission Standard Contractual Clauses issued by the UK Information Commissioner (version B1.0) applies, completed with the information in G.2. For Table 4, neither party may end the Addendum under its Section 19.
G.4. Switzerland. For transfers subject to the FADP, the SCCs apply with these changes: references to the GDPR are read as references to the FADP, the Swiss Federal Data Protection and Information Commissioner is the competent supervisory authority, and the term "Member State" does not exclude Data Subjects in Switzerland from bringing claims in their place of habitual residence.
G.5. Government access requests. If Teachfluence receives a legally binding request from a public authority for Customer Data covered by this Annex, it handles the request in line with Clause 15 of the SCCs: it notifies the Customer where legally permitted, challenges the request where there are reasonable grounds to consider it unlawful, and discloses only the minimum required.
Annex A — Description of the Processing
A.1. Subject matter and purpose: providing the Platform to the Customer: publishing the Customer's website and pages; registering students and contacts; selling and delivering courses, digital products, live events and memberships; access to learning content, progress, exams, assignments and certificates; running payment and invoicing processes; sending emails, notifications and campaigns; community, support and messaging; forms and surveys; CRM and analytics; integrations and AI features that the Customer enables.
A.2. Nature of the processing: hosting, storage, recording, organisation, retrieval, transmission, export and erasure.
A.3. Categories of Data Subjects:
- the Customer's students, buyers, members and subscribers;
- visitors to the Customer's site and people who fill in its forms;
- team members the Customer adds to the Platform (instructors, administrators, support staff);
- other people whose data the Customer brings to the Platform (for example leads and mailing-list subscribers).
A.4. Types of personal data:
Category | Examples |
|---|---|
Identity and contact | Name, email, phone number, profile photo |
Billing details | Billing address, tax number or Turkish national ID number (for e-Fatura or e-Arşiv invoices), company name |
Transactions | Orders, subscriptions, refunds and coupon records |
Payment metadata | The card token issued by the payment provider, last 4 digits and card brand. Card numbers and CVV are never stored on the Platform |
Learning data | Enrolments, progress, video viewing, exam and quiz answers, assignment submissions, certificates |
Communications | Support tickets, messages, community posts and comments, email engagement |
Customer-defined data | Custom fields, form and survey answers, tags and CRM notes defined by the Customer |
Technical data | IP address, browser and device information, session records, push-notification device tokens |
Audio and video | Recordings of live sessions and videos the Customer uploads, to the extent they show people |
A.5. Special categories of data: the Platform's standard features do not collect special categories of personal data. The Customer can, however, collect such data through forms, surveys and custom fields it defines (for example philosophical beliefs stated in belief surveys or profile fields); in that case meeting the conditions of Article 6 KVKK and Article 9 GDPR, and taking the adequate measures set out in Personal Data Protection Board decision No. 2018/10, is the Customer's responsibility. The Platform does not verify End Users' age. The Customer decides whether to accept End Users under 18; if it does, obtaining the parent's or guardian's consent required to process their data, and informing them, is the Customer's responsibility.
A.6. Duration: for the term of the Main Agreement and until the deletion periods in Clause 12 have ended.
Annex B — Technical and Organisational Measures
Teachfluence applies the measures below. No control or certification is promised beyond what this list states.
B.1. Hosting and encryption
- The database and file storage are in AWS eu-central-1 (Frankfurt) and are encrypted at rest with AWS KMS.
- The database is not reachable directly from the internet; it is backed up automatically at least daily and backups are kept for 30 days.
- Uploaded files and videos are protected by object versioning; previous versions of deleted or replaced files are permanently deleted after 30 days.
- Files with restricted access, such as attachments, invoices and protected videos, are served only through signed, time-limited links.
- All traffic over the internet is encrypted with TLS.
B.2. Authentication and access
- Passwords and one-time sign-in codes are stored only as scrypt hashes.
- Each organization's data is logically separated; access is checked against organization membership and role.
- Users sign in with a password, a one-time code or OAuth; no shared or hidden administrator credentials are used.
B.3. Development and operations
- Production secrets (API keys, database credentials) are kept in a managed secret store; automated scanning blocks secrets from entering source code.
- Personal data and secrets are removed from application logs. Server-side error monitoring is configured not to send personal data.
- Security-relevant events (sign-ins, permission changes, etc.) are logged.
- Code changes pass automated checks before they are deployed.
B.4. Payment security
- Card details are entered on the payment provider's page; card numbers and CVV never reach and are never stored on the Platform.
B.5. Personnel
- Staff who can access Customer Data are bound by confidentiality, and their access is limited to their role.
Annex C — Sub-processors
Current list: https://teachfluence.com/yasal/subprocessors. The list is updated under the notice procedure in Clause 7.3, and each update changes its version number and date.
