Skip to content

Version 1.0.9

Privacy Policy

In force since November 18, 2026

This Privacy Policy explains what personal data Young Researchers Hub collects, why, on what legal basis, where it is kept, who can see it, how long we keep it, what rights you have and how quickly we answer. It applies to every user, wherever they live. It is written under the Law of the Republic of Kazakhstan "On Personal Data and Their Protection" (No. 94-V, as amended in 2026, "the Law"), the Rules on collecting and processing personal data ("the Rules") and the Digital Code of the Republic of Kazakhstan, and it applies the stricter rules on children of our users' countries to everyone.

1. Who is responsible

  • Owner and operator of the database: ИП AQZ(Sanzhar Kakenov) (030610551247), an individual entrepreneur, Kosshygulova 124,Kokshetau,Kazakhstan. Your data is processed by this operator only.
  • A company later. The operator may later set up a company (ТОО) to run the Platform. No such company exists today, and your consent does not cover a transfer to one. If a company is set up, we will first tell you its full name and BIN, explain what would be transferred and why, and establish the legal basis for the transfer at that time, asking for your new consent wherever the law requires it. Nothing is transferred before that.
  • Person responsible for organising personal-data processing: the operator named above, reachable at [email protected]. (Article 25 of the Law requires this appointment from a legal entity; while the operator is an individual, the operator fills this role.)
  • Contact for privacy requests: [email protected]. General contact: [email protected].
  • Supervisory authority: the authorised body for personal-data protection of the Republic of Kazakhstan (the Ministry of Artificial Intelligence and Digital Development). You may complain to it, or to a court, at any time.

2. One standard for everyone

All personal data of all users, whatever their country, is stored in a database and file storage located in the Republic of Kazakhstan, on a server rented from the hosting provider PS.kz; every backup is kept in Kazakhstan too (Section 7). Some services that deliver email, protect the site or take payments receive part of the data abroad; Section 6 lists each one. We apply the strictest rules our users' countries require to everyone: nobody under 14, a parent's consent under 18, privacy by default for minors, no advertising and no tracking, and the same rights for everyone.

3. What we collect, why, and on what legal basis

Under Kazakhstan law we process personal data with your consent (or, for a child, the parent's consent), except where a law allows or requires processing without it (Article 7(1) and Article 9 of the Law). The consents are:

  • the Personal Data Consent ("Consent to the Collection and Processing of Personal Data"), with the consent to the cross-border transfers it lists: an adult ticks it at sign-up; for a child aged 14 to 17 the parent gives it when confirming the child's account;
  • separate consents asked at the moment they are needed, each recorded on its own: a public profile (adults: in the Personal Data Consent, switchable in Settings; a minor: the parent's "Profile" permission), the publication of an author's name, the author's licence, the newsletter, session participation, the recording of sessions with a student under 18, a child attending a session alone, the background check of a mentor, the Mentor Agreement, PayPal payouts and a payment through our international reseller.
Data Why we hold it Basis under Kazakhstan law
Account: name, email address, password (hashed), account type (school student, undergraduate, PhD student, researcher, teacher, professor or parent; a researcher is a post-doc or a recent graduate), country, date of birth, language to run your account, apply the age rules, send you codes and notices the Personal Data Consent; for a child, the parent's consent (until the parent confirms, see Section 4)
Optional sign-up answers: what brings you here, how you heard of us, the promo code or link you used, the country your connection came from to understand who the Platform serves and to report aggregate numbers to schools and funders the Personal Data Consent; each answer is optional
Parent (guardian) link and the record of each consent: who gave it, for whom, the document version and its text, the time, language, hashed IP address and browser a minor's use of the Platform rests on the parent's consent; proof of every consent the parent's consent; keeping the proof is the operator's duty to prove consent (Article 25(2)(5) of the Law)
Institutional email address (encrypted) and verification status; a teacher's confirmation the "Verified" badge and eligibility rules: it is needed to apply to mentor and to comment, not to submit a paper; re-checked every 12 months the Personal Data Consent; you start each verification yourself
Profile: display name, headline, biography, institution, department, year, city, research interests, photo, ORCID and other research identifiers, links your researcher profile, shown according to your visibility setting (minors: Section 4) the Personal Data Consent; showing it publicly: the publication clause of that consent (adults) or the parent's "Profile" permission (minors, members only) (Article 7(3) of the Law)
Submissions: manuscripts, figures, tables, supplements, cover images, declarations (including how AI tools were used), ethics approvals, co-author details, reviews and editorial decisions. Location and camera data are removed from images when they are uploaded the editorial process; for published papers, the scholarly record the Personal Data Consent; publishing an author's name and affiliation: the separate consent to the publication of the name and the licence in the Author Agreement (Article 7(3) of the Law)
Comments, reports and moderation records community features and keeping them safe the Personal Data Consent
Mentor applications: CV, motivation, a photo of a student ID card (students), a degree certificate (master's and PhD students, and researchers; a researcher without a university email may apply with the certificate instead), interview notes (encrypted), results and dates of identity, police and reference checks checking the level of study or qualification of people who will work with students, and vetting them the Personal Data Consent; the background-check consent before a police certificate is uploaded; the Mentor Agreement
Mentor tax status: for a mentor in Kazakhstan, the ИИН (encrypted; only its last four digits in clear) and the self-employed or ИП declaration; for a mentor elsewhere, the declaration that they pay their own taxes and, optionally, a residency certificate paying mentors lawfully: a payout is the mentor's agreed share; YRH withholds tax or pays social contributions only where the law requires it, and before the first payout confirms with the mentor how this applies to them the Personal Data Consent and the declaration the mentor gives under the Mentor Agreement
Messages with mentors: the text, who wrote it and when, whether it was read, and when we last emailed you about the conversation letting students and mentors talk on the Platform; a parent's oversight of a minor's messages; handling reports the Personal Data Consent (for a child, the parent's)
Bookings: the mentor, the student, the time slot and time zone, the status, a parent's approval, a parent's permission for the child to attend a session alone, the price, and the meeting link (encrypted) arranging sessions, reminders, cancellations and refunds the Personal Data Consent; the session-participation consent (adult or parent)
Fee waiver applications: which fee and paper, level of study, school or university, country and city, and your answers about your financial situation, other support, your research and why science matters; for a minor, the notice we send the parent deciding whether to waive a fee the Personal Data Consent (for a child, the parent's); you choose to apply
Recordings of sessions with students under 18, which the mentor uploads within 24 hours after each session (we do not record sessions ourselves) checking that sessions with minors are safe, handling complaints and safeguarding concerns, and deciding the mentor's payout the parent's recording consent, given before the first session
A mentor's explanation of a missing recording: the cause the mentor chooses (a technical failure on their side, a problem with YRH or the video service, or something else), their text, an optional evidence file, and the staff decision with its note reviewing the case and deciding whether the mentor is still paid the Mentor Agreement and the Personal Data Consent
Payment records: what was paid for, amount, currency, the provider and its reference, receipts, refunds; for Premium, the dates of a free trial (no card is asked for it), the next monthly renewal date and the provider's reference for the renewal; for a bank transfer, the date and a staff note; never card numbers charging fees, paying mentors, refunds, tax and accounting the Personal Data Consent and the Terms of Sale; keeping the records for the legal period: the accounting and tax laws (Article 9(10) of the Law)
Mentor payout details: for a mentor in Kazakhstan, the bank account details (encrypted); for a mentor outside Kazakhstan who chooses PayPal, the PayPal email address (encrypted) paying mentors the Personal Data Consent and the Mentor Agreement; for PayPal, the mentor's separate PayPal consent
Messages sent through the contact form: name, email address, topic, message and the language of the page answering you; a message sent with the topic "A complaint" goes into the complaints register (next row) your consent, given by sending the message after reading the notice next to the form
Complaints about a payment, a session or another service, however they reach us (the complaint button on a session page, the contact form, email, a letter, in person or by phone): your name, your email or postal address, your account if you have one, the complaint, our reply, and the dates received and answered considering the complaint and giving you the reasoned written reply the law requires within 10 calendar days, and being able to show later that we did the seller's duty to consider a consumer's complaint and to reply in writing (Article 42-4 of the Law "On Protection of Consumer Rights"; Article 9(10) of the Law)
Newsletter subscription and preferences sending the newsletter you asked for the newsletter consent (confirmed by email)
Audit log of security-relevant actions: who did what, when, from which truncated IP address security, accountability, the record of actions with personal data the operator's duties to protect personal data and to record actions with it (Article 22 of the Law)
Interns' confidentiality agreements: the signed copy each intern uploads, and the date a staff member checked it showing that everyone who works with personal data for YRH is bound to keep it confidential the agreement itself and the operator's duty to protect personal data (Article 22 of the Law)
Server logs with full IP address, user agent and request path security and troubleshooting members: the Personal Data Consent; visitors without an account: the operator's duty to protect the site and the data in it (Article 22 of the Law)
Daily counters (visits, sign-ups, submissions per country, promo code or language) the interest dashboard; they contain no personal data not needed

Without a consent or a legal ground listed here, we do not process the data. We may also give data to a Kazakhstan court or law-enforcement body that lawfully requires it (Article 9(1) of the Law), and, where a child is in danger and consent cannot be obtained, to the bodies that protect children (Article 9(5) of the Law).

For users in the European Economic Area and the United Kingdom. The GDPR also applies to you. In its terms, we rely on: performance of a contract (the Terms, the Terms of Sale, the Mentor Agreement) for your account, submissions, messages, bookings, payments and payouts; consent for the optional data, the newsletter, a public profile, the publication of your name and the session recordings; legal obligation for payment records and consent proof; and legitimate interests (a safe service, security, preventing abuse) for moderation, the audit log and server logs. You may complain to your local supervisory authority.

We do not collect precise location, device identifiers, contacts, or anything from third-party advertising or analytics services. There are no tracking cookies (see the Cookie Notice).

What we do with the data. We collect, record, organise, store, update, use, transfer (only as Sections 5 and 6 say), depersonalise, anonymise, block, destroy and delete personal data, by automated means and by hand, and only for the purposes in the table above. Where we can, we depersonalise data instead of keeping it: the daily counters hold no personal data, and 30 days after someone unsubscribes from the newsletter their address is replaced by a keyed hash.

Data about other people. Sometimes you give us data about someone else: the email address of a co-author or supervisor, so that we can invite them to your paper, or, if you are under 18, your parent's email address, so that they can confirm your account. Give it only if the person would expect it. We use it only for that invitation and for that paper or parent link, and the person can write to [email protected] to see, correct or delete it.

4. Minors (users under 18)

  • We do not create accounts for anyone under 14. If the date of birth entered is below 14, nothing is stored.
  • Between 14 and 17 a parent or legal guardian must confirm the account and give the consents on the child's behalf. Until the parent confirms, the account holds only what sign-up needs (name, email address, date of birth, the parent's email address and the child's acceptance of the Terms): the child cannot create a draft, upload a file or take part in a paper, and if no parent confirms within 30 days of sign-up, the account is deleted.
  • The parent sees exactly what the child shares, each consent separately, the child's submissions and mentoring threads, and can withdraw any consent or delete the account at any time. This one approval at the beginning also covers the child's later papers: the child may submit papers, invite co-authors and accept invitations, accept the Author Agreement and apply for a fee waiver without a further approval, and the parent is notified of each of these. If the parent withdraws the consent to the processing of the child's data, the account is deleted 10 working days later, unless a parent gives that consent again (Section 8).
  • A minor's profile is never public. Signed-out visitors and search engines never see it, and adults cannot search or filter for minors. Until the account is confirmed, and whenever the parent has not given the "Profile" permission, the profile is private: only the child, the parent and our safeguarding staff see it. With the parent's permission the child may make it visible to signed-in members whose email is confirmed; they then see only the display name, headline, research interests and number of publications, and the photo. A photo can be added only while that permission stands; if the permission ends, the photo is hidden at once and deleted 30 days later.
  • Adults can only message a minor in threads the parent can see, and the parent can read every message in them. Messages are not filtered automatically: an adult who asks a minor for contact details or to move the conversation elsewhere breaks our rules. Anyone can block messages from another member and report a message to the safeguarding lead.
  • A minor can write messages and book sessions only once the parent link is active. The parent approves each booking and pays for paid sessions. A parent's presence at the session is advised; a parent who cannot attend may allow the child to attend that session alone, and that permission is recorded.
  • We do not record sessions ourselves. The mentor records every session with a student under 18 on the meeting tool and uploads the recording to us within 24 hours after the session; we keep it in Kazakhstan for 90 days and then erase it. The parent agrees to this before the first session; if the parent withdraws that consent, the child's recordings are erased within 10 working days (Section 8).
  • On the child's 18th birthday the parent's access ends and the user is asked to accept the Terms and the Personal Data Consent themselves.

5. Who can see your data

  • You, through your account and the data export.
  • Your parent or guardian, if you are under 18, as described above.
  • Editors and reviewers, for the submissions they handle. Reviewers do not see each other, and authors never see a reviewer's identity.
  • Co-authors and supervisors of a submission see that submission.
  • Mentors see the messages you send them and your bookings with them. A mentor sees a minor as first name, last initial and grade only. The meeting link of a confirmed session is shown only to its participants (and the parent of a minor).
  • Our staff (administrators, editors, moderators and the safeguarding lead), each only within their role, after a second-factor login, and with every access to private files, session recordings and sensitive records written to the audit log. A session recording is opened only by safeguarding staff, when a complaint or a safeguarding concern requires it, with a stated reason. Editors may also open and read mentor applications (with their documents), data requests and complaints; the decisions on them stay with administrators (and, for mentors, with the safeguarding lead): an editor cannot approve or reject a mentor, carry out a request, delete an account or reply to a complaint.
  • People who work for YRH under a signed confidentiality agreement (for example interns), only the parts of the data their task needs: mentor applications, reports, Learn content, and data requests and complaints without the person's name or contact details. Every access is written to the audit log. An intern gets access only after uploading the signed copy of the agreement and after the staff member who appointed them, or an administrator, has checked it.
  • Other members and the public, only what your visibility setting allows: an adult's profile is public by default and can be limited to members or made private; a minor's profile is never public (Section 4).
  • Readers of the journal: published papers show the authors' names and affiliations as consented, under the Creative Commons licence (Section 8 explains how a name or a paper can be removed).
  • Our hosting provider PS.kz, whose server in Kazakhstan holds the database, the files and the backups, and the recipients in Section 6, each only for the purpose shown there.
  • Public authorities of the Republic of Kazakhstan, only when the law obliges us to give them data (for example on the lawful request of a court or a law-enforcement body), and only the data the request covers; and, to protect a child, the authorities named in Section 7 of the Terms of Use.

We do not sell personal data and do not share it with advertisers.

6. Where your data is, and processing abroad

Two rules of the Law apply, and we meet them separately:

  • Storage in Kazakhstan (Article 12(2) of the Law): the database, every uploaded file, every recording once uploaded and every backup are on servers in Kazakhstan. No service abroad holds the Platform's database or a copy of it.
  • Cross-border transfer (Articles 7(6) and 16 of the Law): some services below receive part of your data in another country while they deliver their service. Each such transfer is made only with your consent: the cross-border consent in the Personal Data Consent (for a child, given by the parent), or a separate consent at the moment of use, as the table says.
What Who holds or receives it (contracting party) Where Basis
The database, uploaded files, session recordings after upload, data exports the operator, on a server rented from PS.kz; hourly copies of the database on the same server, kept 48 hours Kazakhstan storage, not a transfer
Backups the hosting provider's own backup service: copies of the whole server, made and kept by PS.kz in Kazakhstan for up to 30 days; and, when we switch it on, an encrypted copy of the database and the files every 6 hours at a second provider in Kazakhstan, kept at most 12 months Kazakhstan storage, not a transfer
Email: your email address, name and the content of each message we send you; a message you send through the contact form, on its way to our mailbox Brevo (Sendinblue SAS) European Union(France,Germany,Belgium) the cross-border consent in the Personal Data Consent; for the contact form, your consent given by sending
Traffic in transit (including your IP address), the invisible bot check on forms, the login check in front of the staff area (staff email address) Cloudflare, Inc. global network, United States the cross-border consent in the Personal Data Consent
Interviews with mentor applicants: names, video and audio Microsoft, under the operator's own Microsoft Teams account outside Kazakhstan (Microsoft's data centres) the applicant's Personal Data Consent with its cross-border consent; the applicant books the interview
Sessions: the participants' names, video and audio during the session; and the recording of a session with a student under 18, which sits in the mentor's own Microsoft Teams or OneDrive account until the mentor uploads it to us (within 24 hours) and deletes it there Microsoft, under the mentor's own agreement with Microsoft outside Kazakhstan (Microsoft's data centres) the session-participation consent; for the recording, the parent's recording consent: because YRH requires the recording, we treat this copy abroad as a transfer made for us, not as the mentor's private matter
Card payments in tenge, and in US dollars where the pay page offers it: order number, amount, currency, a short description, and your email address where it is needed for the receipt our card payment provider (a payment organisation in the Republic of Kazakhstan), named in a new version of this policy before payments open Kazakhstan transfer to a third party inside Kazakhstan, under the version of the Personal Data Consent that names it
Payments in US dollars for Premium, and for the publication fee only once the reseller has confirmed in writing that it accepts it and we have switched this on (never the submission fee or mentoring sessions): order details, your name, email address, country and billing details our international reseller, as merchant of record: it sells to you in its own name and handles sales tax and receipts; named in a new version of this policy before payments open United States a separate consent asked on the payment page before you pay
Payouts to a mentor in Kazakhstan by bank transfer: the mentor's account details and the amount the operator's bank Kazakhstan the Personal Data Consent and the Mentor Agreement
Payouts to a mentor outside Kazakhstan who chooses PayPal: the mentor's PayPal email address, the payout amounts and the currency PayPal, the PayPal company named in the operator's PayPal user agreement United States the mentor's separate PayPal consent, asked when they choose PayPal

Payments are not open yet, so no payment provider receives any data today; before they open, a new version of this policy and of the Personal Data Consent names each provider. Card payments and paid sessions are switched on only from the day the payment page names the provider; you enter card details only on the provider's page, and we never see or store card numbers. When we check a new password against known breaches, only the first five characters of a one-way hash of it go to the Have I Been Pwned service: no password, email or name.

The following are not active. Each will be switched on only after this Policy is updated and the matching consent is asked for at the moment of use: Zoom Video Communications, Inc. (video sessions, participants aged 16 and over only; United States) and Google LLC (optional sign-in; United States).

Nothing else (no analytics script, font server, error tracker or AI service) receives personal data from the Platform. If we ever use an AI system to help screen manuscripts, it will run in Kazakhstan or under a consent requested from you first, and a human will always make the decision (see Section 10).

7. How long we keep data

The retention job runs every night. When a period ends, the record is deleted or anonymised that night; a file is made unavailable at once and erased from storage 30 days later, except a session recording, which is erased from storage at once.

Data Kept for
Account data until you delete the account (30-day grace period, during which the account is blocked), then deleted or anonymised
A minor's account the parent never confirms 30 days after sign-up, then deleted
A minor's account after the parent withdraws the consent to the processing of the child's data (or the last parent's link to the child ends) blocked at once; deleted on the 10th working day after the withdrawal, unless a parent gives the consent again before then (Section 8)
Parent link and consent records the life of the account plus 3 years, as proof, reduced to identifiers, versions and timestamps after deletion
Institutional email address until the verification lapses, then 30 days
Profile until you delete it
A minor's photo after the parent's permission ends hidden at once, deleted 30 days later
Drafts never submitted 12 months of inactivity (reminder at 11 months)
Rejected or withdrawn submissions 2 years after the decision; reviewers' identities anonymised
Published papers as part of the scholarly record, unless a name or an affiliation is deleted, or the paper hidden, on request (Section 8); a departing author's profile link is removed, the consented byline stays
Comments until you delete them or moderation removes them; replaced by "[deleted]" when the account is deleted
Reports and moderation records 2 years
Mentor applications a rejected application: 6 months after the decision; an approved one: while you mentor, cleared when the account is deleted; an application nobody changes for 90 days counts as withdrawn
Mentor application documents student ID photo: 30 days after the decision (approval, rejection or withdrawal); CV and degree certificate: 30 days after a rejection or withdrawal, and for an approved mentor while they mentor, deleted with the account
Police-clearance documents at most 30 days; only the date, country and outcome are kept
Mentor tax status (ИИН, declarations, residency certificate) while the person mentors, deleted with the account; the payouts themselves stay with the payment records
Session recordings kept by us in Kazakhstan for 90 days after the session, then erased from storage; longer only while a complaint or a safeguarding case about the session is open. If the parent withdraws the recording consent: erased within 10 working days, or, while a complaint or a safeguarding case about that session is open, within 10 working days after it closes. The mentor deletes every other copy after the upload
A mentor's explanation of a missing recording the text and the evidence file: 3 years after the staff decision, or earlier if the mentor's account is deleted; the cause, the dates and the decision stay, to count the mentor's earlier excused failures
Mentor payout details, including a PayPal email address while the person mentors, then deleted with the account; a PayPal address is erased at once when the mentor stops PayPal payouts
Fee waiver applications a draft nobody changes for 90 days is deleted; the written answers are erased 1 year after the decision or withdrawal (the decision itself stays with the fee record)
Messages with mentors 2 years after the last message in the conversation
Bookings with the account; a paid booking is also part of the payment records
Payment records as tax and accounting law requires (currently 5 years in Kazakhstan)
Contact-form messages not stored on the Platform, except a complaint sent with the topic "A complaint", which goes into the complaints register (next row); kept in our mailbox only as long as needed to answer you and deal with any follow-up, and at most 12 months
Complaints register: your details, the complaint and our reply 3 years after our reply, or 3 years after the complaint was received if no reply was recorded: the general limitation period (Article 178 of the Civil Code), during which either side may need to show what was asked and answered. Then your name, contact details and account link, the complaint and our reply are erased; only the dates, the subject and whether we replied stay. If you delete your account earlier, they are erased with it
Cover images like the paper they belong to: published with it, or deleted with an unpublished submission
Audit log 3 years
An intern's signed confidentiality agreement while the person is an intern and 3 years after, then deleted (the general limitation period, Article 178 of the Civil Code)
Server logs with IP address full address 30 days; deleted at 90 days
Data exports you request 7 days
Newsletter subscription until you unsubscribe; 30 days later the address is replaced by a keyed hash, kept only so you are not emailed again; a sign-up never confirmed is deleted after 30 days

Backups. Backups are copies for disaster recovery only: nobody uses them for anything else, and they are never searched or restored to look at a person's data. They are kept in Kazakhstan: the hourly copies of the database on our server for 48 hours; the copies of the whole server that our hosting provider PS.kz makes and keeps with its own backup service, for up to 30 days; the off-site copies, once switched on, at most 12 months. Data deleted on the Platform (a session recording included) stays in a backup only until that backup expires. Every deletion is also written to a record of deletions on our server: deleted accounts, comments, photos and other files, papers and manuscripts, session recordings, withdrawn consents, changes to profile visibility, blocks between members, withheld or deleted names and hidden papers. If a backup is ever restored, the site stays closed until every deletion in that record made since the backup was taken has been applied again; the nightly retention job then deletes again everything whose period has ended. One limit: if the whole server has to be restored from the hosting provider's copy, the record of deletions goes back to the time of that copy too, so the deletions made after it can be applied again only from a newer off-site copy of the record, when there is one. Whenever a restore loses changes made after the backup (a deletion, a new paper or a corrected profile), we email our users so that they can make them again.

8. Your rights, how to use them and how fast we answer

Under Settings → Privacy you can, without asking anyone:

  • Download everything we hold about you (JSON plus your files), normally ready within minutes and at the latest within 72 hours, available for 7 days.
  • Correct your profile and account details. Fields we have verified (such as your date of birth) are corrected on request to [email protected].
  • Switch off an optional consent (the newsletter, a public profile), with effect at once.
  • Delete your account, with a 30-day grace period during which you can cancel; the account is blocked during it.

A parent does the same for a child under 18 from the parent dashboard, where every consent given for the child can be withdrawn.

If you ask us by email, by letter or in person to delete your account, our staff delete it for you once they have checked that the request comes from you (or, for a child, from the parent). It is the same deletion as in Settings, with the same 30-day grace period during which you can cancel it by signing in, and the same records kept as Section 7 says.

By email to [email protected] (or by letter to the operator's address) you can use every right the Law gives you. We record each request with its deadline and answer within these periods:

Request Our deadline
Information about your data: whether we hold it, the purposes, sources and ways we collect and process it, the list of data, how long we keep it and which third parties received it (Article 24(1)(1) of the Law) within 3 working days of receiving the request, or a reasoned refusal within the same 3 working days (item 16 of the Rules); seeing your own data is free (Article 25(2)(9) of the Law)
Correcting or completing data, with a document that confirms the change within 1 working day of receiving the document; data that cannot be corrected is deleted (Article 25(2)(8) of the Law)
Blocking your data because the conditions of processing were broken; deleting data processed unlawfully blocked within 1 working day; deleted within 1 working day once the breach is confirmed, unblocked if it is not (Article 25(2)(8) of the Law); data published unlawfully is removed from the site within 1 working day (Article 6 of the Law)
Withdrawing a consent processing based on it stops within 15 working days, unless the law requires us to keep the data; otherwise a reasoned answer within the same 15 working days (Article 8(7) of the Law). A consent cannot be withdrawn where this contradicts a law or while an obligation is unfulfilled (Article 8(2) of the Law), for example a payment already made
Deletion, anonymisation or restriction of processing (Article 41 of the Digital Code) carried out in the periods above; where a law requires us to keep the data (for example payment records), we restrict access to it and stop using it instead (Article 41(3) of the Digital Code)
An objection to automated processing reviewed within 3 working days, with the result sent to you (Article 19-1 of the Law); we make no decision by automated means alone (Section 10)
A complaint about how we handled your data within 15 working days

What a withdrawal does.

Consent withdrawn What happens
Newsletter no more newsletters at once; 30 days later the address is replaced by a keyed hash
Public profile (adult) the profile is shown to signed-in members only, at once; you can also make it private
A child's "Profile" permission (parent) the child's profile is private and the photo hidden at once; the photo is deleted 30 days later
PayPal payouts (mentor) PayPal is switched off and the stored PayPal address erased at once; later payouts go by bank transfer
The Personal Data Consent given for a child (parent), or the end of the last parent's link to the child at once: the child's account becomes read-only "awaiting parent", the profile private, and the child can no longer submit, upload, message or book; nothing new is collected, and the stored data is blocked. The account is deleted on the 10th working day after the withdrawal, unless a parent gives the consent again before then (see below)
The Personal Data Consent (adult) an account cannot work without it, so you withdraw it by deleting the account (Settings → Privacy), or by writing to [email protected]: once we have checked that the request comes from you, our staff start the deletion for you, as described above, and answer within 15 working days; the records the law requires are kept for their periods
Session participation or recording (parent) no new session can be booked or held for the child. Once the recording consent is withdrawn, the recordings of the child's sessions are erased within 10 working days. A recording of a session about which a complaint or a safeguarding case is open is kept as evidence until the case closes and erased within 10 working days after that (Article 41(4)(1) of the Digital Code); we explain this in our answer

When a parent withdraws the consent given for a child. The same applies when the last parent linked to the child ends the link. The child's data is blocked at once: it is used for nothing except the steps below. At once, and again 3 working days before the deletion, we email the parent and the child the date on which the account will be deleted, with a link for a parent to give the consent again. On the 10th working day after the withdrawal (counting Monday to Friday), the account is deleted, unless a parent has given the consent again by then. Nobody needs to ask a second time, and the request is recorded with its deadline. The deletion is the same as any account deletion (Section 7). Only these records stay, each for its own reason and period:

  • payment records, for example for a session the parent paid for: tax and accounting law requires them (Article 9(10) of the Law), currently for 5 years;
  • the consent records and the parent link, reduced to identifiers, document versions and timestamps: proof of consent (Article 25(2)(5) of the Law), for 3 years;
  • the audit log: the record of actions with personal data (Article 22 of the Law), for 3 years;
  • reports and moderation records about the safety of other users, for their 2 years, and the dates, category and outcome of a complaint about a session, without its text: protecting the rights and safety of others (Article 41(4)(1) of the Digital Code);
  • a paper already published with the child's name, under the parent's consent to publish it and the licence; the parent can ask us to delete the name (below).

Files are made unavailable at the deletion and erased from storage 30 days later. The deletion also ends the recording consent, so the recordings of the child's sessions are erased as the last row of the table says.

Published papers. A published paper is part of the scholarly record, and readers rely on it staying the same. That is not an absolute rule. You, a co-author, or anyone named or identifiable in a paper can ask us to correct or delete a name or an affiliation, or to take the whole paper off the website. Staff assess each request and answer within 15 working days, weighing the person's safety (for example a minor, or a risk of harm), whether the data was disclosed unlawfully or without consent, the person's age at publication, and the readers' interest in an unchanged record. Data published unlawfully is removed from the website within 1 working day (Article 6 of the Law). Depending on the request, staff:

  • hide the paper, so that it is shown to nobody; this can be undone;
  • withhold a name or an affiliation while a request is assessed: the name shows as "Name withheld", the affiliation is left out, and the PDF is not offered meanwhile; this can be undone;
  • correct a misspelt name, a wrong affiliation or ORCID identifier, or a typo in the title: the page, the citation and the metadata show the corrected detail with "Corrected on" and the date, the original stays in our record of the paper as published, and the published PDF is not changed; a correction can be undone;
  • delete a name or an affiliation because the law requires it: it is erased from our stored record of the paper (where the name becomes "Name withheld"), the submission record, the page, the citation, the metadata, profiles and lists. The old PDF is deleted at once: a paper written in our editor gets a new PDF with "Name withheld" within minutes; a paper published as an uploaded PDF has no PDF until staff upload a corrected one. This deletion is final: it is never undone, and it is applied again after any restore from a backup. One exception: the private editorial files of the paper (the authors' manuscript, its earlier versions and the PDFs of the review rounds, which only the authors and the editors can see) still contain the name, because they are kept as the journal's editorial record.

Copies that others have already downloaded or archived are outside our control.

Without an account (if you only subscribed to the newsletter or wrote through the contact form), use the unsubscribe link in any newsletter, or write to [email protected] to see, correct or delete what we hold about you. You can also complain to the authorised body or a court. For users in the European Economic Area or the United Kingdom, the rights in the GDPR apply in addition.

9. Security

The Platform is designed around the assumption that unpublished manuscripts, minors' data and staff access are the things most worth protecting. In summary: all traffic is encrypted; the server opens no public ports and is reached only through an outbound tunnel; passwords are hashed and checked against known breaches (Section 6); staff must use a second factor and pass an additional login in front of the staff area; sensitive fields are encrypted in the database; every upload is virus-scanned and re-encoded before anyone can open it, and files are served from a separate domain by short-lived signed links; the database is copied every hour and the hosting provider keeps backups, all in Kazakhstan (Section 6); and every security-relevant action is written to an append-only audit log. Security researchers can report problems under our Security Policy.

10. Automated decisions and artificial intelligence

We make no decision with legal or similarly significant effect about you by automated means alone (Article 19-1 of the Law). Editorial decisions are always made by a person. If we introduce AI-assisted screening of manuscripts, the AI will only advise an editor, the decision letter will say that AI-assisted screening was used, and no manuscript will be sent to an AI provider abroad without your consent. You can object to any automated processing; we review the objection within 3 working days.

11. Data breaches

If a breach affects personal data, we notify the authorised body of the Republic of Kazakhstan within one working day of discovering it, with the contact details of the person responsible for organising processing (Article 25(2)(8) of the Law), tell affected users without undue delay, and keep a record of the incident. Users in other countries are notified as their law requires.

12. Cookies

We use only the cookies the Platform needs to work. Each is listed in the Cookie Notice. There are no advertising or analytics cookies, so no cookie banner is shown.

13. Changes to this Policy

Each version carries a number and an effective date and stays available on the policies page. When a change matters to you, you will be asked to read and accept the new version before continuing; parents of minors are emailed as well. A new purpose, a new kind of data or a new recipient abroad is added here first, and a new consent is asked for where the law requires one.

14. Language

This document is published in Kazakh, Russian and English. The Kazakh and Russian texts have equal force. The English text is a translation for convenience; where it differs, the Kazakh and Russian texts apply.