yt24.center

Customer Information Handling & Confidentiality

The binding rules for every authorized user who may access customer or traveler information, and the duty to protect that information from misuse, disclosure and careless handling.

1. Document Control

FieldValue
DocumentYourTransfer24™ Customer Information Handling & Confidentiality Policy
Policy IDYT24-POL-CUSTOMER-INFORMATION
Version1.0.0
StatusACTIVE
ClassificationPUBLIC
Effective date3 October 2026
Policy OwnerYourTransfer24™
Applies toAll workforce members and authorized internal users who may access customer or traveler information
Review cyclePeriodic, and upon a material legal, regulatory, security or operational change
Canonical languageEnglish

This version is in force. It is the Customer Information Handling & Confidentiality Policy of YourTransfer24™. It replaces any shorter customer-information statement previously published for this Policy ID.

2. Purpose

This Policy protects YourTransfer24 customers and travelers. It also protects YourTransfer24 from liability caused by unauthorized, malicious, negligent, reckless, careless or accidental handling of their information.

Each user who can reach Customer / Traveler Data is accountable for that access and for what the user does with it. Accountability covers malicious access, curiosity access, unauthorized disclosure, negligent disclosure, a message or file sent to the wrong person, misuse, unauthorized export, improper storage, prohibited use of an AI system, delayed reporting, concealment, and repeated careless handling.

3. Scope

This Policy applies to every employee, contractor, temporary worker, consultant, agent and other authorized internal user who may access Customer / Traveler Data, wherever that user works and whichever YT24 System the user uses.

This Policy applies to any authorized system or tool through which personnel may access or process customer or traveler information.

This Policy supplements the Internal Use Terms & Employee Responsibilities, the Responsible AI Use Policy, and the Security & Incident Escalation policy. Where one of those documents, or applicable law, sets a stricter rule, the stricter rule applies.

5. Definitions

“User” means a person to whom this Policy applies.

“Customer / Traveler Data” means information that identifies or relates to a customer or traveler and that a user may reach through YT24 work. It includes identity data, contact data, booking data, itinerary data, location data, and related operational or support information. A combination of these categories may be sensitive even when a single item appears limited.

An email address and a telephone number are personal information. They are not ordinary business trivia.

“YT24 Systems” means the systems named in section 3.

6. Restricted Customer / Traveler Data

For internal handling, Customer / Traveler Data is Restricted Customer / Traveler Data. Users must treat it as restricted even when a single field looks ordinary.

A combination of identity, contact, booking, itinerary and location data can reveal where a person is or is expected to be. That kind of combination creates a substantial safety and privacy risk. A user must not collect, copy or send such a combination unless the authorized task requires each part of it.

The ordinary operational environment is not a place for a Social Security number, a card security code, complete payment-card credentials, or banking-login credentials. This Policy does not authorize a user to collect or store them. If a customer sends any of them, the user must not copy, store or forward them, must remove them as instructed, and must report it under section 21.

7. Authorized Access

Customer / Traveler Data may be accessed only:

  1. by an authorized user;
  2. for a legitimate current YT24 purpose;
  3. within the user's assigned responsibilities;
  4. to the minimum extent necessary;
  5. through authorized YT24 Systems; and
  6. only while that business need exists.

The fact that a screen, search or export can show the information is not authorization to view it, copy it or send it. When the task is finished, the user stops using the information for that task.

8. Need-to-Know / Least Privilege

The user opens only the record required for the booking or other authorized task then in hand. The user does not open nearby records, earlier trips or another customer's file to compare, to satisfy curiosity, or because the search returned them.

A driver, provider or coworker receives only what that person needs to perform the assigned service or task. Location information is opened only for an active, legitimate operational purpose. It is not available merely because the system holds it.

A local copy, a download, a screenshot or a cached view is not the booking record. The user relies on the authoritative YT24 System for the current facts.

9. Prohibited Access / Curiosity Access

Curiosity is never a legitimate business purpose. A user must not access Customer / Traveler Data about a person who is not part of an assigned YT24 task. That prohibition includes information relating to:

  • a celebrity or other public figure;
  • a friend, relative, former partner, neighbor or acquaintance;
  • a coworker;
  • a competitor; and
  • any other person unrelated to the task.

The prohibition applies even if the user does not export or disclose what was seen, and even if the user believes no harm will follow. Looking is itself a breach of this Policy.

10. Recipient Verification

Before sending an email, voucher, PDF, booking details, customer contact information, attachment, operational message or export, the user must check the recipient with reasonable care. The user must confirm:

  • the person who is supposed to receive it;
  • the destination email address, telephone number or account;
  • that the attachment is the correct file and belongs to that booking; and
  • that the booking and the customer context match the message.

A user who is unsure stops and checks. Speed does not excuse sending Customer / Traveler Data to the wrong destination.

11. Communications

Customer / Traveler Data leaves YourTransfer24 only through an authorized channel and only for an authorized purpose. The user writes and attaches only what the recipient needs for that purpose.

Information about one customer must not be placed in a message, voucher, attachment or thread addressed to another customer. A shared mailbox, a copied address or an old thread is checked before send, not after.

The user must not ask a recipient who was not supposed to receive the information to delete it and then treat the matter as closed. Section 20 applies, and the user reports it under section 21.

12. Exports / Downloads / Screenshots / Printing

A CSV export, an Excel export, a PDF, a screenshot, a copy, a print, a browser download and a bulk extract of Customer / Traveler Data are allowed only when they are necessary for an authorized task and the user's role permits that action.

The user must not export a set of records when the task needs one record. The user must not keep a personal archive of Customer / Traveler Data, on a company device or on any other device, after the task no longer requires it.

A file created for a task is stored only in the authorized YT24 location for that task. It is not left in a downloads folder, on a desktop, in a personal drive or in a mailbox as a private copy.

13. Authorized Systems and Channels

Customer / Traveler Data stays in YT24 Systems and in enterprise systems YourTransfer24 has authorized for that information. A user must not move it through:

  • personal email;
  • personal cloud storage;
  • personal WhatsApp;
  • personal SMS, where that channel is not approved for the task;
  • any other private messaging account;
  • removable media;
  • a personal device that YourTransfer24 has not authorized; or
  • an external software service or an external AI service that YourTransfer24 has not authorized.

An approved enterprise system may be used only within the scope of that approval. Approval of one supplier or one channel is not approval of every tool that supplier offers.

14. AI Restrictions

A user must not submit identifiable Customer / Traveler Data to an AI system that YourTransfer24 has not approved for that information. Pasting identity, contact, booking, itinerary, location or related operational information into an unapproved tool is a breach of this Policy.

An AI service YourTransfer24 has approved may process authorized information only inside the scope of that approval. The user remains accountable for what is sent to a customer, driver or provider. The user must not rely on AI output alone for a decision that affects a customer, a traveler or a booking.

A conversation with an AI system, or with a customer, is evidence of what was said. It does not become approved YourTransfer24 knowledge, policy or the official record of a booking unless it passes the governed review YourTransfer24 requires. The Responsible AI Use Policy applies together with this section.

15. Remote and International Access

Users work from more than one country. The user's location does not reduce the protection this Policy gives Customer / Traveler Data.

The user must follow the international data-transfer and access controls YourTransfer24 has approved. The user must not move Customer / Traveler Data across a border by a method outside those controls.

The user must not bypass a geographic control, conceal the user's location in order to get around a restriction, or use an unauthorized VPN, proxy or similar mechanism to defeat a YT24 control.

16. Data Minimization

The user must:

  • access only the Customer / Traveler Data the task needs;
  • disclose only what the authorized recipient needs;
  • copy only what the task needs;
  • keep it only for as long as YourTransfer24 has authorized; and
  • dispose of temporary copies as section 17 requires.

Keeping Customer / Traveler Data “just in case” is prohibited unless a YourTransfer24 retention rule authorizes that retention.

17. Retention and Secure Disposal

Customer / Traveler Data is kept for the time YourTransfer24's retention rules authorize, and no longer, except where a legal hold or an authorized investigation requires preservation. The user must not set a private retention period.

When a temporary copy is no longer needed, the user deletes it from mail, downloads, local drives, printers and any other place the user put it, using the disposal method YourTransfer24 specifies. The user must not discard printed Customer / Traveler Data in ordinary waste.

A duty to preserve evidence under section 22 overrides ordinary deletion until YourTransfer24 releases that hold. The user must not delete records in order to undo a mistake.

18. Customer Rights Requests

A user must not improvise a response to a request for access, deletion, correction or portability, to an objection, to a privacy complaint, or to an inquiry from a regulator or other authority.

The user records the request and sends it, unchanged, through the privacy and customer-rights process YourTransfer24 has authorized. The user must not tell the person that the request is granted or refused, and must not delete or change Customer / Traveler Data in order to answer it, unless that process instructs the user to do so.

19. Confidentiality

The user must not disclose Customer / Traveler Data to a person who is not authorized to receive it. That includes friends and family, another employee who does not need it, a provider or driver who does not need it, a competitor, the media, social media, an external company, and an authority the user is not authorized to inform.

Nothing in this Policy prohibits a disclosure that applicable law protects. To the extent the law protects it, this includes reporting suspected unlawful conduct to a government authority, cooperating with a government investigation, and the protected reporting described in the Internal Use Terms & Employee Responsibilities.

A disclosure that does not meet section 7 or the protection in this section is a breach, whether or not the user intended harm.

20. Wrong-Recipient and Accidental Disclosure

It is a potential privacy and security incident if Customer / Traveler Data about one person is sent or shown to another customer, or to any other person who is not authorized to receive it.

That remains true if no payment-card data was involved, if no government identification number was involved, if only one customer was affected, if the receiving customer is known, if the user believes the information is not sensitive, if the recipient promises to delete it, and if the disclosure was accidental.

The user must report it immediately under section 21. The user must not decide that the event is too small, and must not try to repair it in private and then stay silent.

21. Mandatory Incident Reporting

The user must report immediately, through the channel YourTransfer24 has designated, any event the user knows or reasonably suspects may compromise Customer / Traveler Data. The user must not wait until the user is sure, and must not decide that the event is too small to report.

The duty includes curiosity access, unauthorized disclosure, a wrong recipient, an unauthorized export or screenshot, storage outside an authorized system, Customer / Traveler Data placed in an unapproved AI system, a lost device that can reach the information, and any other breach of this Policy.

Good-faith error

A user who makes an error in good faith and reports it immediately has done what the reporting duty requires. YourTransfer24 may still correct the error, require retraining, or change the user's access where that is needed to protect a customer or YourTransfer24. The act of prompt, truthful reporting is not itself misconduct.

Intentional disclosure, concealment, a deliberately late report, repeated careless handling, recklessness, and knowingly ignoring a required control remain misconduct even if the user reports the event later. This Policy requires reporting. It does not reward silence.

22. Investigations

The user must give reasonable cooperation to an investigation that YourTransfer24 has authorized, to the maximum extent permitted by applicable law and by the user's employment or engagement terms. Cooperation includes answering questions truthfully and preserving the messages, files and records that show what happened.

The user must not destroy or alter evidence, coach another person to hide facts, give an explanation the user knows to be false, or obstruct the investigation. When told to preserve evidence, the user keeps it intact until YourTransfer24 releases that instruction.

23. 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 corrective action, disciplinary measures, 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.

Malicious access, curiosity access, intentional disclosure, concealment and knowingly ignoring a required control are serious misconduct. Recklessness, repeated careless handling and a deliberate failure to report may also be serious, depending on the harm and the user's role.

A single good-faith error that the user reports immediately is handled as section 21 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.

24. Jurisdictional Application

This Policy is the global baseline for Customer / Traveler Data, including where the customer, the traveler or the user is in the Dominican Republic, the United States, Canada, the European Economic Area, the United Kingdom, Brazil, Singapore, Australia, or any other place connected to the service or the access.

Federal, state and provincial privacy and security rules apply where their own scope is met. They sit on top of this baseline. A lighter local rule on employee files, where one exists, does not license a user to handle Customer / Traveler Data below this Policy.

YourTransfer24 does not treat a user in any one country as outside this Policy. Nationality alone does not decide the protection the information receives.

25. 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.

No user may read a limit that the law imposes on one provision as permission to ignore a duty that remains lawful.

26. Electronic Acknowledgement

Acknowledgement of this Policy is a condition of authorized access to YT24 protected internal systems, subject to applicable law.

YT24 uses two separate but complementary acknowledgement controls:

  1. a formal versioned policy onboarding and re-acknowledgement process; and
  2. a recurring acknowledgement presented each time the user signs in.

These controls serve different purposes and must not be treated as interchangeable.

26.1 Formal Versioned Acknowledgement

The formal versioned policy acknowledgement process is the authoritative workforce policy compliance record for this Policy.

When a user first receives authorized access to YT24 internal systems, and whenever YT24 publishes a new version of this Policy, the user must complete the formal acknowledgement process before protected access is granted or restored.

As part of that process, YT24 presents the applicable Policy version to the authenticated user. The user must be given access to the complete Policy content and must reach the end of the presented Policy before the acknowledgement action becomes available.

The user must then enter their full name and affirmatively acknowledge the Policy.

The acknowledgement date and time are generated by YT24 using an authoritative server timestamp. The user does not manually enter, backdate, or future-date the acknowledgement date.

By completing the formal acknowledgement process, the user confirms that the Policy was presented to them, that they had the opportunity to review it, and that they understand their 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 Policy version recorded. When YT24 publishes a new version, the previous acknowledgement does not satisfy the requirement for the new version. Previous versions and previous acknowledgements remain part of the compliance record and are not silently overwritten.

26.2 Recurring Sign-In Acknowledgement

This Policy is one of the three acknowledgements YT24 requires each time the user signs in to the internal access environment.

The user must affirmatively acknowledge the Customer Information Handling & Confidentiality Policy as part of that recurring sign-in control.

The recurring sign-in acknowledgement reinforces the user's continuing recognition of the obligations in this Policy. It does not replace, supersede, or satisfy a missing formal acknowledgement of the current version.

If the user has not completed the required formal acknowledgement for the current version, completing the recurring sign-in acknowledgement does not grant protected access.

YT24 may retain a separate session-level record of the recurring sign-in acknowledgement. That record stays separate from the formal versioned acknowledgement record and must not be used to fabricate or infer acknowledgement of a specific Policy version.

26.3 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

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.