Git TipsContact

Legal Notice and Terms of Use

Important information about using AccessHub and Git operations

Overview

AccessHub is a Git repository management tool designed to help teams efficiently manage member access across multiple repositories. By using this service, you acknowledge and agree to the following terms and conditions.

⚠️ Warning about Git Operations

AccessHub performs direct Git operations on your repositories including adding, removing, and modifying user permissions. These operations are irreversible and can have significant impact on your repository access control.

  • It is recommended to make daily backups of all your repositories to avoid configuration and data loss
  • Test with a single repository before applying changes to multiple repositories
  • Verify user lists and permissions before confirming batch operations

Data Handling and Privacy

Your privacy and data security are important to us:

  • We do not touch repository contents - all operations work on your machine
  • We have no access to your API keys - they remain secure on your device
  • We store limited data about which activities were performed for convenient history
  • Session data is cleared when you close the application
  • All operations are logged locally for security and debugging purposes

Service Limitations

Please be aware of the following limitations:

  • Operations depend on your API token permissions and rate limits
  • Bulk operations may take time and could timeout on large datasets
  • Some Git platforms may have restrictions on API operations
  • Service availability depends on third-party Git platform APIs
  • Historical data accuracy depends on platform API responses

Free Actions and Pro Access

AccessHub is free to browse and scan. Adding, removing, moving or changing the role of a member uses one free action, and every git account gets its own set of them. When they run out, a Pro pass unlocks 30 days of unlimited member actions for 0.99 EUR.

  • A Pro pass is a one-time purchase, not a subscription, and nothing renews automatically.
  • Free actions and Pro access belong to one git account, identified by the provider and the account id we read from your token.
  • If you use a different account, that account has its own free actions and needs its own pass. This is true even on the same platform, for example two separate GitHub logins.
  • Two keys for the same account share one pass, because the pass belongs to the account and not to the key.
  • Buying again at any time adds another 30 days on top of any time remaining, so nothing is lost.

Limitation of Liability

AccessHub is provided 'as is' without warranty of any kind. Users are responsible for:

  • Verifying the accuracy of all operations before execution
  • Understanding the impact of permission changes on their teams
  • Maintaining proper backups of repository configurations
  • Testing operations in non-production environments first
  • Understanding their organization's access control policies

Terms Updates

These terms may be updated periodically. Continued use of AccessHub constitutes acceptance of any updates. Last updated: 2025.