Skip to content

How MSRX Planner works

Early Access. Last updated 14 October 2026. For anyone who wants to know what is under the hood, and why it matters for your data. For a hands-on walkthrough see the User Guide.

The idea: your device first

Most apps keep your data on a server and show you a copy. MSRX Planner does the reverse. The working copy lives in your browser, so the app opens instantly, works offline, and does not need an account. The cloud is a second copy that keeps your devices in step.

The pieces

  • Website and app: a Next.js and React web app, installable to your home screen. Hosted on Vercel.
  • On-device store: your workspace is held in browser storage and updated instantly as you type. A queue records changes that still need to reach the cloud.
  • Cloud database: PostgreSQL on Supabase, with sign-in and private file storage.
  • Bot check: Cloudflare Turnstile on sign-in screens.
  • Email: sign-in and password messages are sent from the msrx.co.in domain.
  • AI: a server route that forwards a small summary and your question to a hosted language model (Groq).

What happens when you sign in and sync

  1. You sign in with Google or email and password.
  2. Your device sends the changes in its queue to the database and receives anything changed elsewhere.
  3. If two devices edited the same thing, the later change wins for that item. Keep one device as your main one while editing a long note.
  4. If you are offline, nothing breaks. Changes wait and send when you reconnect.

Who can read your data

  • You. Only you, once signed in, can read and change your rows. This is enforced inside the database by Row-Level Security, not only in the app, so a bug in the app cannot hand your rows to someone else.
  • People you share with. Only the specific notes, decks or plans you add to a study group, and only to its members.
  • Your files. Uploads go to private storage under a folder named for your account. Others are served through short-lived signed links after a permission check.
  • The operator. The person running the service can technically reach the database in order to run it, fix faults and keep backups, and uses that access only for those purposes.
  • Service providers. Listed in the Privacy Policy.

Your notes are not end-to-end encrypted. They are encrypted in transit and at rest by our providers, which protects against outsiders but not against the services that run the system.

What the AI is, and is not

  • Most intelligence here is not AI. Your readiness, study load, ranking of tasks and revision schedule are ordinary, deterministic calculations that run on your device from your own activity. The same inputs always give the same output.
  • The coach chat and PDF tools are AI. A language model writes text. It can be wrong, can invent detail and can sound certain while doing it.
  • It is told to stay in its lane. PDF answers are pinned to the text you provide; coach answers are given a compact summary of your workspace.
  • It cannot change your data. It returns text and you decide what to do.
  • You can ignore it. Nothing else needs it.

Safeguards

  • HTTPS everywhere; secure, httpOnly session cookies.
  • Deny-by-default database access with per-account policies.
  • The AI route requires sign-in and caps request size.
  • Secret keys exist only on the server, never in your browser.
  • Sign-in is protected by a bot check and the provider’s rate limits.
  • Anonymous, cookie-free visit counts that cannot be tied to a person.

Honest limits

  • This is Early Access software run by one person. It can have bugs and downtime.
  • There is no end-to-end encryption and no guarantee against loss. Export a backup regularly.
  • We depend on third-party providers whose terms and uptime we do not control.
  • The app is a study aid. It does not predict or guarantee any exam result.

Open questions or concerns

Write to mrinalsinghraja@gmail.com. A security issue? Say so in the subject and do not post details publicly first.