Terms

FolioCradle apps are licensed under the Bonterms Standard End User Agreement as adopted by the Atlassian Marketplace, together with the Provider-Specific Terms below.

We use the standard agreement deliberately rather than writing our own. It is a published, professionally drafted contract that many vendors and buyers already use, so your legal team can review it once instead of reading bespoke terms from every small vendor. Where we add anything, it appears below and nowhere else.

Provider-Specific Terms

These are the only additions to the standard agreement. There are no modifications to it — no altered warranty, liability, indemnity or termination provisions. What the standard agreement says on those subjects is what applies.

1. Provider

FolioCradle, operated by James Graham, a sole proprietor in California, USA.

2. Notices and contact

Notices, support requests and legal correspondence: support@foliocradle.com.

3. Support

Support is provided by email on a reasonable-efforts basis during normal business days. Replies typically arrive within one business day. This is a description of how we work, not a service level commitment, and no uptime or response-time guarantee is offered — the apps run on infrastructure operated by Atlassian, whose availability we do not control.

Reports that an app changed pages unexpectedly are prioritised above all other correspondence. See the support page.

4. Your content

You retain all rights to your content. We claim none. Our apps run inside Atlassian's infrastructure and transmit no customer content to us. Optional AI features send text to a language model Atlassian operates within that same infrastructure; nothing is transmitted to us or to any party outside Atlassian — see the privacy policy, and section 4 of it in particular, which forms part of these Provider-Specific Terms.

5. Bulk changes are consequential

These apps change your content when you instruct them to, across many pages at once. Every run shows a dry-run preview before anything is written, and you decide what to apply. You are responsible for reviewing that preview, for the scope you select, and for having the right to modify the content in question. Most edits create an ordinary Confluence page version, so the page body and title can be reverted through page history. Two kinds are not part of a page version at all: a page LABEL and a COMMENT. Reverting a page brings its body and title back and leaves any label this run added or removed, and any comment it rewrote, exactly as the run left them — and a page whose only change was a label or a comment gets no new page-history entry to revert at all. Those are put back by the app's own Undo instead — labels from the record the run keeps, comments from each comment’s own version history.

6. Platform limits affect what a run can do

Our apps run on Atlassian Forge and are subject to Atlassian's platform quotas, invocation time limits and API rate limits. These are set by Atlassian, not by us, and they can change. They have practical consequences you should know about before starting a large run:

• A run is capped at 250,000 pages, which stops discovery rather than trimming results — pages beyond it are not examined. A larger scope is reported as capped — never silently trimmed.
• Small runs finish immediately. Larger ones continue in the background and may take considerably longer, because the platform limits how much work an app may do in one invocation.
• Pages in a knowledge base space where the app could not establish that it can read them, and pages in a space whose type could not be established, are processed in your browser tab, which must stay open until that part of the run finishes. The app tells you when this applies and when it is safe to close the tab.
• Atlassian rate limits, timeouts or platform incidents can cause a run to stop before it finishes. If that happens, the app reports how many pages it reached and anything already written stays written. Page bodies and titles remain revertible through Confluence page history; LABEL and COMMENT changes are not part of a page version, so reverting a page leaves those as the run left them, and the app’s own Undo is what puts them back. Section 5 sets this out in full.

We do not warrant that a run of any particular size will complete within any particular time, because the limits that govern it are not ours to control.

7. Order of precedence

As set out in the standard agreement: any Amendment, then these Provider-Specific Terms, then the Standard Agreement.