Terms & Conditions
Last updated: 13 October 2026 · Applies to meteops.in, demo.meteops.in and the Meteops application
These terms govern access to Meteops, a weather-operations platform run by MozWork Solutions ("Meteops", "we", "us"). If you create or use an account on behalf of an organisation — for example a tower company, contractor or field-operations team — you confirm you are authorised to bind that organisation, and "Customer" or "you" means that organisation. If you are an individual user invited by an organisation, these terms apply to your use too.
Decision support only — not a safety clearance.
Meteops provides weather information, forecast-change alerts and operational advisories to inform — never to replace — your organisation's own safety procedures, statutory obligations and on-ground judgement. A "Go" or "Caution" status is a decision-support signal, not an instruction that work is safe, and a "No-go" status is advice to pause and review, not a legal order. Final decisions about field safety remain with the Customer and its qualified personnel.
1. The Service
Meteops provides, per your organisation's configuration: site-level weather outlooks and statuses; deviation detection between forecast runs; official warning overlays (including NDMA SACHET alerts); observation feeds (airport METAR and, where enabled, satellite rainfall estimates); field-report intake; advisories, acknowledgements and morning briefs; forecast-accuracy reporting; and an offline-capable installable web application.
Features shown but marked not connected — for example SMS/WhatsApp delivery, or a satellite feed without credentials — are not part of the Service until they are actually enabled for your organisation. The interface shows connection status honestly rather than implying feeds that are not active.
2. Accounts and access
- Sign-in is by email one-time passcode. Keep your mailbox secured; anyone who can read your email can sign in as you.
- Your organisation's administrators control membership, roles and site scope. Only they can invite or suspend users.
- One email address belongs to one organisation at a time.
- You must not share sessions, attempt to access another organisation's data, probe security controls, or misrepresent field reports. We may suspend access for abuse or security risk.
- Platform staff (Meteops) can see organisation metadata and counts to operate the service — not your operational content — and their actions are audit-logged.
3. Customer data
- You retain ownership of data your organisation supplies: site inventory, user list, field reports, acknowledgements and configured thresholds.
- You grant us the rights needed to host, process and display that data to provide the Service — nothing more.
- You are responsible for the accuracy of the inventory you upload (site coordinates, districts, circles) and for having the right to share any personal data contained in it (e.g. assigned-user names).
- Imported records are never silently overwritten: re-imports match on site ID and skip or flag conflicts, and every import is audit-logged.
- On termination you may request an export of your organisation's data; see Termination.
4. Data sources, provenance and honest limits
- Forecasts come from third-party model outputs (currently Open-Meteo serving ECMWF IFS and other models). They are estimates, shown with source and issue time.
- Official alerts come from government feeds such as NDMA SACHET; airport observations from METAR via NOAA AWC; satellite rain from JAXA GSMaP — each labelled on screen with its source. Each source's own terms and attribution apply.
- Field reports are qualitative, unverified inputs from your own users — labelled as such, never blended silently into measurements.
- We show freshness and staleness explicitly. When data is missing or stale, the Service says so rather than implying safety — but absence of a warning is not evidence that conditions are safe.
- Default severity bands (what counts as go/caution/no-go) are illustrative starting points intended to become your organisation's configured policy. They are not statutory limits and may not suit your SOPs until configured.
5. What we do not promise
- We do not warrant forecast accuracy. Weather models disagree and change; deviation alerts exist precisely because forecasts move.
- We do not guarantee uninterrupted service. Maintenance windows, provider outages and network conditions — especially on field connections — can interrupt the app. The offline mode shows your last saved snapshot marked with its age.
- Meteops is not a substitute for mandatory regulatory notifications, site-specific safety assessments, or any obligation the Customer owes to its workers or third parties.
6. Pilot and subscription terms
Where you use Meteops under a pilot, proof-of-concept or evaluation agreement, the commercial terms in that agreement (scope, duration, fees, limits on sites and users) apply in addition to these terms and prevail if they conflict. Absent a signed agreement, use of the hosted service is at our discretion and may be limited or withdrawn with notice.
Organisation-level limits (active sites, users, custom roles) shown in the product are enforced server-side; requests to raise them are handled through the limit-request flow or your account contact.
7. Acceptable use
- No unlawful use, and no use that endangers people — including knowingly sending crews out against a No-go advisory without documented review.
- No scraping, bulk extraction, or attempting to bypass scope, rate or permission controls.
- No uploading data you lack rights to, or deliberately false field reports.
- No interference with the Service or other tenants, including attempting cross-organisation access.
8. Intellectual property
The platform, design, code and documentation are ours or our licensors'. Your data is yours. Weather-model and map content remains under its providers' licences (e.g. Open-Meteo CC BY 4.0, ECMWF IFS CC BY 4.0, OpenFreeMap/CARTO, JAXA GSMaP). Feedback you give us may be used to improve the Service without obligation.
9. Confidentiality
Each party will protect the other's non-public information with reasonable care and use it only for the purpose of the Service. Our handling of personal data is described in the Privacy Policy, which forms part of these terms.
10. Liability
To the maximum extent permitted by law: the Service is provided "as is" without warranties of any kind; we are not liable for indirect, incidental or consequential losses, lost profit, or decisions taken in reliance on forecast outputs; and our aggregate liability arising from the Service is capped at the fees you paid us in the three months before the claim (or, during an unpaid pilot, a nominal amount agreed in the pilot letter — typically the fees that would have applied). Nothing in these terms excludes liability that cannot be excluded by law, including for death or personal injury caused by negligence.
11. Termination
- You may stop using the Service at any time; your organisation's administrator controls member access.
- We may suspend an organisation for breach, security risk or non-payment under a commercial agreement, with notice where practicable.
- On termination, your access ends; we retain data as described in the Privacy Policy and will provide a reasonable export window where the commercial agreement provides for it.
12. Changes
We may update these terms as the Service evolves. Material changes will be flagged on this page with a new "last updated" date and, for signed-up organisations, notified to administrators. Continuing to use the Service after the effective date means acceptance.
13. Governing law
These terms are governed by the laws of India. Disputes go to the competent courts of India, and where a commercial agreement names a seat or venue, that clause prevails.
14. Contact
MozWork Solutions — Meteops
Legal & commercial: legal@meteops.in
Privacy: privacy@meteops.in