Privacy Policy for Padlockout

Last updated: 29 July 2026

About Padlockout

Padlockout is used for padlock and key cabinet register operations. The app is intended for controlled workplace use and requires users to sign in before they can access operational features.

Account access

Users cannot create their own accounts inside the Padlockout app. Accounts and access permissions are created and managed outside the app by an authorized administrator or the app owner.

Access may be assigned by company, rig, and department. A user may only access operational data within the scope assigned to their account.

Data we process

Depending on the user's role and how their organization uses Padlockout, the app may process:

• Email address
• User ID
• Name or display name
• Company, rig, and department access scope
• Padlock codes and status
• ICC and equipment information
• Comments entered during padlock or key cabinet operations
• Padlock activity and history events
• Key cabinet and hook assignments
• Backup and export files created from operational records

How the data is used

Data is processed to provide the core functions of Padlockout, including:

• Authenticating users
• Controlling access by company, rig, and department
• Displaying padlock and key cabinet registers
• Recording padlock take-out and put-back activity
• Recording key cabinet and hook activity
• Maintaining operational history and audit records
• Creating backup and export files requested by authorized users
• Maintaining the security and reliability of the service

Data sharing

Padlockout does not sell personal data and does not use personal data for advertising.

The app uses Firebase and Google Cloud services for authentication, database storage, file storage, and hosting. These services act as service providers for Padlockout.

Operational data may be visible to other authorized users within the same assigned company, rig, or department, depending on their access role.

Security

Data transmitted between the Padlockout app and Firebase or Google Cloud services is encrypted in transit using secure HTTPS/TLS connections.

Access to operational data is controlled through authenticated accounts and authorization rules based on company, rig, and department scope.

Data retention

Account and access information is retained for as long as the user requires access to Padlockout or as long as it is necessary to provide and administer the service.

Operational history, audit records, backup files, and export files may be retained for longer periods when required for company operations, safety, legal obligations, regulatory compliance, incident investigation, or audit requirements.

No single universal retention period applies to all organizations using Padlockout. Retention of operational records may depend on the policies and legal obligations of the organization responsible for the relevant data.

Data deletion requests

Users may request deletion of their Padlockout account and associated personal data by sending an email to:

Email: padlockout.support@proton.me

The request should include:

1. The email address used to access Padlockout
2. The user's name or display name
3. The assigned company, rig, or department, if known
4. A clear request to delete the account and associated personal data

Additional information may be requested when reasonably necessary to verify the identity of the requester and prevent unauthorized deletion.

Data that may be deleted

After a valid deletion request has been verified, the following data may be deleted:

• The Firebase Authentication account used to sign in
• The user's Padlockout access record
• Email address
• Name or display name
• User ID or other account identifiers
• Company, rig, and department access assignments

Data that may be retained

Some operational records may need to be retained even after the user's account has been deleted. This may include:

• Padlock activity history
• Key cabinet activity history
• Operational audit records
• Safety-related records
• Backup and export records
• Records required for legal, compliance, or incident-investigation purposes

Where reasonably possible, retained operational records may be anonymized or disconnected from the deleted authentication account.

Children

Padlockout is not intended for children. It is intended for workplace and enterprise use by authorized users.

Changes to this policy

This privacy policy may be updated when the app, its services, or applicable requirements change. The latest revision date will be shown at the top of this page.

Contact

For privacy questions, access requests, or data deletion requests, contact:

Email: padlockout.support@proton.me