Skip to content
gitblog beta
English
العربية Deutsch 한국어 English Español Français Italiano 日本語 Português Português (Brasil) 简体中文 繁體中文
HomeShortsLatestPopularTrendingBlogsMy library
Sign in with GitHubSign in
Home Shorts Popular My library

GitBlog Terms of Service

Version: 2026-10-21 · Effective date: 2026-10-21

These terms govern use of GitBlog between its operator and members. Read and accept them to complete registration with your GitHub account. Public articles can be read without an account.

Before you agree

  • You retain rights to your repositories and content. Publicly deployed material may be indexed by search engines and other services.
  • A gitblog.page address is a service allocation. A released address may be assigned to another member after seven days.
  • Separate terms, limits and charges may apply to GitHub, Cloudflare, translation providers and other external services.
  • Push notifications are optional. Closing your GitBlog account does not automatically delete your GitHub repositories or original posts.

1. Terms and registration

GitBlog helps create, edit and deploy GitHub-based blogs and discover public articles. Registration is completed by GitHub authentication and explicit acceptance of these terms. You may decline and cancel registration; member features require acceptance.

2. Accounts and access

Connect only GitHub accounts and repositories you are authorized to use. Meet GitHub's eligibility rules and the legal requirements to enter into a contract where you live, obtaining a legal guardian's consent where required. Protect your account, manage repository permissions and report suspected misuse. Signing in alone does not grant access to all your repositories.

3. Service features

Features include template-based blogs, content and settings editing, GitHub Actions and Pages deployment assistance, public feeds, previews, search, recommendations, subscriptions, bookmarks, comment integration, addresses and statistics. Availability depends on permissions, plan limits, templates and external services. Review automated or translated output and deployment changes before publishing, and keep appropriate backups.

4. Content rights and publication

You keep rights to your writing, images and code and must have permission to publish them. You grant the operator a non-exclusive right to collect, store, cache and display connected public content in feeds, search, previews and recommendations as needed to provide the service. Content changes, including translations, occur within features you request or configure. These terms do not transfer ownership or grant blanket consent to use content for AI training.

Public material can be read, copied and collected by others. Removing content or stopping its display here does not immediately remove external search results, caches or copies. Use for service delivery ends when use of the service ends, except for necessary technical cleanup and legally required retention.

5. Prohibited use

Do not publish illegal content, infringe copyright or privacy, impersonate others, harass, spam, distribute malware or phishing, or disclose others' credentials or secrets. Unauthorized repository access, bypassing limits or security measures, and attacks or automation that impose excessive load are prohibited.

6. Blog addresses

A gitblog.page subdomain is a conditional right of use, not a domain you own, and is subject to availability and account limits. Address deletion, account closure, repository deletion or a connection mismatch may trigger cleanup of the address and related DNS and Pages settings. Settings already changed to another domain are left intact. A released address may be reassigned after a seven-day holding period; update external links accordingly. You manage ownership, renewal and DNS for personal domains.

7. External services

GitHub repositories, Actions, Pages and Discussions, Cloudflare networking, and chosen translation or domain services have their own terms, limits and charges. GitBlog registration does not replace your agreements or account settings with them. Integrations you choose may receive content and requests needed to perform the requested work.

8. Notifications

Push about subscribed posts and service announcements is available after you enable it on a device; categories can be disabled in account settings. Accepting these terms does not grant push permission or marketing consent. Browser, OS or network conditions can delay or prevent delivery. Check service announcements for important notices too.

9. Member information

During GitHub authentication, identity and authentication information are used temporarily to process registration. After registration, the service uses your account profile, available verified email, selected subscriptions, history and notification settings, operational statistics and acceptance records to provide and operate features. Acceptance records contain your identifier, terms version, language, time and document hash. Your statutory rights to access, correct or delete personal data remain unaffected. These terms do not replace a privacy policy or other legally required notices or consents.

10. Plans and charges

Feature limits follow the account plan shown in the service. Registration currently includes no paid-plan purchase or payment. Future paid features will have separate price, payment, cancellation and refund terms and any necessary consent; acceptance of these terms alone never authorizes automatic charging. External service charges are separate.

11. Changes, interruptions and responsibility

The operator makes reasonable efforts to maintain the service and fix errors. Maintenance, security incidents and external outages may interrupt availability. Planned significant changes or closure will, where possible, be announced in advance with an opportunity to arrange your data. Search rankings, AI citations, complete crawler statistics and uninterrupted availability are not guaranteed. This does not exclude liability for intentional misconduct or gross negligence, or any liability or consumer rights that cannot lawfully be excluded.

12. Restrictions and account closure

Violations of law or these terms, or threats to service safety, may lead to proportionate restrictions on content visibility, features or accounts. Reasons and an appeal route are normally provided. Urgent protective action may precede notice, which will follow to the extent legally permitted. You may ask the operator to review the facts and decision.

You can close your account in account settings. Account information and personal preferences are cleared, and allocated addresses enter the release process. Original GitHub repositories, posts, Discussions and GitHub App installations are not automatically deleted and must be managed separately. Minimum records necessary for security, address recovery, disputes or legal duties may be kept only for the relevant purpose and necessary period. Rejoining does not restore deleted personal data.

13. Updates to these terms

Changes and effective dates are announced on the terms page and through service notices. Ordinarily, notice is given seven days before general changes and thirty days before materially adverse changes. Where law or urgent security needs make this impracticable, reasons and notice are provided as soon as possible. When a new version requires agreement, explicit acceptance is requested again. Silence is not acceptance; you may stop using member features or close your account instead.

14. Contact and disputes

Use the operator's contact route below for questions or appeals. Do not post passwords, tokens or private personal data in public inquiries. Disputes follow applicable law and procedures of courts with lawful jurisdiction. Mandatory consumer rights where you live remain unaffected. Translations aim to convey the same meaning; discrepancies will be interpreted consistently with applicable law and the purpose of these terms, and corrected.

Operator: gitblog · elixirevo

Contact: contact@elixirevo.com

gitblog Discover stories and ideas
공지 Latest Popular Trending Blogs Sitemap Terms of Service
© 2026 gitblog