Privacy policy

Scope and publisher

This policy covers Zawid Accounts, the official website, and related optional subscriptions, connected assistance and support. It also covers earlier activation or licensing records where they exist. Starting a 7-day trial requires an email account and the disclosed trial information, but no payment method. After expiry, adding and editing requires active access; reading, export and backups remain available.

Publisher and contact details are those shown on the About and Support pages. An external website or app follows its own policies when you choose to open it.

Local records and files

Customer and supplier records, transactions and reports you enter are designed to be stored on your device or in files and backups you create. Details can vary by app and operating-system version. A PDF or backup shared through another app is then also subject to that destination’s handling.

Core accounting can work without a connection. This does not mean that every optional feature sends nothing: billing, messaging, connected AI, advertising and diagnostics have the separate flows described below.

Subscription accounts and payments

We process the subscription email, account identifier, verification and session information, store product identifiers, purchase tokens, order reference, entitlement status and purchase, expiry, renewal and refund information needed to verify access. Older licensing records may include an installation or ledger identifier and activation code.

The store processes payment. Zawid’s server does not receive your card number or security code. A sign-in verification code is sent to the account email. Purchase verification does not require uploading your accounting database, customer names, invoices, balances or backup files.

Restoring a purchase does not restore your ledger. Connected-AI, messaging and usage-collection choices remain separate from buying Pro. Account information and purchase records help manage access and prevent the same purchase being used by different accounts.

Optional messages and device notifications

App messages and offers are off by default. Opting in registers a random installation identifier (UUID), app version and language, recent activity and delivery/open receipts. A verified subscription account can be linked when signed in, allowing relevant audiences such as Free or Pro. This does not upload your ledger, customer list, invoices or balances.

Device notifications are a separate choice. Enabling them can request operating-system permission and provide a Firebase Cloud Messaging (FCM) token for delivery. You can use the in-app inbox without enabling device notifications. Text may appear on a lock screen.

Provider acceptance does not prove delivery. Receipt and open confirmations describe app events, not proof that someone read every word. Disabling messages stops new collection and queues an opt-out if offline; delivery can continue until the server receives the change. Disabling alone does not erase past records.

The Delete communication data action removes this installation’s message registration and delivery records after synchronization. It does not delete the ledger or cancel a subscription. Campaign records can retain original and anonymously erased recipient counts.

Trial information and contact

The app has no ads. To activate an available trial or submit a direct subscription request, enter your name, phone with country code and optional business name. Continuing accepts the terms and privacy policy and sends the form to Zawid for trial, subscription and support management. Activation requests include the requested plan, reference and review status. Opening WhatsApp is optional and user-initiated, with a draft containing the request reference; it is not sent automatically.

The activation form does not collect phone model, manufacturer, OS or app version. It does not read contacts or your phone number automatically, or collect IMEI, serial numbers or advertising IDs. Your ledger, customer names and balances are not included. Technical information from earlier registrations may remain until subscription account deletion.

Activation does not grant marketing consent. Renewal offers and marketing require separate consent, which remains off for new registrations. Existing consent can be withdrawn from the subscription page. Consent and timestamps are recorded; form details are not sent to app analytics.

Authorized subscription administrators can view this information, trial status and contact consent, and grant access manually with an audit record. You can request account deletion from the subscription page. Granting or revoking manual access does not cancel a store subscription.

Website advertising is separate from the ad-free app. See the cookie policy for website providers and choices.

Optional usage and crash information

The app includes Google's Firebase Analytics and Firebase Crashlytics services to measure product usage and stability. In version 1.2.4-test.2 and later, collection is enabled automatically when no preference has been saved; any previous opt-out is preserved. You can turn off App improvement under Settings, About the app, Privacy. Earlier versions had both services disabled by default.

The application is designed not to attach customer names, phone numbers, monetary amounts or ledger content to these events. Turning the option off stops future optional collection; it does not claim to delete data already processed by a provider. This choice is separate from advertising consent and connected AI.

Ask Zawid and connected AI

Local calculations use recorded data. Optional online wording and questions use the Zawid gateway and Google Gemini after separate consent. A minimized, sanitized context can be sent; this is not a promise that nothing is sent to Google.

The app is designed to remove customer names, contact details and identifiers from the AI request. It shows the sanitized free-text question before sending and refuses a question reduced to redaction markers. Review that preview rather than inserting sensitive information. AI assistance is read-only and does not save ledger transactions on its own.

Provider processing depends on its current service terms and whether the service uses a paid or unpaid tier. Google’s unpaid tier may use submitted content to improve its services. Connected requests have limits and can be unavailable. You can disable the feature without losing local accounting.

Reporting an inappropriate answer sends limited metadata such as the feature, reason, model, language, timestamp and an anonymous installation token, not the question, answer text or customer content.

Device permissions

Permissions are used for the features you choose, such as selecting or saving files, generating notifications or using device voice input when offered. Voice-input processing can depend on your device’s speech service. Do not assume audio remains entirely on the device unless that service confirms it.

You can manage Android permissions in system settings. Denying one can affect its related feature without converting local accounting into a paid requirement.

Website, support and operational records

Support receives the contact details, problem description and attachments you choose to send. Share only what the request needs. Hosting systems typically process IP addresses, timestamps, requested paths and browser information for operation and security; retention can depend on the provider and security requirements.

The site records limited first-party page/download activity separately from optional app telemetry. Where an external translation or support channel is opened, its provider can process the URL or information you submit.

Storage, security and retention

Protect the phone and keep recoverable backup copies. Current portable .zawid backups are not encrypted by default: anyone with file access may read the data. Protect the destination and external copies. Older encrypted backups require their original password, which cannot be recovered if lost. Transport security and access controls reduce risk but no system can guarantee absolute security.

Data needed for operation, purchase verification, support, legal obligations or fraud prevention can be retained according to the purpose and applicable circumstances. We do not publish a universal retention duration for all hosting or provider records. Inactive messaging installations stop qualifying for new campaigns after the configured activity period; campaign visibility is time-limited.

Deletion and your choices

You can remove records locally or erase the app’s Android storage. Backups, PDFs and files shared elsewhere need separate deletion. Uninstalling the app does not remove every external copy or server-side subscription record.

Request subscription-account deletion from the subscription screen or contact support from the account email; identity verification may be required. Necessary purchase records may be retained for obligations or fraud prevention. Account deletion does not cancel store renewal: manage that separately in Google Play.

Do not send a password, verification code or secret purchase token to support. Use the deletion page for the relevant path and the support page for questions or corrections.

Contact Zawid

Email shehab.mohammed.dev@gmail.com with a short description. Do not send a password, verification code or an unredacted ledger.