SightOps Usage Policy

Last updated: 30 August 2026 · Operated from Kenya · Read with the Terms of Service and Pricing Policy.

1. Who this applies to

This policy applies to anyone who creates a workspace, signs in, or is invited as a user. The organisation (company account) is responsible for the people it authorises.

2. What you may use SightOps for

You may use SightOps to run legitimate healthcare and related retail operations that match your paid plan (or the free demo, within its caps), including:

You must hold any licences, permits, and tax registrations your business needs (for example pharmacy, clinical, or KRA obligations). SightOps does not grant those licences and is not a substitute for professional or legal advice.

3. Free demo versus paid plans

The free demo is the only zero-cost start. It is a playground: it does not expire on a calendar date, but activity and catalogue size are capped so it cannot be used as a live shop.

Unless we publish different caps on your account, the demo typically allows:

Paid plans start after payment. Clicking a paid package on the pricing page does not open that plan for free. Pay from Account (or as we agree in writing). After payment, SightOps platform admin unlocks the paid plan. We do not convert a paid organisation to the free demo because a billing period ended; unpaid access is locked on the same plan until you pay.

4. Accounts, owner, and staff

5. Your data

Each organisation is scoped so one client cannot open another client’s records. You own the business data you enter. We host it to provide the service. We do not build SightOps to inspect client business data for personal use.

You are responsible for the accuracy of stock, prices, patients, invoices, and fiscal documents you generate. Backup and export options depend on your plan. If you leave, ask support in writing about export within a reasonable period while the account still exists.

6. Integrations (eTIMS, M-Pesa, and others)

Where your plan includes fiscal or payment workflows, SightOps can connect to third parties (for example KRA eTIMS or M-Pesa). Those parties have their own terms. You remain responsible for device serials, OSCU/VSCU setup, PINs, and payment references. An integration is not tax advice, not a KRA filing service, and not a standalone M-Pesa POS product.

7. Fair use of cloud resources

Plans include application bandwidth for ordinary till and office use. Indicative included amounts for owner reporting are about 1 GB (demo), 3 GB (Retail Solo), 5 GB (Pharmacy Lite), 15 GB (Retail Pro / Clinic Lite), and 40 GB (Growth / Health Network). Enterprise may have no published cap. These are not a guarantee of a third-party host’s bill.

Automated scraping, stress testing against production, mining, or using the service as a general file host is not fair use. We may throttle, suspend, or require an upgrade if usage harms other customers or the platform.

8. Prohibited use

You must not:

9. Suspension

We may suspend or limit access for non-payment, breach of this policy or the Terms, abuse of the demo, or risk to the platform, with notice where practicable. Paid-plan lock for overdue maintenance is described in the Pricing Policy.

10. Changes

We may update this policy. Material changes will be posted on this page with a new “Last updated” date. Continued use after that date is acceptance, unless a separate written contract says otherwise.

11. Contact

Usage and account questions: support@pharmasight.co.ke

Terms of Service · Pricing Policy · Pricing