Legal

Accounts & Sign-in

There are two kinds of account here, they are authenticated differently, and one cannot become the other. This explains which you have and what it reaches.

Last updated 9 September 2026 · Alfa HazardX, Indore, Madhya Pradesh, India

In short

A buyer account is created by verifying your email with a six-digit code. No password. It shows you your own orders and nothing else.

A dashboard account reads live plant data and is invite-only. Buying hardware does not create one, and it cannot be escalated into one.

01Buyer accounts

Created when you verify your email address in the buy flow. We send a six-digit code, valid for 15 minutes, with five attempts before it is burned. There is no password to choose, forget, or have stolen.

A buyer account holds your factory profile, your saved configuration and your orders. It can see those and nothing else. It is not a login to the operator dashboard, it grants no access to any plant’s sensor data, and no sequence of actions in the shop turns it into one.

The session lasts 30 days and lives in a cookie holding a random token. Only that token’s SHA-256 is stored on our side, so a leaked copy of our database cannot be used to sign in as you. Sign out at any time from your orders page.

02Dashboard accounts

The operator dashboard shows live readings, incidents and emergency controls for real plants. Access is invite-only and granted per person, per plant, by an administrator.

An address with no grant is refused before a sign-in code is ever sent — it does not receive a code, and no account is created for it. That is deliberate: on a system where a session can read a factory’s live hazard data, self-service signup would be the whole security model undone in one form field.

Roles are: administrator (all plants, and may grant access), editor on a named plant, and viewer on a named plant. What each may read and change is enforced in the database by row-level security, not only in the interface — so a missing check in a screen cannot expose another plant’s rows.

03Why the two are kept apart

A shop must let anybody in; a hazard dashboard must not. Merging them would mean either refusing customers or admitting strangers to plant data, so they are separate systems with separate credentials and separate cookies. Your dashboard workspace is opened after your unit is commissioned, with access granted to the people you name.

04Keeping your account secure

  • A code is for you alone. We will never ask you to read one out or forward it, and anybody who does is not us.
  • We will never ask for your password, card number, UPI PIN or bank details by email, phone or message.
  • Tell us at once if you think someone else has your access, and we will revoke the sessions.
  • Tell an administrator when someone leaves, so their grant can be removed. Access is per person for exactly this reason.

05Suspension and closure

We may suspend an account that is being used to attack the service, to reach data it was not granted, or in breach of the terms of use. Where we can, we will tell you why.

To close a buyer account, email agresh@agreshagrawal.com. We delete the profile and any saved configuration; orders and payment records are kept for as long as tax law requires, as set out in the privacy policy.

Questions about this document, or a request under it, go to agresh@agreshagrawal.com. It reaches Agresh Agrawal directly.