13Trust & contact
Document updates
Tajir Global Limited · contact@utajir.com
On this page
Document change log
1.1Current version
Release 2026-09-15.2 updates readiness descriptions across the fourteen documents in Arabic and English. The Utajir services described here are ready. Ravinto is an independent payment service that is ready for use, with a separate account and agreement with its provider; its referral program is ready and requires separate enrollment. Public registration and support remain deferred. This update distinguishes service readiness from activation for an individual account and confines future-development rules to future additions. It does not change fees or eligibility terms or automatically open an account or enroll anyone in a referral program. Previous releases remain preserved under their original text and identifiers.
1.2Recording later changes
An approved release record identifies the document, version, publication and effective dates, change summary, section links and affected audience or feature. Editorial corrections are distinguished from changes to price, rights or processing purposes. No record is created to imply a publication that never occurred.
1.3Release 2026-09-12.2 — historical record
Release 2026-09-12.2 contains fourteen documents in Arabic and English, including the Accessibility Statement. Its original text remains unchanged in the archive for release 2026-09-12.2. This record identifies the previous version and its archive; it does not establish when it was published to the public or accepted.
Publication, effectiveness & version identification
2.1Publication is not effectiveness
A release identifier identifies text; it does not alone establish publication or your acceptance date. Contract terms apply when the subscription and relevant documents are accepted, or on the date agreed in the Order. Privacy notices explain actual processing when you interact with a service; statutory privacy rights do not depend on accepting the notice. For an existing contract amendment, its notice identifies effective date, choices and any required new acceptance before application.
2.2Identifying the relevant release
Orders are linked to accepted terms and annex versions, with precedence rules applied to conflicts. An earlier agreement is not automatically restated by the newest text, and page updates do not replace acceptance evidence where renewed acceptance is required. Customer-specific annexes identify their date, scope and relationship to general documents.
Change notices & acceptance
3.1Material-change notices
Changes affecting obligations, rights, price or data are explained before effectiveness under contract and law, including application date and relevant options. Notices use authorized contacts and suitable channels; a general instruction to keep checking the site does not replace required direct notice. Urgent security or legal changes follow their reasons and limits with practicable notice.
3.2Separating acceptance and consent
Contract or amendment acceptance does not automatically grant marketing, tracking or new-purpose data consent. Each consent follows its purpose and conditions; prior withdrawal and refusal remain respected until a valid new choice where required. An optional box is not preselected to complete a legal update.
Version archive
4.1Retaining versions
We retain a fixed copy of each release in both languages. The archive link provides release 2026-09-15.2, and previous releases 2026-09-12.1, 2026-09-12.2 and 2026-09-15.1 remain preserved under their original identifiers and text. We do not replace accepted text under the same identifier. Customer-specific annexes, processing schedules and change notices are associated with the relevant customer record without requiring public disclosure of private information.
4.2Requesting a previous copy
An authorized party may request its subscription documents and annexes at contact@utajir.com after appropriate authority verification and without disclosure of others’ data. Each party’s record is associated with its actual release and acceptance date; we do not create a record implying publication or acceptance that did not occur.
Acceptance records & language consistency
5.1Acceptance evidence
Necessary evidence identifies party, account, authorized user, acceptance method and time, document identifier, Order and annex versions and minimal suitable technical evidence. Do not collect a broad device fingerprint merely to prove acceptance where less evidence suffices. Records follow their purpose, legal requirements and approved retention policy.
5.2Arabic and English consistency
Arabic and English are reviewed together for matching obligations, exceptions, rights, numbers and references. Terms clause 16.2 governs language discrepancies, including protection against imposing a harsher consumer term because of translation. Material errors are corrected with required notice or acceptance, without silently changing rights under an earlier contract.
Questions & document corrections
6.1Reporting an error
If a link fails, translations conflict or information differs from the service, email the document name, section link and a brief description to contact@utajir.com. Full account or customer data is not needed to report an editorial error. We review its effect across related documents and pages and explain any rights impact where necessary.
6.2Review before approval
Tajir Global Limited reviews documents when services, markets, providers or processing purposes change and ties commitments to agreed service scope. For any future addition beyond the ready services currently described, a payment service, commission program or processing requiring a provider or transfer instrument is not activated before its necessary identity, terms and safeguards are supplied. Showing a future addition in an illustrative interface neither authorizes operation nor contracts with an unidentified party.