Effective date: The date Conf2Git first becomes publicly available through Atlassian Marketplace.
These Supplemental Terms apply to Conf2Git – Markdown Sync for Confluence, provided by Magnascale Inc., Ontario, Canada.
They supplement the applicable Atlassian Marketplace customer agreement governing the customer’s acquisition and use of Conf2Git.
Where these Supplemental Terms conflict with the applicable Atlassian Marketplace agreement, the Atlassian Marketplace agreement controls unless the applicable Marketplace listing expressly provides otherwise.
1. The service
Conf2Git is a one-way synchronization service that reads customer-selected Confluence Cloud content and generates Markdown and eligible referenced images in a customer-selected GitHub repository.
The direction is:
Confluence → GitHub.
Conf2Git does not publish changes from GitHub back to Confluence.
2. Customer authorization and responsibilities
The customer is responsible for:
- having the rights and permissions necessary to process the selected Confluence content;
- authorizing installation of the Atlassian application;
- authorizing the GitHub App for the intended repositories;
- selecting an appropriate non-default GitHub branch and base path;
- maintaining appropriate Confluence and GitHub administrators;
- controlling access to the destination repository;
- reviewing product warnings, synchronization status, and generated output before downstream use; and
- maintaining any independent backup, source-retention, or continuity arrangements the customer requires.
Customers must not provide passwords, credentials, tokens, private keys, or other secrets to Magnascale through support communications.
Customers must not use Conf2Git to violate law, infringe third-party rights, bypass access controls, or intentionally distribute content to persons who are not authorized to receive it.
3. Managed GitHub content
Confluence remains authoritative for Conf2Git-managed output.
A later synchronization may replace human edits made directly to files that Conf2Git previously published and continues to identify as managed content.
Conf2Git’s ownership and provenance controls are designed to preserve files outside its managed-file boundary.
Conf2Git:
- does not write to the GitHub repository default branch;
- does not force-push; and
- does not intentionally delete files it cannot establish as Conf2Git-managed.
4. Synchronization behavior
Conf2Git is not a real-time synchronization service.
Public v1 provides manual synchronization and a fixed daily schedule. A daily schedule does not guarantee execution at an exact customer-local clock time.
Unsupported Confluence content may be represented using a safe textual representation, link, placeholder, or warning rather than silently discarded.
Conf2Git is not a complete Confluence backup, point-in-time restore, disaster-recovery, or archival product.
5. Public-v1 limits
Current public-v1 limits include:
- up to five active mappings per Confluence site;
- up to 1,000 pages per mapping and synchronization run;
- up to 1,500 generated files per run, including the Conf2Git ownership manifest;
- up to 10 MiB per individual image;
- up to 64 MiB of image data per run; and
- up to 100 MiB of total generated data per run.
Where required safety evidence is incomplete or a supported limit is exceeded, Conf2Git may fail the synchronization without publishing an incomplete or potentially destructive result.
Current product documentation should be consulted for the complete supported behavior and limits.
6. Atlassian and GitHub
Use of Conf2Git requires Atlassian Cloud and GitHub.
Those platforms are provided by third parties and remain subject to their own availability, account administration, security controls, privacy practices, and terms.
The customer’s selected GitHub repository is an intentional destination for the Confluence content the customer directs Conf2Git to publish.
Removing a Conf2Git mapping or uninstalling Conf2Git does not automatically delete previously published GitHub content or uninstall the GitHub App.
7. Evaluation, subscription, and billing
Conf2Git is offered through Atlassian Marketplace using Atlassian’s applicable evaluation, licensing, subscription, billing, renewal, cancellation, refund, and tax processes.
The application relies on Atlassian Marketplace licence state to determine whether synchronization is currently authorized.
Magnascale does not operate a separate in-app trial or promotional entitlement system for public v1.
8. Support
Support is available through:
https://magnascale.com/contact-us/
Published support-response objectives are operational targets and do not create a contractual service-level agreement unless an applicable written agreement expressly states otherwise.
Customers reporting problems should avoid sending page bodies, generated Markdown, image contents, credentials, tokens, authorization headers, or raw provider responses.
9. Privacy and data protection
Privacy information is available at:
https://magnascale.com/privacy-policy/
The Conf2Git Data Processing Addendum is available at:
https://magnascale.com/data-processing-addendum/
The privacy policy and applicable Data Processing Addendum describe the processing roles, data flow, retention, deletion, security, and international-transfer terms applicable to customer data.
10. Security
The Conf2Git Security Policy is available at:
https://magnascale.com/security/
11. Changes
Magnascale may update these Supplemental Terms to reflect product, legal, security, or operational changes.
Material changes will be dated and made available through this page and will apply in accordance with the applicable Marketplace agreement and law.