Digital Asset Privacy Policy

For Digital Asset version 7 and the upgraded account service. Updated 16 September 2026.

Digital Asset is operated by Christos Malliarakis. For privacy questions or requests, contact malliarakis@gmail.com.

What Digital Asset does

Digital Asset provides a shared workspace for virtual credits. These credits have no monetary value, cannot be purchased or cashed out, and are kept separately from any external blockchain account. An internet connection is needed to use the account service.

Try the app without an account

The optional demo opens a connected guest wallet without an email address or password. The service creates an anonymous account identifier and gives that wallet 1,000 virtual welcome credits once. Its profile, balance, saved people, transfers and notes are stored in the shared database. Guest transfers change registered recipients’ virtual balances; recipients can see the guest name, handle and transfer details. Authentication access is saved in the app on your device (or in local browser storage for the web version). Exit demo keeps that access so reopening resumes the same wallet, balance and history; there is no reset or automatic refill. Clearing app data or uninstalling may lose access, and a guest wallet cannot be recovered by email. Export your records or delete the wallet in Settings before doing so. Guest wallets have no administrator or blockchain API access and are not included in the verified-member directory. An internet connection is required for guest wallets. The built-in educational lessons work offline; opening an optional documentation link visits that external website.

Information used to operate your account

• Your email address, account identifier, display name, handle, verification status, role and account status.
• Authentication records managed by Supabase Auth, including protected password credentials if you choose a password, sign-in sessions and administrator authenticator enrollment.
• Virtual-credit balances, your one-time welcome-credit grant, sender and recipient identifiers, amounts, dates, request references and any transfer notes you enter.
• Members you save as frequent recipients, and records of administrator actions such as credit issuance and membership changes.
• Technical security and service logs processed by our hosting and authentication providers, which can include IP addresses, approximate city or country inferred from an IP address, app/browser session identifiers, browser or device metadata, request status and diagnostic information. These logs support security and troubleshooting; the app does not obtain GPS location.

We use this information to sign you in, maintain a reliable shared ledger, prevent unauthorized or duplicate operations, manage membership, and respond to support and privacy requests. The legal bases are providing the service you request and our legitimate interests in security, reliability and preventing abuse; legal obligations may also apply.

Community rules, blocking and reports

We store the version and date of your community-rule acceptance, members you block, and any reports you submit. A report includes the reported profile, the selected received note if applicable, your reason and optional details, the involved account identifiers, and its review status. Reports are private to the reporting account and authorized administrators; they are not displayed to the reported member. Administrators can remove reported text, reset a reported profile or suspend an account, with an audit record. These actions do not change recorded credit amounts. Blocking hides the other member’s content in your workspace and stops further transfers between you.

Who can see information

Signed-in members, including guests, can browse or search the list of active, email-verified members, including your display name and handle, and see the details of transfers they participate in. Your email address and authentication credentials are not shown in member search. Administrators can manage profiles and balances and review credit operations and audit records.

Supabase provides the database, authentication and server functions. The project is configured in Frankfurt, Germany. Service providers may process operational or support data in other locations under their applicable data-protection arrangements. Email delivery providers process the address and authentication message needed to deliver verification or password-reset emails. Support email is handled through the operator’s email service.

We do not sell personal data. The upgraded mobile app contains no advertising SDK or advertising-identifier collection, Facebook sign-in SDK, or Firebase SDK. It does not request access to your phone contacts, photos, microphone, camera or precise location.

Optional original blockchain integration

The original integration with api.banan.es is preserved but disabled and unconfigured in the upgraded service. In virtual-credit mode, credit transfers do not contact that API. Before enabling external operations, the operator must verify the connection, account ownership and applicable requirements.

If enabled, linked account identifiers and country, your verified email for account registration, and the sender, recipient and amount for a requested external transfer may be sent to that provider. External request status and reconciliation references are stored separately. External or blockchain records may be outside our control and may not be erasable. Virtual credits are never automatically converted into external funds.

Storage, export and deletion

Account and credit records remain in the shared database while your account is active. You can edit your name and handle and export your records in Settings. A native export creates a temporary private file for the device share menu; the app clears it at its next cold start or sign-out and overwrites it on the next export. Copies you choose to save or share remain under your control.

Deleting your account removes your login, profile, saved people, linked-account mapping and your own stored external requests, and forfeits your virtual credits. Your authored virtual-transfer notes are removed. Your community-rule acceptance, blocks you created, and reports you submitted or that identify you as the reported account are removed with your account. Moderation audit references may remain without the reported text. Shared virtual-transfer amounts, dates and opaque identifiers remain for the other participants’ history and ledger integrity while the workspace operates. Records of another participant’s external requests may also remain. Previously shared exports and external provider records cannot be recalled by deleting the app account. Security logs may remain for the providers’ limited operational retention periods or where required by law.

Uninstalling the app does not delete the shared account. See account-deletion instructions. Administrators must arrange ownership transfer with support before their own account can be deleted.

Your choices and rights

You can request access, correction, deletion or restriction, obtain a copy of your data, or object to processing based on legitimate interests where applicable. Contact the address above from your registered email. For a guest wallet, include its handle or account identifier and use the app’s Settings while you still have access. We may need to verify account ownership. Never email your password or authenticator codes. You may also complain to your data-protection authority; in Greece this is the Hellenic Data Protection Authority at dpa.gr.

Website and policy changes

These support pages are hosted on drtomcat.gr. Visiting the website involves its own hosting logs and cookies; the mobile account database is separate from WordPress. This policy applies to the upgraded Digital Asset service and does not claim that unavailable records from the discontinued Firebase service have been recovered. Material changes will be reflected here with an updated date.

Support & sign-in help · Privacy policy · Delete your account