Skip to content
← Back to home

Privacy Policy

Last updated: 15 November 2026

This Privacy Policy explains how Polatof, trading as Edunison, handles personal data. It is written to meet Regulation (EU) 2016/679 ("GDPR") and Turkish Law No. 6698 on the Protection of Personal Data ("KVKK"), which impose materially similar duties on us. Where you are reading the Turkish version of this page, that version is the operative text for services sold in Türkiye.

1. Who we are, and in which role

The company behind Edunison:

Polatof Yapı Üretim Sanayi Ticaret Anonim Şirketi, a joint stock company incorporated in the Republic of Türkiye ("Polatof", "we", "us"), trading as Edunison.

Registered address: Şirinevler Mah., Meriç Sk. Özgül No:17 İç Kapı No:11, 34188 Bahçelievler/İstanbul, Türkiye.

MERSIS: 0732198180300001 · Tax ID: 7321981803 (Kocasinan Tax Office) · Trade registry: Istanbul Chamber of Commerce, No. 1028656.

Contact: support@edunison.com · +90 555 650 41 11.

Edunison is school and course management software delivered as a service. Our role under data protection law depends on whose data is involved, and the distinction decides who you should approach:

Controller. For the account, contact, billing and usage data of the institution that buys Edunison and of the staff who use it, we decide why and how the data is processed. We are the controller and we answer requests directly.

Processor. For the personal data an institution enters about its students, parents, guardians and staff, the institution decides why and how it is processed. The institution is the controller; we act only on its documented instructions. If you are a student or a parent, your first point of contact is your school, not us — we will forward requests we receive to the institution concerned.

We do not sell personal data, we do not use it for advertising or profiling, and we do not use customer content to train machine learning models.

2. Categories of personal data

As controller, for our customers and their staff:

Identity and contact data: name, surname, job title, email address, telephone number, postal address.

Account data: username, role and permission assignments, login and session records, language preference.

Billing data: institution name, tax identifiers, subscription and payment records. Subscription fees are paid by bank transfer; we never receive or store card numbers.

Technical data: IP address, device and browser information, application logs, error reports.

As processor, on behalf of the institution, the categories its own configuration determines — typically:

Student and guardian identity and contact data, including data about children.

Academic records: classes, timetables, attendance, homework, examinations and results.

Financial records relating to tuition: fee schedules, instalments, payments and receipts.

The school's payment settings: the user the school allows to manage payment settings (by default the school owner) can record, in the staff panel and in the mobile app, the bank name, account holder name and IBAN of the account the school collects payments into. They are processed so that the school can manage how it takes payments from families. Viewing or changing the payment settings requires that permission. Every change to the IBAN is written to the security log together with the user who made it and when. This record is separate from card details, which are entered on the payment provider's own page during an online payment and are not sent to Edunison.

Any files or free text the institution chooses to upload.

Health data (a special category of personal data): documents such as a medical note that authorised school staff may choose to attach to a student's record. They are visible only to school staff permitted to view student records; they are not shown in the parent or student portal, are never used for advertising, marketing or analytics, and are not shared with third parties.

3. Why we process it, and on what legal basis

As controller, we rely on the following legal bases under Article 6(1) GDPR (and the corresponding grounds in Articles 5 and 6 KVKK):

Performance of a contract (Article 6(1)(b)): creating and running the institution's account and subdomain, delivering the software, providing support, and handling subscriptions, invoicing and payments.

Legal obligation (Article 6(1)(c)): retaining accounting, tax and commercial records as Turkish law requires, and responding to lawful requests from competent authorities.

Legitimate interests (Article 6(1)(f)): keeping the service secure and available, preventing abuse, diagnosing faults and improving the product. We balance these against your interests and you may object as described in section 8.

Consent (Article 6(1)(a)): analytics cookies on our public marketing pages, and nothing else. Consent can be withdrawn at any time without affecting the service.

As processor, the legal basis for student and guardian data is determined by the institution acting as controller, not by us.

Health data such as a medical note is special-category data (Article 9 GDPR; Article 6 KVKK). The institution, as controller, decides the condition under which it is processed and obtains a parent's explicit consent where its law requires it. Edunison never requires a medical note to be uploaded.

4. Who we share it with

We use a small number of service providers ("sub-processors") to run Edunison. Each is bound by a written agreement, may process personal data only on our instructions, and is listed here so you can assess them:

Vercel Inc. (United States) — application hosting and delivery.

Neon Inc. (United States) — managed PostgreSQL database. The database that holds customer data is provisioned in the European Union (Frankfurt, eu-central-1).

Vercel Blob (region fra1, Frankfurt, European Union) — storage for files uploaded through the product.

Resend (United States) — transactional email delivery (password resets, notifications).

Functional Software, Inc. d/b/a Sentry (United States) — application error monitoring.

iyzi Ödeme ve Elektronik Para Hizmetleri A.Ş. ("iyzico") (Türkiye) — processing of tuition payments that an institution collects online through its own iyzico merchant account. Card data is captured and stored by iyzico, never by us.

ImprovMX (France) — inbound email forwarding for our support address.

Google Ireland Limited — Google Analytics, on our public marketing pages only and only with your consent. It is not present in the administration panel or the family portal.

We also disclose personal data to competent public authorities where we are legally required to do so, and to professional advisers under a duty of confidentiality. If we are ever involved in a merger or sale of the business, personal data may transfer to the acquirer, subject to this policy.

We give reasonable prior notice of a new or replacement sub-processor to customers who ask to be notified, so that they can object.

5. International transfers

We are established in Türkiye, and some of our providers are established in the United States. Personal data is therefore transferred outside the European Economic Area and, in some cases, outside Türkiye.

Where personal data is transferred out of the EEA, we rely on the European Commission's Standard Contractual Clauses (Commission Implementing Decision (EU) 2021/914) as incorporated into our agreements with the providers named above, together with the supplementary technical measures described in section 7 — in particular encryption in transit and storage of customer data inside the European Union. Where the recipient is certified under the EU-U.S. Data Privacy Framework, we may rely on that adequacy decision instead.

Transfers out of Türkiye are made in accordance with Article 9 KVKK, on the basis of the undertakings, standard contracts or explicit consent that the legislation requires.

You may request a copy of the relevant transfer safeguards by writing to support@edunison.com.

6. How long we keep it

Customer and account data: for the life of the subscription and for as long afterwards as we need it to resolve disputes or enforce our agreements.

Accounting, invoicing and tax records: ten (10) years, as Turkish commercial and tax legislation requires.

Data we hold as processor: for the duration of the subscription. On termination we return or delete it within thirty (30) days, at the institution's choice, except where law requires us to keep it longer.

Database backups: our managed database provider keeps three kinds of copy, each used only to restore and verify the service and each with access restricted. First, a change history that lets the database be returned to an earlier point in time; it covers at most the last seven (7) days of changes. Second, automatic daily backups; each is deleted automatically by the provider fourteen (14) days after it is taken. Third, backup copies (snapshots or copies of the database) taken manually before maintenance or a data migration; these currently have no predetermined deletion date. Deleted data therefore leaves the change history and the daily backups within about fourteen (14) days, but may remain in a manually taken copy until that copy is deleted.

Student documents (including medical notes): deleted from the database when the school deletes the document or the student's record; what is said above about backups and the recovery window applies to them too.

Homework files: when a user removes a file they attached to homework, it is deleted from the file store and no longer served; it can take a few minutes to leave the provider's cache. How long deleted data takes to be permanently destroyed within the provider's own infrastructure depends on the provider.

Security and error logs: kept only as long as needed for diagnosis and abuse prevention.

7. How we protect it

We apply technical and organisational measures appropriate to the risk, including:

All traffic encrypted in transit over TLS; data at rest encrypted by our hosting providers.

Passwords stored only as bcrypt hashes; password reset links stored as hashes, valid once and for sixty (60) minutes; changing a password invalidates every existing session.

Strict separation of each institution's data: every query against customer-owned tables is scoped to the institution it belongs to, and that scoping is enforced by automated tests that fail the build if a new query omits it.

Role-based access control with per-user permission overrides, each recorded with its reason and an audit trail.

Scheduled jobs and internal endpoints authenticated by secret; administrative functions reachable only on a separate console host.

Continuous error monitoring, dependency review, and an automated test suite that must pass before any change reaches production.

No system is perfectly secure. If a personal data breach occurs, we will notify the competent supervisory authority within 72 hours where the GDPR requires it, notify affected institutions without undue delay so they can meet their own obligations, and notify individuals directly where the law requires.

8. Your rights

Where we act as controller and the GDPR applies to you, you have the right to: access your personal data and receive a copy (Article 15); have inaccurate data corrected (Article 16); have data erased (Article 17); restrict processing (Article 18); receive your data in a portable format (Article 20); object to processing based on our legitimate interests, including at any time (Article 21); and not be subject to decisions based solely on automated processing producing legal or similarly significant effects (Article 22) — we do not make such decisions.

Where Turkish law applies, Article 11 KVKK gives you materially the same rights, including the right to learn whether your data is processed, to request correction or erasure, to learn the third parties to whom it has been transferred, and to claim compensation for damage caused by unlawful processing.

Where processing rests on consent, you may withdraw it at any time; withdrawal does not affect processing carried out before it.

To exercise any of these rights, write to support@edunison.com or to the postal address above. We will respond within one (1) month under the GDPR and within thirty (30) days under the KVKK. We may ask for information to verify your identity, and we will not charge a fee unless your request is manifestly unfounded or excessive.

If your request concerns data an institution holds about a student or parent, we will refer you to that institution, which is the controller.

9. Children

Edunison is sold to schools and course providers, not to children, and we have no direct relationship with students. Student accounts — including those of students under 18 — are created by the school the student attends.

For children's data, the school is the controller. It decides the legal basis for processing and obtains parental consent where its national law requires it. We process children's data only as a processor, on the school's instructions and only to provide the service.

Children's data is never used for advertising, marketing or profiling, never sold, and never shared with third parties for their own purposes.

In the web portal, students see only their own records (timetable, attendance, homework, announcements); student accounts cannot sign in to the mobile app. Each institution's data is kept separate from every other institution's. There is no open chat in the portal in which students could contact people they do not know.

Parents can see their child's information in the parent portal and can ask the school to correct or delete it.

A school may attach a student's medical note to their record. It is not shown in the parent or student portal; only school staff permitted to view student records can see it. Parents can ask the school to correct or delete it.

We apply the same security measures to children's data as to all other customer data, and we do not use it for any purpose of our own.

10. The Edunison mobile app

The Edunison Android app opens your school's Edunison address and provides the same service as the panel and the parent portal on the web. This policy applies to the app as well.

The app is for school staff and parents. Student accounts cannot sign in to the app; students use Edunison through their school's web address in a browser and keep all their rights in the web portal. When the school opens a new staff or parent account, it confirms that the person is 18 or over and, for a parent account, that the person is not the student. No date of birth is asked for this; the confirmation is recorded together with the school user who gave it.

Accounts: accounts are created by your school; there is no sign-up in the app. You sign in with the account your school gave you.

Choosing a school: the first time you open the app you enter your school's address (for example, schoolname). It is stored only on your device and can be changed with "Change school".

Session: when you sign in, session information is stored on your device and ended by "Sign out".

Camera and files: Android app packages up to and including version code 3 declare the camera permission. The app can use it only when you use a photo-taking field on a page, and only after asking for your permission; Edunison pages currently have no such field. The source code prepared for the new package, version code 4, does not include the camera permission. A photo or document (for example a PDF) is uploaded only if you choose it from your device and upload it.

What the app does not ask for: any location permission (GPS or otherwise, precise or approximate), or access to contacts, microphone or calendar. It shows no ads and collects no advertising ID. The school screens (panel and portal) run no analytics or user tracking. Even if you open Edunison's marketing pages from inside the app, no analytics runs on them.

Error reports: when something goes wrong, the technical details of the error (the error message and code lines, the browser or device type, and the address of the page where it happened) are sent to our provider Sentry. Error reporting is configured so that your password, session cookies, the information you type into forms, the query part of addresses and the security keys in links are not attached to reports, or are removed from them before they are sent. The app tells Sentry not to add your IP address to the report; the connection's IP address still technically reaches Sentry's servers when the report is sent. Error reports are used only to fix errors and are kept at Sentry for the retention period of our service plan.

Approximate location and time zone in error reports: while Sentry receives and processes an error report, it can derive approximate geographic information (at country, region or city level) from the connection's IP address, and the browser adds the device's time zone to the report. In our Sentry account the setting that prevents IP addresses from being stored is on, and data-scrubbing rules remove these geographic fields and the time zone, so they are not written to stored error records. In other words, Sentry may process this information briefly while diagnosing an error, but it is not kept in the error records. We verified this with synthetic test reports containing no real person's data: the stored records contained no IP address, geographic fields or time zone. How Sentry handles this information inside its own infrastructure while processing it is governed by Sentry's own practices. This processing is for diagnosing errors only and is not analytics: no Google Analytics or other analytics tool runs on the school screens (panel and portal).

Payments: if your school offers online payment, you pay on iyzico's payment page through the school's own iyzico account; card details are entered on that page and are not sent to Edunison. Student accounts cannot sign in to the app; in the web portal, student accounts cannot start a payment unless the school separately allows it. A school user with permission to manage payment settings can also record the school's bank name, account holder and IBAN in the app; this record is separate from card details and is described in section 2.

All traffic is encrypted (HTTPS).

11. Asking for your personal data to be deleted or anonymised

You can ask for your personal data to be deleted or anonymised. Three things are different from each other:

Creating an account: accounts are created by your school; there is no sign-up in the app.

Closing an account: your school can close your portal account. A closed account can no longer sign in and its open sessions end, but closing an account does not delete your personal data.

Deleting personal data: this is requested separately, as described below.

How to ask: email support@edunison.com with the subject "Personal data deletion request", stating your school and the email address you use in Edunison. Please write from your registered address if you can, so that we can confirm the request is yours; we may ask for further information to verify your identity. For students under 18, a parent or legal representative may make the request on their behalf.

What this address does: support@edunison.com is the contact address that receives requests and passes them to the right party. If your request concerns data your school has entered into the platform, we forward it without delay to your school, which is the controller, and tell you that we have done so.

Who decides: our role depends on whose behalf and for what purpose the data is processed, and is assessed for each processing activity. For student, parent and staff data that your school enters into the platform, the school is, as a rule, the controller; Polatof acts as a processor on the school's instructions, and the request is handled as the school decides. For data Polatof processes for its own purposes (for example the institution's customer account, billing and support correspondence), Polatof is the controller and handles your request directly. Where the role is not clear, we say so in our reply.

Records that may not be deleted at once: the education contract, payment and accounting records, and other records that the law requires to be kept cannot always be deleted immediately, before their legal retention period ends. During that period they are kept only for the relevant obligation, with access restricted; when the period ends, they must be deleted, destroyed or anonymised.

Timing and outcome: under Turkish law (Law No. 6698, Article 13, and Article 12 of the Regulation on the Deletion, Destruction or Anonymisation of Personal Data), the controller concludes your request and informs you within thirty (30) days of receiving it. If none of the conditions for processing the data still applies, the Law and the Regulation require the data concerned to be deleted, destroyed or anonymised within that period and, if it was previously transferred to third parties, those third parties to be notified. If a condition for processing still applies (for example a legal obligation to keep the record), the request may be refused for that data with the reasons explained; the refusal is also given in writing or electronically within thirty (30) days. When the retention period ends, that data must be deleted, destroyed or anonymised within the periodic destruction interval set in the controller's retention and destruction policy, which under the Regulation may not exceed six (6) months.

Where the GDPR applies: the controller responds without undue delay and in any event within one (1) month of receiving the request. That period may be extended by up to two (2) further months where necessary, taking into account the complexity and number of requests; if so, you are told of the extension and the reasons for it within the first month.

Backups: backups are not a reason to postpone deletion. How backups are kept is described in section 6; when a deletion request is carried out, our reply also says what was done about copies remaining in backups.

Uninstalling the app: uninstalling the app does not delete your account or the personal data we hold on our servers. The school address and session stored on your device are normally removed with the app, but this can depend on your device and operating-system settings (for example device backups).

12. Complaints

If you believe we have handled your personal data unlawfully, please contact us first at support@edunison.com so that we can put it right.

You also have the right to lodge a complaint with a supervisory authority — in the EEA, the authority of the country where you live, work, or where the alleged infringement took place; in Türkiye, the Personal Data Protection Authority (Kişisel Verileri Koruma Kurumu, kvkk.gov.tr).

13. Changes to this policy

We may update this policy as the product or the law changes. The date at the top of this page shows when it was last revised. If a change materially affects how we handle personal data, we will tell our customers by email before it takes effect.