মূল অংশে যান

আইনি

চুক্তিগুলো, সহজ ভাষায়।

প্রতিটি নথির সংস্করণ রাখা হয়, আর প্রতিটি সংস্করণে লেখা থাকে কবে থেকে তা কার্যকর।

ডেটা প্রসেসিং

সংস্করণ ১ · কার্যকর ২৮ অক্টোবর, ২০২৬

খসড়া। এই লেখা এখনো কার্যকর নয়।

এই দলিলটি ইংরেজিতে।

What this addendum is

This addendum is part of our terms. It applies whenever [Company legal name] (“we”) processes personal data for your platform.

You are the controller: you decide why and how the personal data of your staff, learners, guardians and buyers is used. We are your processor: we process it for you, on your instructions, and for nothing else.

Where this addendum and our terms disagree about personal data, this addendum wins.

Whose data, and what data

It covers the people your platform deals with: your staff, your learners, their guardians, the people who enquire or buy on your site, and the people who visit it.

It covers whatever your platform holds about them. That depends on the modules you use, and can include:

  • names, contact details, sign-in details and language;
  • enrolments, batches, attendance and progress through courses;
  • exam attempts, answers, marks and results;
  • fees, orders, payments, receipts and refunds, with the buyer's IP address and location kept as evidence of each order;
  • messages sent to learners and guardians, and whether they arrived;
  • marketing consent, and the forms your site captured;
  • files and videos your staff and learners upload;
  • your platform's activity log.

Your instructions

Your instructions are our terms, the settings you choose, and what your staff do in your platform. We process your platform's personal data only to run your platform for you.

We don't use it for our own purposes.

If we think an instruction breaks data protection law, we tell you.

Your part as controller

You need a lawful basis for what you collect, and you tell your people about it. Your site's privacy page is yours to write; we never write it.

Where a learner is a child, you get the consent your law requires, from a parent or guardian where it is needed.

You decide what goes into the fields you add. If you record special categories of data, such as health, you need a lawful basis for that too.

You decide who on your staff sees what, through the roles you give them.

You choose and contract with the services you connect yourself: your payment gateway, your AI provider, your WhatsApp Business account. They work for you, not for us, so they are not our subprocessors.

Our people

Only our staff who need to can reach your platform's data, and they work under a duty of confidentiality.

Our office has three roles, support, billing and admin, each with a fixed set of acts. Our staff always sign in with a second factor, and every act they take on a customer is logged with its reason.

Outside a support visit, our office sees how your platform is set up and billed, not your people's records.

Support visits

Our staff look inside your platform only on a support visit:

  • every visit states its reason, ends by itself, and is logged before it starts;
  • your owner is emailed when a visit starts, with its reason and its time on your platform's clock;
  • by default, our support staff need your grant. You can grant access for a day, a week or a month, and end it at any time;
  • in an emergency, one of our administrators can enter without your grant, giving a reason. Your owner is emailed at once, and the entry always shows on your platform's log;
  • a visit can only read until one of our administrators allows it to make changes.

Subprocessors

Other companies do parts of the work for us: hosting, the database, file storage, email delivery, text messages and video hosting. Our subprocessors page lists them by job, with the data each receives.

Each is bound by a written agreement that protects your data at least as well as this addendum, and we stay responsible to you for their work.

We tell you before we add or replace one: [Notice period for a new subprocessor — set before launch]. You can object: [How a customer objects — set before launch].

Security

Some of the ways we protect your platform's data:

  • each platform's data is kept apart by the database itself, under a rule a platform can't bypass;
  • the keys to your own services are encrypted when stored and never shown back;
  • sign-in links and codes work once, and your platform can ask for a fresh two-step code before acts you mark as sensitive;
  • uploaded files are checked by what they contain, and served with a type we set;
  • formatted text your authors write is cleaned of scripts before it is stored and again before it is shown, and embed code they paste runs only inside a closed-off frame;
  • a bulk export of your records is logged before the file leaves;
  • [Encryption in transit and at rest — confirm at launch].

Helping you answer your people

Your staff can find, correct and remove a person's records, and take out what your platform holds, so you can answer people's requests yourself.

If someone asks us directly about data your platform holds, we pass the request to you, and don't answer it ourselves unless the law requires us to.

Marketing consent your site captures is kept as a history of every change, never rewritten, and a withdrawal stops marketing to that person at once.

Breaches

If we learn of a security breach that affects your platform's personal data, we tell your owner without undue delay, and in any case within [Breach notice period — set before launch].

We tell you what we know, and keep telling you as we learn more.

How long we keep it, and deletion

Today's periods are:

  • your platform's data: while the platform exists;
  • your platform's activity log: 180 days by default. Our staff can set it between 90 and 3,653 days for your platform;
  • receipts and other money documents: at least 10 years, counted from the end of the calendar year they were issued in, and each order's location evidence for the same period. We can lengthen this for your platform; nobody can shorten it;
  • when your plan ends, the platform shuts and its data is kept. Once it has been shut for 90 days since its plan ended, we schedule its deletion and email your owner the date;
  • a deletion waits 20 days, and can be cancelled until then. Then every record, file and domain claim of the platform is removed;
  • until then, your owner can take everything out in one archive, even while the platform is shut;
  • payments we recorded by hand, and our own log, are our records as controller, not yours, and are kept for their own periods, given in our privacy notice;
  • backups: [Backup retention — set before launch].

Showing that we keep to this

On request, we give you the information you need to show that we keep to this addendum.

Audits: [Audit terms — set before launch].

Where data is kept, and questions

Your platform's data is kept in [Hosting region — named at launch]. Where it leaves a country whose law restricts that, we protect it with [International transfer safeguards — set before launch].

The liability section of our terms applies to this addendum too.

Questions: [Privacy contact email].