This policy describes the data processed by the Miksumia Publisher application (“the application”), published by Miksumia SARL (“we”), and how it is used, retained and deleted.
The application is an Atlassian Forge application installed by an administrator on a Confluence Cloud site. It reads files in Google Drive and publishes their content as Confluence pages.
MIKSUMIA, société à responsabilité limitée (limited liability company), SIREN 919 860 452, whose registered office is at 70 boulevard Desgranges, 92330 Sceaux, France.
For any question about this policy or about exercising your rights: contact@miksumia.com.
For the content of the documents published through the application, the customer is the data controller and MIKSUMIA the processor (terms of use, Provider-Specific Term 5). MIKSUMIA is the controller for the connection data described below: Google tokens and the email address of the connected account.
The application requests three Google permissions, and only these:
https://www.googleapis.com/auth/drive.readonly — read-only
access to Google Drive. The application can neither create, nor
modify, nor delete a file in Google Drive.
openid — technical OpenID Connect sign-in scope, required by
Google to provide the email address below. It grants access to no
content, and the account identifier it provides is neither read nor retained
by the application.
https://www.googleapis.com/auth/userinfo.email — the email
address of the connected account, in order to display it to the administrator. It is
kept in the encrypted secrets storage of Atlassian Forge, next to the tokens, so the
administrator still sees which account is connected when Google is briefly unreachable.
It is deleted when the Google account is disconnected, or when Google reports the
authorisation as withdrawn.
| Data | Why it is needed |
|---|---|
| File and folder metadata: identifier, name, type, modification date, parent folder | Rebuild the folder tree in Confluence and determine which documents have changed since the last synchronisation |
| Content of the files in the connected folders | Convert each document into a Confluence page |
| Google Drive change notifications | Trigger a synchronisation when a document is modified |
| Email address of the connected Google account | Show the administrator which account the connection uses |
Only the folders explicitly connected by a Confluence administrator are read. The rest of the connected account's Drive is never browsed.
Miksumia Publisher's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
In particular, we use this data only to provide and improve the user-facing features described above; we do not transfer it to third parties, except to provide these features, to comply with a legal obligation, or as part of a merger or an acquisition; we do not use it for advertising purposes; and no human reads it, except with your explicit consent for a support need, for security reasons, or where the law requires it.
Data obtained from Google APIs is not used to train generalised artificial intelligence models.
The application runs entirely on the Atlassian Forge platform. Processing and storage take place within Atlassian's infrastructure; we operate no server of our own and hold no copy of your documents outside this platform.
Once published in Confluence, the content resides in your own Confluence space and is subject to your organisation's retention policy, as well as to Atlassian's terms.
The application has no server of its own: all processing and all storage are hosted by Atlassian. The only data that leaves this infrastructure is the data listed below.
Two processes, and only two, send content belonging to you to the Google Gemini API. Both depend on a choice made by an administrator: AI reading is requested document by document; translation, once a language has been chosen for a folder, applies to every synchronisation of that folder.
These APIs receive the access token and the identifiers of the folders and files you have connected, and return the metadata and the content to convert. The Sheets API is used in addition to the Drive API because only it reveals the hidden ranges of a spreadsheet — and therefore makes it possible not to publish data you had chosen to hide.
The authentication service receives the authorisation code or the refresh token, as well as the application's credentials. No data belonging to you passes through it. On disconnection, the application calls token revocation with Google and deletes the token from its encrypted storage, whether or not Google responds.
To be informed that a document has changed, the application registers with Google a notification address and a verification token that it generated itself. No content passes through them.
These services are used under their paid offerings, whose terms exclude the use of transmitted data for training models.
Processing is based on the performance of the service requested by your organisation: publishing in Confluence documents that you have explicitly designated to us. No data is used for advertising, profiling or resale purposes.
In accordance with the General Data Protection Regulation (GDPR), you have a right of access, rectification, erasure, restriction and objection regarding data concerning you. Send your request to contact@miksumia.com: the application offers no self-service export, and we respond within 30 days. You may also lodge a complaint with the CNIL.
Any substantial change to this policy will be published on this page, with an updated version date. We inform the administrators of the sites where the application is installed when the change affects the data processed.