Bulk Page Cloner for Confluence

Specs & security

What Bulk Page Cloner for Confluence requires, what it can reach, and where your data goes.

v10.0.0 — Latest Runs on Atlassian Atlassian Forge Confluence Cloud
← Back to the guide Technical Specifications Privacy & Security

Technical Specifications

DetailValue
PlatformAtlassian Forge (Cloud only)
ProductConfluence Cloud
InstallationAtlassian Marketplace
LicensingFree for teams up to 10 users; paid tiers above, billed through the Atlassian Marketplace. See the pricing calculator for current rates.
Page Batch LimitUp to 25 pages per batch
Template SearchNo fixed limit — spaces and pages load via pagination
Runs on AtlassianYes — verified by Atlassian. The app runs entirely on Atlassian infrastructure with no external data egress.
Data StorageForge storage — no external servers, data stays in Atlassian cloud
ThemesLight & dark, matched to your Confluence theme
Personal dataThe app keeps no user records. Forge storage holds a short-lived page list cache and any template snapshots you save — page titles, space keys and page content. If a source page carries an @mention, that markup travels with the copy exactly as it would in any Confluence copy. No external egress is declared, so nothing reaches a DataPingo server, and uninstalling removes everything the app stored.
Current Version10.0.0
Last UpdatedJuly 2026

System Requirements

  • Active Confluence Cloud instance
  • Modern web browser (Chrome, Firefox, Safari, Edge)
  • Active internet connection
  • Appropriate Confluence permissions

Permissions Required

Six scopes, and no others:

  • read:page:confluence — read the page you pick as a source, so it can be listed, previewed and copied.
  • read:space:confluence — list the spaces you can already see, so you can choose where copies land.
  • write:page:confluence — create the new pages.
  • read:label:confluence — read the source page's labels so they carry across to every copy.
  • write:confluence-content — used by Confluence's own copy API, which duplicates attachments, macros and page properties server-side.
  • storage:app — the app's own storage on Atlassian's platform. Holds your saved template snapshots and a short-lived cache of your page list (5-minute expiry). It stays inside Atlassian — nothing is sent to DataPingo.

No admin rights needed. The app acts as you and can only ever see and create pages you already have access to. It does not request space administration or site administration permissions.

Cloud only: Bulk Page Cloner is built on Atlassian Forge and runs exclusively on Confluence Cloud. Confluence Server and Data Center are not supported.

Privacy & Security

  • Data Privacy: DataPingo Privacy Policy
  • Security: DataPingo Security Policy
  • Data Storage: All app data is stored in Atlassian Forge Storage — no data is sent to or stored on external DataPingo servers
  • Media Handling: Pages are duplicated by Confluence's own server-side copy, so attachments, labels and page properties move inside Atlassian's infrastructure — never through an external server DataPingo operates
  • Customer information: We receive customer details only through the Atlassian Marketplace. We do not sell, distribute or share that information.
  • GDPR status: Atlassian has approved our declaration that DataPingo is neither a data controller nor a data processor under the GDPR with reference to this app. Verify it yourself on the Privacy & Security tab of the Marketplace listing.
  • Compliance: Follows Atlassian security standards and the Forge platform security framework