Keevia Privacy Policy

Effective / Last updated: October 8, 2026 Developer / operator: MokaIO Application: Keevia — Personal Product & Ownership Records Android package: com.mokaio.keevia Official website: https://mokaio.store Privacy contact: support@mokaio.store Public policy URL: https://mokaio.store/privacy/keevia

1. About this policy

This policy explains how MokaIO handles information when people use Keevia, an application for documenting products they own, their purchase evidence, warranties, returns, maintenance, repairs, claims, household inventories and related ownership records. Keevia is designed to work locally without requiring an account for basic use. Some optional features may use an online account, cloud synchronization, sharing or third-party services. Availability depends on the released version and the features you choose to enable.

This policy concerns Keevia. Other MokaIO products have their own product-specific policies.

2. Information you provide

Depending on how you use Keevia, your records may include:

• Product details: brand, model, identifiers and serial numbers, purchase date, price, currency, merchant, condition, location labels, warranty/return dates, maintenance and repair history.
• Documents and media: receipts, invoices, manuals, warranty cards, product images, labels, barcode/QR contents, claim evidence and related files. Such files can incidentally contain names, addresses, order IDs, partial payment information or other personal details.
• Household and sharing details: names or labels you assign to households, rooms, members, collaborators, ownership or public-passport shares and permissions.
• Account details if you register: email address, account ID, authentication-provider metadata and security/session information. For Google sign-in, the authentication provider may share limited profile/account information needed to sign you in.
• Communications you send to MokaIO support, including contact details, correspondence and attachments you choose to provide.

Do not upload material you have no right to use or share. Avoid storing full payment-card numbers, passwords, security codes or other unnecessary secrets in product records.

3. Local-first processing and device permissions

Keevia's basic product library and supported capture workflows are designed to operate on your device. The app can request access to the camera for receipts, product labels and barcodes, and request access to individual images or files that you select for import. Supported on-device OCR and indexing may analyze selected content to generate editable product information.

Merely granting camera/file access does not mean Keevia uploads your entire photo library or documents to MokaIO. Imported content and generated records remain locally stored unless you choose a cloud or sharing operation that needs data to be transmitted. Android may also expose notification permissions for local reminders.

4. Optional accounts and cloud synchronization

If you create an account or enable supported cloud services, Keevia uses Supabase infrastructure for authentication, database, storage and functions. The service may process account identifiers, device/sync metadata, record identifiers, access-control metadata, encrypted or otherwise protected synchronized content, document storage objects, sharing metadata and operation/audit records necessary to provide the features.

Keevia uses local storage and supported encryption mechanisms for sensitive records and backup/sync workflows. Encryption design varies by data type and processing path. Do not assume all metadata is end-to-end encrypted, that all information is invisible to servers, or that recovery is possible without the necessary keys. Certain account, routing, quota, authorization and transaction metadata must remain processable by the service. We do not promise that every feature can run without any server-side processing.

You should store recovery material securely and maintain an independent backup of important documents where appropriate.

5. Product identification, OCR and intelligence

Keevia may recognize text, product labels, barcodes and documents on your device. Product matching, warranty/return information, manuals, recalls or answers from optional intelligence features may use curated external/public sources or additional services, depending on availability and your selection. We aim to distinguish verified-source information, user-provided information and estimates. Such results can be incomplete or incorrect and must be checked with the original manufacturer, retailer or official source where important.

If a future feature sends content to an external processing provider, the app should disclose that processing and applicable controls before use, and this policy will be updated if necessary. The present policy does not assert that a particular paid AI provider is already active.

6. Public passports, sharing and other users

If you create a public product passport, claim share, transfer invitation or other sharing link, Keevia may make only the selected or authorized information accessible to recipients. Do not include addresses, full serial numbers, unredacted receipts or other sensitive details unless you intend to disclose them and the feature permits it. Revoking a link can prevent future authorized retrieval through Keevia, but cannot erase content another person already downloaded, copied, photographed or otherwise retained.

Shared households and repairer/collaborator workflows may expose permitted product and history information to people to whom access has been granted. Access depends on the roles and permissions configured for that feature.

7. Billing and purchases

If paid features are offered, purchases may be processed by Google Play or another applicable platform store. RevenueCat may be used for subscription/entitlement management once configured and enabled. Keevia may receive purchase state, entitlement identifiers and transaction metadata needed to recognize access. We do not need your full payment-card number for standard store purchases. Billing integration and individual plans must not be described as available until they are actually enabled in the applicable release.

8. Diagnostics and communications

Keevia's current design includes privacy-conscious local, opt-in diagnostics. Diagnostic event summaries can be generated without automatically transmitting raw receipt text or full document contents to MokaIO. Information you deliberately send in a support report or email is received and processed for support and security purposes. Operational server logs may record request times, errors, IP-related connection metadata or security events as necessary to operate and protect hosted services; avoid inserting personal documents or secrets into logs.

We do not sell Keevia users' personal information, and Keevia is not designed to show third-party behavioral advertising.

9. Why information is processed

We process information as appropriate to: provide and improve Keevia's requested features; create and secure accounts; synchronize authorized records; create requested exports and shares; manage permissions and eligible entitlements; detect abuse and maintain reliability; respond to support/privacy requests; and comply with applicable legal obligations.

Where privacy law requires a legal basis, it may include performance of requested services, legitimate interests in security and service operation, compliance with law and consent for processing that legally requires it. Available rights and legal bases depend on your location and the particular processing.

10. Service providers and disclosures

Depending on the feature, information may be handled by infrastructure and service providers such as Supabase; Google for Android, Play services, authentication or purchases; an email delivery service for verification/support; and RevenueCat if paid entitlement processing is enabled. Those providers operate under their own terms and privacy notices where applicable.

We may disclose information when reasonably necessary to provide a feature you initiated, respond to lawful requirements, protect security and rights, or handle an authorized business transition subject to applicable law. We do not publish private product libraries by default.

11. Retention and deletion

Locally stored products and documents generally remain on the device until you remove them through supported app/device controls, clear Keevia app storage, uninstall the app (subject to operating-system backup behavior), or restore/replace local data. Deleting your Keevia cloud account is designed to preserve the separate encrypted local library on the current device while detaching the deleted account from future cloud sync; it is not a command to wipe the local device library. If you wish to erase local records too, use available local data controls or Android's app-data removal options after safely exporting anything you need.

For a successfully verified account-deletion request, Keevia's backend is designed to delete or de-identify applicable MokaIO-controlled account data and authorized cloud artifacts. Some records may be retained for a limited period when needed for legal obligations, fraud prevention, security, backup lifecycle, disputes or audit integrity; such records should not remain available as ordinary active account data. Independently retained copies held by recipients or third-party services are not automatically erased.

See: https://mokaio.store/delete-account/keevia

12. Data security

We use security controls appropriate to the system, including access controls, row-level database policies, private storage access, authentication, encryption in applicable workflows and restricted sharing. No storage, network or software system can guarantee absolute security. Keep device lock protection enabled and safeguard account credentials and backup recovery keys. Report security concerns to support@mokaio.store with the subject SECURITY — Keevia.

13. International processing

Cloud service providers may process information in countries outside your own. Where required, applicable legal safeguards and service-provider protections govern such transfers. Local-only use can reduce cloud data processing but does not prevent external processing that you explicitly initiate.

14. Your choices and rights

Depending on applicable law and the services used, you may be able to access, correct, export, restrict or delete data and object to certain processing. You can choose not to register for supported local-only use, decline optional cloud processing, revoke shares, manage notifications, and request account deletion. Contact support@mokaio.store with Keevia Privacy Request in the subject; we may require reasonable verification before disclosing or deleting account-related data. Do not email passwords, access tokens or recovery keys.

15. Children

Keevia is a general-purpose ownership-record utility and is not designed to solicit children's personal information. A parent or authorized adult should supervise any use involving a minor's records and comply with applicable age and consent requirements.

16. Changes

We may update this policy when Keevia's features, providers or legal requirements change. The published version will show its effective date. Material changes will be communicated as required by applicable law.

17. Contact

MokaIO — Keevia Privacy Email: [support@mokaio.store](mailto:support@mokaio.store?subject=Keevia%20Privacy%20Request) Support: https://mokaio.store/support/keevia Account deletion: https://mokaio.store/delete-account/keevia