Privacy policy

CommViewer does not require an account. We process the information below to provide the service. If you email us, we also process your sender address and message to respond.

The search API receives your query to return results. Our own analytics events record that a search occurred and its character count instead of the query text.

• Device identifier: a random UUID generated for an installation or browser. This identifier is not Apple’s IDFV or Google’s advertising ID.
• Push notifications: FCM token, registered keywords, selected communities, matches, and delivery history.
• Device environment: platform, OS and app version, model, language, and region settings.
• Usage and diagnostic records: access URLs, screen changes, post views, event and error timestamps and messages, and performance metrics.
• IP address: processed for request routing, security, and rate limiting. Our own analytics classify country and language using device language and region settings instead of IP addresses.

Read history, bookmarks, hidden communities, theme preferences, offline archives, and downloaded material are stored on your device. Material you choose to share or export is also subject to the destination service’s policies.

Optional saved community usernames and passwords are managed in iOS Keychain or encrypted Android storage and are not sent to CommViewer servers. They are sent to the relevant community when you sign in there. Social sign-in is governed by your chosen provider’s policies.

iOS Keychain entries and files separately saved to Photos or other locations may remain after uninstalling the app. Remove saved credentials in login management and delete exported files from their respective locations.

We do not provide information collected directly for service operations, such as keyword notifications, to advertisers for ad targeting. See the advertising section for information processed by advertising SDKs.

• Providing post browsing, search, keyword alerts, and user settings.
• Analyzing usage, crashes, and performance to improve features and quality.
• Troubleshooting, security, and preventing abuse or excessive requests.
• Responding to inquiries and privacy requests.

When FCM identifies an invalid token, the corresponding processing removes the device record and linked settings. Uninstalling the app or revoking notification permission does not immediately delete server records.

Electronic records are deleted when their purpose or retention period ends. Where law requires retention, we keep information within the required scope and period. Server backups are rotated out within a maximum 7-day retention cycle.

• Device information and FCM tokens become eligible for scheduled deletion after at least 90 days of inactivity. Linked keyword settings are deleted with the device record.
• Push delivery history and app event and error logs: normally retained for 30 days before scheduled deletion.
• Firebase Crashlytics reports: handled under Google’s retention policy and generally deleted after 90 days.
• IP-based rate-limit records: periodically deleted after their limiting window expires.

We do not sell personal information. We use the external services below to operate CommViewer. We may disclose necessary information in response to lawful requests under applicable procedures.

• Google LLC: Firebase Cloud Messaging (push), Analytics (app statistics), Crashlytics (errors), and Performance Monitoring.
• Oracle Cloud Infrastructure: server and database hosting. The existing deployment uses the Chuncheon region in the Republic of Korea.
• Our own OpenTelemetry and SignOz infrastructure in Korea: usage events and performance analysis. Records may contain device identifiers and are not treated as fully anonymous.
• Google AdMob and other advertising processing are described in the advertising section.

Google LLC is based in the United States. Some Firebase and advertising data may be processed on Google’s global infrastructure, including in the United States. See Google’s documentation for service-specific locations and retention.

• Recipient: Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA.
• Data and purposes: installation and device identifiers, push tokens, usage events, and error and performance information processed by the relevant SDK, for push delivery and usage, error, and performance analysis.
• Timing and method: encrypted network transmission when the relevant feature or SDK communicates.
• Choices and requests: change device permissions or contact us to request processing restrictions or deletion. This may limit the related features. We follow separate consent procedures where required by law.

• Firebase privacy and service-specific retention

The website uses browser storage for a device identifier, theme, read status, and usage events waiting to be sent. You can delete site data or restrict storage in browser settings; some features may be affected.

Apps may use Firebase analytics, diagnostics, and performance tools. The website and apps may use our own OpenTelemetry analytics. Records containing device identifiers may be linked with other information and are managed as pseudonymous usage information.

Cookies and storage set by original community sites and social sign-in providers are governed by their own policies.

The Android and iOS apps show Google AdMob advertising. Advertising SDKs may process advertising identifiers (iOS IDFA or Android advertising ID), approximate IP-based location, device information, and ad impressions and clicks. Required tracking permissions and consent follow applicable laws and platform procedures.

Manage tracking and advertising preferences under Privacy & Security → Tracking on iOS, or Google → Ads and related device settings on Android. Menu names vary by OS version.

The website currently includes AdSense ownership verification information and does not load the advertising script. Verification alone does not set advertising cookies. Before enabling web advertising, we will update this policy and explain IP, device, ad interaction, and cookie processing and required consent procedures.

• How Google uses information for advertising
• Google privacy policy
• Google My Ad Center
• Participating advertising providers’ choices

• Delete keywords in the app or disable push notifications in device settings.
• Contact us to request access, correction, deletion, restriction of processing, or withdrawal of consent where applicable. We explain any minimal verification needed to handle the request.
• We may ask for your device UUID to locate server records. Do not send passwords or community sign-in credentials.
• Uninstalling does not immediately delete server information. Contact us if you want immediate deletion. Delete local browser information using your browser’s site-data controls.

We use technical and organizational safeguards including encrypted API communications, restricted administrative access, encrypted on-device credential storage, and access-record reviews.

We do not intentionally collect personal information from children under 14. If we learn that a child’s information was processed without legally valid guardian consent, we take appropriate steps, including deletion, under applicable law.

Privacy and rights requests: CommViewer operator / cs@devryner.com. As previously announced, we aim to respond within 7 business days and comply with statutory handling deadlines.

You may also seek dispute resolution or report privacy concerns through these Korean organizations.

• Personal Information Dispute Mediation Committee
• Korea Privacy Portal

We may update this policy as laws or the service change. We announce changes at least 7 days before they take effect, or 30 days for significant changes such as additional collection or changed purposes, and obtain separate consent where legally required.

This revision adds Korean and English presentation and clarifies existing processing. Visiting this page is not treated as consent to new information collection.