Privacy policy

Controller and contact

The data controller is Marcin Korzeniowski, operating under the trade name CODEVERTURE. Privacy contact: [email protected]. The controller's business address is disclosed without undue delay at the request of the person concerned.

JISHINDESU has no customer accounts, newsletter or marketing mailing list and sends no promotional email. Correspondence is processed only to handle the matter initiated by the sender, including enquiries, corrections, privacy requests and security reports.

Location and preferences

A selected map point, up to eight optionally named saved places with their coordinates and reading radii, language, theme, sound preference and alert settings are stored in the user's browser. The service also stores interface files and a limited cache of previously requested map resources on the device so that installation, offline information and faster repeat use are possible. These items can be removed by clearing site data or uninstalling the application.

Precise coordinates selected on the map, entered manually or obtained with browser permission are processed only to calculate the requested results. On an earthquake page, distances and nearby station readings for saved places are matched in the browser against observation data already delivered for that event; saved place names and coordinates are not sent to the server for this comparison. They are not added to the earthquake catalogue or sent as Analytics event parameters.

When the user opens the saved-place dashboard or its history, coordinates and the chosen radius are sent to the first-party API only to find nearby measured station readings. User-defined place names are not sent. Request logging is disabled and these coordinates are not retained in the earthquake catalogue, a user profile or a location history.

When the user chooses to share a map point, its coordinates and search radius are included in the generated link. Anyone who receives that link can view the shared point. JISHINDESU does not create a separate stored record of the link; the user decides whom to send it to.

If the user voluntarily enables earthquake notifications, one anonymous browser subscription can contain up to eight resolved municipality codes and a separate Shindo threshold for each municipality. JISHINDESU stores those alert rules, the subscription identifier and the technical information needed to deliver and manage notifications. Precise coordinates, user-defined saved-place names, a name, an email address and continuous location history are not stored with the server-side subscription. Notification settings can be updated, disabled and deleted at any time.

An approximate country derived from the connection is used temporarily to select the applicable privacy and advertising settings. It is not used to create a JISHINDESU user profile. When the country cannot be determined, Google storage and personalisation start disabled.

Android application

In the native Android application, up to eight saved-place names, their coordinates, monitoring radii and Shindo thresholds, together with language and application preferences, are stored in the application's private storage on the device. Current location is requested only after a user action while the application is visible. JISHINDESU does not request background location and does not continuously track the device.

When the application requests current or historical observations near a saved place, its coordinates and selected radius may be transmitted over HTTPS to the service's first-party interface. They are processed transiently to return the requested station readings. User-defined place names are not transmitted, request logging for these operations is disabled, and the coordinates are not retained as a profile or location history.

If the user enables Android earthquake notifications, the application sends a Firebase installation ID, language, monitoring coordinates, radius and Shindo threshold to the first-party API. The coordinates are used transiently to resolve nearby observation stations. The server stores the installation ID, language, resolved station identifiers and thresholds needed to deliver alerts, but not precise coordinates or user-defined place names. Disabling notifications removes the server-side subscription and unregisters the Firebase installation from messaging.

Community Shaking is optional and is activated only after the user chooses to submit a felt report. Before transmission, the Android application rounds the current coordinates to two decimal places and sends only this approximate location, the selected felt level, the report time, a random client report identifier and an installation identifier used to operate and protect the feature. The server converts the location to an H3 resolution-6 cell and stores that cell, its derived centroid, the felt level and anti-abuse information instead of the raw coordinates. Public activity is shown only as aggregated H3 resolution-5 areas after an anonymity threshold is met, never as a person's exact location. The report can be changed or deleted using its deletion token and is not used for advertising, analytics or personalisation.

iOS application

In the native iOS application, up to eight saved-place names, their coordinates, monitoring radii and Shindo thresholds, together with language and application preferences, are stored in the application's private storage on the device. Current location is requested only after the user selects Use my location while the application is visible. The application requests When In Use access, makes a single current-location request and does not request background location or continuously track the device.

When the application requests current or historical observations near a saved place, its coordinates and selected radius may be transmitted over HTTPS to the service's first-party interface. They are processed transiently to return the requested station readings. User-defined place names are not transmitted, request logging for these operations is disabled, and the coordinates are not retained as a profile or location history.

If the user enables iOS earthquake notifications, the application sends a Firebase installation ID, language, monitoring coordinates, radius and Shindo threshold to the first-party API. The coordinates are used transiently to resolve nearby observation stations. The server stores the installation ID, language, resolved station identifiers and thresholds needed to deliver alerts, but not precise coordinates or user-defined place names. Firebase Cloud Messaging also processes the installation ID, APNs token and technical app and device information needed for delivery. Disabling notifications removes the server-side subscription and unregisters the installation from Firebase Messaging.

Community Shaking is optional and is activated only after the user chooses to submit a felt report. Before transmission, the iOS application rounds the current coordinates to two decimal places and sends only this approximate location, the selected felt level, the report time, a random client report identifier and an installation identifier used to operate and protect the feature. The server converts the location to an H3 resolution-6 cell and stores that cell, its derived centroid, the felt level and anti-abuse information instead of the raw coordinates. Public activity is shown only as aggregated H3 resolution-5 areas after an anonymity threshold is met, never as a person's exact location. The report can be changed or deleted using its deletion token and is not used for advertising, analytics or personalisation.

Purposes and legal grounds

Essential processing is used to deliver requested map results, remember local choices, provide notifications expressly requested by the user, secure the service, prevent abuse and diagnose failures. Notifications are activated only after a separate user action and operating-system permission. Depending on applicable law, processing is based on providing the requested service, the user's consent where required, and the operator's legitimate interest in running a secure, reliable information service.

On the website, Google Analytics 4 is not loaded for connections classified as coming from the EEA, the United Kingdom or Switzerland, or when the country cannot be determined. Cookie-free Cloudflare Web Analytics may be used for aggregate site and performance measurement. Before any future activation of web advertising, the required regional privacy controls and Google-certified consent message will be enabled. Information may also be processed where necessary to comply with law or establish, exercise or defend legal claims.

Connection data and service providers

Hosting, content-delivery, security and map providers process standard connection information such as IP address, time, requested resource and browser information when needed to deliver and protect the service.

These providers may process information outside Japan under their own privacy terms and contractual safeguards. JISHINDESU limits access to authorised persons and providers needed to operate, secure and measure the service, or to comply with law.

Web analytics, Google and advertising

Cloudflare Web Analytics may provide aggregate page-view, referrer-host, approximate-country, device, browser and website-performance metrics without cookies. Cloudflare states that Web Analytics does not collect or use visitors' personal data and does not log URL query strings. Google Analytics 4 is not loaded on the website for visitors classified as being in the EEA, the United Kingdom or Switzerland, or when the country cannot be determined.

In the Android and iOS applications, Firebase Analytics processes screen views and limited interaction events for service measurement and improvement; analytics can be disabled and its local identifier reset in the application settings. Google may process an app-instance identifier, app and device information, approximate location derived from IP and interaction events. User-defined place names, precise map coordinates, location-search text and the Firebase installation ID used for notifications are excluded from Analytics event parameters. The iOS application uses the Firebase Analytics package without IDFA support.

Google AdSense advertising is not currently displayed on the website. Before any future activation, JISHINDESU will enable the applicable Google privacy message and required user choices. Once advertising is active and permitted, Google and participating advertising vendors may process IP address and approximate location, online and device identifiers, viewed content, website interactions, performance data and diagnostic information to select, deliver, measure and protect ads. Users can manage personalised Google advertising at https://myadcenter.google.com.

Google AdMob in the Android and iOS applications loads only after activation by the operator and, where required, the applicable Google privacy message and the user's choices. Google and participating advertising vendors may process IP address and approximate location, device or app identifiers, advertising data, app interactions, performance data and diagnostic information to deliver, measure and protect ads. The Android application removes permission to access the Android advertising ID. The iOS application does not request App Tracking Transparency permission and therefore does not obtain permission to use the IDFA for tracking, although Mobile Ads may use other identifiers permitted by iOS and the user's privacy choices.

External transmission notice

Cloudflare provides content delivery, security and cookie-free Web Analytics. Its performance beacon reports through the site's /cdn-cgi/rum endpoint and may process the requested path, referrer host, approximate country, device and browser category, navigation type and performance metrics. Query strings are not logged by Web Analytics.

Where website Google Analytics 4 is enabled outside the excluded European and unknown-country profiles, Google LLC may receive standard connection information, online identifiers, device and browser information, approximate location, viewed content and interaction events for audience measurement, service improvement, reporting, fraud prevention and security. If Google AdSense is activated in the future, Google and its advertising partners may also receive the advertising information described above. Precise map coordinates are excluded from Analytics and advertising event parameters.

OpenFreeMap and its delivery infrastructure receive standard connection information and the requested map resource in order to supply the map background and protect their infrastructure.

If notifications are enabled, the Web Push service selected by the user's browser receives an anonymous subscription identifier, encrypted notification content about one matching municipality and standard delivery information. The provider may be Apple, Google, Mozilla, Microsoft or another browser provider. This processing is used only to deliver the requested notification; precise map coordinates, user-defined place names, a name and an email address are not included in its content.

In the Android application, Google Firebase receives an app installation identifier, application and device metadata and notification-delivery or interaction information to register the installation, provide requested Cloud Messaging notifications and measure application use.

In the iOS application, Firebase Cloud Messaging receives the Firebase installation ID, APNs token, device model, language, time zone, operating-system version, application identifier and application version needed to register the installation and deliver requested notifications. When usage analytics is enabled, Firebase Analytics receives an app-instance identifier, app and device metadata, approximate location derived from IP, screen names and the limited feature events described above. Google Mobile Ads and its advertising partners may receive the advertising, device, interaction, performance and diagnostic information described above when in-app advertising is active. Transfers to these providers are encrypted in transit.

Google describes its processing and controls at https://policies.google.com/privacy and https://myadcenter.google.com. Google lists certified third-party advertising vendors at https://support.google.com/adsense/answer/94149. If web advertising is activated in the future, European users will be able to withdraw or change consent through the privacy and cookie settings link supplied by Google's CMP; supported US users will be given the applicable opt-out control.

Deleting mobile application data

JISHINDESU does not require an account. To delete data associated with the Android application, open JISHINDESU, go to Settings, select Delete my data and confirm the deletion. The command removes saved-place names and coordinates, monitoring radii and Shindo thresholds, alert preferences, downloaded articles, cached API responses and other temporary files from the device. It also resets the local Firebase Analytics identifier, disables Firebase Cloud Messaging and requests deletion of the server-side notification subscription.

Uninstalling JISHINDESU also removes data held in the application's private storage, but using Delete my data first is recommended when notifications were enabled because it also requests deletion of the server-side subscription. JISHINDESU has no user account and does not keep a server-side profile or location history that requires a separate deletion request.

In the iOS application, turning off Usage analytics stops Analytics collection and resets the local Analytics data and app-instance identifier. Settings > Delete all places removes saved-place names, coordinates, monitoring radii and Shindo thresholds and requests deletion of the server-side notification subscription when no monitored places remain. Settings > Disable notifications removes the server-side subscription, unregisters the installation from Firebase Messaging and clears the notification badge. Other local preferences and cached responses can be removed by uninstalling the application. If notifications were enabled, using one of these in-app controls before uninstalling is recommended so the server-side subscription is removed promptly.

Aggregated or provider-controlled Analytics and advertising records already processed by Google are not directly addressable through JISHINDESU and remain subject to Google's retention rules and user controls. Limited connection or security records may also be retained for the periods described below when necessary to protect the service or comply with law. For assistance with a deletion request, contact [email protected].

Retention

Browser preferences, Android and iOS application data and cached files remain on the device until they expire, the user clears them using available controls or uninstalls the application. A push subscription remains until it is deleted, expires, becomes invalid or is no longer needed; both mobile applications provide controls that request deletion of the server-side notification subscription. Connection and security records are kept only for as long as needed to operate and protect the service, investigate an incident or meet a legal obligation. Provider-controlled records follow the providers' retention settings.

A Community Shaking report may be retained on the server for up to 30 days unless the user deletes or replaces it earlier. The active report receipt shown by the iOS application expires after 30 minutes; this shorter interface period does not extend the server retention period.

Aggregate Web Analytics records follow Cloudflare's retention settings. Analytics and advertising data processed by Google follow Google's retention rules and the settings selected for the JISHINDESU accounts. Correspondence initiated by a user is kept only while the matter is handled and for any additional period needed for security, legal claims or statutory duties.

Rights and requests

Depending on applicable law, a person may request information about processing, access, correction, deletion, restriction or cessation of use or disclosure. A request should be sent to [email protected] with enough information to identify the relevant record; proportionate identity verification may be required.

The operator responds without undue delay and within any mandatory statutory period. A complaint may also be submitted to the competent data-protection authority.

Security and changes

JISHINDESU applies organisational and technical safeguards appropriate to the nature and risk of the processing. No Internet service can guarantee absolute security.

This policy may be updated when the service, providers or law change. The current version and update date are published on this page; material changes are presented before new optional processing begins where consent is required.