This deployment’s privacy notice is incomplete: the operator has not yet supplied all contact, hosting, retention and legal-basis details. Check with the operator before sharing sensitive locations.
The selected place, coordinates, timezone, date, duration, event type and optional interests are sent to the app’s server-side API. Avoid entering a private home or sensitive meeting location unless you are comfortable with this processing.
External checks
The server requests public data using only the fields each source needs: for example, coordinates for a forecast, a bounding box for roads, a country for holidays or a programme ID for television. The Sources page describes each transfer.
Location permission
Your device location is requested only when you press “Use my location” and grant browser permission. The resulting pin is sent for location matching and included when you run a check. You can instead search or place a pin manually.
Optional news
News searches run only when you enable them. They use the venue’s city/country and general disruption terms, not your name or an inferred political preference. Headline mentions are not treated as verified incident locations.
Map requests
OpenStreetMap tiles load directly from OpenStreetMap’s servers when you use the map. These requests reveal ordinary connection data such as your IP address and the viewed map area. See the OpenStreetMap Foundation privacy policy. Other data-source requests go through this app’s server; this does not make coordinates anonymous.
Storage and logs
This code has no accounts, private-calendar access, event-history database, advertising or analytics. The event and report remain in the current browser page; refreshing clears them. The application does not write an event history to local storage.
Public API responses and search results are temporarily cached in server memory. Reuse expires according to the source or application cache policy; expired entries are removed during eviction or when the server instance is recycled. A salted hash of the request IP is held briefly for rate limiting. API routes do not log event bodies or key values.
The hosting platform and external publishers may maintain their own access/security logs. App-level non-storage is not a claim that those organisations keep no records.
Workers Logs are retained for 3 days on the Free plan.
Purposes and legal basis
Details are processed to answer the checks you request, compare alternatives, protect API capacity and display public source information. Optional interests are used only for that check, not for an advertising profile.
The operator has not yet supplied the applicable legal basis for this deployment.
Providers and transfers
The host processes requests for this app. Public-data services are separate recipients and are not automatically all subprocessors: their role depends on the service and actual contractual arrangements. Their own notices govern their processing. The operator must maintain its real processor agreements and any required transfer safeguards.
The operator has not yet described international processing locations or transfer safeguards for this deployment.
Your choices and rights
You can avoid device geolocation, leave optional interests blank, disable news searches, choose a non-sensitive public location, or close the page. Permissions already granted can be revoked in your browser settings.
Depending on the applicable law and processing basis, you may have rights to access, correct, delete or receive your personal data, restrict or object to processing, and withdraw consent where processing relies on it. Contact the operator above. Some requests will depend on what the operator or host actually retains. You may complain to the competent data protection authority..
Recommendations and third-party links
Recommendations are rules-based comparisons, not decisions imposed on you. BAD TIMING does not assess a person’s eligibility or attendance. Opening a source article or publisher link takes you to a separate service with its own privacy policy.
Notice version: 22 September 2026. Changes to the deployment’s data handling require an updated notice.