Privacy Policy

Privacy Policy — Hullspark Forge Apps

Effective date: 2026-10-25 · Operator: Hullspark (sole proprietor) · Contact: support@hullspark.com

1. What this policy covers.

This policy applies to every Atlassian Forge app published by Hullspark (each an "App", together "the Apps"). At the time of writing these are Label Sweep for Confluence, Attachment Sweep for Confluence, Page Sweep for Confluence, Page Review Reminders for Confluence, Field Sweep for Jira, Cross-Space Task Report for Confluence, Sub-task Field Inheritor for Jira, Project Archiver Lite for Jira, Last Comment Column for Jira, Content Status Report for Confluence and Template Copier for Confluence. Each App runs entirely on Atlassian's Forge platform ("Runs on Atlassian"). We operate no servers of our own for any App.

2. Data the Apps process.

Each App reads and, where it changes anything at all, changes Confluence or Jira content only through Atlassian's APIs, only with the permissions of the user who started the job or scan, and only within the scope of that job or scan.

Label Sweep for Confluence lists, renames, merges and deletes labels in your Confluence Cloud site. It reads label names and the IDs, titles and space of pages and blog posts that carry those labels. It changes labels on pages and blog posts only when you start a rename, merge or delete job.

Page Sweep for Confluence adds and removes labels on many pages of your Confluence Cloud site at once. It reads the list of spaces (so you can choose one) and, for the space you choose or the descendants of a parent page you choose, the IDs and titles of pages and each page's labels. It does not read page bodies, comments or attachments, and it does not touch blog posts. A dry run only reads. The app adds or removes labels on pages only when a Confluence site administrator starts a label-change job from a dry run and confirms it, and it does so with the permissions of that administrator. To decide whether a user may apply changes, and which jobs a user may see (non-administrators see only their own), it reads that user's group memberships; the result is cached for 10 minutes.

Attachment Sweep for Confluence finds and cleans up attachments in your Confluence Cloud site. It reads attachment metadata (file name, size, media type, dates, IDs and the page or blog post each attachment belongs to). It reads page bodies only to detect whether an attachment is still referenced; page bodies are not stored. When you start a job it moves the selected attachments to Confluence's trash, from which your Confluence administrators can restore them. It never purges attachments permanently.

Page Review Reminders for Confluence lets you set a review date and a reviewer on pages in your Confluence Cloud site and reminds the reviewer when a review is due. It reads page metadata (IDs, titles, space, last-modified date and version number). It writes and reads the review policy as a content property on the page (review date, the reviewer's Atlassian account ID, review interval and status) — never the page body. It keeps an index of pages that have a policy in Forge storage (page IDs, dates and status). When a review is due or overdue it posts a footer comment on the page that @mentions the reviewer, at most one per page per 30 days; Confluence then sends its own notification email under your site's notification settings. To decide whether to show the administrator dashboard it checks whether the current user is a site administrator by reading that user's group memberships; the result is cached for 10 minutes and not stored beyond that.

Field Sweep for Jira shows Jira site administrators where each custom field is actually used. It reads custom field metadata (type, screens, contexts, last-value-change date); the JQL text and owner of saved filters, including filters owned by users other than the administrator running the scan; board configuration (filter, quick filters, estimation field, rank field); and dashboards and their gadget configuration, where readable. A scan always runs with the permissions of the administrator who starts it, using Jira's "run as another user" capability provided by Forge, and only after the app has independently confirmed on the server that the user holds the Administer Jira permission. A scan only reads. Field Sweep makes exactly two kinds of change in your Jira Cloud site, and only when a licensed Jira administrator chooses fields and confirms: it moves a custom field to Jira's trash, and it restores a field from the trash. These calls run as that administrator, never as another user. Jira keeps a trashed field for 60 days and then deletes it permanently; the app never deletes a field permanently and never changes field values or issues.

Cross-Space Task Report for Confluence shows the tasks from every space you can view in one table. It is read-only: it changes no task, page or space. It reads tasks (task text, status, assignee account ID, and due, created and completed dates), the list of spaces (names and keys), the titles and links of the pages and blog posts that hold the tasks, and the display names of the assignees. It requests all of this with the permissions of the person who opens the report, so that person sees only what Confluence already lets them view. Page bodies, comments and attachments are not read. Without an active license it requests no task text and shows counts only. The CSV export is shown as text for you to copy; the app does not save or send it.

Sub-task Field Inheritor for Jira copies fields you choose from a parent issue to its sub-tasks. Only Jira administrators can open it. It reads the list of projects and fields, the administrator's permissions, and, for the projects you configure, the selected fields of parent issues and their sub-tasks. It writes only those selected fields on sub-tasks, as the app, and only when a sub-task is created, when a selected field changes on the parent, or when an administrator confirms Apply now or Undo. It creates and deletes no issues, and it sends update notification emails only where Jira refuses to suppress them.

Project Archiver Lite for Jira archives a company-managed project by assigning it a shared permission scheme that grants nothing to people, and restores it by assigning the original scheme back. Only Jira administrators can open it. It reads the list of projects (key, name, type, style, lead's display name and last issue update time), permission schemes and project categories. It writes only when an administrator confirms Archive or Restore for one project: it assigns a permission scheme to that project, creates the shared scheme "Archived (no access)" if none exists, and optionally sets the category "Archived". It deletes no project, issue or permission scheme.

Last Comment Column for Jira adds a read-only custom field, "Last Comment", that shows the start of the newest public comment on an issue (about 120 characters), its date (in UTC) and its author, so it can be used as a column in the issue navigator. Only Jira administrators can open its administration page. It reads the list of projects and, whenever a comment is added, edited or deleted, or when an administrator fills the existing issues of a project, the comments of the issue. It copies only public comments: comments restricted to a role or group, and internal Service Management comments, are never copied, and a mention in the text is shown as "@user". It writes only the value of its own field on issues, as the app. It changes no comment and creates and deletes no issue.

Content Status Report for Confluence shows the pages that have a content status (such as Rough draft, In progress, Ready for review or a custom status) from every space you can view in one table. It is read-only: it changes no status, page or space. It reads the list of spaces (names and keys), the statuses each space offers, the pages and blog posts that carry a status (title, link, space, last-modified date, last modifier and creator) and the display names of those people. It requests all of this with the permissions of the person who opens the report, so that person sees only what Confluence already lets them view. It also reads the custom statuses that person created for themselves; it cannot read the personal statuses other people created, so pages that carry only those are not counted. Page bodies, comments and attachments are not read. Without an active license it shows counts only. The CSV export is shown as text for you to copy; the app does not save or send it.

Template Copier for Confluence copies page templates from one space to other spaces. It reads the list of spaces, the page templates of the source and target spaces (name, description, labels and content) and the number of blueprint templates; blueprints are excluded and not copied. It writes with the permissions of the person who uses it (Confluence requires the Admin permission on the target space): it creates templates in the target spaces, and it replaces the content of a target template with the same name only when that person chooses to overwrite and confirms. Templates with the same name are otherwise skipped. Before overwriting, it saves the original content as a backup, and it offers to undo the last overwrite. It never deletes a template.

3. Data the Apps store.

Except for Cross-Space Task Report for Confluence and Content Status Report for Confluence (which store nothing), and Sub-task Field Inheritor for Jira, Project Archiver Lite for Jira, Last Comment Column for Jira and Template Copier for Confluence (described below), each App stores only job state (or, for Field Sweep, scan state) in Forge Key-Value Storage, which is hosted and operated by Atlassian inside your site's Atlassian data region: job type, job parameters (for example source and target label names, or attachment selection criteria), IDs and titles of affected content, progress counters, error messages, timestamps, an execution log, and the Atlassian account ID of the user who started the job (so the job can run with that user's permissions and be attributed in the log). For Page Sweep for Confluence the job parameters are the space ID, the optional parent page ID, the optional title filter and the label names to add and remove, and the stored data also includes, for each dry run, the ID, title and current labels of every page it listed; a label-change job stores the ID, title and current labels of the pages selected. A weekly task also reports the account IDs still on file to Atlassian and erases any that belong to a closed account, as Atlassian's Forge developer guidelines require. In addition, Page Review Reminders for Confluence stores in the same Forge storage: its settings; an index of pages that carry a review policy (page IDs, review dates, status and the reviewer's Atlassian account ID, as a copy of the policy on the page), kept for as long as the policy exists on the page and removed when the policy is cleared or the page is deleted; scan snapshots (page IDs, titles, space keys, last-modified dates, review dates, reviewer account IDs and status), deleted 30 days after the scan finishes; a per-page record that a reminder was posted (page ID, date and kind — not the recipient), kept for up to one year so the 30-day limit can be enforced; and a 10-minute cache of whether a user is a site administrator. The review policy itself lives on the page as a Confluence content property, not in Forge storage. Field Sweep for Jira stores its settings and, for each scan, a snapshot of every custom field (name, type, screens/contexts counts, and which filters, boards and dashboards reference it) together with the Atlassian account ID of the owner of each referencing saved filter or dashboard — which may be a user other than the administrator who ran the scan — and the account ID of the administrator who started the scan; and a record of each field moved to or restored from the trash (field ID, name and type, time, status, the reasons shown at the time, and the Atlassian account ID of the administrator who moved or restored it), kept for 90 days so it is always available while Jira can still restore the field; scan snapshots and the underlying job records are deleted 30 days after the scan finishes, and a weekly task also reports the account IDs still on file to Atlassian and erases any that belong to a closed account, as Atlassian's Forge developer guidelines require. We do not store page bodies, comments, attachment file contents, issue data, field values, names, email addresses, passwords or API tokens for any App, except as described below for the short comment excerpt of Last Comment Column for Jira and the template backups of Template Copier for Confluence.

Cross-Space Task Report for Confluence has no storage of its own and stores no data, in Forge storage or anywhere else. Task data is read for each request, shown in your browser and discarded. Its runtime logs hold only fixed text, HTTP status codes and error class names, never task text, titles or account IDs. It holds no personal data, and it does not report personal data to Atlassian because it has none to report.

Sub-task Field Inheritor for Jira stores, per project, in the same Forge Key-Value Storage: its settings (the chosen field IDs, the write mode of each field and the two timing options); an activity log of the last 50 changes (time, source, parent and sub-task issue keys, field IDs and result, but no field values); the progress of a running Apply now or Undo job; the last count of what Apply now would change, kept for 30 minutes; and an undo record of the last Apply now run, which holds the previous and new values of the copied fields for up to 200 sub-tasks. Because a copied field can be a user field, or a long-text field with an @mention, the undo record can contain Atlassian account IDs. Account IDs are the only personal data the app keeps. Its runtime logs hold only fixed text, issue keys, project keys, HTTP status codes, error class names and counts. A weekly task reports the account IDs on file to Atlassian and removes the entries for any that belong to a closed account, as Atlassian's Forge developer guidelines require (scope report:personal-data).

Project Archiver Lite for Jira stores in the same Forge Key-Value Storage: the id and name of the shared scheme it uses; one record for each project it has archived (project key, the id and name of the original permission scheme, the original category id, whether the category "Archived" was set, the shared scheme id, the time, and the account ID of the administrator who archived it); and an activity log of the last 200 actions (time, archive or restore, project key, the administrator's account ID, result and a short note). Account IDs are the only personal data the app keeps; names and email addresses are not stored. Its runtime logs hold only fixed text and HTTP status codes. A weekly task reports the account IDs on file to Atlassian; for an account that has been closed, the app replaces the account ID in the log and in the project records with "unknown" and keeps the record (scope report:personal-data). This weekly task runs whether or not the app is licensed.

Content Status Report for Confluence has no storage of its own and stores no data, in Forge storage or anywhere else. Page and status data is read for each request, shown in your browser and discarded. Its runtime logs hold only fixed text, HTTP status codes and error class names, never page titles or account IDs. It holds no personal data, and it does not report personal data to Atlassian because it has none to report.

Last Comment Column for Jira keeps the following. In Jira, on the issue, the value of its field: the first 120 characters of the newest public comment, its date (UTC), the comment ID and the author's account ID. The author's name is not stored; it is looked up when the column is shown. In the same Forge Key-Value Storage: for each issue it has filled, the creation time, ID and author's account ID of the comment it used, and an index entry from the account ID to the issue key (so that an account ID can be removed when it must be); for each account ID it has written, the time it was last written; and, for each project an administrator fills, the progress of the fill (counters, time and status). Restricted comments are never stored. Account IDs are the only personal data the app keeps; names and email addresses are not stored. Its runtime logs hold only fixed text, issue and project keys, job IDs and HTTP status codes, and the platform's error message when a check or queue call fails. A weekly task reports the account IDs on file to Atlassian; for an account that has been closed, the app removes the account ID from the field values and deletes the records for it (scope report:personal-data). This weekly task runs whether or not the app is licensed.

Template Copier for Confluence stores in the same Forge Key-Value Storage: a history of the last 100 copy operations (time, the account ID of the person who copied, the source and target space keys, and the counts of created, overwritten, skipped and failed templates; no template names or content); and, only when a template is overwritten, a backup of the template as it was before (space key, template ID, name, description, labels and content, plus a short fingerprint of the content to detect later edits), for the last 5 overwrite operations. A backup is deleted when it is restored, when the overwrite did not take place, or when newer backups push it out. The account ID in the history is the only personal data the app keeps; names and email addresses are not stored, though a backup holds whatever the template content contained. Its runtime logs hold only fixed text and HTTP status codes.

4. Where data goes.

Nowhere outside Atlassian. The Apps declare no external endpoints, send nothing to us or to any third party, and contain no analytics, tracking or advertising. Atlassian may collect platform-level metrics as described in its own privacy policy.

5. How we use data.

Only to perform the job you requested and show you its progress and log. We do not sell, share, profile or use the data for any other purpose. We (the developer) cannot read your site's storage; only your site's Confluence users with access to an App can.

6. Retention.

Job records are kept so you can review the log. A weekly scheduled task inside each App deletes each job record (state, log and index entry) 30 days after the job finishes. As a backstop, every job and log record is also written with a Forge storage TTL of 365 days from its last update, so nothing outlives that even if the weekly task fails. Uninstalling an App deletes all of that App's storage for your site, as handled by Atlassian. Where an App offers it, you may delete individual job records from its Jobs tab. Page Sweep for Confluence has no such button: its job records are removed by the 30-day deletion above or by uninstalling. Cross-Space Task Report for Confluence stores nothing, so it has nothing to retain. For Sub-task Field Inheritor for Jira, the activity log keeps only the latest 50 entries, the undo record is replaced by the next Apply now run and deleted when an Undo completes, and everything is deleted when the app is uninstalled. For Project Archiver Lite for Jira, the activity log keeps only the latest 200 entries, a project's record is deleted when it is restored, and all app storage is deleted when the app is uninstalled. Content Status Report for Confluence stores nothing, so it has nothing to retain. For Last Comment Column for Jira, a stored comment record is replaced or removed when the issue's value is rewritten, the records for an account are removed when the account is closed, and all app storage is deleted when the app is uninstalled; the field values themselves are issue data held by Jira. For Template Copier for Confluence, the history keeps only the latest 100 entries, backups cover only the last 5 overwrite operations and are deleted once restored, and all app storage is deleted when the app is uninstalled.

7. Your rights (GDPR / UK GDPR and similar laws).

For data stored by the Apps, your Atlassian site's organisation is the controller and Hullspark is a processor acting on your instructions through the Apps. The only personal data involved is the Atlassian account ID of users who start jobs and, for Sub-task Field Inheritor for Jira, the account IDs inside its undo record, for Project Archiver Lite for Jira, the account IDs of the administrators who archived or restored a project, for Last Comment Column for Jira, the account IDs of comment authors in the field values and its records, and, for Template Copier for Confluence, the account IDs in its copy history. Cross-Space Task Report for Confluence and Content Status Report for Confluence store no personal data. You can erase it by uninstalling the App, or by deleting the job where the App offers that (Page Sweep for Confluence removes job records after 30 days). We honour Atlassian's personal-data erasure and rectification requests forwarded through the Forge platform (https://developer.atlassian.com/platform/forge/user-privacy-guidelines/). Because nothing is transferred outside Atlassian, no cross-border transfer by us takes place; Atlassian's data residency for your site applies. On request we will sign a data-processing addendum consistent with GDPR Article 28.

8. Security.

Hosting, encryption at rest and in transit, tenant isolation and access control are provided by the Atlassian Forge platform (https://developer.atlassian.com/platform/forge/security/). The Apps never ask for, and cannot use, passwords, API tokens or personal access tokens. Report security issues to support@hullspark.com.

9. Children.

The Apps are business tools for Confluence and Jira users and are not directed at children.

10. Changes.

We will post changes at this URL and update the effective date. Material changes will also be noted in the affected App's Marketplace release notes.

Privacy Policy — Markshot for Windows

Effective date: 2026-10-09

1. Scope.

This section applies to Markshot, Hullspark's screenshot annotation app for Windows, distributed through the Microsoft Store. The Forge-app policy above does not apply to Markshot.

2. Data Markshot processes.

Markshot captures the screen region you select, lets you annotate it, and saves the result as a PNG file to a location you choose. Everything happens on your PC. The app does not collect, store or transmit personal information, usage statistics or crash reports, and contains no analytics, tracking or advertising.

3. Data Markshot stores on your PC.

Markshot writes a small settings file (your hotkey, the clipboard option and the date the app was first started) to your Windows user profile folder (%LOCALAPPDATA%). Captured images exist only where you save them.

4. Network access.

Markshot 0.4.0.0 and later make no network connections of their own. Earlier versions contact api.polar.sh only when you enter a license key and press Activate, and send that key so it can be checked; 0.4.0.0 and later have no license key entry. The Microsoft Store handles installation and updates under Microsoft's privacy statement.

5. Contact.

Questions about this policy: support@hullspark.com.

Privacy Policy — CSV Splitter & Joiner for Windows

Effective date: 2026-10-30

1. Scope.

This section applies to CSV Splitter & Joiner, Hullspark's Windows app that splits large CSV files and joins CSV files together, distributed through the Microsoft Store. The Forge-app, Markshot and other policies on this page do not apply to it.

2. Data CSV Splitter & Joiner processes.

The app reads the CSV files you choose and writes the split or joined result to new files in a folder you choose. Your originals are not changed. Everything happens on your PC. The app does not collect personal information, usage statistics or crash reports, and contains no analytics, tracking or advertising. The content of your files is never sent anywhere.

3. Data CSV Splitter & Joiner stores on your PC.

Two small files in your Windows local app data folder (%LOCALAPPDATA%\CsvSplitJoin\): settings.json, holding your choices (language, light/dark appearance, split and join options), and journal.json, which records, only while a job is running, the output folder it writes into (its path) and the running program's process ID and start time, so the app can remove leftover temporary files if it is shut down unexpectedly; the entry is removed when the job ends. Neither contains the content of your files. Deleting that folder removes both. The split or joined files exist only where the app saved them. Also a file rating.json in %LOCALAPPDATA%\Hullspark\ (the app's own sub-folder): counts of successful runs and the date the rating line was shown or closed, used only to decide when to show it; never sent anywhere.

4. Network access.

CSV Splitter & Joiner makes no network connections. The Microsoft Store handles installation and updates under Microsoft's privacy statement.

5. Contact.

Questions about this policy: support@hullspark.com.

Privacy Policy — CSV Encoding Fixer for Windows

Effective date: 2026-10-30

1. Scope.

This section applies to CSV Encoding Fixer, Hullspark's Windows app that detects the character encoding of CSV and TSV files and converts them, distributed through the Microsoft Store. The Forge-app, Markshot and Wix policies on this page do not apply to it.

2. Data CSV Encoding Fixer processes.

The app reads the CSV/TSV files you choose and writes converted copies next to them, under a new name. Your originals are not changed. Everything happens on your PC. The app does not collect personal information, usage statistics or crash reports, and contains no analytics, tracking or advertising. The content of your files is never sent anywhere.

3. Data CSV Encoding Fixer stores on your PC.

One small settings file in your Windows local app data folder (%LOCALAPPDATA%\CsvEncodingFixer\settings.json) holding your choices: language, light/dark appearance, conversion target, line-ending option, the options for unconvertible characters, double-encoding repair, include-subfolders, and the filename suffix. Converted files exist only where the app saved them. Deleting that folder removes the settings. Also a file rating.json in %LOCALAPPDATA%\Hullspark\ (the app's own sub-folder): counts of successful runs and the date the rating line was shown or closed, used only to decide when to show it; never sent anywhere.

4. Network access.

CSV Encoding Fixer makes no network connections. The Microsoft Store handles installation and updates under Microsoft's privacy statement.

5. Contact.

Questions about this policy: support@hullspark.com.

Privacy Policy — CSV Viewer & Extractor for Windows

Effective date: 2026-10-30

1. Scope.

This section applies to CSV Viewer & Extractor, Hullspark's Windows app that opens very large CSV files, searches them, finds duplicate rows and exports chosen rows, distributed through the Microsoft Store. The Forge-app, Markshot and other policies on this page do not apply to it.

2. Data CSV Viewer & Extractor processes.

The app reads the CSV files you choose and writes exported rows (search matches, or the result of removing duplicates) to a new file you name. Your originals are not changed. Everything happens on your PC. The app does not collect personal information, usage statistics or crash reports, and contains no analytics, tracking or advertising. The content of your files is never sent anywhere.

3. Data CSV Viewer & Extractor stores on your PC.

Two small files in your Windows local app data folder (%LOCALAPPDATA%\CsvViewer\): settings.json, holding your choices (language, light/dark appearance, header and search options, duplicate-row options), and journal.json, which records the names of temporary files while an export is running so the app can remove them if it is shut down unexpectedly. The words you search for and the content of your files are not saved. Deleting that folder removes both. Exported files exist only where you saved them. Also a file rating.json in %LOCALAPPDATA%\Hullspark\ (the app's own sub-folder): counts of successful runs and the date the rating line was shown or closed, used only to decide when to show it; never sent anywhere.

4. Network access.

CSV Viewer & Extractor makes no network connections. The Microsoft Store handles installation and updates under Microsoft's privacy statement.

5. Contact.

Questions about this policy: support@hullspark.com.

Privacy Policy — Excel Splitter by Hullspark for Windows

Effective date: 2026-10-30

1. Scope.

This section applies to Excel Splitter by Hullspark, Hullspark's Windows app that splits an Excel (.xlsx) table into separate files by the values in a column, by sheet or every N rows, distributed through the Microsoft Store. The Forge-app, Markshot and other policies on this page do not apply to it.

2. Data Excel Splitter by Hullspark processes.

The app reads the .xlsx file you choose and writes the results (.xlsx or CSV) as new files in the folder you choose. Your original file is only read, never changed, and the app never overwrites an existing file. Excel is not started. Everything happens on your PC. The app does not collect personal information, usage statistics or crash reports, and contains no analytics, tracking or advertising. The content of your files is never sent anywhere. In "By column value" and "Every N rows" each output file holds only its own rows: other people's rows, other sheets you did not tick, hidden sheets and the author's name are not copied into it. In "By sheet" each file holds all rows of that one sheet (that is the point of the mode). Values that were calculated from other rows (for example running totals or ranks) stay as values, and the result screen lists them under "Check before you hand them out". The app can only spot values that come from formulas: a total or text typed into a cell is not on that list, so please open one output file and look before you give the files to anyone. If Windows diagnostic data is switched on, Microsoft may receive error reports under your Windows diagnostic settings; the app itself sends nothing.

3. Data Excel Splitter by Hullspark stores on your PC.

Two small files in the app's data folder, which Windows places under your local app data (%LOCALAPPDATA%\ExcelSplit\; for the Microsoft Store version Windows redirects it into the app's own package folder under %LOCALAPPDATA%\Packages\): settings.json, holding your choices (language, light/dark appearance, how to split, output format, rows per file), and journal.json. While a split is running, journal.json records the full paths of the temporary files being written, which include the folder you chose to save into and a file name built from the value in your split column; the entries are removed when the run ends, and if the app is shut down unexpectedly they stay until the next start, when the app deletes those temporary files and clears them. The content of your files is not saved. Uninstalling the app removes this data; you can also delete the folder yourself. Output files exist only where you saved them. Also a file rating.json in %LOCALAPPDATA%\Hullspark\ (the app's own sub-folder): counts of successful runs and the date the rating line was shown or closed, used only to decide when to show it; never sent anywhere.

4. Network access.

Excel Splitter by Hullspark makes no network connections. The Microsoft Store handles installation and updates under Microsoft's privacy statement.

5. Contact.

Questions about this policy: support@hullspark.com.

6. Changes.

If this section changes, the effective date above is updated on this page.

Privacy Policy — Workbook Link Finder for Windows

Effective date: 2026-10-30

1. Scope.

This section applies to Workbook Link Finder, Hullspark's Windows app that finds the external links in Excel workbooks (links to other workbooks, data connections and similar references) and shows where they are, distributed through the Microsoft Store. The Forge-app, Markshot and other policies on this page do not apply to it.

2. Data Workbook Link Finder processes.

The app reads the Excel files or folders you choose and lists the external links it finds in them. It only reads your files: it never writes to, changes or deletes a scanned file, and Excel is not started. Everything happens on your PC. The app does not collect personal information, usage statistics or crash reports, has no account or sign-in, and contains no analytics, tracking or advertising. The content of your files, and the file names, folder paths and link targets it finds, are never sent anywhere. The app only reads the text of a link; it never opens or contacts the address a link points to. If Windows diagnostic data is switched on, Microsoft may receive error reports under your Windows diagnostic settings; the app itself sends nothing.

3. Data Workbook Link Finder stores on your PC.

One small file, settings.json, in the app's data folder, which Windows places under your local app data (%LOCALAPPDATA%\ExcelLinks\; for the Microsoft Store version Windows redirects it into the app's own package folder under %LOCALAPPDATA%\Packages\). It holds only your choices: language, light/dark appearance, whether to show only links that cause warnings, and whether to include the folder in the CSV. File names are not stored. The only other thing the app writes is the CSV file of results, and only when you choose Save and pick a location; it exists only where you saved it. Uninstalling the app removes the settings; you can also delete the folder yourself. Also a file rating.json in %LOCALAPPDATA%\Hullspark\ (the app's own sub-folder): counts of successful runs and the date the rating line was shown or closed, used only to decide when to show it; never sent anywhere.

4. Network access.

Workbook Link Finder makes no network connections. The app has no licence key and no purchase screen. The price and the free trial period are handled by the Microsoft Store under Microsoft's privacy statement, as are installation and updates.

5. Contact.

Questions about this policy: support@hullspark.com.

6. Changes.

If this section changes, the effective date above is updated on this page.

Privacy Policy — Table Flattener by Hullspark for Windows

Effective date: 2026-10-30

1. Scope.

This section applies to Table Flattener by Hullspark, Hullspark's Windows app that turns Excel reports into plain tables (one header row, one record per row) in a new workbook, distributed through the Microsoft Store. The Forge-app, Markshot and other policies on this page do not apply to it.

2. Data Table Flattener processes.

The app reads the Excel files or folders you choose and writes the result to a new file. It only reads your files: it never writes to, changes or deletes a source file. Everything happens on your PC. The app does not collect personal information, usage statistics or crash reports, has no account or sign-in, and contains no analytics, tracking or advertising. The content of your files and their names are never sent anywhere. If Windows diagnostic data is switched on, Microsoft may receive error reports under your Windows diagnostic settings; the app itself sends nothing.

3. Data Table Flattener stores on your PC.

One small file, settings.json, in the app's data folder, which Windows places under your local app data (%LOCALAPPDATA%\TableFlattener\; for the Microsoft Store version Windows redirects it into the app's own package folder under %LOCALAPPDATA%\Packages\). It holds only your choices: language, light/dark appearance, and the on/off options (include subfolders, unpivot, keep subtotals, also write a CSV and its encoding, add source columns, convert numbers stored as text). File names and cell contents are never stored. The only other things the app writes are the new workbook (and, if you switch it on, a CSV) in the location you pick; they exist only where you saved them. An existing file is replaced only if you confirm it in the Save dialog; when you convert several files, a number is added to the name instead. The new workbook contains a report sheet that names the source file and its sheets, and the "add source columns" option also writes those names into every row, so check the file before you share it. Uninstalling the app removes the settings; you can also delete the folder yourself. Also a file rating.json in %LOCALAPPDATA%\Hullspark\ (the app's own sub-folder): counts of successful runs and the date the rating line was shown or closed, used only to decide when to show it; never sent anywhere.

4. Network access.

Table Flattener makes no network connections. The app has no licence key and no purchase screen. The price and the free trial period are handled by the Microsoft Store under Microsoft's privacy statement, as are installation and updates.

5. Contact.

Questions about this policy: support@hullspark.com.

6. Changes.

If this section changes, the effective date above is updated on this page.

Privacy Policy — Document Image Extractor by Hullspark for Windows

Effective date: 2026-10-30

1. Scope.

This section applies to Document Image Extractor by Hullspark, Hullspark's Windows app that takes the pictures out of Word, Excel and PowerPoint files and saves them as image files, distributed through the Microsoft Store. The Forge-app, Markshot and other policies on this page do not apply to it.

2. Data Document Image Extractor processes.

The app reads the Office files or folders you choose, finds the pictures in them and writes those pictures, and (in the full edition) an index CSV, to a folder you pick. It only reads your files: it never writes to, changes or deletes a source file, and Word, Excel and PowerPoint are not started. Everything happens on your PC, and the pictures and the index stay in that folder. The app does not collect personal information, usage statistics or crash reports, has no account or sign-in, and contains no analytics, tracking or advertising. The content of your files, the pictures, and the file names, folder paths and cell references it finds are never sent anywhere. The app does not open web addresses it comes across in a file: a picture that a spreadsheet loads from the web is reported as not in the file, not downloaded. If Windows diagnostic data is switched on, Microsoft may receive error reports under your Windows diagnostic settings; the app itself sends nothing.

3. Data Document Image Extractor stores on your PC.

One small file, settings.json, in the app's data folder, which Windows places under your local app data (%LOCALAPPDATA%\DocumentImageExtractor\; for the Microsoft Store version Windows redirects it into the app's own package folder under %LOCALAPPDATA%\Packages\). It holds only your choices: language, light/dark appearance, the on/off and naming options, and the path of the last output folder you used. Names of the files you scan are not stored. The only other things the app writes are the pictures and the index CSV, in the output folder you chose (each document gets its own sub-folder, and an existing file is never overwritten). The index CSV lists the full path of each source file together with the pictures taken from it, so check it before you share the folder. Uninstalling the app removes the settings; you can also delete the folder yourself. Also a file rating.json in %LOCALAPPDATA%\Hullspark\ (the app's own sub-folder): counts of successful runs and the date the rating line was shown or closed, used only to decide when to show it; never sent anywhere.

4. Network access.

Reading your files and writing pictures involve no network connection. The only network use is the Microsoft Store: the app asks the Store (through the Windows Store service) whether the one-time "Full edition" add-on is owned by your Microsoft account, and the purchase window you see when you buy it is the Store's own. The purchase, the payment and the licence check are handled by Microsoft under Microsoft's privacy statement. The app receives only whether the add-on is owned (or whether a purchase succeeded); it never sees your payment details, and sends the Store nothing from your files. If the Store cannot be reached, the app works in the free edition and offers to check again. Installation and updates are also handled by the Microsoft Store.

5. Contact.

Questions about this policy: support@hullspark.com.

6. Changes.

If this section changes, the effective date above is updated on this page.

Privacy Policy — Path and Filename Checker by Hullspark for Windows

Effective date: 2026-10-30

1. Scope.

This section applies to Path and Filename Checker by Hullspark, Hullspark's Windows app that lists the paths that are too long and the file and folder names that cannot be used, and (in the full edition) renames the ones you select, distributed through the Microsoft Store. The Forge-app, Markshot and other policies on this page do not apply to it.

2. Data Path and Filename Checker processes.

The app reads the names of the files and folders in the folder you choose, and the folder you enter as the destination, and shows the result on screen. It reads names only: it does not open your files or read what is inside them, and a check never writes to, changes or deletes anything. Everything happens on your PC. The app does not collect personal information, usage statistics or crash reports, has no account or sign-in, and contains no analytics, tracking or advertising. File names, folder paths and the contents of your files are never sent anywhere. If Windows diagnostic data is switched on, Microsoft may receive error reports under your Windows diagnostic settings; the app itself sends nothing.

3. Data Path and Filename Checker stores on your PC.

The app stores two things in its data folder, which Windows places under your local app data (%LOCALAPPDATA%\PathFilenameChecker\; for the Microsoft Store version Windows redirects it into the app's own package folder under %LOCALAPPDATA%\Packages\). (a) settings.json, with your choices: language, light/dark appearance, the path length limit, the wider-characters option, and the last folder and destination you typed. (b) In the full edition, when you rename, one file per rename run in the history folder, which lists the full old and new path of each renamed item so that Undo can put the names back. The names of files you only check are not stored. The only other thing the app writes is the CSV list, which you can save in the full edition to the location you pick in the Save dialog; it lists the full path of each problem item, so check it before you share it. Uninstalling the app removes these files; you can also delete the folder yourself. Also a file rating.json in %LOCALAPPDATA%\Hullspark\ (the app's own sub-folder): counts of successful runs and the date the rating line was shown or closed, used only to decide when to show it; never sent anywhere.

4. Network access.

Checking, the destination, the CSV and renaming involve no network connection. The only network use is the Microsoft Store: the app asks the Store (through the Windows Store service) whether the one-time "Full edition" add-on is owned by your Microsoft account, and the purchase window you see when you buy it is the Store's own. The purchase, the payment and the licence check are handled by Microsoft under Microsoft's privacy statement. The app receives only whether the add-on is owned (or whether a purchase succeeded); it never sees your payment details, and sends the Store nothing from your files. If the Store cannot be reached, the app works in the free edition. Installation and updates are also handled by the Microsoft Store.

5. Contact.

Questions about this policy: support@hullspark.com.

6. Changes.

If this section changes, the effective date above is updated on this page.

Privacy Policy — Comment & Change List for .docx for Windows

Effective date: 2026-10-30

1. Scope.

This section applies to Comment & Change List for .docx (Japanese name: コメント・変更履歴一覧（.docx）), Hullspark's Windows app that lists the comments, replies and tracked changes of .docx files in one table and, in the full edition, reads several files or a whole folder and writes an Excel workbook, distributed through the Microsoft Store. The Forge-app, Markshot and other policies on this page do not apply to it.

2. Data Comment & Change List processes.

The app reads the .docx and .docm files you choose, or those in the folder you choose, and shows the result on screen. This includes what is inside the files: the names of the authors of comments and tracked changes, the dates, the text of comments and replies, the text of insertions and deletions, the sentence a comment is attached to, the headings, and the document properties (author, last editor and last-modified date). It also shows the file names. The files are only read: the app never changes, moves or deletes a document, and it can read a file that Microsoft Word has open. Everything happens on your PC. The app does not collect personal information, usage statistics or crash reports, has no account or sign-in, and contains no analytics, tracking or advertising. Documents, author names and the text of comments and changes are shown on the screen and are never sent anywhere. If Windows diagnostic data is switched on, Microsoft may receive error reports under your Windows diagnostic settings; the app itself sends nothing.

3. Data Comment & Change List stores on your PC.

The app stores one thing in its data folder, which Windows places under your local app data (%LOCALAPPDATA%\WordCommentsList\; for the Microsoft Store version Windows redirects it into the app's own package folder under %LOCALAPPDATA%\Packages\): settings.json, with your choices: language, light/dark appearance, and the last folder you picked. Nothing from your documents is stored: no author names, no text and no file names. Two things leave the window only when you ask. A CSV file or an Excel workbook is written to the location you pick in the Save dialog; it lists the file name, author, date, text, attached sentence (a part of the document body), heading and reply-to author of each item (and, in the Excel workbook, the author and the last editor of each document). "Copy table" puts the same rows on the Windows clipboard; what Windows does with the clipboard is under your Windows settings. Uninstalling the app removes the settings file; you can also delete the folder yourself. Also a file rating.json in %LOCALAPPDATA%\Hullspark\ (the app's own sub-folder): counts of successful runs and the date the rating line was shown or closed, used only to decide when to show it; never sent anywhere.

4. Network access.

Reading files, filtering, CSV, copy and Excel involve no network connection. The only network use is the Microsoft Store: the app asks the Store (through the Windows Store service) whether the one-time "Full edition" add-on is owned by your Microsoft account, and the purchase window you see when you buy it is the Store's own. The purchase, the payment and the licence check are handled by Microsoft under Microsoft's privacy statement. The app receives only whether the add-on is owned (or whether a purchase succeeded); it never sees your payment details, and sends the Store nothing from your documents. If the Store cannot be reached, the app works in the free edition. Installation and updates are also handled by the Microsoft Store.

5. Contact.

Questions about this policy: support@hullspark.com.

6. Changes.

If this section changes, the effective date above is updated on this page.

Privacy Policy — Folder Compare by Hullspark for Windows

Effective date: 2026-10-30

1. Scope.

This section applies to Folder Compare by Hullspark, Hullspark's Windows app that compares two folders and lists what is left only, right only, different and the same, and in the full edition writes a colour-coded Excel (.xlsx) report, distributed through the Microsoft Store. The Forge-app, Markshot and other policies on this page do not apply to it.

2. Data the app processes.

The app reads the two folders you choose: the names, sizes and modified times of the files and subfolders in them, and, when you choose to compare content, the contents of files of equal size (read byte by byte on your PC to see whether they are the same). It shows the result on screen. The folders are only read: the app never changes, moves, copies or deletes anything in them, and it cannot save a report inside a compared folder. Everything happens on your PC. The app does not collect personal information, usage statistics or crash reports, has no account or sign-in, and contains no analytics, tracking or advertising. File names, folder paths and the contents of your files are never sent anywhere. If Windows diagnostic data is switched on, Microsoft may receive error reports under your Windows diagnostic settings; the app itself sends nothing.

3. Data the app stores on your PC.

The app stores one small file in its data folder, which Windows places under your local app data (%LOCALAPPDATA%\FolderCompare\; for the Microsoft Store version Windows redirects it into the app's own package folder under %LOCALAPPDATA%\Packages\): settings.json, with your choices: language, light/dark appearance, the compare method, whether to include subfolders, the names to skip, and the last two folders you chose. Nothing from the folders is stored. Two things leave the window only when you ask: a CSV file or an Excel workbook is written to the location you pick in the Save dialog; it lists the path, sizes and modified times of each difference (or of every item, in the workbook), so check it before you share it. Uninstalling the app removes the settings file; you can also delete the folder yourself. Also a file rating.json in %LOCALAPPDATA%\Hullspark\ (the app's own sub-folder): counts of successful runs and the date the rating line was shown or closed, used only to decide when to show it; never sent anywhere.

4. Network access.

Comparing, the list, CSV and the Excel report involve no network connection. The only network use is the Microsoft Store: the app asks the Store (through the Windows Store service) whether the one-time "Full edition" add-on is owned by your Microsoft account, and the purchase window you see when you buy it is the Store's own. The purchase, the payment and the licence check are handled by Microsoft under Microsoft's privacy statement. The app receives only whether the add-on is owned (or whether a purchase succeeded); it never sees your payment details, and sends the Store nothing from your folders. If the Store cannot be reached, the app works in the free edition. Installation and updates are also handled by the Microsoft Store.

5. Contact.

Questions about this policy: support@hullspark.com.

6. Changes.

If this section changes, the effective date above is updated on this page.

Privacy Policy — Inside File Search by Hullspark for Windows

Effective date: 2026-10-30

1. Scope.

This section applies to Inside File Search by Hullspark, Hullspark's Windows app that searches inside .xlsx, .docx, .pptx and (in the full edition) PDF files in a folder and lists where each match is, and in the full edition writes an Excel (.xlsx) report, distributed through the Microsoft Store. The Forge-app, Markshot and other policies on this page do not apply to it.

2. Data the app processes.

The app reads the files in the folder you choose, including what is inside them (cell values, body text, tables, text boxes, slide and notes text and, in the full edition, the text of PDF pages), looks for the text you type, and shows the file name, the place (sheet and cell, paragraph, slide or page) and the text around each match on screen. The files are only read: the app never changes, moves or deletes a file, and it cannot save a report inside the searched folder. Everything happens on your PC. The app does not collect personal information, usage statistics or crash reports, has no account or sign-in, and contains no analytics, tracking or advertising. Your files, file names, search text and results are never sent anywhere. If Windows diagnostic data is switched on, Microsoft may receive error reports under your Windows diagnostic settings; the app itself sends nothing.

3. Data the app stores on your PC.

The app stores one small file in its data folder, which Windows places under your local app data (%LOCALAPPDATA%\OfficeSearch\; for the Microsoft Store version Windows redirects it into the app's own package folder under %LOCALAPPDATA%\Packages\): settings.json, with your choices: language, light/dark appearance, match case, whole words, whether to include subfolders, and the last folder and the last text you searched. Nothing from your files is stored. Two things leave the window only when you ask: a CSV file or an Excel workbook is written to the location you pick in the Save dialog; it lists the file name, the place and the text around each match (a part of the file's contents), so check it before you share it. Uninstalling the app removes the settings file; you can also delete the folder yourself. Also a file rating.json in %LOCALAPPDATA%\Hullspark\ (the app's own sub-folder): counts of successful runs and the date the rating line was shown or closed, used only to decide when to show it; never sent anywhere.

4. Network access.

Searching, the list, CSV and the Excel report involve no network connection. The only network use is the Microsoft Store: the app asks the Store (through the Windows Store service) whether the one-time "Full edition" add-on is owned by your Microsoft account, and the purchase window you see when you buy it is the Store's own. The purchase, the payment and the licence check are handled by Microsoft under Microsoft's privacy statement. The app receives only whether the add-on is owned (or whether a purchase succeeded); it never sees your payment details, and sends the Store nothing from your files. If the Store cannot be reached, the app works in the free edition. Installation and updates are also handled by the Microsoft Store.

5. Contact.

Questions about this policy: support@hullspark.com.

6. Changes.

If this section changes, the effective date above is updated on this page.

Privacy Policy — Comment List for .xlsx & .pptx by Hullspark for Windows

Effective date: 2026-10-30

1. Scope.

This section applies to Comment List for .xlsx & .pptx by Hullspark, Hullspark's Windows app that lists the comments, replies, links and speaker notes of .xlsx and .pptx files in one table and, in the full edition, reads several files or a whole folder and writes an Excel workbook (Japanese name: コメント一覧（.xlsx・.pptx）), distributed through the Microsoft Store. The Forge-app, Markshot and other policies on this page do not apply to it.

2. Data the app processes.

The app reads the .xlsx, .xlsm, .pptx and .pptm files you choose, or those in the folder you choose, and shows the result on screen. This includes what is inside the files: the names of the authors of comments and replies, the dates, the text of comments, replies, links and speaker notes, the sheet and cell or the slide each one belongs to, and the file names. The files are only read: the app never changes, moves or deletes a file, and it does not need Excel or PowerPoint. Everything happens on your PC. The app does not collect personal information, usage statistics or crash reports, has no account or sign-in, and contains no analytics, tracking or advertising. Your files, author names and the text of comments are shown on the screen and are never sent anywhere. If Windows diagnostic data is switched on, Microsoft may receive error reports under your Windows diagnostic settings; the app itself sends nothing.

3. Data the app stores on your PC.

The app stores one small file in its data folder, which Windows places under your local app data (%LOCALAPPDATA%\OfficeCommentList\; for the Microsoft Store version Windows redirects it into the app's own package folder under %LOCALAPPDATA%\Packages\): settings.json, with your choices: language, light/dark appearance, and the last folder you picked. Nothing from your files is stored: no author names, no text and no file names. Two things leave the window only when you ask. A CSV file or an Excel workbook is written to the location you pick in the Save dialog; it lists the file, place, author, date and text of each item. "Copy table" puts the same rows on the Windows clipboard; what Windows does with the clipboard is under your Windows settings. Uninstalling the app removes the settings file; you can also delete the folder yourself. Also a file rating.json in %LOCALAPPDATA%\Hullspark\ (the app's own sub-folder): counts of successful runs and the date the rating line was shown or closed, used only to decide when to show it; never sent anywhere.

4. Network access.

Reading files, filtering, CSV, copy and Excel involve no network connection. The only network use is the Microsoft Store: the app asks the Store (through the Windows Store service) whether the one-time "Full edition" add-on is owned by your Microsoft account, and the purchase window you see when you buy it is the Store's own. The purchase, the payment and the licence check are handled by Microsoft under Microsoft's privacy statement. The app receives only whether the add-on is owned (or whether a purchase succeeded); it never sees your payment details, and sends the Store nothing from your files. If the Store cannot be reached, the app works in the free edition. Installation and updates are also handled by the Microsoft Store.

5. Contact.

Questions about this policy: support@hullspark.com.

6. Changes.

If this section changes, the effective date above is updated on this page.

Privacy Policy — Merge xlsx Workbooks by Hullspark for Windows

Effective date: 2026-11-03

1. Scope.

This section applies to Merge xlsx Workbooks by Hullspark, Hullspark's Windows app that merges many .xlsx workbooks into one new workbook, either with every sheet as a tab or with same-shaped tables stacked into one table (Japanese name: xlsx ブック結合), distributed through the Microsoft Store. The Forge-app, Markshot and other policies on this page do not apply to it.

2. Data Merge xlsx Workbooks by Hullspark processes.

The app reads the .xlsx and .xlsm files you drop on the window or choose, or those in the folder you choose (including its sub-folders), and writes the merged result as one new .xlsx workbook at the place you pick in the Save dialog. This includes what is inside the files: sheets, cell values, formulas, formatting and sheet names. Your source files are only read, never changed, moved or deleted, and the app refuses to write over one of the files it is merging. Excel is not started. If you pick the name of an existing file in the Save dialog, Windows asks you to confirm the replacement first, and the merged file replaces it only after it has been written completely: the result is first written under a temporary name in the same folder and renamed when complete, and the temporary file is deleted if the merge fails or is stopped. In "Stack into one table" mode the app also uses a temporary working file in the Windows temporary folder, which is deleted when the app closes it. If the app is shut down unexpectedly, a leftover temporary file (its name starts with a dot and ends in .tmp) may remain in the folder you saved into; you can delete it. Everything happens on your PC. The app does not collect personal information, usage statistics or crash reports, has no account or sign-in, and contains no analytics, tracking or advertising. The content of your files is never sent anywhere. If Windows diagnostic data is switched on, Microsoft may receive error reports under your Windows diagnostic settings; the app itself sends nothing. After a merge, the "Open" and "Show in folder" buttons open the merged file with the program Windows has for .xlsx files, or show it in File Explorer; they do so only when you press them.

3. Data Merge xlsx Workbooks by Hullspark stores on your PC.

One small file in the app's data folder, which Windows places under your local app data (%LOCALAPPDATA%\WorkbookMerge\; for the Microsoft Store version Windows redirects it into the app's own package folder under %LOCALAPPDATA%\Packages\): settings.json, holding your choices (language, light/dark appearance, merge mode and options, number of heading rows) and the last folder you picked (its path). Nothing from your workbooks is stored: no sheet names, no cell contents and no file names. The merged workbook exists only where you saved it. Depending on the options you choose, it can contain the source file names (a "Source file" column, or file names in front of tab names) and hidden sheets (only if you tick the option to include them). In versions after 1.0.0.0, the app also stores a file rating.json in %LOCALAPPDATA%\Hullspark\WorkbookMerge\ (the app's own sub-folder): the count of successful merges, the dates of the first success and of when the rating line was shown, and what you did with it, used only to decide when to show that line; never sent anywhere. Uninstalling the app removes the settings file and this file; you can also delete the folders yourself.

4. Network access.

Reading files, merging and saving involve no network connection, and the app makes no network connection of its own. The only network use is the Microsoft Store. The app asks the Store (through the Windows Store service) whether the one-time "Full edition" add-on, which lifts the limit of 3 files per run, is owned by your Microsoft account, and the purchase window you see when you buy it is the Store's own. The purchase, the payment and the licence check are handled by Microsoft under Microsoft's privacy statement. The app receives only whether the add-on is owned (or whether a purchase succeeded); it never sees your payment details, and sends the Store nothing from your files. If the Store cannot be reached, the app works in the free edition. In versions after 1.0.0.0, after a few successful merges the app may show a small dismissible line asking you to rate it; only if you click it, the Store's own rating window (or the Store page for the app) opens, handled by Microsoft. Installation and updates are also handled by the Microsoft Store, and the app has no update check of its own.

5. Contact.

Questions about this policy: support@hullspark.com.

6. Changes.

If this section changes, the effective date above is updated on this page.

Privacy Policy — Hullspark Wix Apps

The privacy policy for our Wix apps is at hullspark.com/wix-privacy.

プライバシーポリシー — Hullspark Forge アプリ

発効日: 2026-10-25 ・ 運営者: Hullspark（個人事業主）・ 連絡先: support@hullspark.com

1. 本ポリシーの適用範囲.

本ポリシーは、Hullspark が公開するすべての Atlassian Forge アプリ（個別に「本アプリ」、総称して「各アプリ」）に適用されます。本書作成時点では Label Sweep for Confluence、Attachment Sweep for Confluence、Page Sweep for Confluence、Page Review Reminders for Confluence、Field Sweep for Jira、Cross-Space Task Report for Confluence、Sub-task Field Inheritor for Jira、Project Archiver Lite for Jira、Last Comment Column for Jira、Content Status Report for Confluence、Template Copier for Confluence の 11 です。各アプリは Atlassian の Forge プラットフォーム上でのみ動作します（Runs on Atlassian）。当方はいずれのアプリのためにも独自のサーバを運用しません。

2. 処理するデータ.

各アプリは、Atlassian の API を通じてのみ、ジョブ・走査を開始した利用者ご自身の権限で、かつそのジョブ・走査の範囲内でのみ Confluence または Jira のコンテンツを読み取り・（変更するアプリの場合のみ）変更します。

Label Sweep for Confluence は、Confluence Cloud サイトのラベルを一覧・リネーム・統合・削除します。ラベル名と、そのラベルが付いたページ・ブログの ID・タイトル・スペースを読み取ります。ページ・ブログのラベルを変更するのは、利用者がリネーム・統合・削除のジョブを開始したときだけです。

Page Sweep for Confluence は、Confluence Cloud サイトの複数のページにラベルをまとめて付け外しします。スペースの一覧（選択用）と、選んだスペース、または選んだ親ページの子孫について、ページの ID・タイトルと各ページのラベルを読み取ります。ページ本文、コメント、添付ファイルは読み取らず、ブログ記事には触れません。ドライランは読み取るだけです。ページのラベルを追加・削除するのは、Confluence のサイト管理者がドライランからラベル変更のジョブを開始して確定したときだけで、その管理者本人の権限で行います。適用してよい利用者か、どのジョブを見せてよいか（管理者以外は自分のジョブだけ）を判定するため、その利用者のグループ所属を読み取ります。結果は 10 分間キャッシュされます。

Attachment Sweep for Confluence は、Confluence Cloud サイトの添付ファイルを検索・整理します。添付ファイルのメタデータ（ファイル名、サイズ、メディア種別、日時、ID、所属するページ・ブログ）を読み取ります。ページ本文を読むのは添付ファイルがまだ参照されているかを検出するためだけで、ページ本文は保存しません。利用者がジョブを開始すると、選択した添付ファイルを Confluence のゴミ箱へ移動します。ゴミ箱からは Confluence 管理者が復元できます。添付ファイルを完全消去（purge）することはありません。

Page Review Reminders for Confluence は、Confluence Cloud サイトのページにレビュー期日と担当者を設定し、期日が来たら担当者に知らせます。ページのメタデータ（ID、タイトル、スペース、最終更新日時、版番号）を読み取ります。レビュー方針（レビュー期日、担当者の Atlassian アカウント ID、レビュー間隔、状態）はページのコンテンツプロパティとして書き込み・読み取りします。ページ本文には一切書き込みません。方針を持つページの索引（ページ ID、日付、状態）を Forge ストレージに保持します。レビューが期限間近または期限切れになると、担当者を @メンションするフッターコメントをそのページに投稿します（同一ページにつき 30 日に 1 回まで）。その後の通知メールは Confluence 自身がサイトの通知設定に従って送ります。管理者用ダッシュボードを表示するかどうかを判定するため、操作中の利用者のグループ所属を読み取ってサイト管理者かどうかを確認します。結果は 10 分間キャッシュされ、それ以上は保持しません。

Field Sweep for Jira は、サイト管理者に、各カスタムフィールドが実際にどこで使われているかを示します。読み取るのは、カスタムフィールドのメタデータ（種類、screens・contexts 数、最終使用日）、保存フィルタの JQL と所有者（走査を行う管理者以外が所有するフィルタを含みます）、ボードの構成（フィルタ・クイックフィルタ・見積りフィールド・ランクフィールド）、ダッシュボードとそのガジェットの設定（読める範囲）です。走査は必ず、開始した管理者の権限で（Forge が提供する「別ユーザーとして実行する」機能を用いて）行われ、その前にサーバ側で当該利用者が Administer Jira 権限を持つことを独自に確認します。走査は読むだけです。Field Sweep が Jira Cloud サイトに加える変更は 2 種類だけで、ライセンスを持つ Jira 管理者がフィールドを選んで確認したときに限ります。カスタムフィールドを Jira のゴミ箱へ移すことと、ゴミ箱から戻すことです。この呼び出しはその管理者本人として行い、別の利用者になりかわっては行いません。Jira はゴミ箱のフィールドを 60 日間保持した後に完全に削除します。本アプリがフィールドを完全に削除することはなく、フィールドの値や課題を変更することもありません。

Cross-Space Task Report for Confluence は、見られるすべてのスペースのタスクを 1 つの表に出します。読み取り専用で、タスク・ページ・スペースは変更しません。読み取るのは、タスク（本文、状態、担当者のアカウント ID、期限・作成日・完了日）、スペースの一覧（名前とキー）、タスクを持つページ・ブログ記事のタイトルとリンク、担当者の表示名です。これらはすべて、レポートを開いた本人の権限で取得するため、本人が Confluence で見られる範囲しか表示されません。ページ本文、コメント、添付ファイルは読み取りません。有効なライセンスがないときは、タスクの本文を取得せず、件数だけを表示します。CSV 出力はコピー用の文字として表示するだけで、アプリが保存・送信することはありません。

Sub-task Field Inheritor for Jira は、選んだ項目を親課題からサブタスクへ写します。開けるのは Jira 管理者だけです。読み取るのは、プロジェクトと項目の一覧、管理者の権限、そして設定したプロジェクトの親課題とそのサブタスクの、選んだ項目です。書き込むのは、サブタスクのその選んだ項目だけで、アプリ自身として行い、サブタスクの作成時、親の選んだ項目の変更時、管理者が「今すぐ反映」や「取り消し」を確定したときに限ります。課題の作成・削除はしません。更新の通知メールは、Jira が抑止を断った場合にだけ送られます。

Project Archiver Lite for Jira は、企業管理プロジェクトに、人に何も許可しない共有の権限スキームを割り当ててアーカイブし、元のスキームを割り当て直して復元します。開けるのは Jira 管理者だけです。読み取るのは、プロジェクトの一覧（キー、名前、種別、スタイル、リードの表示名、最終の課題更新時刻）、権限スキーム、プロジェクトカテゴリです。書き込むのは、管理者が 1 つのプロジェクトについて「アーカイブ」または「復元」を確定したときだけで、そのプロジェクトに権限スキームを割り当て、共有スキーム「Archived (no access)」がなければ作り、任意でカテゴリ「Archived」を付けます。プロジェクト・課題・権限スキームは削除しません。

Last Comment Column for Jira は、課題の最新の公開コメントの冒頭（約 120 字）、その日付（UTC）、投稿者を出す読み取り専用のカスタム項目「Last Comment」を足し、課題ナビゲーターの列として使えるようにします。管理ページを開けるのは Jira 管理者だけです。読み取るのは、プロジェクトの一覧と、コメントの追加・編集・削除のとき、または管理者がプロジェクトの既存の課題に反映するときの、その課題のコメントです。写すのは公開コメントだけで、ロールやグループで制限したコメントと Service Management の内部コメントは写さず、本文中のメンションは「@user」と表示します。書き込むのは課題にある自分の項目の値だけで、アプリとして行います。コメントは変更せず、課題の作成も削除もしません。

Content Status Report for Confluence は、閲覧できるすべてのスペースの、コンテンツステータス（Rough draft、In progress、Ready for review、独自のステータスなど）が付いたページを 1 つの表にします。読み取り専用で、ステータス・ページ・スペースは変更しません。読み取るのは、スペースの一覧（名前とキー）、各スペースで選べるステータス、ステータスが付いたページとブログ投稿（題名、リンク、スペース、最終更新日時、最終更新者、作成者）、その人たちの表示名です。これらはすべて、レポートを開いた人の権限で取得するため、その人は Confluence がすでに閲覧を許している内容だけを見ます。その人自身が作った個人用ステータスも読みますが、他の人が作った個人用ステータスは読めないため、それだけが付いたページは数えられません。ページ本文、コメント、添付ファイルは読みません。有効なライセンスがないときは件数だけを表示します。CSV 出力はコピー用の文字として表示するだけで、アプリが保存したり送ったりすることはありません。

Template Copier for Confluence は、ページテンプレートをあるスペースから別のスペースへコピーします。読み取るのは、スペースの一覧、コピー元とコピー先のスペースのページテンプレート（名前、説明、ラベル、内容）、ブループリントテンプレートの数で、ブループリントは対象外でコピーしません。書き込みは使った人の権限で行い（Confluence はコピー先スペースの管理者権限を求めます）、コピー先にテンプレートを作成し、同名のテンプレートの内容を置き換えるのは、その人が上書きを選んで確認したときだけです。それ以外では同名のテンプレートをスキップします。上書きの前に元の内容を控えとして保存し、直近の上書きを取り消せるようにします。テンプレートは削除しません。

3. 保存するデータ.

Cross-Space Task Report for Confluence と Content Status Report for Confluence（どちらも何も保存しません）、および後述の Sub-task Field Inheritor for Jira・Project Archiver Lite for Jira・Last Comment Column for Jira・Template Copier for Confluence を除き、各アプリが保存するのはジョブ状態（Field Sweep の場合は走査状態）のみで、保存先は Atlassian がサイトのデータリージョン内で運用する Forge Key-Value Storage です。内容は、ジョブ種別、ジョブのパラメータ（元・先ラベル名や添付ファイルの選択条件など）、対象コンテンツの ID とタイトル、進捗、エラー、時刻、実行ログ、およびジョブを開始した利用者の Atlassian アカウント ID（その利用者の権限で実行し、ログに記録するため）です。Page Sweep for Confluence のジョブのパラメータは、スペース ID、任意の親ページ ID、任意のタイトル絞り込み、付ける・外すラベル名で、保存されるデータには、ドライランごとに、一覧にしたすべてのページの ID・タイトル・現在のラベルも含まれ、ラベル変更のジョブは選んだページの ID・タイトル・現在のラベルを保存します。週次のタスクが保存中のアカウント ID を Atlassian に報告し、アカウントが閉鎖されていれば消去します（Forge の開発者向けプライバシーガイドラインが求める対応）。加えて Page Review Reminders for Confluence は同じ Forge ストレージに次を保存します。アプリの設定。レビュー方針を持つページの索引（ページ ID、レビュー期日、状態、およびページ上の方針の写しとしての担当者の Atlassian アカウント ID）— ページに方針がある限り保持し、方針の解除またはページの削除で消えます。走査のスナップショット（ページ ID、タイトル、スペースキー、最終更新日時、レビュー期日、担当者のアカウント ID、状態）— 走査完了から 30 日後に削除します。ページごとの通知済み記録（ページ ID、日時、種別。宛先は含みません）— 30 日に 1 回の上限を守るため最長 1 年保持します。利用者がサイト管理者かどうかの 10 分間のキャッシュ。レビュー方針そのものは Forge ストレージではなく、ページの Confluence コンテンツプロパティとして存在します。Field Sweep for Jira は、アプリの設定に加え、走査ごとに全カスタムフィールドのスナップショット（名前、種類、screens・contexts 数、参照元のフィルタ・ボード・ダッシュボード）と、参照元の保存フィルタ・ダッシュボードの所有者の Atlassian アカウント ID（走査を行った管理者とは別の利用者の場合があります）、走査を開始した管理者のアカウント ID、およびゴミ箱へ移した・戻したフィールドごとの記録（フィールドの ID・名前・種類、日時、状態、そのとき示した理由、移した・戻した管理者の Atlassian アカウント ID）を保存します。この記録は、Jira でフィールドを戻せるあいだ必ず残るよう 90 日間保持します。走査のスナップショットと基になるジョブ記録は走査完了から 30 日後に削除され、週次のタスクが保存中のアカウント ID を Atlassian に報告し、アカウントが閉鎖されていれば消去します（Forge の開発者向けプライバシーガイドラインが求める対応）。いずれのアプリも、ページ本文、コメント、添付ファイルの中身、課題データ、フィールドの値、氏名、メールアドレス、パスワード、API トークンは保存しません（後述の Last Comment Column for Jira のコメントの抜粋と、Template Copier for Confluence のテンプレートの控えを除きます）。

Cross-Space Task Report for Confluence は自前のストレージを持たず、Forge ストレージにもほかの場所にも、データを保存しません。タスクのデータは要求のたびに読み取り、ブラウザに表示して破棄します。実行ログに残るのは、固定の文、HTTP ステータス、エラーのクラス名だけで、タスクの本文・タイトル・アカウント ID は書きません。個人データは保持せず、報告すべきものがないため Atlassian への個人データの報告もしません。

Sub-task Field Inheritor for Jira は、同じ Forge Key-Value Storage に、プロジェクトごとに次を保存します。設定（選んだ項目の ID、項目ごとの書き方、2 つのタイミングの選択）、直近 50 件の変更の操作ログ（時刻、きっかけ、親とサブタスクの課題キー、項目 ID、結果。項目の値は入れません）、実行中の「今すぐ反映」や「取り消し」の進み具合、「今すぐ反映」で変わる件数の直近の数え（30 分間保持）、そして直近の「今すぐ反映」の取り消し用の記録です。取り消しの記録には、最大 200 件のサブタスクについて、写した項目の変更前と変更後の値が入ります。写した項目がユーザー項目、または @メンションを含む長文項目の場合があるため、取り消しの記録には Atlassian のアカウント ID が含まれることがあります。アプリが保持する個人データはアカウント ID だけです。実行ログに残るのは、固定の文、課題キー、プロジェクトキー、HTTP ステータス、エラーのクラス名、件数だけです。週次の処理が、保存しているアカウント ID を Atlassian に報告し、閉じたアカウントのものを消去します（Atlassian の Forge 開発者ガイドラインに従うもので、スコープは report:personal-data）。

Project Archiver Lite for Jira は、同じ Forge Key-Value Storage に次を保存します。使う共有スキームの ID と名前。アーカイブしたプロジェクトごとの記録（プロジェクトキー、元の権限スキームの ID と名前、元のカテゴリ ID、カテゴリ「Archived」を付けたかどうか、共有スキームの ID、時刻、アーカイブした管理者のアカウント ID）。直近 200 件の操作の記録（時刻、アーカイブか復元か、プロジェクトキー、管理者のアカウント ID、結果、短い注記）。アプリが保持する個人データはアカウント ID だけで、名前とメールアドレスは保存しません。実行ログに残るのは、固定の文と HTTP ステータスだけです。週次の処理が、保存しているアカウント ID を Atlassian に報告し、閉じたアカウントについては、操作の記録とプロジェクトの記録のアカウント ID を「unknown」に置き換えて、記録は残します（スコープは report:personal-data）。この週次の処理は、ライセンスの有無に関係なく動きます。

ウィンドウにドロップした、または選んだ .xlsx・.xlsm のファイル、あるいは選んだフォルダー（サブフォルダーを含む）の中のそれらのファイルを読み取り、結合した結果を、保存ダイアログで指定した場所に新しい .xlsx ブックとして保存します。ファイルの中身（シート、セルの値、数式、書式、シート名）も読みます。元のファイルは読み取るだけで、変更・移動・削除はせず、結合の対象にしているファイルへ上書き保存することも拒否します。Excel は起動しません。保存ダイアログで既にあるファイルの名前を選んだ場合は、先に Windows が置き換えの確認を出し、結合したファイルは最後まで書き終えてから置き換わります。結果はまず同じフォルダーに一時的な名前で書かれ、完成してから名前が変わります。結合に失敗したり中止したりしたときは、その一時ファイルを削除します。「1 つの表に積む」では、Windows の一時フォルダーにも作業用の一時ファイルを使い、使い終わると削除されます。アプリが予期せず終了した場合は、保存先のフォルダーに、名前が「.」で始まり .tmp で終わる一時ファイルが残ることがあります。その場合は自分で削除できます。処理はすべてお使いの PC の中で行われます。個人情報・利用状況・クラッシュ情報は収集せず、アカウントやサインインもなく、解析・トラッキング・広告もありません。ファイルの内容を外部へ送信することはありません。Windows の診断データの設定によっては、エラー報告を Microsoft が受け取ることがあります（アプリ自身は何も送信しません）。結合のあとの「開く」「フォルダーで表示」は、押したときだけ、結合したファイルを Windows が .xlsx に割り当てているプログラムで開く、またはエクスプローラーで表示します。

3. PC に保存されるもの

アプリのデータの場所に、settings.json を 1 つ保存します。通常は Windows のローカルアプリデータ（%LOCALAPPDATA%\WorkbookMerge\）で、Microsoft Store 版では Windows がアプリ専用のパッケージフォルダー（%LOCALAPPDATA%\Packages\ の下）へ振り替えます。中身は、言語、ライト / ダーク、結合の方法とオプション、見出しの行数、最後に選んだフォルダー（そのパス）です。ブックの中身は保存しません。シート名も、セルの内容も、ファイル名も保存しません。結合したブックは、保存した場所にだけ存在します。選んだオプションによっては、結合したブックに元のファイル名（「元ファイル」列、またはタブ名の前に付けたファイル名）や非表示のシート（含めるオプションにチェックを入れた場合のみ）が入ります。バージョン 1.0.0.0 より後のバージョンでは、あわせて、%LOCALAPPDATA%\Hullspark\WorkbookMerge\（アプリ専用のサブフォルダー）に rating.json を保存します。成功した結合の回数、最初に成功した日、評価のお願いの行を表示した日、その行への操作だけを記録し、表示のタイミングの判定にのみ使います。どこにも送信しません。アプリをアンインストールすると、設定のファイルとこのファイルは消えます。フォルダーを自分で削除することもできます。

4. 通信

ファイルの読み込み・結合・保存では通信せず、アプリ自身が通信することもありません。通信するのは Microsoft Store との間だけです。1 回の実行で結合できるファイルを 3 つまでとする制限を外す、買い切りの「製品版」アドオンをお使いの Microsoft アカウントが所有しているかを、アプリが Windows のストア機能を通じて Store に問い合わせます。購入時に表示される画面も Store のものです。購入・決済・ライセンスの確認は、Microsoft が Microsoft のプライバシーに関する声明に従って扱います。アプリが受け取るのは、アドオンを所有しているか（購入が成功したか）だけで、お支払い情報は見えず、ファイルの内容を Store に送ることもありません。Store に接続できないときは無料版として動作します。バージョン 1.0.0.0 より後のバージョンでは、結合が何回か成功したあと、評価をお願いする小さな行（閉じられます）を表示することがあります。それをクリックしたときだけ、Store の評価画面（またはアプリの Store ページ）が開き、Microsoft が扱います。インストールと更新も Microsoft Store が扱い、アプリ独自の更新確認はありません。

5. お問い合わせ

support@hullspark.com

6. 変更

本節を変更したときは、上の発効日を更新します。

プライバシーポリシー — Hullspark Wix アプリ

Wix アプリのプライバシーポリシーは hullspark.com/wix-privacy にあります。