Bitbucket vs GitLab

Subscriptions renew automatically at the then-current rate unless notice of non-renewal is given before the term ends. Users should plan cancellation in advance to avoid unexpected charges.

Atlassian can limit access, remove data, or suspend accounts if it believes data or usage violates the rules or threatens security or operations, or if legally required. This gives the provider substantial discretion over service continuity.

Most claims are capped at fees paid in the prior 12 months, and many damages like lost data or lost profits are waived. This can leave users with limited recovery if something goes wrong.

Atlassian promises to defend and indemnify customers against third-party claims that authorized use of the product infringes IP rights. That is a substantial protection for business customers relying on the platform.

Most fees and expenses are non-refundable, so ending service early usually does not mean getting money back. The main exception is the 30-day initial return policy for products.

Atlassian may modify the agreement by posting updates, with changes often taking effect at renewal and sometimes mid-term. If you object, your main remedy may be to terminate the affected subscription.

The documentation is supposed to explain how customers can retrieve their data from the cloud products. That is helpful for migration planning and exit preparation.

After the agreement ends, Atlassian says it will delete customer data according to the documentation unless law prevents it. That is a meaningful exit-right, though the exact timing and method depend on the docs.

The service is licensed for internal business use, not as a general-purpose consumer tool. That means your use is limited to the organization’s scope and the contract’s usage rules.

If you enable third-party products, those providers may access your data and their own terms apply. This can expand data sharing beyond Atlassian itself.

If an employer or organization provides the account, that organization controls the personal information and manages the account. Individual users may need to go through that organization for privacy requests.

GitLab collects account, profile, payment, support, content, device, usage, cookie, email, and integration data, plus data from vendors and connected apps. For a user, that means a fairly deep data footprint across the service and related tools.

The privacy policy says GitLab uses cookies and similar technologies for interest-based advertising and session replay on its websites. That creates tracking beyond basic service functionality.

When using GitLab Duo and other AI features, your code, prompts, and context may be transmitted to third-party AI providers. GitLab says it will not train models on your inputs without consent, but your data still leaves GitLab for processing.

GitLab keeps personal data while your account is active or as needed for contracts, legal obligations, disputes, and security, and it may retain some community content indefinitely. Public posts and open-source contributions may remain visible even after account deletion.

You can access, correct, restrict, delete, and port your personal data, and GitLab says these rights are free of charge. That gives users meaningful control, though some requests can still be denied.

GitLab provides an in-app Delete Account option for SaaS accounts and a separate privacy request for broader deletion. This is helpful because it gives users a concrete path to remove data, at least outside paid-enterprise constraints.

If your account is tied to a paid namespace or enterprise, GitLab says the enterprise controller must approve your request before it can act. That can block or slow deletion and other data rights for workplace accounts.

You can port projects using export functionality that includes metadata, or by cloning repositories, and profile information can be exported via API. That makes switching services or backing up data easier.

GitLab publishes a detailed agreement history with dated prior versions of its policies and contracts. This helps users and enterprise customers figure out which version applies to their use or purchase date.

GitLab says it may change its Privacy Statement and will update the date, with notice for significant changes. That is normal, but it means the privacy rules are not fixed.