Straight answers, including the ones that are "no"

GymOS records and reconciles every payment mode your members actually use — cash, UPI, card and bank transfer — in one place, so your books are always complete. We do not process payments through a payment gateway, which also means no per-transaction commission is skimmed from your revenue.

You take payment the way you already do; we make sure it's recorded, reconciled and tied to a gap-free invoice.

Because it changes what we are. A gateway means holding a slice of your collections, chargeback handling, card-data scope, and a dependency on someone else's uptime for your revenue. Indian gyms overwhelmingly collect in cash and UPI at the desk already. We'd rather make recording and reconciling that flawless than insert ourselves into it.

Sequential and gap-free per gym, in the form INV-{year}-{sequence}, generated under database row-locking. Even if your front desk and your manager record a payment at the same instant, you cannot get a duplicate or a skipped number.

No. Recorded payments are immutable. A correction is raised as an edit request and needs manager approval, and both the request and the approval are logged. That's the whole point — a payment that can be quietly edited isn't a record, it's a note.

Partly, and we'll be precise about it. Invoice numbering already meets the sequential and gap-free requirement, and amounts are stored to two decimals. Full statutory tax-invoice formatting — CGST/SGST breakdown and SAC code on the printed invoice — is in progress and not shipped yet.

Yes — a mobile-friendly member app that opens in any browser, with no app-store install needed. It's a rebrandable web app, so it carries your gym's branding.

It is not a native app downloaded from the Play Store or App Store. That also means members get updates instantly, with nothing to install and no store review delays.

Phone number plus their member code — no password to forget, and nothing for your front desk to reset. Each gym has its own member login address.

See their plan and dues, book and view classes, follow their assigned workout and diet plan, track progress and measurements, log water, view streaks and badges, refer friends, read gym announcements, and manage their own consent and privacy settings.

Yes, through one-tap WhatsApp reminders. Staff can send renewal, dues and class reminders to members in a tap using ready-made message templates.

To set expectations honestly: this is click-to-send messaging, not automated WhatsApp Business API campaigns. There is no hands-off automation today.

No. Check-in is by QR code scanned with the browser camera, so there's no extra hardware to install, support or troubleshoot on-site. This is a deliberate design choice: fewer moving parts, nothing to break at the front desk, and no device vendor to chase when it does.

Three things. The scan screen flashes the member's photo so your desk sees who should be standing there; duplicate scans in a short window are refused; and every scan is rate-limited and written to the audit log, so patterns show up.

The rule engine blocks the check-in and the screen goes red, with the reason. Overdue fees flag the same way, and members close to expiry show an amber warning so your desk can have the renewal conversation while they're standing there.

GymOS is built around the principles of India's DPDP Act — bilingual consent capture, an append-only consent and audit ledger, a real data-erasure routine, encrypted medical notes, purpose-mapped data, and a deliberate choice not to collect Aadhaar numbers.

We're careful not to claim "fully compliant", because compliance is a shared responsibility between the software and the gym, and we have two known gaps we're transparent about: there is no automated breach-notification workflow yet, and no per-gym data-retention configuration yet. Both are on the roadmap and both are listed on our Trust page.

No, and there is no field for one anywhere in the system. If your gym needs ID on file, you upload a masked government-ID document instead. The less sensitive data you collect, the less risk you carry.

No. Trainer access is scoped at the policy layer and covered by tests — a trainer cannot reach another trainer's assigned members, even by editing a URL.

No. Every tenant-owned model is forced through an audited isolation layer, and that rule is enforced automatically in our build pipeline rather than left to a developer to remember. Cross-gym isolation is tested per resource.

There's a real erasure routine. It removes their personal data and retains only what tax and financial law require you to keep — which is why "delete everything" isn't quite the right ask for a paying customer's records. You can also export a member's data for them.