Data handling

Privacy Policy

Last updated: 7 November 2026

This policy covers the GuardScheduler desktop application, its PayPeriod / PDF Renamer tools, and the public information website at guardschedulerapp.com. Privacy questions can be sent to LGFPaySlips@gmail.com.

1. Information on the operator's PC

The desktop application works with the scheduling information and files supplied by its operator. PDF Renamer uses payslip IDs from file names, saved output names, optional recipient email addresses and selection preferences. It processes imported ZIP files locally to create renamed PDF files; it does not interpret or alter the PDFs' contents.

Saved PDF Renamer mappings and email preferences use Windows data protection on the PC. Operator-created backup and transfer files may contain these settings and scheduling information. Such files, exported ZIPs and original payslips must be protected by the operator and are not automatically uploaded to this website.

2. Intended Google permissions and purpose

When a release supports Gmail sending, connection will be optional and initiated by an authorized operator through Google's sign-in page. The intended permissions are:

• openid and userinfo.email: identify the connected Google account and display its email address, so the operator can check the sender.
• gmail.send: send the individual payslip messages explicitly approved by the operator.

The integration is not intended to request permission to read an inbox, browse existing messages, delete mail, access contacts or use Google Drive. This website itself does not provide a Google sign-in form or collect a Gmail password.

3. Intended use and sharing for sending

The intended sending workflow will use the selected recipient address, message subject and body, and the corresponding ID-matched PDF to construct a separate email. Those contents will be transmitted to Google for delivery and to the selected recipient through their email provider. Email copies retained by Google, recipients or their organizations remain subject to their own policies and controls.

Google account identity and authorization credentials will be used only to establish the requested connection and provide the visible sending feature. They will not be sold, used for advertising, used for credit decisions, or used to train general-purpose AI models. Payslips will not be routed through this website or an application-operated mail relay.

GuardScheduler's use of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.

4. Intended storage and security

The planned connection will use encrypted transport and Windows-protected local authorization tokens rather than storing a Gmail password. Each PC will be authorized separately. Tokens must not be included in application installers, ordinary Export Data / Import Data transfers, or the public website.

The planned sender will keep local delivery records for status review and duplicate-send protection. These records may include recipient addresses, document identifiers, timestamps, delivery-attempt results and returned message identifiers; they are not intended to contain PDF contents or authorization tokens.

No security measure eliminates all risk. Operators remain responsible for Windows account access, device security, backups, verified recipient details and authorized handling of payroll information.

5. Retention, deletion and connection controls

Current local mappings, preferences, schedules and files remain on the operator's PC until removed through the applicable application controls or storage-management process. Creating an export or deleting a mapping does not delete separate original PDFs, exports, backups or transfer files.

For the planned Gmail feature, disconnecting will remove the active local authorization credentials. The account holder will also be able to revoke access in Google Account connections. Revocation does not delete previously sent messages, recipient copies or separately retained local records.

For help identifying or deleting local data, contact support. Support does not have automatic remote access to your PC. Authorized office personnel should handle employee requests involving the organization's payroll records and retention requirements.

6. This website and support messages

The website contains information pages only. It has no payslip upload form, user account database, advertising scripts or application-added analytics. Cloudflare hosts and delivers the pages and may process technical connection information, such as IP addresses and request details, for delivery and security under its privacy policy.

If you email support, the support mailbox and its email provider receive your email address and anything you include. Messages are used to respond to the request and may be retained as needed for support and applicable recordkeeping. To request deletion of support correspondence, email the support contact; any applicable retention requirements will be explained.

Do not include passwords, authorization codes, connection files or full payslips in an initial support email. Where troubleshooting needs additional information, share only the minimum necessary through an agreed channel.

7. Changes and contact

This policy must be reviewed when the Gmail feature is implemented or data practices change. Material changes will be disclosed before affected Google permissions or new uses are requested.

Contact: LGFPaySlips@gmail.com.