Privacy Policy — Pocket Invoice: Invoice Maker & Manager
Effective and last updated: 25 October 2026
Developer: Sakhi Solution
Application package: com.pocketinvoice.app
Privacy contact: contact@sakhisolution.com
Scope and the difference between content and technical data
This policy explains the app’s core on-device processing, technical services, user-initiated sharing and privacy choices. On-device content processing does not mean the application has no network activity or that technical data cannot leave the device. Practices can vary between app versions and enabled service components.
App content and on-device processing
Business profile details, client records, items, prices, taxes, invoices, estimates, receipts, payment status, signatures and PDF generation are handled on the device for the core app features. Local document storage is not represented as an encrypted vault.
The core features described here do not require creating a developer-hosted user account. An app lock, local profile or master password is not a cloud account.
Technical analytics and crash reporting
The app integrates Google Analytics for Firebase and Firebase Crashlytics. Measurement and diagnostic collection are enabled in its current configuration. These services can process app-instance or installation identifiers, app and device/operating-system information, usage and screen events, crash traces, error context and related network metadata to measure app use and diagnose reliability problems. This technical service processing is separate from the core content processing described above.
Do not assume that clearing local app records also deletes technical information already received by these services. No policy statement here says that all app data remains on the device.
Advertising SDK components
The app also includes Google Mobile Ads SDK components. Where its components initialise or operate, the SDK can process network/IP information, device or advertising identifiers, app interactions and diagnostics for advertising, measurement and fraud prevention. Whether ads are shown, and the available consent or advertising controls, depend on the app build, service configuration and region. Inclusion of these components is not a promise that an ad is displayed in every app session.
Google privacy information: https://policies.google.com/privacy
Firebase privacy information: https://firebase.google.com/support/privacy
Google Mobile Ads data information: https://developers.google.com/admob/android/privacy/play-data-disclosure
Device access and permissions
File pickers and sharing controls support importing or exporting supported documents and business images. Notifications may be used for the reminder features you enable.
SDK and system-library permissions may also be included in the installed app. Device settings allow you to review and revoke supported permissions. A feature that requires a permission may stop working if that permission is denied.
App-specific network requests and sharing
The PDF font library can download a font when it is not cached, which sends a request and network metadata to its provider. A PDF, CSV or backup only goes to a share destination when you choose one. A payment URL you include in a document is handled by the payment provider when opened; the app’s document-generation feature is not itself a payment processor.
Your device’s backup, file-provider, browser, sharing and operating-system services have their own privacy practices. Data you intentionally send to another service is subject to that service’s handling.
Retention, deletion and privacy requests
Local app content is retained until you remove it, clear app storage or uninstall, subject to the device’s own storage and backup behaviour. Delete documents and clients with available controls, clear app storage or uninstall to remove the app’s local records. Exported PDFs, CSVs, signatures and backups held elsewhere must be deleted separately.
Google/Firebase technical records are retained according to the service’s retention rules and the developer’s service configuration. Contact contact@sakhisolution.com to ask about the current retention configuration or request access, correction or deletion where available. We may need limited information to identify relevant technical records; do not send sensitive app content, passwords or financial/health records unless a specific, secure process has been agreed. Requests are assessed against available identifiers and any applicable retention obligations.
If you contact support, we receive the information you provide and use it to address the request. The contact mailbox forwards messages to the developer’s monitored Gmail inbox.
Security
Core processing is performed on the device as described above. Protect your device, app locks and exported files. Technical-service communications use the protections supplied by the relevant SDK and provider. No transmission or storage system is guaranteed to be completely secure.
Children and families
This app is not offered as a service specifically directed to young children. If a parent or guardian believes a child has provided personal information through technical services or support, contact the privacy address above so the request can be investigated. The app’s current store audience information should be checked before use by a child.
Changes and contact
Updates to app features, SDK configuration or data practices may require a policy update. The date above identifies this version. Questions and privacy requests: contact@sakhisolution.com.