Privacy Policy

This policy applies only to Naite pages under life.konviny.com and to Naite's native apps for Android, iOS, and iPadOS that display those pages in a WebView. Other apps that may later be hosted on the same domain can have different data practices and notices.

MADFORDEV operates Naite.

Naite is currently a personal journal and reflection tool, not a medical or mental-health treatment service.

Naite stores each journal's date key, title, entry, creation time, and update time in the browser's IndexedDB database named naite. MADFORDEV has not implemented a journal API or server database, and these journal fields are not sent to MADFORDEV or Google Analytics.

Language, font, font size, letter spacing, line height, theme, and analytics choice are stored in localStorage or first-party cookies so the app can restore your settings. Locale and theme cookies are set for up to one year; localStorage and IndexedDB records have no automatic expiry.

Naite currently has no user account, Naite-managed remote backup, server synchronization, or built-in Google Drive or iCloud Drive account connection. Choosing one of those providers as an export destination in the operating system's file picker does not connect that account to Naite. If an automatic connection is added later, MADFORDEV will update this policy and the store disclosures before enabling it.

Naite's static web files are delivered through Cloudflare Pages. When a page or asset is requested, Cloudflare may process an IP address, request time, requested path, user-agent or system configuration, routing information, and security signals to deliver, secure, and troubleshoot the service.

The Naite source code does not create a separate application request-log database. Infrastructure data available to MADFORDEV is kept only as needed for delivery, security, troubleshooting, Cloudflare service settings, and applicable legal obligations, and is deleted or anonymized when those purposes and obligations end.

Current Naite navigation places a selected journal date in a URL fragment, which browsers do not include in a normal HTTP request. A legacy link that still contains a date query parameter may include that parameter in the initial infrastructure request before Naite converts the link. Journal titles and entries are never placed in Naite URLs.

The regular Naite website loads Google Analytics by default to measure service usage. While active, it can send a page path, page location, referrer, language, browser/device/screen information, session information, a pseudonymous first-party _ga client identifier, and approximate location derived by Google from the connection IP address. Google's documentation states that GA4 discards the IP address before logging it.

Google Analytics is never loaded on Naite's app-only WebView routes or on this privacy-policy route. Naite also never sends a journal date, title, or body to Google Analytics, whether through page values, event parameters, or URLs. Advertising storage, advertising user data, advertising personalization, Google Signals, and advertising-personalization signals are denied or disabled in the Naite tag configuration. Naite currently displays no ads.

On the regular website, you can opt out at any time in Naite Settings. Turning analytics off blocks future Naite analytics requests and removes accessible _ga cookies from the device. Data already processed by Google is retained under the GA4 property setting only for usage measurement and service operation, then deleted or aggregated when that period ends. It cannot necessarily be matched back to a particular journal or person by MADFORDEV.

Android System WebView may send usage statistics and crash diagnostics to Google when the device user has enabled sharing usage and diagnostics. This platform reporting is separate from Naite's Google Analytics choice and is controlled by Android and the WebView provider.

Google states that WebView reports can include system, feature-use, performance, responsiveness, memory, crash, app-package, and pseudonymous-token information, and that URLs are not collected in those reports. Naite does not currently set the app-level WebView MetricsOptOut flag, so this reporting follows the device user's Android diagnostics choice.

Local journals remain until you delete an individual dated entry, clear the browser site data or native-app storage, or uninstall the app. Naite does not yet provide a single in-app button that deletes all local journals and preferences at once.

Uninstalling a native app normally removes its app-specific WebView data. Standard Android cloud auto-backup is disabled for Naite, but behavior during some operating-system or manufacturer device-to-device transfers must be verified on real devices and is not promised as an absolute guarantee.

On the regular website, your browser downloads the export ZIP directly to the destination you choose. Naite does not upload the journal database or export ZIP to a Naite or MADFORDEV server.

When you export from the native app on Android, iOS, or iPadOS, Naite creates a temporary ZIP in the app cache and opens the operating system's file picker. If you complete the save, the system places a permanent copy in the external location you choose. Naite deletes its temporary cache file after the file-picker flow finishes.

The externally saved copy remains after you delete a journal or uninstall Naite. You control that copy and must delete it yourself from the selected location.

If you choose iCloud Drive, Google Drive, or another storage provider in the system file picker, that provider may transfer, store, and otherwise process the copy under its own privacy and retention terms. Naite does not connect to the provider in the background or automatically upload or synchronize journals or ZIP files.

Analytics and infrastructure data is kept only while needed for usage measurement, delivery, security, troubleshooting, provider service settings, or applicable legal obligations, and is deleted or aggregated when those purposes, settings, and obligations end.

Cloudflare processes web-delivery and security data. Google processes analytics from the regular website unless you turn it off in Settings, but not from the app-only WebView or this privacy page; Google may also process the separate device-level WebView diagnostics described above. These providers can process data in countries outside your residence under their own infrastructure and data-protection terms.

When you explicitly choose iCloud Drive, Google Drive, or another storage provider in the system file picker, Apple, Google, or that provider may process the exported copy under its own terms. Naite does not automatically upload a journal or ZIP to any of those providers.

MADFORDEV does not sell Naite journal data or analytics data. If Naite later introduces ads or a new processor, this policy and the in-app choice will be updated before collection begins.

Naite uses HTTPS for web delivery and limits journal processing to browser storage in the current version. Local journal fields are not separately encrypted by Naite at rest, so device passcode, operating-system security, backups, shared-device access, and exported-file handling remain important.

No internet or storage system can be guaranteed completely secure. Report a suspected privacy or security issue to the contact address shown on this page.

Naite is not designed specifically for children and does not ask for an age or create an account. If Naite later targets children or introduces age-based processing, MADFORDEV will add any required guardian-consent handling and update this policy before that change.

You control local journal deletion on the device and can opt out of regular-website analytics in Settings. The app-only WebView and this privacy page do not load Google Analytics. Because MADFORDEV does not receive the local journal database, it cannot retrieve or remotely delete a journal that exists only on your device.

For questions about analytics, infrastructure data, this policy, or applicable privacy rights, contact MADFORDEV using the privacy inquiry address on this page.

MADFORDEV will update the date and provide an appropriate in-app or website notice before a material change, such as adding accounts, automatic server or cloud synchronization, advertising, new analytics purposes, or a materially different native-platform data flow.