This page brings together three policies: vulnerability disclosure, incident response, and information security. It describes what we actually do, at our own scale — an independent publisher releasing an application hosted entirely on the Atlassian Forge platform, with no server or infrastructure of its own.
Send any report to contact@miksumia.com. We acknowledge receipt within two business days and keep you informed of progress. Anonymous reports are accepted.
French and English are equally acceptable.
They run from the triage of the report. They comply with the Atlassian Marketplace security bug fix policy, which sets the maximum timeframes for a Cloud application.
| Severity | Target | Atlassian maximum timeframe |
|---|---|---|
| Critical | 7 days | 10 days |
| High | 4 weeks | 4 weeks |
| Medium | 12 weeks | 12 weeks |
| Low | 25 weeks | 25 weeks |
This policy covers the “Miksumia Publisher” application and the miksumia.com website. The platform on which the application runs — Atlassian — falls outside this scope: contact its programme directly.
The following are not authorised: denial-of-service testing, social engineering and physical testing.
Research conducted in accordance with this policy is considered authorised. We will not take legal action against it and we will work with you to understand and fix the problem.
This policy defines the course of action in the event of a security incident or data breach concerning the application. As MIKSUMIA is a one-person company, the managing director assumes all roles: receiving the report, investigation, remediation, communication.
Any suspected or confirmed incident must be reported without delay to contact@miksumia.com, whether the report comes from a customer, a security researcher, a third-party platform or our own monitoring.
In the event of a personal data breach likely to result in a risk to the data subjects, we notify the CNIL within 72 hours of becoming aware of the breach, in accordance with Article 33 of the GDPR. Where the risk is high, the data subjects are informed without undue delay, in accordance with Article 34. The administrators of the Confluence sites concerned are informed in all cases.
The application runs entirely within Atlassian Forge's managed sandbox. We operate no server, no database and no network of our own. The security of the hosting infrastructure is the responsibility of Atlassian; what follows describes what is our responsibility.
The application retains, per Confluence site, in the Forge storage hosted by Atlassian:
The content of documents is not retained: it is read, converted and published in Confluence. An object erased from the Forge Object Store stays restorable by Atlassian for 21 days, on a support request only.
Data is processed and stored on the Atlassian Forge infrastructure. Miksumia operates neither a server nor a database. No data leaves Atlassian; calls to Confluence go through Forge and are not an egress to the outside. For hosting (location, encryption, certifications), see Atlassian's pages: Atlassian Trust Center and Forge security.
| Subprocessor | Role |
|---|---|
| Atlassian | Application hosting and storage (Forge); Confluence |
None. The application's manifest declares no external address, and the platform enforces it at runtime: the application can reach nothing outside Atlassian. No AI service, no telemetry, no audience analytics, no external logging.
Logs contain event names, technical identifiers, counters and error codes. Error messages displayed or logged are composed by the application; text coming from an upstream service is classified, then discarded. No customer content in production logs.
Any user who may create a page in a space can publish there with the application. Before an upload starts, the application checks server-side, with the uploader's own Confluence rights, that they may create a page at the chosen place; the screen checks it too, but is never trusted alone. An uploaded file is stored under the uploader's own account and read back only for them.
The publisher's administration accounts — Atlassian developer console and code repository — are personal and protected by two-factor authentication.
No secret appears in the source code. The application holds no third-party token. Deployment secrets are kept in Forge's encrypted environment variables. No secret is logged, returned in a response, or included in an error message.
All communications use HTTPS. The authorised network destinations are declared in the application's manifest and enforced by the platform at runtime: no other destination is reachable.
Miksumia Publisher V2.7.0 was assessed by TAC Security against the CASA specification v2.1.1 at assurance level AL1 (grey-box testing, 7–23 September 2026; report issued 25 September 2026). Result: In Compliance. The assessment was carried out for Google's OAuth restricted scopes (Drive read-only).
The tests used the “App Defense Alliance ADA Burp Audit Scan Configuration” configuration. That version read Google Drive; the current version, which no longer connects to Google, has not been assessed again.
Our answers to the Cloud Security Alliance CAIQ Lite v4.1.0 questionnaire are listed on the CSA STAR registry since 6 October 2026 (STAR Level One): Miksumia Publisher for Confluence on the STAR registry. Level One is a self-assessment: the answers are ours, not checked by an auditor.
These policies are reviewed at least once a year, and with every substantial change to the application's architecture.