Legal

Security and Responsible Disclosure

Effective 23 October 2026 Version 2.1

Learners trust VAKOTIX with their work, their names and sometimes their payments. This page describes how we protect them, what we do if something goes wrong, and how security researchers can report a weakness safely.

In short

  • Passwords, sessions and codes are stored only as hashes. Administrators confirm every sign-in with an emailed code.
  • Every request is checked against who may see the data. Sign-in attempts and requests are rate-limited.
  • If a breach puts your data at risk, we tell you and the authorities as the law requires.
  • Found a vulnerability? Email vakotix@gmail.com — we will not take legal action against good-faith research.

The summary helps you read; the full text below is what applies.

1.Protecting your account

  • Passwords are hashed with scrypt and a unique salt; we cannot see them. New passwords must meet length and strength rules.
  • New accounts verify their email with a 6-digit code. Administrators and educators confirm every sign-in with an emailed code. Codes are stored as hashes and expire in 10–15 minutes.
  • You can sign in with Google, using OpenID Connect with PKCE; we never see your Google password.
  • Repeated failed sign-ins are slowed down and then blocked for a while. Password resets use an emailed code.
  • Sessions last 30 days and end when you sign out; the cookie is HttpOnly and only a hash of it is stored.

2.Protecting the platforms

  • Access to every journey, file and record is checked on the server for every request: only the team, educators, the learner's organisation staff and VAKOTIX can read a journey, and only its own learner can write a record.
  • Requests are rate-limited; registration has a bot trap; browsers receive strict security headers (content security policy, frame protection, HTTPS enforcement).
  • Uploaded files are checked before they are accepted, and stored outside the public website.
  • Server-to-server connections between the VAKOTIX platforms use a secret key and are never exposed to browsers.
  • A security log records sign-ins, failures and other security events, and a monitor watches the platforms around the clock and alerts VAKOTIX to threats.
  • The database is backed up every night. Only VAKOTIX management, signed in within the last 24 hours with a verified address, can reach management systems.

3.What you can do

  • Use a password you use nowhere else, and never share it or your sign-in codes. VAKOTIX will never ask for them.
  • Sign out on shared computers.
  • Check that emails really come from VAKOTIX, and pay only to the UPI details on the VAKOTIX checkout page.

4.If something goes wrong

If a personal data breach happens, we contain it, investigate, and inform the people affected and the Data Protection Board of India (and, where they apply, POTRAZ in Zimbabwe and the European authorities) as the law requires, describing what happened, what data was involved, what we are doing and what you can do. In India, CERT-In is informed of reportable cyber incidents within 6 hours.

5.Reporting a vulnerability

Email vakotix@gmail.com with the subject "Security report", what you found, where, and the steps to reproduce it. We acknowledge it within 24 hours, keep you informed, and credit you if you wish once it is fixed.

Please

  • test only with your own accounts and data;
  • do not read, change or delete other people's data, and stop as soon as you reach any;
  • do not disrupt the platforms (no denial-of-service, spam or automated scanning at volume) and do not use social engineering;
  • give us reasonable time to fix the problem before telling anyone else.

If you follow these rules in good faith, we will not take legal action against you or ask others to. VAKOTIX does not yet offer paid rewards. Other problems are reported through Grievance Redressal.

Questions or complaints

Simbarashe Vakisai, Founder, Grievance Officer and Data Protection Officer: vakotix@gmail.com. We acknowledge every message within 24 hours and resolve it within 15 days. See Grievance Redressal.

Operated by
Simbarashe Vakisai, trading as VAKOTIX, India
Postal address
Sent on request by email while VAKOTIX's registered office is being set up.
Email
vakotix@gmail.com
Version history
  • Version 2.1, 23 October 2026: Grievance times of the IT Rules 2021 (24 hours, 15 days), content removal and the Grievance Appellate Committee, copyright takedown, sensitive personal data, log retention, restriction of processing, automated decisions, languages, consent managers and general terms.
  • Version 2.0, 23 October 2026: Complete policies for the commercial pilot: twelve policies and the legal hub.
  • Version 1.0, 18 October 2026: First pilot versions of the Terms, Privacy and Cookie policies.

Earlier versions are available from the Grievance Officer on request.