Myworkingmemory LLC · Metadata Cleaner for Confluence

Privacy Policy

Effective and last updated: October 21, 2026

This Privacy Policy explains how Myworkingmemory LLC (“Company,” “we,” “us,” or “our”) handles information for Metadata Cleaner for Confluence, its support and the related pages linking here (the “Services”). Separate Apple, Microsoft 365, hosted-web and ChatGPT editions have their own product notices.

1. Product facts

You choose a PDF or Word .docx attachment on a Confluence Cloud page. The app reads that attachment through Confluence and processes it in Atlassian Forge. It returns inspection findings. When you choose Save cleaned copy to this page, the app creates a new cleaned attachment on the same Confluence page. After a confirmed save, choose Open page attachments to review the copy or use Confluence’s download controls. Processing is not solely on your computer. The original attachment stays unchanged.

The app does not send documents to an outside document-processing service or AI/model provider. It is not anonymization or visible-content redaction. Visible content, form answers and embedded images can remain, and metadata inside images is not inspected.

2. Information the app handles

Account, license and attachment context

To operate the app, we handle Atlassian account and installation context, app license state, page and attachment identifiers, and the attachment’s filename, media type, size and version. The app requests the selected attachment as the current user and uses Forge-provided context to verify access. Saving a cleaned copy also requires permission to add attachments to that page.

Documents and results

The selected document and its supported metadata are read in memory during processing. Inspection returns generic categories and preservation notes rather than extracted author names, comments or other private metadata values. For Save cleaned copy to this page, the app sends the output to Confluence as a new attachment, checks the saved file and returns its attachment details. The save response does not include the document bytes.

A signed inspection token links a later cleaning request to the same account, installation, attachment version and file checksum. It includes service identifiers and timestamps, expires after ten minutes, and is held in the app’s browser memory. It is not a stored document copy.

Usage records

To enforce allowances and prevent a repeated request from being processed twice, the app stores a UTC calendar month, request category, revision counter, used count and keyed request hashes in Forge SQL. The hashes are derived from service, account, operation and request identifiers. We do not describe them as anonymous.

This usage table does not store document bytes, filenames, raw account or attachment identifiers, extracted metadata values, inspection reports or cleaned copies. When you choose Save cleaned copy to this page, the app writes the cleaned file to Confluence. It does not save document bytes or cleaned copies in a separate Company file-storage service.

Marketplace records

Atlassian handles the Marketplace purchase and billing interface. We do not collect payment-card details in the app. Where Atlassian makes purchase, evaluation, subscription, license or customer-contact records available to us, we use those records to administer access, support customers and maintain business records. The app’s narrow usage database does not describe all records in the Marketplace seller account.

Support and website requests

If you contact us, we receive your email address, message and anything you send. Please do not send sensitive documents. Remove confidential information from screenshots and use a synthetic example where possible.

Requests to these public pages are handled by our website host, Vercel, and network providers. They may process connection information such as an IP address, requested address, time and browser information to deliver and operate the website. These static pages contain no advertising, analytics script or tracking cookie code.

3. How we use information

We use the information described above to perform the requested inspection and cleaning, verify access, enforce allowances, maintain security and reliability, answer support requests, maintain business records, comply with law, and establish or defend legal claims. We do not use document contents for advertising, product analytics, artificial-intelligence training or product development.

4. Providers and disclosures

Atlassian Confluence, Forge and Forge SQL handle attachment access, requested new attachments, app execution, licensing context and app usage records. Atlassian also operates its own account, Marketplace and infrastructure systems. Vercel hosts the related public website pages. Our email and network providers deliver support communications and requests.

We disclose information only as reasonably necessary to operate these Services through those providers; comply with valid process; protect rights or safety; investigate abuse; establish or defend claims; or carry out a financing, reorganization, merger, acquisition or sale subject to appropriate protections.

A copy saved to a Confluence page is available to people with access to that page and remains subject to the site’s permissions and retention settings. Copies you download, upload or share afterward are under your control. Confluence, your device, email, a file provider or another destination may retain copies according to your settings and that provider’s practices.

5. Sale, targeted advertising and tracking

We do not sell personal information, use targeted advertising, share information for cross-context behavioral advertising, or track you across other companies’ apps or websites. The app contains no advertising or tracking code.

6. Retention

The app processes document contents and outputs in invocation memory. It does not save them in its usage database. Copies you request with Save cleaned copy to this page are stored as Confluence attachments and are not automatically deleted by the app. This is not a promise of secure erasure of runtime memory or deletion of copies you have downloaded.

Daily maintenance attempts to delete usage records older than the immediately preceding UTC calendar month. The intended allowance-record window is the current and previous month while maintenance succeeds. Platform logs, backups and post-uninstall retention are separate from this app-level cleanup; we do not promise a fixed platform deletion time.

We retain Marketplace and support records as reasonably needed to administer access, respond, maintain business records, resolve disputes and meet legal obligations. We do not promise a specific retention period for provider infrastructure logs. Original Confluence attachments and saved copies are not deleted by this app.

7. Security and locations

App controls include current-user attachment access, server-side license and context checks, signed short-lived inspection authorization, processing limits, separate output files and output verification. No storage or transmission method is completely secure. Keep independent backups and review each cleaned copy before sharing.

Processing uses Atlassian infrastructure; the related website and support also use their service providers. Processing locations depend on the applicable services and configurations. We do not promise a particular region or geographic confinement. Where required, we use transfer and contractual safeguards appropriate to the information and provider relationship.

8. Your choices and requests

You choose the attachment, whether to inspect or clean it, whether to approve described content changes, and where to save or share the output. Your Confluence administrator manages installation and app access. Subscription changes should be handled through the applicable Atlassian billing interface; do not rely on simply stopping use to change billing.

Depending on your location and applicable law, you may request access, correction, deletion or a copy of covered personal information, object to or restrict certain processing, or appeal a denied request. We do not discriminate for exercising applicable rights. Email dean@myworkingmemory.ai. We may need to verify the request.

We do not sell personal information or use targeted advertising, so there is no sale or targeted-advertising opt-out to exercise. Authorized agents may submit requests where applicable law permits. We will explain any lawful denial and available appeal process.

9. Children

The Services are general-audience business tools and are not directed to children under 13. We do not knowingly collect personal information from a child under 13. If you believe a child supplied personal information through the Services, contact us so we can evaluate and delete it as required.

10. Changes

We may update this Policy when the product, providers, law or practices change. We will change the date above and provide any notice or renewed acknowledgement required by law.

11. Contact

Privacy questions, requests or complaints: Myworkingmemory LLC, 1515 Demonbreun St. 1121, Nashville, TN 37203, United States; dean@myworkingmemory.ai.