Shifts, tips, schedules, payroll settings, OCR reviews, and tip-slip records work from device storage without a network connection.
Privacy & Security
How Gratuvia stores and processes your records
The Android build keeps its main work and earnings record on the device. Tip-slip OCR also runs on the phone. This page lists the storage, file-integrity, and backup mechanisms behind those claims.
The Android build includes a private native OCR module and its recognition models inside the app. The OCR pass runs on the phone.
Structured records are stored in a SQLCipher-protected SQLite database. The database key is generated on the device and stored with the platform's secure-storage system.
Gratuvia keeps the original selected or captured image separately from OCR working files. A recognition pass can crop or transform a working copy without rewriting the original.
Original tip-slip files are hashed with SHA-256. Gratuvia can compare that hash with an imported or restored file to check whether the bytes match the saved record.
Portable backups are encrypted on the device with AES-256-GCM. The recovery key is stored separately from the encrypted backup file.
Local-first storage
The main tracking workflow does not require a remote database. A user can record shifts, tips, wages, schedules, payroll settings, OCR reviews, and original tip slips from the phone itself.
That also limits what Prokvik can recover. If a record exists only on one phone and that phone is lost or erased, Prokvik does not have a server copy to restore. The portable backup feature gives you a second encrypted copy that you can store somewhere else.
OCR review before a record is saved
The OCR engine reads the image. The parser identifies likely fields. Gratuvia then shows the result for review before it becomes part of the saved earnings history.
Supported document templates can run targeted recognition passes for fields such as tip amounts. Those working passes do not replace the original image stored with the record.
Portable backup format
Gratuvia encrypts a portable backup before the file leaves the device. AES-256-GCM protects the backup contents, and the recovery key is kept separate from the encrypted file.
You choose the storage location. Saving the encrypted file to iCloud Drive, Google Drive, Dropbox, OneDrive, a NAS, or another provider does not give Prokvik the recovery key.
Optional online features
Future releases can add optional account, sync, or backup services. Those services are not required for the current local tracking workflow.
If a new feature sends a new category of personal data to Prokvik or another provider, the Privacy Policy and the related in-app disclosure will be updated before that feature depends on the new processing.
Limits of the security claims
No app can promise perfect security. Gratuvia does not claim to be unhackable. We also do not describe the system as zero-knowledge or end-to-end encrypted unless the implementation and a security review support those exact terms.
Security reports
Email security or privacy reports to admin@prokvik.com. Include the Gratuvia version, device model, and steps that reproduce the problem when those details are available. Do not attach a pay stub or tip-slip image unless the file is needed to show the issue.