1. Document Control
| Field | Value |
|---|---|
| Document | YourTransfer24™ Security & Access Control Policy |
| Policy ID | YT24-POL-SECURITY-ACCESS |
| Version | 1.0.0 |
| Status | ACTIVE |
| Classification | PUBLIC |
| Effective date | 3 October 2026 |
| Policy Owner | YourTransfer24™ |
| Applies to | Employees, contractors, administrators, developers and all other authorized users of YT24 systems |
| Review cycle | Periodic, and upon a material legal, regulatory, security or operational change |
| Canonical language | English |
This version is in force. It is the Security & Access Control Policy of YourTransfer24™. It replaces any shorter security-and-access statement previously published for this Policy ID.
2. Purpose
This Policy protects YourTransfer24, its customers and travelers, independent transport providers and their drivers, workforce information, internal systems, credentials, technical and confidential information, and operational continuity.
It addresses malicious insiders, unauthorized access, negligence, credential compromise, privilege abuse, carelessness, social engineering, poor device security and circumvention of access controls. Each user is accountable for the identity, credentials and access the user holds.
3. Scope
This Policy applies to every employee, contractor, administrator, developer and other authorized user of a YT24 system, wherever that user works.
This Policy applies to YourTransfer24™ internal systems, applications, platforms, services, development tools, communications systems, and authorized technology resources.
It supplements the Internal Use Terms & Employee Responsibilities, the Customer Information Handling & Confidentiality Policy, the Responsible AI Use Policy and the Security & Incident Escalation policy. Where one of those documents, a contract, or applicable law sets a stricter rule, the stricter rule applies.
4. Security Principles
This Policy establishes YT24's minimum global security and access-control standard. Stricter applicable legal, contractual or regulatory requirements prevail where required.
Access is individual, limited to the role and the task, and removed when the authorization ends. A control that YourTransfer24 has enabled is mandatory. A user must not weaken it because it is inconvenient.
Authority for a record or an action sits in the YT24 system that owns it. A screen, a cached view or a value supplied by the user's own client does not create that authority.
5. Individual Identity
Every internal user has an individual identity. The user must not:
- use a shared account;
- share a password or a passkey;
- share a multi-factor authentication factor or a one-time code;
- share a session;
- use another person's account;
- allow another person to use a device or a session the user has authenticated; or
- impersonate another user, customer, provider, driver or workforce member.
The user is responsible for activity carried out with the user's identity or with a session the user authenticated, unless the user has reported that the identity or session is compromised and has followed the instructions then given.
6. Authentication
Users authenticate through the identity and authentication system approved by YourTransfer24™. This Policy does not create a separate identity provider.
Where YourTransfer24 has enabled them, the user must complete multi-factor authentication, session controls, identity verification, the password lifecycle, a required password change, and the recovery or security step the approved system presents. The user must not bypass those controls.
Password change, account recovery and similar security actions occur only through the functions the approved identity system provides. A user must not set up a side process for passwords, recovery codes or account restoration.
7. Credentials and MFA
The user must protect passwords, passkeys where they are used, multi-factor authentication factors, recovery codes, API keys, tokens, service credentials and signing secrets. The user must not write them on a shared note, send them in an ordinary message, or store them outside the place YourTransfer24 has approved.
The user approves a multi-factor prompt only when the user started that sign-in. An unexpected prompt is refused and reported under section 19. Approving a prompt the user did not start is a breach of this Policy.
If the user suspects that a credential, factor, token, device or session is compromised, the user reports it immediately and stops using it until instructed otherwise.
8. Least Privilege
Technical access does not constitute authorization.
Access is role-based, need-to-know and least privilege. The user opens only the systems, records and functions the current assigned task requires, and only for as long as that task requires them.
A user who can search every booking is still prohibited from opening a booking that is not part of the user's assigned responsibilities. The same limit applies to customer, traveler, provider, driver, workforce, financial and security records.
The user must tell the user's lead if the user still holds access the role no longer needs.
9. Privileged Access
A higher duty applies to administrators, security users, developers, support personnel, finance users, operational supervisors, and any user with elevated rights to data or to export. Privileged access is for the authorized administrative or support task only.
A privileged user must not use that access for curiosity or personal benefit, to change a record without authorization, to grant access without authorization, to skip a required workflow, to hide activity, or to suppress or alter an audit log.
Temporary elevation ends when the authorized task ends. The user must not keep the elevated right, and must not share it.
10. Device Security
The user locks the screen when leaving the workstation, uses the authentication YourTransfer24 requires, and protects the device from loss and from use by another person.
The user runs only software approved for the work and complies with the endpoint-security controls YourTransfer24 requires. The user must not disable, pause or weaken an endpoint-security control.
A lost or stolen device that holds or can reach YT24 systems or information is reported immediately under section 19.
11. Remote Access
Remote access is allowed only through the method YourTransfer24 has authorized. The user's location does not reduce the controls in this Policy.
The user must not circumvent a geographic restriction, use an unapproved tunnel, use a proxy to defeat this Policy, open an unauthorized remote-desktop path, or share a device or a session so that another person can enter through it.
12. Secrets and Tokens
Secrets are security-sensitive information. A user must not place a password, passkey material, multi-factor secret, recovery code, API key, token, service credential or signing secret in:
- source code, where YourTransfer24 prohibits that placement;
- a screenshot;
- a chat system YourTransfer24 has not approved for secrets;
- an external AI system;
- a public ticket;
- a public repository;
- documentation that is not secured for that secret; or
- email, when YourTransfer24 requires an approved secure mechanism instead.
A secret that may have been exposed is reported immediately. The user must not reuse it after that report unless YourTransfer24 instructs the user to do so.
13. Engineering / Source Code Security
Where the user's role includes engineering work, the user must not copy source code without authorization, expose proprietary code, publish it to a public repository, commit a credential or other secret, or use an unauthorized package or tool in a way that exposes code or data.
The user must not bypass a code review, a security review, or another engineering control YourTransfer24 requires before a change is accepted. A local workaround is not an exception.
14. Phishing and Social Engineering
The user must report, and must not comply with:
- a suspicious sign-in page;
- a request for a password, a one-time code, a recovery code or any other credential;
- an unexpected multi-factor prompt, including repeated prompts intended to wear the user down;
- a suspicious link or file;
- a person impersonating a coworker, a customer, a provider, an executive or a vendor;
- a request to reset an account that the user did not expect; and
- a request to skip a required process or control.
The user approves a multi-factor prompt only for a sign-in the user initiated. Urgency, rank or a familiar name does not authorize an exception.
15. Logging and Audit
Authorized systems may maintain proportionate technical and audit records for legitimate purposes such as security, fraud prevention, compliance, investigation, and operational integrity.
Users have privacy interests in workforce personal information and in private activity that is not company business. This Policy is not consent to unlimited monitoring, and it does not authorize surveillance beyond the purposes in this section.
Audit records are protected. A user must not browse them without authorization, copy them into an unapproved place, alter them, or delete them.
16. Access Lifecycle
Access is provisioned for a role. It changes when the role changes. Temporary elevation is granted for a defined task and is removed when that task ends. Access is reviewed, and it is suspended or revoked when the authorization no longer holds, including when employment or the engagement ends.
The user must not keep using an identity, a credential, a token or a session after authorization ends. Company information and company devices are returned or deleted as instructed at offboarding.
The user must not grant, extend or restore another person's access except through the authorized provisioning process.
17. Prohibited Circumvention
Intentional circumvention of a security or access control is serious misconduct. A user must not:
- alter, delete or suppress a log;
- disable or weaken a security control;
- bypass multi-factor authentication;
- call an API, or use a token, without authorization;
- get around a limit on what the user's role may see or do;
- impersonate another person; or
- exploit a weakness outside the authorized testing in section 18.
18. Authorized Security Testing
Security testing is allowed only inside a scope YourTransfer24 has authorized in writing for that test, that system and that time. The tester stays inside that scope and stops when it ends.
Without that authorization, penetration testing, exploitation of a vulnerability, privilege escalation, and scanning intended to bypass a control are prohibited. Finding a weakness does not authorize the user to use it. The user reports it under section 19.
19. Mandatory Security Reporting
The user must report immediately, through the channel YourTransfer24 has designated, and must not decide that the event is too small. The duty includes:
- a compromised or suspected credential, token, factor or session;
- suspicious activity on an account or system;
- a lost or stolen device;
- unauthorized access, or access the user cannot explain;
- suspected malware;
- phishing or another social-engineering attempt;
- an unexpected multi-factor prompt;
- a security control that has failed or been bypassed;
- unexplained access to data; and
- a concern that an insider is acting maliciously.
A prompt, truthful report of the user's own error is what this Policy requires. Concealment, a deliberately late report, and a knowingly false account of the event are misconduct. Nothing in this Policy prohibits a report that applicable law protects, including the protected reporting in the Internal Use Terms & Employee Responsibilities.
20. Investigation and Evidence
The user must give reasonable cooperation to an investigation YourTransfer24 has authorized, to the maximum extent permitted by applicable law and by the user's employment or engagement terms.
The user must not destroy or alter evidence, coach another person to hide facts, or obstruct the investigation. When told to preserve logs, devices, messages or other records, the user keeps them intact until YourTransfer24 releases that instruction.
21. Enforcement
A breach of this Policy may result, as applicable law and the user's contract allow, in restriction or suspension of access, investigation, required retraining, other disciplinary action, and termination of employment or of the engagement. YourTransfer24 may preserve evidence, seek civil remedies available to it, and refer a matter to a public authority where that is appropriate.
Intentional circumvention, credential abuse, impersonation, privilege abuse and concealment are serious misconduct. Negligence and repeated carelessness may also be serious, depending on the harm and the user's role.
A prompt, truthful report of the user's own error under section 19 is handled as that section describes. It is not treated as serious misconduct merely because the user reported it.
This Policy does not require the user to indemnify YourTransfer24. It does not authorize a deduction from wages or other pay that applicable law forbids. It does not create an automatic personal debt, fine or penalty. Any consequence is decided under applicable law and the terms of the user's employment or engagement.
22. Jurisdictional Application
This Policy is the global baseline for every authorized user, including users who work in or access YT24 systems from the Dominican Republic, the United States, Canada, the European Economic Area, the United Kingdom, Brazil, Singapore, Australia, or any other place.
Workforce-monitoring notice, privacy and security duties that apply in the place of work, the employing entity or the place of the people affected sit on top of this baseline. Logging under section 15 follows those duties. Nationality alone does not decide which of them applies.
23. Severability
Each provision of this Policy is applied to the maximum extent the law allows. If a provision cannot be applied to a particular user, a particular place, or a particular set of facts, it is applied as far as it lawfully can be, and the rest of the Policy continues in force. A provision that cannot be applied at all in that situation is severed for that situation only.
24. Electronic Acknowledgement
Acknowledgement of this Policy is a condition of authorized access to YT24 protected internal systems, subject to applicable law. This Policy is an active mandatory corporate policy. It is not one of the three acknowledgements presented each time the user signs in, and completing those three acknowledgements does not satisfy this Policy.
The authoritative record is the formal versioned acknowledgement. When a user first receives authorized access, and whenever YourTransfer24 publishes a new version of this Policy, the user must complete that acknowledgement before protected access is granted or restored.
YourTransfer24 presents the applicable version to the authenticated user. The user must be able to read the complete Policy and must reach the end of the presented Policy before the acknowledgement action becomes available. The user then enters their full name and affirmatively acknowledges the Policy.
The acknowledgement date and time are generated by YourTransfer24 using an authoritative server timestamp. The user does not manually enter, backdate, or future-date that time.
By completing the formal acknowledgement, the user confirms that the Policy was presented, that the user had the opportunity to review it, and that the user understands the obligation to comply with it as a condition of authorized access to YT24 systems, subject to applicable law.
Electronic acknowledgement of this Policy is not, by itself, consent to the processing of personal data where consent is not the applicable lawful basis for that processing.
YourTransfer24™ maintains versioned and auditable records of required policy acknowledgements.
Additional technical evidence may be retained where authorized, proportionate, and permitted by applicable law and workforce privacy requirements.
An acknowledgement applies only to the exact version recorded. A new version requires a new formal acknowledgement. Previous versions and previous acknowledgements stay in the compliance record and are not silently overwritten.
The recurring sign-in acknowledgements for the other workforce policies remain separate. They must not be used to fabricate or infer acknowledgement of this Policy or of a specific version of it.
24.1 Relationship Between Authentication, Policy Compliance and Authorization
Authentication, policy compliance and application authorization are separate controls.
The governing sequence is:
Authentication→ Policy Compliance→ Application Authorization→ Access
Authentication through the approved identity system establishes identity. It does not, by itself, establish compliance with this Policy, and successful authentication does not bypass an outstanding formal acknowledgement of this Policy.
Formal acknowledgement of this Policy does not independently grant access to an application for which the user is not otherwise authorized.
Recurring sign-in acknowledgement does not replace either formal policy compliance or application authorization.

Issued by YourTransfer24 for internal use. Where your employment agreement or the internal compliance programme sets stricter terms, those terms apply.