1. Who this policy covers
CashKitab is a business cashbook and ledger product developed by ByteFlares. This policy covers the CashKitab Android app, related account and sync services, and this website. For a privacy question or request, email [email protected] or call +92 310 7337066.
CashKitab is intended for business record keeping. When you enter information about a customer, supplier or team member, only enter information you are authorized to use.
2. Information the service processes
- Account information: name, email address, sign-in provider, optional profile image, preferences, authentication and session records. Password-based accounts use a password-verification process; never send your password to support.
- Business records: business and book details; people and contact details you enter; transaction amounts, currency, dates, notes, categories and payment methods; invoices, items, payments, reminders, limits and repeating-entry settings.
- Files you choose to add: receipt images, other supported attachments, voice notes and support attachments, depending on the feature used.
- Operational and diagnostic information: device and app information, sign-in/session identifiers, push-notification tokens, service request details, usage events, crashes and error diagnostics, according to the services enabled in the app.
- Support information: the contact details, messages and attachments you choose to send by email, phone, WhatsApp or in-app support.
Records can be stored on your device and synchronized to service infrastructure. A record being available offline does not mean it is never sent to a server.
3. How information is used
Information is used to operate accounts, save and synchronize records, provide shared-business access, prepare documents and reports, deliver notifications, respond to support requests, investigate errors and protect the service against misuse.
If you request server-based insights, relevant business-record information may be processed by the configured AI service to prepare that response. Such online features need a connection. Review generated suggestions before relying on them.
Exporting or sharing a statement, report or invoice sends the selected information to the destination you choose. Check the recipient and document before sharing.
5. Device permissions
Depending on the features you use, the app may request camera or photo access for receipts and attachments, microphone access for voice notes, notification permission, and access needed to save or share files. Use your Android settings to review or change permissions. Some related features may stop working after a permission is withdrawn.
We use account authentication and access controls to restrict service access. Network service connections use HTTPS. No storage or communication system can be guaranteed completely secure.
6. Retention, account closure and erasure
Active account and business records are retained to provide the service and the record history you use. Exported files and copies you share can remain in the locations and recipient apps you choose.
The current in-app flow schedules account closure after a 48-hour grace period. Closure disables the active login and retains an account/business recovery archive. Closing the account does not automatically erase that archive or all business records.
To request permanent erasure of your account information, business records or retained archive, use the account and data deletion page or email us from the account email address. Support must verify ownership and clarify the scope, any records that must be retained and the applicable timeline. A fixed automatic archive-purge period is not currently published.
Shared-business records may involve other authorized users. We will review the request and explain what can be removed and any specific reason for retaining data. Uninstalling the app does not itself request deletion of cloud records. Removing app storage can delete local records, including changes that have not synced.
7. Your choices
You can manage supported profile preferences and device permissions, review access to shared books, use available export options, and contact us about access, correction or deletion of personal information. Tell us which account and records your request concerns; do not include a password or verification code.
CashKitab is not directed at children. If you believe a child has provided personal information through the service, contact us so we can review it.
8. This website and contact requests
This website does not include advertising trackers or analytics tags by default. Cloudflare, as the hosting and Worker provider, may process technical request information for delivery, security and abuse prevention.
The contact form submits your name, email address, inquiry type, subject, message and optional phone number to the business-suite Cloudflare Worker operated by ByteFlares. It creates a support ticket in the service database. The existing email queue sends a confirmation to the email you provide and a notification to the configured support team through Brevo, the email-delivery provider. The service uses technical request information, including an IP-based rate limit, to reduce abuse. You do not need an app account to submit this form.
Contact details and messages are used to handle the inquiry, provide follow-up and protect the service. No fixed automatic support-ticket purge period is currently implemented. Contact us to request access, correction or deletion of inquiry data. Do not include passwords, verification codes or unrelated customer information.
The separate account-deletion page prepares an email draft unless you choose to use the contact form. Preparing a draft does not send it or delete an account. Form values are not deliberately stored in this website's browser storage. External links, including email and WhatsApp, open services governed by their own policies.
9. Contact and policy changes
For questions or requests, email [email protected], call +92 310 7337066, or visit support. We may update this policy when the product or its data handling changes. The effective date above identifies this version.