Privacy policy for the hiClient mobile app

This policy describes data processing in the hiClient mobile application for Android, identified as com.hiClient.app on Google Play and com.hiclient.mobile in the direct APK. It is separate from the website and commercial service policy.

Mobile privacy policy, edition 5 of November 11, 2026.

1. Responsibility, purpose and contact

hiClient provides an app to manage your profile, register with businesses, present access credentials and communicate with them. The hiClient provider is responsible for data processed by its account, connection, security and support services. Each business is responsible for the records and processing in its own installation, including its access decisions. Accepting this policy does not replace a business's specific consent or authorize registering another person.

You can consult the provider's details through the public resource Provider details without registering. For privacy questions, rights requests or deletion requests from outside the app, use the contact email published at Support and contact or at the end of this policy. You do not need a paid subscription.

2. Profile and data you choose to share

Names, contact details, profile fields, photographs, additional identities, business credentials and conversations are stored with protection on your phone. No automatic copy of this vault is created in a hiClient cloud account. You can move it to another phone using the encrypted transfer flow, with verification on the source phone.

When registering with or updating details at a business, you choose what information to send; the request and its photo are encrypted for that recipient. The copy the business receives is managed separately from your profile. Changing local details does not silently update every business's copy. The hiClient server does not receive the record in readable form.

3. Facial captures and phone verification

If a business offers facial recognition and you authorize that use, the app can guide you through capturing images of your face from the front and while turning. It sends them encrypted exclusively to that business, whose computer analyzes the capture and, if it accepts enrollment, stores a biometric template, up to three small photos and the last ten matches with the record. The business must explain its purpose, conditions and retention and provide the mechanisms required by law. hiClient does not use these faces to train models and cannot read them on its intermediary server.

The server issues a signed challenge and retains evidence of the policy the account accepted, including language and date. If device verification is enabled, it also receives a phone key certificate and integrity information such as boot state, patch level and app signature; it does not receive images or recognition results. The biometrics Android uses to verify the owner remain within the operating system: they are separate from the business's facial recognition.

4. Messages, calls and posts

Private messages and attachments are encrypted for their recipients. Our server can relay connections and temporarily store already encrypted requests and messages for an offline business; it knows the sending account, destination business, size and dates, but not the content. Calls and video calls require acceptance; they use encrypted signaling and may require a media relay. The other participant receives the audio or video you share, and the connection may reveal network addresses to the endpoints or relay infrastructure.

Public business posts are handled differently: the server stores and distributes text and media the business authorized for public distribution. Reading them does not make your records, conversations or private lists public.

Promotional email requires separate, optional and explicit consent through an initially unchecked box. We retain the date, source and consent wording. You can revoke consent in your profile or through the one-click unsubscribe and visible link in each promotional email, without signing in. We retain the minimum suppression record needed to honor opt-outs and prevent sending to addresses with permanent bounces or complaints. Opting out of promotions does not prevent requested transactional messages or security notices. We do not send cold outreach through SES or hiClient campaigns.

5. Account, security and access activity

The mobile account uses a random identifier and a verifier of its credential. If you configure authorization by email or an authenticator app, the server stores the email or corresponding secret with protection, together with attempts, lockouts and verifications. It also records the versions, language and date of the legal texts you accepted.

When you use an access QR, the business's authorized computer can send the mobile account, business and device identifiers, date and access outcome. This mechanism does not send names, identity documents, photos, templates or local record identifiers. Other businesses receive only, where applicable, a summary in bands of account age and days with prior activity: no visited businesses, individual dates or other businesses' denials. This represents account continuity; it does not establish civil identity or decide access by itself.

6. Diagnostics and telemetry

To find faults and improve operation, the app may send events from a closed vocabulary about capture, calls, notifications and connections; numerical timing, count, approximate turn and quality metrics; random session identifiers; app and operating system versions; and the phone's make and model. These are associated with the mobile account. They do not include names, messages, photos, templates, phone numbers or business or record identifiers. This telemetry can be disabled on the server or in the app build.

Error reports include a random reference, technical category, version, operating system, architecture and up to twelve positions of functions in hiClient's own code; they do not include exception messages, values, paths, arguments or secrets. They may remain in a bounded local queue until they can be sent. Network infrastructure also processes the IP address and connection metadata needed to deliver the service and prevent abuse.

To diagnose failures, supported clients also send the distribution channel, technical application state and up to 20 recent actions with their origin, result and relative time. The trace omits arguments, personal identifiers, record counts and recognition counts. If you report a problem, we receive the category, the optional description you enter and your preference for contact at your account email address. Please leave names and personal information out of the description. Administrators can review these reports for 30 days.

Error and failure reports also include closed-vocabulary technical signals to diagnose each component: brand and model of the computer or phone, processor, graphics adapter and its driver, architecture, system edition and build, component versions (for example WebView and Flutter), memory, free storage and load in ranges, screen size and density, theme, system language, region and time zone, network type (Wi-Fi, mobile or wired), whether it is metered or has data saver on, whether Google Play services are available, link, license and plan status, outcome and delay of the latest connections with the server, status of the messaging channel and of calls, cameras in use and their frame rate, camera, microphone and notification permissions, battery optimization and charge level, push notification status, pending queues and the latest error codes. The mobile app adds the names of its latest 40 operational events and the random identifier of the telemetry session. These signals do not include the computer or user name, serial numbers, IMEI, advertising identifiers, Wi-Fi network name, IP addresses, data about people, messages or images, and they are not shown in the form. They are kept for up to 30 days like the other diagnostics.

7. Permissions and background functions

The camera is used to scan QR codes, take captures you authorize and make video calls; the microphone is used for calls. Files or images you select are used for sharing in the chosen feature. Notifications alert you to messages or calls; Android may maintain a foreground service and display call alerts on the lock screen. An alert does not authorize answering or enabling the camera or microphone. Operating system biometric verification protects certain local actions.

You can change permissions in Android Settings. Denying them prevents the functions that need them; it does not imply accepting other processing. The app does not request general access to your contacts or precise location.

8. Recipients and providers

Data recipients include the businesses and participants you choose, authorized service staff, and necessary hosting, network and support providers. Cloudflare helps deliver and protect connections; Brevo delivers email codes if you use that factor. When push notifications are enabled, Google Firebase Cloud Messaging processes an installation token and a generic message or call notice, plus technical delivery information. The notice does not contain chat text, images or biometric data. Google Play distributes and updates the app under its own terms.

These services may process metadata outside your country. You can request information about recipients and applicable transfer safeguards through the privacy contact. hiClient does not sell your data or use behavioral advertising in this app. It may disclose information where required by a legal obligation or valid request.

Amazon Web Services provides email services through Amazon SES (sending and receiving), S3 (temporary message storage), SNS (notifications) and SQS (queues), in us-east-2, Ohio, United States. These services process email addresses, message content and delivery metadata. Brevo remains a backup provider during the transition.

Processing in the United States involves an international transfer when you are in another country. You may request information about contracted entities and applicable safeguards through the privacy contact.

9. Retention

The profile and histories on your phone remain until you delete them, subject to the app's storage limits. Account data and acceptances are retained while the account exists. Continuity records have a 180-day window. The content of encrypted requests and messages kept for an offline business is deleted when delivery is acknowledged or by periodic cleanup after its original retention period expires, at most seven days from receipt. Content-free metadata is cleaned up when that same period expires; delivery does not restart it. Phone verification verdicts are valid for seven days.

Technical diagnostics are retained for up to 30 days. Operational telemetry has configurable retention of up to 90 days; the distributed configuration specifies 30. Deleting the account also deletes its telemetry and legal acceptances. Business data, external services and their backups have their own policies. Any legally necessary retention should have its purpose and period disclosed and its use restricted; account suspension is not presented as deletion.

10. Deletion, consent and rights

In the app you can edit your profile, manage links, request deletion of the mobile account and erase the phone's data. Revoking a link sends a request to the business; if it cannot communicate, check the pending state and contact that business. Local deletion or uninstalling does not prove the business received the request and does not by itself erase its exports or backups. The option to erase only this phone after a transfer retains the account and links on the destination phone.

You can also request account or data deletion from outside the app using the public email at Support and contact . State that your request concerns hiClient mobile and provide only what is needed to locate it. Do not send faces, passwords, codes or credentials. We may request proportionate identity verification. For a record or biometrics stored by a business, contact that controller: hiClient does not have remote access to its database.

Depending on applicable law, you may exercise access, copy, correction, erasure, objection, restriction or portability rights and withdraw consent without affecting prior lawful processing. You may complain to the competent data protection authority.

Account and data deletion

The public Delete account or data channel lets you start a request without reinstalling the app or holding a subscription. There are two options: delete the mobile account and its data, or delete data while keeping the minimum information needed for account access. In the latter case, account identifiers and credentials, authentication factors, security controls and minimal case evidence remain. Sharing data again requires a new action and authorization.

Receiving an assisted request does not establish identity or authorize deletion. An email address, reference, link or record ID is insufficient. Confirmation must be bound to the verified subject and the reviewed scope. Tracking can continue after account closure through access limited to the case.

Automatic coordination is enabled only with reviewed policies, operational configuration and compatible versions. Companies receive only their own destinations; their privacy panel does not require an active subscription or acceptance of a new commercial edition. Retention requires an enabled policy, categories, grounds, a responsible person and an end condition; it does not authorize continued use for other purposes. List membership alone does not establish an exception.

Account closure, business receipt, execution and verification are separate milestones. Offline devices, incomplete coverage, retention, errors and outstanding backups or copies are reported separately. Managed copies must reconcile deletions before restored use; a custodian’s declaration about exports or external copies is not remote technical verification. The software does not establish forensic physical erasure or detect unknown copies.

The case retains opaque references, decisions and minimal evidence under restricted access and its own retention policy; chat message expiry does not govern it. These records and marks that prevent reappearance remain protected data, not anonymous information. Applicable policy and deadlines are shown when determined; an issue or reconnection does not restart original receipt.

11. Data protection

The app uses encrypted local storage and system-protected keys, HTTPS connections and authentication of operations. Private exchanges with businesses are encrypted for their recipients; credentials must not be shared. These measures do not eliminate all risks and are not presented as an independent cryptographic audit. Protect your phone's lock and keep the app and operating system updated.

12. Children and additional identities

Creating an additional identity does not establish legal representation or authorize registering a child or another person. Anyone acting on their behalf must have the appropriate authority, and each business must assess applicable rules and the need for processing. Facial recognition is probabilistic and must not be the sole basis for decisions with significant consequences.

13. Changes to this policy

The mobile policy and its date are available at Privacy policy for the hiClient mobile app and in the app's privacy reader. Acceptances are linked to the content and language shown. Material changes will be communicated by an appropriate means and will require renewed acceptance where appropriate; a text change does not replace specific consent required for new processing.

Support and contact · Terms