This Path Privacy Policy supplements the COMLUK Solutions Privacy Policy and applies specifically to the Path application and Path-related device features.
Path is a visual project-memory and build-log application. It records project history as chronological steps and may also attach dates, reminders, branches, links and other project metadata to those steps.
The COMLUK Solutions Privacy Policy remains the company-wide privacy framework.
About This Policy
This policy explains how information is handled when users create projects, record steps, schedule reminders, export project files, create backups or use Android integrations such as notifications, shortcuts and widgets.
Path is designed as a local-first application. Core project information is stored on the device rather than in a mandatory centralized Path account.
Information Path Stores on the Device
Depending on how Path is used, locally stored information may include:
- Project names and project identifiers
- Step titles, notes, dates and user-entered descriptions
- Step icons, status information and other display metadata
- Branches between projects and links between existing steps
- Pinned-project information and the last project used
- Reminder dates, times, durations and reminder-state information
- App settings and preferences
- Local backup configuration and references to user-selected backup locations
- Native reminder registry information and locally queued reminder actions where needed for notification handling
The content entered into a Path project is chosen by the user. Users should avoid recording unnecessary sensitive information and should protect access to their device and backup files appropriately.
Projects, Steps and Schedule
A scheduled item in Path remains the same project step rather than becoming a separate cloud calendar record. Adding a date, time or reminder causes that step to appear in Path's Schedule view.
Project history, branches, linked steps and Schedule information are part of the same local Path library.
Reminders and Notifications
On supported Android builds, Path may use Android alarms and notifications to remind the user about a scheduled Path step.
The Android wrapper may retain the information needed to schedule or restore reminders, including after a device restart or app replacement. Notification actions such as Done, Snooze or Noted may be stored temporarily on the device until Path can synchronize the action with the related local step.
Notification permission can be managed through the device's operating-system settings. Disabling notifications may prevent Path from presenting reminder alerts.
Backup, Export and Import
Path can export an individual project as a .path file and can create or restore a full-library .pathbackup file.
Exported and backup files may contain the project names, steps, notes, reminder information, branches, links and other content stored in the selected project or library. Anyone who obtains a readable copy of such a file may be able to view the information it contains.
Users are responsible for choosing where exported and backup files are stored and for protecting those files using appropriate device, storage-provider and account security.
Android Storage Access
For automatic local backup, Path may use Android's Storage Access Framework. The user chooses the document or folder location that Path is allowed to use.
Path may retain the operating-system document reference and permission needed to continue writing to the selected backup location. This does not give Path unrestricted access to all files on the device.
If the user chooses a location supplied by a third-party document provider or cloud-storage app, that provider may process the file under its own terms and privacy practices.
Shortcuts, Widgets and Deep Links
Supported Android builds may provide app shortcuts, a Path Quick Actions widget, reminder links or other deep-link actions that open a specific Path workflow, project or step.
These features use Path's local project and step identifiers to route the requested action. They are designed to open existing Path data rather than copy the entire Path database into another COMLUK application.
Network and Cloud Use
Path's current core architecture is designed to remain useful without an account, cloud synchronization service or continuous internet connection. Core project data is not required to be uploaded to a Path cloud account in order to use the application.
If a user follows a web link from Path, opens the hosted Path Privacy Policy or deliberately stores a Path export/backup through an external provider, the destination service may receive normal web or file-service information under its own privacy practices.
If future versions introduce cloud synchronization, online accounts, analytics or other network-connected services, this policy should be updated before those features are treated as part of the public Path baseline.
Data Retention and Deletion
Local project information generally remains on the device until it is edited or deleted by the user, cleared through device or app controls, removed with the application's stored data, or replaced through an intentional restore/import action.
Exported and backup files remain wherever the user chose to save them until the user or the applicable storage provider removes them.
Reminder registry information and temporary notification-action state may be removed or updated as reminders are completed, cancelled, rescheduled or otherwise changed.
Security
Path is designed to keep core project information local and to use operating-system-controlled storage access for user-selected backup locations.
Local information is also dependent on the security of the user's device, operating system, screen lock, device backups and any external storage provider selected by the user.
No device, application or storage system can be guaranteed to be completely secure.
User Choices and Control
Users decide what projects and steps to create, what information to record, whether to set reminders, which projects to export and whether to configure automatic backup.
Users can delete or edit project information through Path's controls, manage notification permission through Android settings, and change or reset the backup location where supported.
Questions about privacy practices may be submitted through the COMLUK Solutions Contact page.
Children's Privacy
Path does not require a Path account as part of its current local-first baseline and is not designed to solicit personal information from children for advertising or profiling.
Where Path is used by a child or young person, an appropriate adult should help determine what personal information is appropriate to record in project notes or backup files.
Changes to This Policy
COMLUK may update this Privacy Policy as Path, its technology, legal requirements or business practices change.
The current version will be published on the COMLUK Solutions website with its effective date. Material changes may be communicated through the app, website or another appropriate channel where reasonably necessary.
Contact Information
Questions, privacy concerns, correction requests or complaints may be submitted through the COMLUK Solutions Contact page.
Do not send passwords, payment-card information, one-time codes or other security credentials in an ordinary privacy enquiry.
Companion Documents
This product-specific Privacy Policy supplements the COMLUK Solutions Privacy Policy and may be read together with:
- COMLUK Solutions Privacy Policy
- COMLUK Solutions Terms of Service
- Any Path download, installation or release notices published by COMLUK
- Any additional notice presented for a future Path feature or connected service
Path is local first: your project history stays on your device unless you deliberately export, back up or send it somewhere else.