Privacy Policy

Operator

Personal data related to this site is handled by Sekimosoft LLC (service name: LifeNaviHub). See the contact section below and the on-site contact form for how to reach us.

Information we collect (Access analytics)

Our server-side first-party collector may record the following kinds of data.

• IP address (stored server-side only; masked by default in admin UI) and a coarse IP prefix (IPv4 /24, IPv6 /48)
• A daily visitor identifier that rotates each UTC day (HMAC over the coarse prefix and related inputs; not reversible to the IP)
• Session id, request id, timestamps, and event types (for example page_view, page_exit, tool actions, login-related events)
• Path, query string (with sensitive-looking values stripped where attempted), landing URL, page category, locale
• Referrer URL / domain, UTM parameters, and ad click ids (gclid / gbraid / wbraid) when present
• Network-derived geo / org hints (for example country code; region, city, or ASN organization when available)
• Device class, OS / browser family and version, screen and viewport size, DPR, browser language, User-Agent string
• When you are signed in, an internal user id linking usage to your account (email is not stored in the analytics store)
• Soft “suspicious signal” flags (never used alone to declare a person fraudulent)

Cookies and browser storage

To operate the service we may use the following cookies and on-device storage. These are not Google Analytics consent cookies (this site does not use GA4).

• Authentication session cookie (for example lnh_session, HttpOnly) and a CSRF cookie (for example lnh_csrf)
• OAuth state cookie during Google sign-in (for example lnh_oauth_state)
• Tool preferences, recently used tools, travel checklist, and home Daily Utility preferences in localStorage (keys typically prefixed with lnh_). These values are not placed in analytics event bodies

Google sign-in and accounts

Public tools work without an account. Where Google sign-in is enabled, we use Google OAuth for authentication and may store linked account information (which can include an email address) in our authentication database. Email, display name, and OAuth tokens are not placed in analytics event metadata. When you are signed in, analytics events may include an internal user id so activity can be associated with your account. My Page favorites, history, and saved views are server-side data linked to your account.

Contact form

When you use the on-site contact form, we process the following. We do not publish an email address on the site. In the current v1 implementation we do not persist inquiries in a CRM or dedicated inquiry database; the server delivers an internal notification and an acknowledgement to the submitter by SMTP.

• Name, if entered
• Email address
• Subject
• Inquiry content
• Submission timestamp, locale, and a contact ID for the receipt

Purposes for contact-form data

We use contact-form submissions for:

• Receiving the inquiry
• Responding to the inquiry
• Sending an acknowledgement / copy email
• Operational or security handling where necessary

Information we do not collect

We do not store the following in the analytics store.

• Email address, display name, passwords, or OAuth tokens in analytics events (see “Google sign-in and accounts” for the auth database)
• Cookie contents, Authorization headers, or free-text form bodies as analytics event payloads
• Browser fingerprints via canvas, fonts, plugins, or similar techniques
• Sends to third-party access-analytics tags such as Google Analytics (including GA4) or Meta Pixel

Purposes

We use this information for:

• Understanding and improving pages and tools
• Understanding referrers and campaigns
• Reviewing outages, unusual access, and bot-like patterns (soft signals)
• Providing authentication and My Page features for signed-in users
• Responding to contact-form inquiries
• Operations and support by authorized administrators

Retention

Verified defaults are as follows. We do not state retention periods we have not confirmed. Analytics retention days may change via environment configuration. After expiry, raw analytics data is removed via an explicit purge process.

• Access analytics raw events and full IP: default 30 days
• Access analytics session rollups: default 90 days
• Access analytics daily rollups: default 730 days
• Auth session cookie: default 14 days (renewed on sign-in)
• Contact form: no CRM/inquiry DB in v1; delivered by SMTP. Mailbox retention follows the operator’s email handling (this policy does not assert a month count)
• Browser localStorage: may remain on the device until the user clears it

Admin access

Analytics dashboards are available only on the Japanese admin routes (/ja/admin) and only to allowlisted operators. Lists show masked IPs by default; raw IP detail is limited to separately allowlisted admins. Admin pages are not intended for search indexing.

About IP addresses

We record IP addresses as a network endpoint signal. We do not treat an IP alone as uniquely identifying a person. Soft suspicion flags are never used alone to label a person fraudulent based solely on IP.

Third parties and external services

We do not run third-party advertising analytics that sell or share our first-party analytics data with ad networks. Operating the service involves:

• Google sign-in when enabled — for authentication, not as an analytics ad tag or GA4
• Google AdSense — we load advertising-technology script for site ownership verification and review, and we publish ads.txt authorizing Google. LifeNaviHub has not intentionally enabled visible ad units at this time. If advertising is enabled later, applicable policies may involve cookies or similar technologies, and consent management may be presented where required
• SMTP — contact-form notification and acknowledgement email delivery
• Cloudflare and hosting — delivery and connectivity infrastructure
• Public statistical sources (World Bank, OECD, and similar) and holiday libraries — for on-site indicators and holiday display, not visitor analytics profiling

Access, correction, and deletion

If you request access to, correction of, suspension of use of, or deletion of personal data we hold about you, we will respond within a reasonable scope under applicable law. Please use the on-site contact form.

Revisions

We may revise this policy when laws or our operations change. Material changes will be announced on this site.

Contact

For questions about this policy or the service, use the on-site contact form. You may also reach the operator Sekimosoft LLC via the public site sekimosoft.com. This page does not list an email address.