Privacy Policy
Last updated: 19 October 2026 · Applies to meteops.in, demo.meteops.in and the Meteops application
Meteops is operated by MozWork Solutions ("Meteops", "we", "us"). Meteops is a weather-operations platform for organisations that manage field infrastructure — initially telecom tower operations — helping teams decide whether work can proceed at a site given current and forecast weather. This policy explains what personal data we collect, why, how long we keep it, who it is shared with, and the rights you have under applicable law including India's Digital Personal Data Protection Act, 2023 (DPDP Act).
1. Scope and roles
This policy covers the public website (meteops.in), the demo/preview deployment (demo.meteops.in), and the Meteops web application (the "Service").
Two different relationships matter here:
- You use Meteops through your organisation (for example, a tower company or contractor that has subscribed to Meteops). Your organisation decides who gets an account, which sites you can see, and what field data you are asked to submit. For that data, your organisation is the data fiduciary (it determines purpose and means) and we act on its instructions as a data processor. Privacy questions about your work account should go to your organisation's administrator first — but you may always contact us too.
- You interact with us directly — visiting the website, requesting access, or contacting us. For that data, we are the data fiduciary.
2. Information we collect
2.1 Account and identity data
- Work email address — used for sign-in via one-time passcode (OTP) and for service emails. We do not use passwords.
- Name and role — supplied by your organisation's administrator when they invite you (e.g. operations supervisor, research analyst, field engineer).
- Phone number — optional; only if your organisation adds it for alert delivery.
- Scope assignments — the operating areas (circles/districts) or sites your administrator assigns to you.
2.2 Organisation and site data (uploaded by customers)
- Site inventory: site identifiers, names, coordinates, state/district, operating circle, criticality and team labels — imported by your organisation.
- Organisation details: name, member list, roles, and usage limits configured by platform staff or your administrators.
Site inventory is business data about infrastructure, not personal data — except where a site record names an individual (e.g. an assigned field user). We treat any embedded personal data with the same safeguards as the rest of the Service.
2.3 Field reports and operational activity
- Field condition reports you submit: category (e.g. lightning, flooding), optional note, observed and received timestamps, and the site they relate to.
- Acknowledgements and verifications: which advisories you viewed, acknowledged, or gave a field verdict on.
- Audit log: sign-ins, permission changes, imports, publishes and other administrative actions, recorded with actor and timestamp for accountability.
- In-app navigation: which sections of the app you open (for example Map, Sites or Reports) and when. Your organisation's administrators can see this per person; Meteops staff see only organisation-level totals, such as how many people were active and which sections are used most.
We do not continuously track your device's location. Field reports attach the site's coordinates from the inventory — not your live GPS position — unless a future feature explicitly asks for it and you consent.
2.4 Technical data
- Standard request metadata processed by our hosting and edge providers (IP address, user agent, timestamps) for security, rate limiting and reliability.
- A session cookie (strictly necessary) that keeps you signed in.
- Offline data on your device: our installable app caches the application shell and — for signed-in users — a scoped offline snapshot of the sites you are permitted to see, so field views work on weak connections. This snapshot is purged on sign-out and is never replayed under a different signed-in user.
3. How weather and hazard data is fetched
Meteops retrieves forecast and observation data on the server side, and the queries we send to weather providers do not contain your personal data or your organisation's identity:
- Forecasts are requested per district reference point (a fixed anchor per Indian district), not per individual user or — in the default configuration — per individual site. The weather provider sees geographic coordinates and requested variables only.
- Official warnings come from the NDMA SACHET public Common Alerting Protocol feed; airport observations come from the public METAR feed (NOAA Aviation Weather Center); satellite rainfall estimates, where enabled, come from JAXA GSMaP. These are public datasets fetched by the server.
- Basemap tiles in the app are loaded from public tile services (OpenFreeMap/CARTO); your browser's standard request headers go to those tile hosts. No account data is sent to them.
4. How we use information
- To authenticate you (email OTP) and keep your session.
- To show you the sites, forecasts, advisories and reports your organisation has scoped to your account.
- To send service communications your role has opted into — no-go notices, morning briefs, security and account notices — via the channels your organisation configures (in-app today; email delivery where enabled).
- To maintain the audit trail regulators and your organisation's governance require (who changed what, when).
- To show your organisation's administrators how the Service is used, and to improve the Service using organisation-level usage totals.
- To operate, secure and improve the Service: abuse prevention, debugging, capacity planning.
We do not sell personal data, run advertising, or use third-party analytics/tracking SDKs.
5. Cookies and local storage
| Name / mechanism | Purpose | Lifespan |
|---|---|---|
meteops_session cookie | Keeps you signed in; carries the session and CSRF token binding. | Session; expires on sign-out or session expiry |
| Service-worker cache | App shell + public basemap tiles so the app works on flaky connections. | Until app version change / cache expiry |
| Offline snapshot (per user) | Scoped workspace data for offline viewing in the field. | Marked stale on age; purged on sign-out |
There are no advertising or marketing cookies. Blocking the session cookie will prevent sign-in; blocking the service worker only removes offline behaviour.
6. Who we share data with
| Processor | What they handle | Why |
|---|---|---|
| Resend (transactional email) | Recipient email address, email content (OTP codes, notices, briefs) | Delivering sign-in codes and service emails |
| Hosting provider (application + database) | All service data, at rest | Running the Service |
| Cloudflare | Website requests (meteops.in), edge delivery | Serving the public website |
| Weather providers (Open-Meteo and others we may add) | Geographic coordinates of forecast points and requested variables only | Retrieving forecast/observation data |
| Map tile providers (OpenFreeMap, CARTO) | Standard tile requests from your browser | Rendering the map |
We may also disclose data where law requires it, or to protect the rights, safety and security of the Service and its users. We do not share your organisation's site inventory or your field reports with other customers.
7. Retention
- Account data: kept while your organisation's account is active; removed or anonymised when your administrator deletes your access or the organisation's contract ends (subject to legal holds).
- Audit log, delivery ledger, field reports: retained for the life of the organisation's account unless your administrator requests deletion — these records exist precisely so past operational decisions remain accountable.
- In-app navigation records: deleted automatically after 90 days.
- Weather observations and snapshots: retained per internal schedules (observations days; forecast snapshots per run) — they contain no personal data.
- Offline snapshot on your device: expires and is purged on sign-out.
8. Security
We use sign-in codes that are hashed, single-use, short-lived and attempt-limited; TLS in transit; server-side authorisation on every request (organisation, operating-area and site scope are enforced on the server, not just hidden in the UI); and an audit trail for administrative changes. No method is 100% secure; if we become aware of a breach affecting your personal data we will notify your organisation and, where required, the Data Protection Board and you.
9. Your rights (DPDP Act, 2023)
- Access — a summary of the personal data we hold about you and how it's used.
- Correction & erasure — ask us to correct inaccurate data or erase data we no longer need. If your data is held under your organisation's account, your administrator controls it and we act on their instruction.
- Grievance redressal — raise a concern and have it addressed.
- Nominate — nominate another person to exercise rights on your behalf where applicable.
To exercise any right, email privacy@meteops.in. We respond within a reasonable period and no later than the statutory timeline once the DPDP rules are fully in force. If your request concerns data controlled by your organisation, we may direct you to your administrator — we cannot unilaterally alter an organisation's records.
10. Where data is processed
The Service is hosted on cloud infrastructure that may be located outside India, and our processors (email, edge, weather) operate globally. Transfers are limited to what the Service needs and are governed by our agreements with those processors. Where Indian law restricts cross-border transfer, we will comply.
11. Children
Meteops is a business service. It is not directed at anyone under 18, and we do not knowingly collect their data.
12. Changes to this policy
If we change how we handle personal data we will update this page and change the "last updated" date; for material changes we will give additional notice to organisation administrators. Continued use after the effective date means you accept the revised policy.
13. Contact and grievance
Data protection contact, MozWork Solutions:
Email: privacy@meteops.in
Website: meteops.in
For anything related to your organisation's data or your account's scope, contact your organisation's Meteops administrator first — they control membership and assignments.