Privacy Policy

Who is responsible

Emiral Inc operates emiralX and emiralX Business. A corporation incorporated in Delaware, United States.

Business and mailing address: 14 Wall Street, 20th Floor, New York, NY 10005, United States. For support, privacy and account/data requests, email info@emiral.app, identifying the app and request. You do not need to reinstall the app to email us. Do not send passwords, sign-in codes, device keys or identity scans by ordinary email.

Applicable privacy and data protection laws govern the processing described here, including mandatory laws that apply where you live or use the service. Corporate registration is not a financial-services licence or regulatory approval of this app. Accepting service terms does not enable marketing or optional sharing.

Information used by each experience

The updated apps verify email ownership using a one-time code. This is not government identity or business-registration verification. A verified email can recover the same account in the same app on another phone; emiralX and emiralX Business keep separate accounts. Existing device-only accounts must prove control of their original device before adding a verified sign-in email. Public card/profile contact email is separate from the sign-in email. The Business shop-transfer feature transfers shop control between accounts.

Purposes and your choices

Core account, card delivery, invoice and reward operations use information needed to provide the requested service. Other processing requires an applicable legal basis, such as a specific legal obligation or your consent. Core processing is necessary to provide the service you request; optional processing uses the choices described below, subject to applicable data protection requirements.

Nearby visibility, the contact fields you share, shop contact sharing, shop insights and AMiN connection/sharing are separate choices. Before new signup, the apps ask you to accept the Terms & Conditions, acknowledge this Privacy Policy and confirm that you are at least 18. We record your account, the document versions and fingerprints, the time and the entry source. Business setup separately records authority and acceptance of the Business Terms. Agreement to terms does not itself authorise every optional use. Authentication emails use the account-verification provider; verification codes and provider refresh tokens are not stored by the apps. Provider access tokens stay on the server. After email verification the app may briefly hold an encrypted, session-bound enrolment ticket in memory to add a passkey; it is discarded after setup, sign-out or its ten-minute enrolment window and cannot be used directly with the authentication provider. Expired sign-in challenges are removed on subsequent authentication requests after a limited security window; this does not establish a general retention schedule for other data. You can withdraw the relevant sharing choice; that does not undo processing that was lawful before withdrawal or erase a recipient’s independent copy.

The reviewed landing has no advertising pixels or marketing signup. Marketing or new profiling purposes require their own appropriate notice and choice before activation.

Cards and returning your details

A card link can be opened by anyone who has it and can be forwarded. The page shows the fields the card owner made available. A recipient may save a contact file or, after previewing and confirming, send their own contact details to that owner. A reply is stored for the card owner to view in Received. Send only details you have authority to share.

Card interaction records include views, saves, shares, discovery channels and related account or pseudonymous visitor information. These are service analytics, not proof that a phone completed its final Contacts import. Removing or changing a card does not remove contact files, screenshots or details already saved independently by recipients.

Importing from a website or public LinkedIn page requests available public information and presents it for review. It does not give emiralX access to a private LinkedIn account. Brand images may be copied to the public image store for display on cards.

Optional Nearby, venues and events

emiralX uses a foreground approximate location only when you choose a Nearby check-in. Coordinates are rounded before storage; the service also records the purpose, chosen card, selected sharing fields and expiry. It does not request background location in the reviewed emiralX build. A venue or event can be joined by code.

Visibility expires after the chosen period or ends when you pause it. Expired sessions are excluded from discovery results; in the reviewed test service, clearing stored rounded coordinates occurs on a subsequent discovery request, rather than a guaranteed scheduled erasure time. Connection and safety records can remain after visibility ends. Other people do not receive your coordinates in a discovery preview.

Connections require approval. Block and Report are available. Dating is restricted to adults under the service rules; the current confirmation is not independent age verification. The dedicated Business variant does not request location or provide personal Nearby discovery.

Business verification and passkeys

emiralX Business collects the business registration or licence and the representative’s identity document through its private verification screen. If the representative is not named as the owner on registration evidence, an ownership extract or signed authority mandate is also needed. Do not send identity scans by ordinary email. The applicant declares that they are authorised to submit the evidence and to represent the business.

Authorised reviewers check registration against a source, check the person through a live video, in-person or trusted identity-provider check, and check their relationship and authority. The review records its outcome, reason, source references and expiry. An email code, uploaded ID or automated scan alone is not approval. Status and requests for changes appear in the app. Shop moderation remains a separate decision. New shop services stay unavailable until the current owner’s evidence and review are approved; a handover requires the new owner to be checked.

Evidence is stored in a separate private file area. Only the authenticated owner and authorised reviewers can obtain short-lived access links; review access is audited. Approved evidence is bound to the reviewed revision. It is not a public card attachment, a marketing audience or an automatic AMiN share. Keep identity numbers out of free-text notes and provide only the requested evidence.

Passkeys are optional. The authentication provider stores public credentials and related authentication metadata. Private credentials are managed by your device or password manager; emiralX does not receive your fingerprint, face scan or device PIN. You can manage passkeys in account security and keep verified email as a recovery method. A passkey does not replace business identity and authority review.

Documents and AMiN

The Vault handles document files and metadata such as type, title, number, issuer and expiry. Local emiralX storage and an AMiN-connected Vault are different processing locations. When you connect AMiN and save or synchronise a document there, the selected file and its metadata are transmitted to AMiN. Recipient shares can include selected documents and, when chosen, additional verification information.

AMiN sharing applies recipient checks, expiry and download choices. Revocation stops future authorised access through the share; it cannot recall an already downloaded file. Disconnecting AMiN does not itself delete its stored documents or a recipient’s copy. AMiN’s own notice and the final allocation of responsibilities with its operator must be available before production use.

In the current test service, removing a local document from the Vault hides its record and does not itself permanently erase the stored file. Request permanent erasure through the operator; the production deletion process is a launch requirement.

Receipts, VAT and shop insights

Receipt recognition for English, Arabic and Persian runs on the phone using bundled models. It can suggest the merchant, printed amount before VAT, VAT, final total, date, time and category. The scan is not sent to a cloud OCR service by this flow. A receipt and its reviewed expense information are uploaded after you save. Recognition can be wrong; your saved corrections remain important.

When you opt into a shop’s insights sharing, the reviewed test service can expose membership-tier information and spending-category interest labels derived from expenses. Such labels may reveal sensitive information. Leave insights sharing off if you do not want it shared. Sensitive-category exclusion and a documented insights purpose are required before public rollout. Contact sharing is a separate switch; shop records of their own visits and invoices are separate from these optional insights.

Optional AI-assisted features

When you ask for AI card suggestions, the feature can send selected card/profile text to the configured provider, including Anthropic when configured. This is separate from the on-device receipt scanner.

In emiralX Business, choosing Build with AI sends the menu photo, PDF or public webpage content you select to OpenAI to extract an editable first draft. Use only material you are authorised to provide and avoid confidential, sensitive or unnecessary personal information. The feature explains this transfer before you choose Create editable draft. AI does not publish a menu, set your taxes or determine allergen claims; you review and edit the result.

Uploaded menu sources are kept privately for processing and removal is requested after the attempt. Prepared AI drafts are retained with the business account so you can review and reopen them. Subscription allowances limit new AI imports; reopening a prepared draft and manual menu editing do not use another import. A failed import returns its reserved allowance.

AI output may be inaccurate. Check names, prices, sizes and other details before using or publishing it.

Who receives data and where

Information can therefore be processed outside the UAE. The operator must establish and disclose the applicable transfer arrangements before public release. Provider safeguards must meet the applicable cross-border data protection requirements; accepting service terms is not blanket consent to overseas processing. For the arrangements applicable to your data, contact info@emiral.app.

Information may also be disclosed when a valid legal requirement applies or to address abuse and security incidents, subject to applicable law. The reviewed emiralX and Business release does not route payments to a payment processor.

Retention and removal

Active accounts retain the records needed for the features used. The reviewed code does not yet implement a complete automated retention schedule for all card analytics, security/audit records, reports, shop invoices and stored files. No universal deletion period is promised for all categories; ask info@emiral.app about a specific record or request.

Before public launch, the operator must approve a category-specific schedule, retention grounds for any required records, backup handling and deletion jobs. Ending visibility, clearing browser storage, uninstalling an app and hiding a record are different from erasing server data. Business invoices and legal/security records may need restricted retention for a supported purpose; the operator must explain any exception and its duration when handling a request.

Copies saved by another recipient or controlled by an independent shop/company may require a request to that recipient as well.

Verification evidence has separate purge controls: abandoned staged uploads older than one day, superseded or deleted evidence older than 90 days, inactive draft or rejected applications older than 90 days, and evidence for approvals expired for more than 90 days can be purged by authorised staff. Current approval evidence is retained while needed for that review and its validity period. Purging removes private files and unnecessary application fields; a minimal decision/security audit can remain. These are operator-run controls, not a promise that every file is deleted by a scheduled job. You can request an earlier review of retention or erasure through the contact above.

Your information rights

Subject to applicable law, you may request information, access, a portable copy, correction, erasure or restriction; object to applicable processing and marketing; withdraw optional consent; and seek human review of qualifying automated decisions. Email info@emiral.app. We verify ownership proportionately and respond under the applicable privacy rules and response periods. You may complain to the competent privacy or consumer protection authority in your jurisdiction. These rights do not depend on purchasing a paid service.

Security and incidents

The reviewed service uses HTTPS, account/device authentication and access-controlled document and receipt delivery. Those measures do not justify a guarantee of perfect security or a claim that all stored fields are end-to-end encrypted. Keep device credentials, card links and business transfer codes private. A transfer code gives control of a shop to its claimant.

Public release requires a named incident owner, access controls and a documented response process. Where legally required, the operator must notify the competent authority and affected people. A breach-response workflow has not been verified by publication of this notice.

Adults and updates

The proposed public service is for people aged 18 or older. Do not register a child’s account or use personal discovery on a child’s behalf. This is a service eligibility rule, not a statement that UAE data-protection law sets a universal digital-consent age of 18. New accounts must deliberately confirm that they are at least 18 before registration; this is not independent age verification.

This notice is effective 20 October 2026, version 2026-10-20.4. We explain material changes and obtain any new acknowledgement or optional-purpose consent required before that processing starts.