Confluence to SharePoint processes the Confluence page open in Chrome and creates a native unpublished page in the SharePoint site selected by the user, or saves it into an existing page of that site the user chooses, as an unpublished draft of that page. It has no developer-operated server, analytics, advertising, or telemetry.
The extension uses this data only to perform the transfer requested by the user. The developer does not sell or transfer it to third parties, use it for advertising, or use it to determine creditworthiness or lending eligibility. The SharePoint copy is delivered only to the destination site the user selects.
Data processed
During capture, the extension reads the open Confluence page's title, author, update date, supported text and layout, links, and pictures. The author is read as Confluence gives it: their name and, where Confluence shows it, their e-mail address. When a send gives the SharePoint page the Confluence page's title and byline (a new draft, or an overwrite or update of a page that took them), the extension asks the selected SharePoint site for its users with that name or e-mail address, and names the one that matches in the page's byline, or else the signed-in user. A Confluence live doc, or a page open in Confluence's editor (including a draft never published), has no reading view, so its content is read from the page's stored document: for a page in the editor, the draft Confluence saves while the editor is open. Pictures and files are identified in the attachment lists of the page, or of another page on the same Confluence site whose files it shows, when Confluence has not finished describing them on screen or the page is a live doc or open in the editor. When a capture is sent, the extension reads the selected SharePoint site's metadata and the responses needed to verify the new draft, or the page it saves into, and its uploaded pictures. A send into an existing page also reads that page's content, title, byline and version state, and whether someone is editing it or has it checked out, so that it stops rather than writes over their work.
On Confluence Cloud pages, a content script checks the page's Confluence markup and address and adds the SharePoint button beside Share on document pages. Opening the popup over a Confluence page inspects that tab: it recognizes Confluence from the page's own markup and reads the page's title and page type from that same site with the existing signed-in session. Full page capture begins only when the user selects Capture page, or Update for a page sent before, or Update selected in the dashboard, which opens each selected Confluence page in a background tab and captures it there. When the user sends a capture, the extension opens the chosen SharePoint site in a background tab and reads the site's address, name, and Site Pages library settings and permissions there before creating the draft.
Remembered SharePoint sites and pages. When the user opens a SharePoint Online page (not a personal OneDrive or the SharePoint admin center), a content script reads that site's address and name from the page itself and, for a page of the site's Site Pages library other than its home page, the page's address and title. When SharePoint has moved to another page without reloading, so the page no longer names the site its address belongs to, the script asks that same SharePoint site for its address and name instead, with read requests made under the user's own sign-in (the page's address first, then its parent sites). The extension also remembers the pages it creates or sends into, and which Confluence page it sent to which of them (the Confluence site's address and the page's number, the permanent ID SharePoint gives the page, and the identities SharePoint gives the parts of the page the send wrote), so the user can update the SharePoint page from its Confluence page later, also after the page was renamed or moved within its Site Pages. It keeps them in Chrome's extension storage on this computer so the user can send pages there. They are not sent anywhere, with two exceptions: the record of which Confluence page was sent where is also kept in the user's Confluence account if the user turns on Keep in my Confluence account, and the pinned sites are kept in Chrome's synced storage (see Chrome sync). The user can remove them, one at a time or all at once, in the popup's Sites view (removing a site or page also forgets what was sent to it); uninstalling the extension deletes them.
Keep in my Confluence account. This setting, in the popup's Sites view, is off until the user turns it on. While it is on, the record of which Confluence page was sent to which SharePoint page (as described under Storage and retention) is also saved, with the user's existing sign-in, as private user properties of the user's own account on the Confluence Cloud sites the user sends pages from. To address them, the extension asks that Confluence site which account is signed in (its account ID), and does not store the answer. Atlassian documents that user properties can be read only by the account or app that created them. The extension reads them back, on any computer where the setting is on, to show the SharePoint pages a Confluence page was sent to, with Update; on a Confluence site where the account holds nothing of the extension and the user sent nothing from, nothing is written. The account copy holds what every computer with the setting on sent. Removing a site or page in the Sites view removes it there too: a dated mark of the removal (the SharePoint site's address and, for a page, its address and permanent ID, and for each sent link it takes, the Confluence page's number) is kept in the account on the Confluence sites this browser has sent pages from or found the extension's data on, so that older copies from other computers stay out; a page an update found deleted, and a link an overwrite replaced or an update found gone, are marked the same way. Turning the setting off turns it off on the user's other Chrome browsers with Chrome sync on (see Chrome sync), deletes the copy from the account on the Confluence sites this browser used, and leaves there a small note that it was turned off, with the time: a computer where the setting is still on, without Chrome sync, reads the note the next time it saves or reads there and turns the setting off as well; turning the setting on again deletes the note on the Confluence sites that browser has sent pages from or found the extension's data on. A removal that could not be made at once (for instance while signed out) is made later only in an account that holds one of the entries this browser put there, or the note of the same turning off left by another of the user's computers; otherwise nothing is removed there and the popup says so. A removal for a Confluence site that is gone is dropped, as nothing is left there. One that has failed for two weeks, over at least ten tries (for instance while signed out, or while the site does not answer), is given up, and the popup says so. Forget all clears this browser's lists, unpins the synced pins and turns the setting off. Uninstalling the extension does not remove the copy from the account; turning the setting off first does. Nothing of it is sent to the developer or to any server other than that Confluence site; only the setting itself follows Chrome sync (see Chrome sync).
Chrome sync. The Keep in my Confluence account setting (on or off, and when it was chosen) and the pinned SharePoint sites (their address and name, whether pinned, and when) are kept in Chrome's synced extension storage. When the user is signed in to Chrome with sync on, Chrome syncs them through the user's Google account to the user's other Chrome browsers, so a pin, an unpin, or turning the setting on or off in one applies in all of them; with Chrome sync off they stay in this browser. The extension itself sends them nowhere. Up to 29 pinned sites and the 50 most recent unpinned ones are kept there: a site the user unpins, removes or forgets stays there, marked unpinned, among those 50, so the user's other browsers unpin it too.
The extension uses the existing signed-in browser sessions for Atlassian and SharePoint. It does not extract, copy, log, or persist browser cookies, access tokens, or passwords. It obtains a SharePoint request digest for authorized same-site writes, uses it in memory, and does not log or persist it. It reads the signed-in Confluence account's ID, to address that account's own user properties, and the signed-in SharePoint user's login name, to tell whether a page is checked out to them and to scope a verified picture-upload fallback to that account, and, when the Confluence author has no single matching account on the site, that user's name, e-mail address and sign-in name, to name them in the page's byline; it keeps these only in memory, apart from that byline.
For the current browser session, the extension may remember a verified picture-upload fallback together with the SharePoint site's address, asset library identity, import folder, signed-in SharePoint login name and verification time. The hint is used for at most 30 minutes after verification; reuse does not extend that period. This information stays in the extension's session memory, is not synced or sent to another service, and is cleared when the browser restarts or the extension is reloaded, updated or uninstalled.
Storage and retention
The captured model and verified picture bytes are stored in extension-owned browser storage for the current Chrome session. Clear in the popup deletes that local capture. A later browser session discards any prior capture record that is no longer accessible to the session, when the browser starts.
Remembered SharePoint sites (address, name, when the site was last visited or used, whether it is pinned, the reason a site could not take a draft, and up to 10 of its pages, each with its address, title and when it was last visited or sent to) are kept in the extension's local storage on this computer, where only the extension reads them (with, while a capture or send runs, a note of the site and page it writes and of the browser tab it uses, removed when it ends, and, for the Chrome session, the tab a send that stopped before writing left open), at most 30 sites, until the user removes them or uninstalls the extension. So is the record of which Confluence page was sent to which SharePoint page (the Confluence site's address and page number, the SharePoint site, page address, title and permanent ID, the identities of the parts of the page the send wrote and of the parts this Confluence page's earlier sends to it wrote, how many parts each send wrote, whether the page takes its title from the Confluence page and whether the part starts with its heading, when it was sent, its locally captured source version and edit date or an unknown-update marker (these local fields are excluded from the account copy), and when the page was last found at a new address), at most 2,000 records within 4 MB, the earlier sends' identities and then the oldest records dropped first, until the user removes that SharePoint page or its site in the popup's Sites view, selects Forget all, or uninstalls the extension. With Keep in my Confluence account on, the extension also keeps whether the setting is on, the addresses of the Confluence sites holding the account copy (kept while the setting is off too, and after Forget all, until a removal there is given up or the extension is uninstalled), the last message about the account and the site it concerns, which records did not fit, and the changes still to be saved there.
With Keep in my Confluence account on, the same record is also kept as user properties of the user's Confluence account, with the marks of removals made in the Sites view or by the extension (the most recent ones that fit), in at most 33 properties of at most 32 KB each (a link that does not fit stays in the browsers that sent it), until the user turns the setting off or selects Forget all; after that, on the Confluence sites this browser has sent pages from or found the extension's data on, one small property notes that it was turned off, until the setting is turned on again from a browser that has used the site.
A send writes picture files to the selected site's Site Assets library and either creates one new unpublished page in its Site Pages library or saves an unpublished draft of the existing page the user chose, whose earlier version stays in the page's version history. Those SharePoint files remain until a SharePoint user deletes them. Clear does not delete SharePoint content because a stopped send may already have produced a draft or files that require review.
Network access
The dashboard reads this browser's tracked links when opened. Requested Refresh reads source titles, versions and edit dates, opens one inactive SharePoint library tab per site and checks tracked destinations using only extension-originated GET requests, without checkout, saving or check-in. SharePoint’s own library frontend can make POST requests that read library data. It closes successful check tabs. A sign-in, access-denied or redirected tab remains available, with one retained check tab per site and browser context reused on later Refresh checks. Confirmed renames update local tracking, remove the old offered address and mark the site as visited. With Keep in my Confluence account on, Refresh reads saved-history buckets on known or open Confluence sites and may save pending history changes or repair history records through the existing account-copy operation. Selected updates capture only selected sources and update drafts one at a time; rendering-dependent capture losses pause before writing; permanent conversion limitations produce draft updates with notes and an unknown source-update status.
Fetched source labels, versions and edit dates, destination check results and times, selected-batch link references, progress, draft URLs, errors, notes and retained inspection-tab IDs, browser context and last-access times are kept in trusted extension session storage. They expire with the browser session or an extension reload/update; Forget all removes the fetched source details, check results and batch results sooner; they contain no captured document bodies, picture bytes or authentication secrets. A verified reading-view send remembers its captured source version and edit date locally for comparisons, alongside an incomplete marker when content was omitted. An editor capture or uncertain send keeps a local unknown-update marker. Neither the revision nor either marker is copied to Confluence account history. The existing transfer store still holds only the current capture. The dashboard adds no telemetry or third-party service, and starts no scheduled scans or automatic writes.
Network requests go to the signed-in Atlassian and SharePoint sites, and to another website only for a picture a Confluence page shows from it. With Keep in my Confluence account on, the extension also reads and writes its user properties on the Confluence Cloud site, with the user's sign-in. Pictures are downloaded through Confluence's original-attachment link, which forwards to Atlassian's media service (api.media.atlassian.com) with a signed address; the user's session cookies are sent only to the Confluence site itself. When that download fails, the copy of the picture Confluence shows on the page, from Atlassian's media-cdn.atlassian.com, is used instead, after its address is checked. A picture a Confluence page shows from another website, rather than as an attachment, is requested from that website so it can be copied into SharePoint. The request sends no cookies and no page address; as with any cross-site request, the browser tells that website the address of the Confluence site (not the page). The picture is copied only if the website allows the Confluence site to read it; otherwise it becomes a link to it. External smart-link favicons are neither contacted nor copied. Remembering a SharePoint page makes no network request beyond those reads of the site's address described above. The extension does not send captured content or remembered sites to the developer or any analytics service.
SharePoint publishing
The extension saves only unpublished minor drafts, of a new page or of the page the user chose, and opens the page for review. It has no Publish, Submit for approval, Schedule, or Promote operation. Publishing remains an explicit SharePoint user action.
Permissions
scriptingrecognizes a Confluence page in the tab the popup opens over, reads supported page content from it, and performs signed-in SharePoint requests in the site tab a send opens. When the extension is installed or updated, or site access is granted, it also adds its content scripts to the Confluence and SharePoint pages already open, so the button and the site memory work there without a reload. The dashboard's Refresh reads each SharePoint site's tracked pages from a background tab of that site, and Update selected captures each selected Confluence page in a background tab.storageholds the session-bound capture, picture bytes, progress, and safe recovery state, the remembered SharePoint sites and pages, which Confluence page was sent to which SharePoint page, and, with Keep in my Confluence account on, the changes still to be saved to the account, and, for the browser session, the dashboard's Refresh and update results and verified picture-upload fallback hints. It also keeps the Keep in my Confluence account setting and the pinned sites (address, name, pinned or not, and when) in Chrome's synced storage, so they follow the user's Chrome sync.- The extension reads the addresses of open SharePoint Online and Confluence Cloud tabs, which the host permissions allow, and keeps nothing of them: the popup, to offer the sites and pages open there under Send to; a send, to stop while the page is open in SharePoint's editor in this browser and to show the page afterwards in a tab already open on it; the dashboard's Refresh, to include the Confluence sites open in a tab when it reads the saved history in the user's account.
- Host permissions are restricted to
*.atlassian.netand*.sharepoint.com. With Keep in my Confluence account on,*.atlassian.netalso serves to save and read the sent list in the user's own Confluence account. The content script on SharePoint Online pages, which does not run on personal OneDrive or the admin center, only reads the site's address and name, and the page's address and title, from the page, or asks that SharePoint site for the site's address and name. - The toolbar popup, which holds the Capture and Send controls, needs no permission of its own.