Understand how
your data is handled.

1. Scope and controller

This page describes the LINKDGER mobile app offered under the LinkDit brand. Privacy questions can be sent to support@moavia.dev.

2. Information processed

Depending on the features you use, the app may handle account identifiers, phone number, profile details, contacts you choose to connect with, ledger entries, transaction disputes, business listings, chat messages, voice media, device-related security information and support communications.

3. Why information is used

We use relevant information to authenticate accounts, display connected ledgers, deliver messages, synchronize transactions, manage roles and permissions, enable purchases, improve reliability and respond to support requests.

4. Local data and server storage

Some records and delivered media may remain encrypted in local device storage. The current direct-chat voice delivery configuration temporarily saves AES-256-GCM encrypted media to Oracle server storage; server copies are cleaned up after confirmed delivery to a receiver's device. Undelivered voice files currently expire after seven days. Other categories of information may have different retention schedules.

5. Service providers

The service may use Oracle infrastructure, Google sign-in, Firebase/Google Play, AdMob and Google Maps where those components are enabled. Specific provider usage and data categories must match the final application build and its disclosures.

6. Permissions

Camera, microphone, notifications or location permission may be requested when a relevant feature needs them. You can manage app permissions through Android settings.

7. Sharing and connected records

Connected ledger participants may see information relating to their shared records. Business listings or communications may be visible according to their configured audience and permissions.

8. Retention and deletion

Requests for deletion or access can be made using the account deletion instructions. Some information may need to be retained temporarily for reconciliation, fraud prevention, dispute handling or legal reasons; those cases should be disclosed in the final policy.

9. Security

Security measures include access controls and encryption for relevant data. No product can guarantee absolute security. This statement does not claim end-to-end encryption for all message types.

10. Updates and contact

Practices may change as features evolve. This policy should be versioned and dated when approved for release. Contact support@moavia.dev for questions.