Privacy Policy - HeatNudge
1) Who we are
HeatNudge is provided by Saifullah Ahad ("we", "us", "our"). Learn more at saifullah.ai.
2) What HeatNudge does
HeatNudge helps outdoor workers and their supervisors plan tasks using forecast weather. You search for a place, compare estimated wet bulb globe temperature (WBGT) in sun and shade, and choose workload, duration, sun exposure, clothing and acclimatization. The app uses the Liljegren et al. (2008) model and NIOSH (2016) heat-stress limits to suggest work and rest minutes per hour, compare lower-heat-stress daylight windows, and save plans.
Safety scope: This is a planning aid built from forecast weather, not a WBGT measurement, medical advice, a workplace compliance decision or a guarantee of safety. The limits concern healthy workers, not every individual or age. Worksite conditions, the supervisor on site, local rules and how people feel come first. HeatNudge is an independent app, not an official or government app. It is not a medical device and does not diagnose, treat, cure or prevent any medical condition. Consult a healthcare professional for medical advice.
3) Information handled by the app
HeatNudge has no account system or developer-operated forecast backend. The following information leaves the app for its search and forecast features:
- Place searches: the text you submit, with leading and trailing whitespace removed, goes to Open-Meteo's geocoding service. Search terms can reveal a city or other place of interest. Do not put unnecessary personal details in a place search.
- Selected-place coordinates: the latitude and longitude returned for the place you select go to Open-Meteo's forecast service. The app sends those numeric values without rounding them to a broad area. These can specify a precise place point; they do not establish where you or your phone actually are.
- Technical request information: Open-Meteo receives your connection's public IP address and ordinary HTTP request metadata. An IP address can relate to a device or shared Internet connection; HeatNudge does not add an advertising ID, hardware ID or account ID.
These transfers are needed for the primary place-search and forecast-planning features. HeatNudge does not request Android device-location permission or obtain GPS location. Planner choices, acclimatization, temperature unit and saved plans are not added to the forecast requests.
The app reads Android temperature/region preferences and, where available, SIM and mobile-network country codes locally to choose an initial Celsius or Fahrenheit setting. These inputs are not sent to Open-Meteo or the developer. It also checks three named apps from the same developer locally to offer Open or Install links; it does not upload an installed-app list.
4) Network requests and Open-Meteo
Place search uses geocoding-api.open-meteo.com/v1/search. Its request contains the submitted search text plus result-count, English-language and JSON-format options.
Forecast requests use api.open-meteo.com/v1/forecast. They contain the selected latitude and longitude, requested weather fields (temperature, relative humidity, precipitation probability, solar radiation, wind speed, weather code and surface pressure), sunrise/sunset/daylight fields, forecast-length options, Unix-time format and automatic time-zone selection. The place name is not separately sent in the forecast request.
These requests go over HTTPS directly to Open-Meteo. The developer does not receive copies of them. This policy describes the transfer of place/search and technical request information to Open-Meteo as sharing with an external service; it does not promise that all provider processing is covered by a service-provider exception.
Open-Meteo uses requests to return results and says its public API may retain technical information for maintenance, troubleshooting and preventing misuse. Its Terms and Privacy describe server logs that can contain coordinates, with deletion of logs after 90 days. The app therefore does not promise that request data is processed only in memory or immediately discarded. The exact handling of a particular search query or deletion request depends on Open-Meteo.
In Data safety terms, the disclosures cover approximate place information, precise selected-place coordinates, in-app search history, and IP-related identifiers. Purposes are app functionality, provider troubleshooting (Analytics), and IP-based misuse prevention (Fraud prevention, security, and compliance). The app does not use these data for advertising or marketing.
5) Local storage
HeatNudge stores the following in its private Android app storage:
- Selected place: place ID, name, administrative area, country, latitude, longitude and time zone.
- Last forecast: the most recently cached forecast response, the time it was fetched and its matching place key.
- Planner choices: task duration, workload, sun exposure, clothing and acclimatization, plus an explicit temperature-unit choice when you make one. These choices persist between app visits.
- Saved plans: the place, task times and duration, workload, work/rest result, completion state and creation time. New plans also retain the time zone, coordinates, sun exposure, clothing, acclimatization, estimated WBGT, comparison limit, forecast time and calculation-method version. Older plans may retain the earlier score/level fields without the newer estimate details.
This local storage uses Android DataStore and a Room database. There is no developer cloud copy of it. Merely saving a plan does not send it elsewhere. A plan only passes to another app when you choose the share action described below.
Use More > Delete local data, then tap Delete in the Delete all local data? dialog to remove the selected place, last forecast and saved plans and reset planner choices and temperature unit. Clearing app storage or uninstalling HeatNudge also removes its local app data.
6) Permissions
INTERNET is declared for place-search and forecast requests. HeatNudge does not request device-location, camera, microphone, contacts, notifications, calendar, phone, SMS or shared-storage access. Its phone contact action opens your dialer; it does not place a call automatically.
7) Sharing and feedback
Sharing a saved plan opens Android's chooser with a text brief. Depending on the plan's age, the brief includes the place name, task times, time zone, duration, workload, sun exposure, clothing, acclimatization, work/rest result, estimated WBGT and limit, forecast time and weather attribution. It does not include the raw latitude and longitude fields. You choose the destination app and whether to send it. That app and any recipient handle the shared information under their own practices.
Send feedback opens your chosen email app addressed to [email protected], with a feedback subject. HeatNudge does not attach a message body, diagnostic footer or saved plan, and does not submit a web form or use Web3Forms. No feedback email is sent automatically.
If you compose and send an email, we receive the message, your sender address and any details or attachments you choose to include. We use that correspondence to answer your request and address the issue you raised. Your email provider handles its delivery. This is separate from in-app collection by HeatNudge.
Source, developer, privacy and other-app links open external apps or websites using fixed addresses without adding your place search, plan or profile. Those services process visits under their own policies. If no suitable app can open an action, HeatNudge may copy the intended brief, link, email address or phone number to Android's clipboard and notify you.
8) Selling or sharing personal information
We do not sell personal information. HeatNudge contains no advertising, analytics, crash-reporting or tracking SDK. The Open-Meteo transfers and any user-directed sharing or email are described above; this is not a claim that no information ever leaves the phone. Open-Meteo's troubleshooting logs are distinct from an in-app analytics SDK.
Opening another app from the About Developer page does not send it your HeatNudge plans or settings. We do not operate a social feed, account directory or public plan service.
9) Security and retention
HeatNudge's search and forecast connections use HTTPS, and its network configuration rejects cleartext traffic. Your chosen email or sharing service has its own security practices; we cannot guarantee its delivery encryption.
Local records remain until you delete them, replace the relevant saved choice/forecast, clear app storage or uninstall. We do not keep those local records on developer servers. Open-Meteo's published log-retention period is 90 days; HeatNudge cannot itself erase or verify erasure of provider logs. Correspondence you send to the developer is kept as needed to handle your request and can be the subject of a deletion request.
10) Your controls
- Change the selected place and planner choices at any time.
- Delete an individual saved plan from the saved-plans screen.
- Delete all local data with More > Delete local data > Delete, or clear app storage or uninstall through Android Settings.
- Request deletion of correspondence held by the developer by emailing [email protected]. The same address is available through More > Send feedback and More > About Developer > Email.
- For information retained by Open-Meteo, use the contact details in its Terms and Privacy. We can help route a request, but do not control its logs or guarantee deletion of a particular entry. Describe the relevant date and place/search only as needed; do not send passwords or unnecessary sensitive information.
Deleting local data does not recall a shared brief, erase an email already sent or delete provider logs. Contact the relevant recipient or service about copies they hold. HeatNudge has no user account to delete.
11) Children's privacy
HeatNudge is intended for users aged 13 and above, including outdoor workers and their supervisors. It is not directed to children under 13. Younger workers need adult supervision. The work/rest estimates use occupational limits for healthy adult workers; they are not child-specific guidance or permission to perform hazardous work. Users and supervisors must follow local age and workplace rules.
The app does not ask for a birth date or verify age. Place searches and forecast requests use the same external services for all users; there is no separate collection exemption for younger users. If you have a concern about a child's information in developer correspondence, contact us at the address below. Provider-held information requires a request to the provider as described above.
12) International processing
Open-Meteo, external sites, your chosen sharing/email services and the developer's email service may process information outside your country. The developer is based in Dhaka, Bangladesh. No HeatNudge account or developer-hosted forecast profile is created.
13) Changes to this policy
We may update this policy when the app's practices change. The published policy will remain at privacy.saifullah.ai/HeatNudge.html with an updated effective date.
14) Contact
For privacy questions or requests, contact Saifullah Ahad: