Proment — Privacy Policy

There is no company, organisation, studio or registered entity behind Proment. Lucanise is the name this site is published under. Proment is a hobby project, built and maintained part-time by a solo developer in Belgium, publishing under the name Lucanise.

Contact: mail.lucanise@gmail.com

Proment runs entirely inside your own Atlassian tenant, on Atlassian infrastructure. There is no vendor server, vendor database or vendor infrastructure.

Your app data does not reach the developer. There is no analytics, telemetry, usage tracking or outbound network call made by Proment.

Everything is stored inside your own Atlassian tenant. Its location is the location of your Atlassian site, governed by your own data-residency settings with Atlassian and changed by you through Atlassian, never by the developer.

There is no second copy in any country, because there is no vendor infrastructure for one to sit on.

In Confluence, Proment uses ordinary pages in the space a user chooses. In Forge storage, it keeps the structure around those pages: status, priority, type, dates, owner, participants, followers, summary, next action, timeline entries, and the organisations and contacts that topics concern.

Proment never edits, moves or deletes a page it did not create. This is enforced in code, not merely promised. Existing pages retain Confluence's history, export and backups, and nothing about them changes when Proment is installed.

Topics created by Proment are ordinary Confluence pages in your own spaces and remain if the app is removed.

The developer does not receive or access the information stored by Proment. There is no console, export tool or support path into your tenant.

Atlassian is your platform provider under your own agreement. Proment has no additional sub-processors.

If you send an email, its contents arrive in an ordinary mailbox. Send as little as possible. Do not include personal information, page contents, customer correspondence or contact lists when a plain description is enough.

Anything sent by email leaves your tenant because you chose to send it. It is kept only for as long as answering requires.

Proment does not store a copy outside your tenant, collect analytics or telemetry, send crash reports, or make outbound network calls.

A user who acts on a topic is represented by an Atlassian account identifier. Proment does not create a vendor-side list of users, names, email addresses, customers or installations.

What Proment adds around pages — statuses, timelines, stakeholders and configuration — exists only inside your Atlassian tenant, in one copy, with no vendor-side restore path because there is no vendor side.

Keep anything important in your own records and back it up. Do not let Proment be the only place something exists. A CSV export is available as a practical export, not as a backup service.

Proment adds no permission model of its own. It asks Confluence what a person may see and shows that. Your Confluence space permissions remain the boundary.

You are responsible for what you enter, whether you are entitled to enter it, and the permissions and backups you maintain. Anyone who can open the app can change its shared configuration. Everyone who uses it can see the list of organisation names, though not their contacts or notes.

Topic pages can be read and edited in Confluence. A CSV export is available. Because the developer holds nothing and has no access, requests concerning app data must be handled inside your own Atlassian environment.

This policy is updated when Proment's behaviour changes. The app holds no contact list and sends no policy notifications. This page is the record.

mail.lucanise@gmail.com