Privacy Policy for MineBlog

Last updated: 2026.9.4 · 简体中文

MineBlog (Chinese name: 我博客) is a third-party client for Cnblogs (博客园) provided by Weigan Technology (Shenzhen) Co., Ltd. (hereinafter referred to as "we" or "us"). This Privacy Policy applies to MineBlog on iOS, iPadOS, macOS, and visionOS.

We attach great importance to the protection of your personal information and privacy. We will provide appropriate security measures for your personal information in accordance with legal requirements and industry-standard security practices.

This Privacy Policy works together with our User Agreement for MineBlog.

MineBlog does not operate a separate account system. You may sign in with an existing Cnblogs account through OAuth to use features such as viewing following feeds, managing bookmarks, publishing status updates, Q&A, and classroom interactions. When not signed in, you can still browse some public content. Sign-in credentials, access tokens, MetaWeblog image-hosting tokens, interface preferences, drafts, and cached data are mainly stored on your device. The Service currently does not integrate third-party advertising SDKs and does not use ads to unlock core features. The Service currently does not charge in-app subscription or one-time purchase fees.

1. How We Collect and Use Your Personal Information

We use your personal information only where we have a lawful basis. Depending on applicable law, we may rely on your consent, performance of a contract with you, compliance with legal obligations, or other lawful bases.

1.1 Cnblogs account sign-in. When you choose to sign in, the app guides you to Cnblogs' official authorization page through an embedded web view to complete OAuth authorization. After authorization, we receive an authorization code and exchange it for an access token and refresh token to call Cnblogs APIs on your behalf. We may obtain account profile information such as nickname, avatar, blog URL, and user identifiers from Cnblogs APIs to display your profile and provide signed-in features. Account registration, identity verification, password recovery, and account cancellation are handled by Cnblogs under its own rules.

1.2 Anonymous browsing. When you are not signed in or your token has expired, the app may obtain an anonymous access token through Cnblogs client credentials so you can browse some public content such as blog posts, news, knowledge base articles, and Q&A. This process does not require you to provide personal identity information to us.

1.3 Content browsing and search. To show home feeds, post details, news, knowledge base articles, Q&A, status updates, classroom assignments/announcements/polls, and search results, the app requests content from Cnblogs servers and renders and caches it on your device. Author names, avatars, article bodies, comments, and other displayed content generally come from Cnblogs and are also subject to Cnblogs' rules.

1.4 Publishing and interaction. After you sign in, when you publish status updates, ask or answer questions, post comments, vote, submit classroom assignments, or (with management permissions) publish classroom assignments, announcements, or polls, the text, links, images, and related metadata (such as visibility) that you actively provide are submitted to Cnblogs servers through Cnblogs APIs or related service endpoints so they can be displayed or processed on the Cnblogs platform. We do not permanently store full copies of your published content on our own servers.

1.5 Photo selection and upload. When you publish a status update and choose images, the app requests access to the selected photos in your library. Selected images are uploaded to Cnblogs image hosting through the MetaWeblog API and return image URLs for publishing. The app prefers the MetaWeblog access token you configure in settings; if none is configured, it may use your current OAuth access token for authentication. Upload may fail if you are not signed in or your blog is not bound. We do not upload other photos from your library to our servers.

1.6 Bookmarks and local preferences. Your bookmarks may be retrieved, added, edited, or deleted through Cnblogs APIs. Following feeds and related statistics are mainly obtained from Cnblogs APIs to display content from blogs you already follow after sign-in (the app currently does not provide follow or unfollow actions). Theme color, appearance mode, language preference, search category preference, unpublished drafts, and interface settings are mainly stored locally on your device to improve your experience.

1.7 Local cache and secure storage. To improve loading speed, the app may cache images and API responses locally. OAuth tokens, refresh tokens, and MetaWeblog tokens are preferably stored in the system Keychain and may fall back to local preference storage when Keychain is unavailable. You can clear cache in app settings. Signing out clears locally stored sign-in state.

1.8 What we do not do. The Service currently does not integrate third-party advertising or user-behavior analytics SDKs such as Firebase, Umeng, Pangle, or AdMob. We do not operate a separate user account database on our own servers, and we do not upload your SMS, call logs, contacts, precise location, or camera captures (except photos you actively select for publishing) to our servers. The Service currently does not use remote push notifications as a core feature.

1.9 To meet privacy laws and app-store compliance requirements, we disclose below the categories of personal information MineBlog may involve. The purpose, method, and scope described for each category apply only to the versions or scenarios noted. Categories marked as "not collected" mean the app does not actively collect, read, or upload that type of information for the stated purpose.

2. Third-Party Services

This section describes third-party services the Service may involve. Available capabilities may vary by OS version.

2.1 Cnblogs

Core content, account authorization, publishing, comments, bookmarks, following-feed viewing, classrooms, and image hosting depend on Cnblogs websites, OAuth authorization, Open API (api.cnblogs.com), MetaWeblog API (rpc.cnblogs.com), and related services. When you sign in, publish content, or browse others' content, related information is processed by Cnblogs under its privacy policy and terms.
See the Cnblogs website and API documentation: https://www.cnblogs.com/, https://api.cnblogs.com/help

2.2 Apple Services (iOS / iPadOS / macOS / visionOS)

The Service uses Apple system UI components, Keychain, PhotosPicker, networking, local storage, and app distribution. If future versions enable push notifications, CloudKit, or other Apple capabilities, related processing will be governed by Apple's policies.
Apple privacy policy: https://www.apple.com/legal/privacy/

2.3 Operating System Capabilities

The Service mainly uses local storage, networking, WebView (for Cnblogs OAuth sign-in), and UI rendering provided by the operating system. Except for content and API requests you actively submit to Cnblogs, we do not centrally store your personal data on our own cloud servers.

3. Device Permissions

MineBlog requests permissions only when necessary for relevant features. We ask for your consent in system permission dialogs or feature guidance. Denying permission affects only the corresponding feature.

iOS / iPadOS / visionOS

Photos

Used when you choose images for status updates. Only selected photos are read; the app does not scan or upload your entire library.

Network

Used for sign-in, browsing, search, publishing, image upload, token refresh, and loading web resources.

macOS

May provide content browsing, publishing, and management capabilities corresponding to iOS / iPadOS. Photo and network permissions are used for the same purposes. Actual availability depends on your version.

You can manage permissions at any time in system Settings. Signing out, clearing cache, or uninstalling the app stops related processing and deletes locally stored cache and sign-in state (content already submitted to Cnblogs remains subject to Cnblogs' rules).

4. Managing Your Personal Information

If you have questions, comments, suggestions, or requests regarding your data subject rights, contact us as described in "How to Contact Us" below.

For information processed by Cnblogs (account profile, published content, comments, bookmarks, etc.), use Cnblogs' official channels to access, correct, or delete it. You can sign out in the app or manage account cancellation in Cnblogs account settings. You can clear local cache in app settings and remove local tokens, drafts, and cache by uninstalling the app.

5. Storage Location and Retention

5.1 OAuth tokens, MetaWeblog tokens, interface preferences, drafts, and content cache are mainly stored on your device. We currently do not provide cloud account sync operated on our own servers.

5.2 Content, comments, bookmarks, and account information you submit to Cnblogs through the app are stored and processed by Cnblogs on its infrastructure, which may involve servers outside your country or region.

5.3 Local cache is kept for a reasonable period needed for faster display and can be cleared in settings. Signing out clears local sign-in credentials; content already published on Cnblogs is not automatically deleted.

5.4 Unless otherwise required by law, we retain local information only for the shortest period necessary for the processing purpose. Uninstalling the app usually deletes local tokens, cache, and drafts.

6. Protection of Minors

If you are a minor, please read this Policy and use the Service with guardian guidance and consent before signing in to Cnblogs or publishing content. Cnblogs account registration and use must also comply with applicable laws and Cnblogs rules for minors.

7. How to Contact Us

You may contact us using the information below to exercise your rights. We will respond as soon as reasonably possible.

Email: weigantechnology@outlook.com

If you are not satisfied with our response, especially where personal information processing has harmed your lawful rights, you may seek resolution through a court with jurisdiction, industry self-regulatory organizations, or relevant government authorities. You may also ask us about other complaint channels that may apply.

Effective date: 2026.9.4