Briska Pay is an hours and estimated-pay tracking app developed by Berkzerker Software. This policy explains how information is handled when you use the app.
Information you enter
Briska Pay lets you enter work and pay information such as work/day records, custom pay rates, allowances, uplifts, pay schedules, employer or company details, sites, notes and app preferences. Earnings and pay calculations are estimates based on this user-entered information. Export-library metadata and optional app-lock configuration are also stored by the app. Briska Pay does not require an account and Berkzerker Software does not operate a cloud account or cloud-sync service for it. We do not sell your personal information.
Local device storage
Briska Pay stores its core work/pay records and settings locally on your device. Anyone who can access the unlocked app or device may be able to view this information. Android automatic cloud backup and device-to-device transfer are disabled for Briska Pay’s protected app data; use Briska Pay’s manual backup feature if you want a transferable copy.
The optional Briska Pay app lock may use either device authentication or a separate Briska Pay PIN. Fingerprint, face and device-credential checks are handled by the operating system; Briska Pay does not receive or store biometric data.
User-initiated files and sharing
PDF reports, Excel spreadsheets, CSV files and manual backup files are created only when you request them. Information can leave Briska Pay when you choose to share an export or backup, save or open an exported file through another app, print, or select and restore a backup. You control these actions and destinations. Once a file is sent to another app, service or person, their privacy and security practices apply.
Google AdMob advertising
Briska Pay uses Google AdMob to show banner advertising on the Home screen. It does not use interstitial, rewarded, app-open or native ads. Google and its advertising technologies may process information needed to provide, measure, secure and manage advertising. Briska Pay does not intentionally send your wage/work records, employer name, site or job entries, or exported wage files to AdMob as advertising content.
Details of Google’s processing can vary by device, location, consent state and applicable requirements. Learn more from Google’s Privacy Policy and How Google uses information from sites or apps that use its services.
Advertising consent and privacy choices
Where applicable, Briska Pay uses Google’s User Messaging Platform (UMP). Google may present advertising privacy choices, and Briska Pay requests ads only when Google’s authoritative consent/privacy state says advertising may be requested. When Google requires the option, you can review or change advertising privacy choices from Briska Pay Settings.
Declining personalised advertising does not necessarily stop all advertising. Google may still permit non-personalised or limited advertising depending on your consent state and applicable requirements.
Analytics and internet access
Briska Pay does not use a separate app analytics service. Google AdMob may provide advertising performance, security and diagnostic reporting as described above. The Android app uses internet access for advertising and privacy services, but connectivity is not required to view or manage core wage records already stored locally.
Retention, deletion and your rights
Local records remain on your device until you edit or delete them using available app controls, reset local data, clear the app’s data, or uninstall the app. Briska Pay cannot remotely delete local records from a server because it does not operate a user-account server. Depending on where you live, you may have rights relating to personal information and consent. Advertising-related information controlled by Google is separate from Briska Pay’s local application records, and requests about that information may need to be directed to Google.
Contact details
Questions or privacy requests can be sent to berkzerkatron@hotmail.com.