PayClose keeps your shift and pay records on your device. It has no account and no server that we operate. This policy explains the limited data the app does send, and to whom.
Last updated: 7 September 2026
PayClose ("the app") is published by LzyLabs ("we", "us"), the data controller for any personal data described here. PayClose is an independent tool. It is not affiliated with your employer or any payroll provider, and it produces gross-pay estimates from the rules you enter — not tax, net/take-home pay, or legally owed wages.
Contact: agents@lzylabs.com.
Everything you enter to track your pay is stored in PayClose's private application storage on your device and is never transmitted to us or to any third party:
This data is excluded from Android cloud backup. If you move to a new device using Android's device-to-device transfer, only the pay ledger file is carried over; your privacy and purchase settings are not, so you are asked for them again on the new device.
You can export a closed pay period as a CSV file, or export a full backup file, at any time. Those files are created only when you ask for them and are handed to your device's own file/share picker. Their contents are never sent to us and never included in analytics.
Usage analytics and crash diagnostics are part of the app rather than a per-user setting: there is no in-app switch for them. The lists below are the complete description of what leaves your device. None of it includes your pay records. If you would rather send nothing at all, do not install the app, or uninstall it.
The app records a fixed list of fifteen interaction events describing your progress through the app — for example that onboarding was viewed, a job was set up, a shift was confirmed, a pay period was closed, a CSV was exported, or PayClose Pro was purchased — plus a numeric funnel-step and a single property indicating whether you are a free or Pro user. The event and screen names are fixed in the app's source; nothing you type can become one. Firebase also collects standard identifiers automatically: an app-instance ID, device model, operating-system version, app version, coarse (country/region-level) location derived from IP, and language.
We do not send pay amounts, employer names, rates, shift times, typed labels, file names, or the contents of any export.
The app reports crashes and unhandled errors: a stack trace, an internal error code, the error's programming type name, device state at the time, and a Firebase installation identifier. Exception messages are removed before sending so that a wage, an employer name or a file path cannot leak into a report.
The app retrieves advertising-frequency settings from Firebase. This request sends standard Firebase installation data (an installation ID and basic app/device metadata). No information you entered is sent.
The free version of PayClose shows ads through Google AdMob:
PayClose Pro is a one-time purchase processed by Google Play Billing. To grant and restore it, the app receives a purchase token and order identifier from Google Play. These are verified on your device and stored locally as proof of your entitlement. They are not shared with us and are never placed in analytics or diagnostics. Google processes the payment and retains transaction records under its own terms.
We do not sell personal data and we do not operate a server that receives your information. The data described above is processed by Google as the provider of the Firebase and AdMob SDKs, under Google's own privacy terms:
| Data | Purpose | Processor |
|---|---|---|
| Interaction events, app-instance ID, device/app metadata, coarse location | Understand how features are used so the app can be improved | Google (Analytics for Firebase) |
| Crash traces, error codes, installation ID, device state | Find and fix stability defects | Google (Firebase Crashlytics) |
| Installation ID, app/device metadata | Deliver advertising-frequency settings | Google (Firebase Remote Config) |
| Device identifiers, IP/approximate location, ad interactions | Show and measure ads (only with consent; not for Pro users) | Google (AdMob) |
| Purchase token, order ID | Sell and restore PayClose Pro | Google (Google Play Billing) |
Relevant Google policies: Google Privacy Policy, Firebase & privacy, AdMob & data. Data processed by Google may be transferred to and stored on servers outside your country.
We hold no separate copy of any of this data.
PayClose is a workforce-pay tool for working adults. It is not directed to children, and we do not knowingly collect personal data from anyone under 13 (or under the minimum age of digital consent in your country). If you believe a child has provided data, contact us and we will address it.
On-device records are held in PayClose's private application sandbox, which other apps cannot read. Any network requests the Firebase and AdMob SDKs make use encrypted (HTTPS/TLS) connections. No method of storage or transmission is perfectly secure, but because your pay data never leaves your device, its exposure is limited to that device.
If we change this policy we will update the page and the "last updated" date above. Material changes that affect data we collect will also be surfaced in the app.
Questions, requests or complaints about privacy: agents@lzylabs.com.