yt24.center

Security & Incident Escalation

The binding rules for reporting every security or privacy incident immediately, and for leaving external notification, severity and legal decisions to YT24.

1. Document Control

FieldValue
DocumentYourTransfer24™ Security & Incident Escalation Policy
Policy IDYT24-POL-SECURITY-INCIDENT
Version1.0.0
StatusACTIVE
ClassificationPUBLIC
Effective date3 October 2026
Policy OwnerYourTransfer24™
Applies toAll employees, contractors and authorized internal users
Review cyclePeriodic, and upon a material legal, regulatory, security or operational change
Canonical languageEnglish

This version is in force. It is the Security & Incident Escalation Policy of YourTransfer24™. It replaces any shorter security-and-incident statement previously published for this Policy ID.

2. Purpose

This Policy protects YourTransfer24, its customers and travelers, independent transport providers, their drivers and the workforce by requiring every suspected security or privacy incident to be reported at once and handled through one governed process.

Speed of the internal report matters more than the user's view of the outcome. YourTransfer24 cannot contain an event, preserve evidence, or meet an external duty that the user has kept inside a private conversation.

3. Scope

This Policy applies to every employee, contractor and other authorized internal user, wherever that user works and whichever YT24 system the user uses.

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 Security & Access Control Policy and the Responsible AI Use Policy. Where one of those documents, a contract, or applicable law sets a stricter rule, the stricter rule applies.

4. Governing Principle — Employee Reports / YT24 Assesses

The user reports. YourTransfer24 assesses.

This Policy establishes YT24's minimum global standard for reporting and escalating security and privacy incidents. Stricter applicable legal, contractual or regulatory requirements prevail where required.

The internal reporting threshold is intentionally lower than any external legal-notification threshold. An event is reported inside YT24 before anyone decides whether the law requires a notice outside YT24.

The user must not decide whether the event legally qualifies as a breach, whether a regulator must be notified, whether a customer must be notified, whether the incident is serious enough, whether law enforcement must be contacted, or whether the incident is reportable. Those decisions belong to the central YT24 incident process.

5. Definitions

An incident is a suspected or confirmed event that may affect the confidentiality, integrity or availability of a YT24 system or of information YourTransfer24 holds, or that section 6 or section 7 describes. The user reports a suspicion. Confirmation is not required before the report.

A privacy / data incident is an incident involving personal information or other confidential operational information, including customer, traveler, provider, driver or workforce information. A cyber / security incident is an incident involving a system, an identity, a credential, malware, or another compromise of security. One event may be both.

The time an event happened, the time a person or a system first noticed a possible concern, and the time YourTransfer24 identified that concern as a suspected incident are separate. None of those times is, by itself, the legal moment at which YourTransfer24 becomes aware for a particular statute. The central process determines that moment for each law that applies.

Notifiable, in this Policy, means that an applicable law or contract requires notice outside YT24. Non-notifiable means that the central process has determined that no such notice is required. Non-notifiable does not mean that the incident did not occur.

6. Privacy / Data Incidents

The user reports a privacy / data incident immediately. The following are incidents under this Policy, whether or not the user believes an external notice will be required:

  • Customer A's information is sent or shown to Customer B, or to any other person who is not authorized to receive it;
  • a voucher, a PDF, an email attachment or another file goes to the wrong recipient;
  • a booking is visible to a person who is not authorized to see it;
  • a user opens a record out of curiosity or for a purpose outside the assigned task;
  • a user exports, downloads, copies or screenshots information without authorization;
  • information is disclosed by accident, including a brief exposure;
  • customer or traveler information is lost;
  • customer, traveler or workforce information is placed in an AI system that YourTransfer24 has not approved for that information; and
  • any other use or disclosure that the Customer Information Handling & Confidentiality Policy prohibits.

Name, email address and telephone number are enough. The incident does not wait for a payment-card number, a Social Security number, or a government identity number. Combinations of travel-related information that can show where a person is or will be are treated as sensitive.

7. Cyber / Security Incidents

The user reports a cyber / security incident immediately. The following are incidents under this Policy:

  • a compromised or suspected credential, password, passkey, token, recovery code or API key;
  • phishing, or any request for a credential or a one-time code;
  • a compromise or suspected compromise of multi-factor authentication, including an unexpected prompt or repeated prompts;
  • a suspicious login;
  • malware or ransomware;
  • an intrusion, or a system that appears to be under someone else's control;
  • privilege escalation, or a privilege that changed without authorization;
  • exploitation of a vulnerability, including one the user found and has not been authorized to test;
  • exfiltration, or a reason to believe information has left an authorized system;
  • unauthorized API access;
  • an anomalous bulk download or an unusual export;
  • a malicious insider, or a credible concern that one exists;
  • a lost or stolen device that holds or can reach YT24 systems or information;
  • sabotage; and
  • any other compromise, or suspected compromise, of a YT24 system or of the controls in the Security & Access Control Policy.

8. No Minimum Internal Reporting Threshold

There is no minimum size, sensitivity or duration for an internal report. The user reports even if:

  • only one customer was affected;
  • only a name, an email address or a telephone number was exposed;
  • no financial data was involved;
  • no Social Security number or equivalent government identity number was involved;
  • the recipient is known;
  • the recipient promises to delete the information;
  • the exposure lasted briefly;
  • the user has already corrected the mistake;
  • no customer has complained; or
  • the user believes an external notification is unlikely.

A correction made before the report does not close the incident. The report still includes what was exposed, to whom, and what the user already did.

9. Immediate Required Actions

As soon as the user knows or reasonably suspects an incident, the user must:

  1. stop the ongoing unauthorized activity where it is safe to do so;
  2. prevent further disclosure where that is reasonably possible;
  3. report immediately through the channel YourTransfer24 has designated;
  4. preserve the evidence;
  5. give the facts accurately, including what is known and what is not known;
  6. follow the containment instructions then given; and
  7. cooperate with the investigation.

A safe stop includes holding an unsent message, ending a session the user controls, and ceasing a download or an export the user started. It does not include exploiting a weakness, scanning to bypass a control, opening records the user is not authorized to open, or shutting down a system the user has not been told to shut down.

The designated channel is the report. A side message to a coworker, a chat, or an email is not a substitute unless YourTransfer24 has designated that channel. Telling only the person involved in the mistake is not a report.

10. Prohibited Actions

The user must not conceal an incident or handle its external consequences alone. The user must not:

  • hide the event, minimize it, or delay the report while deciding whether it qualifies;
  • delete or alter a log;
  • delete an email, a message or another record because it shows the event;
  • destroy evidence, including by wiping a device that may hold it, unless containment instructions expressly require that step;
  • alter a booking, a message or another record to hide a mistake;
  • ask another person to conceal the event or to alter evidence;
  • make a public statement, or contact the media, about the incident;
  • notify a regulator, a supervisory authority or another public authority as a representative of YourTransfer24, unless the authorized workflow instructs the user to send a specific communication;
  • admit legal liability on behalf of YourTransfer24;
  • promise compensation, credit, a refund or any other remedy on behalf of YourTransfer24; or
  • contact an affected customer, traveler, provider, driver or other person about the incident outside the authorized incident-response workflow.

Nothing in this Policy prohibits or restricts a report, disclosure or activity that applicable law protects, including the protected reporting stated in the Internal Use Terms & Employee Responsibilities. To that extent, a user may report suspected unlawful conduct to a government authority and may cooperate with a government investigation. That protection does not authorize the user to speak for YourTransfer24, to announce the incident publicly, or to admit liability or promise compensation on YourTransfer24's behalf.

A user may contact emergency services when that is immediately necessary to protect a person from physical harm. The user reports that contact internally as soon as it is safe to do so.

11. Automated Detection

YourTransfer24™ may use technical and automated controls to identify activity that may be anomalous, unauthorized, or indicative of a security or privacy incident.

Automated detection supplements the user's duty. It does not replace it. A control that did not alert, or an alert the user did not see, does not excuse a report the user should have made. An alert the user does see is itself a reason to report, not a reason to investigate alone.

The authoritative incident record is the governed record created in the YT24 process. A chat message, a local note or an email is not the system of record, even when it is used to transmit a report.

12. Incident Record

YourTransfer24™ maintains a governed and durable record of reported incidents, assessments, actions taken, and relevant compliance decisions.

The user supplies the facts the user has. The user does not invent a count, a cause or a jurisdiction. Unknown remains unknown until the investigation establishes it.

A recorded incident may ultimately be classified as non-notifiable. YourTransfer24 still retains the record for as long as this Policy, an investigation, a legal hold, a contract or applicable law requires. Closure of an incident is not deletion of the record.

13. Severity and Risk Assessment

Severity is classified by the central process, not by the reporting user. The classification can change as facts are established. The user's belief that the event is minor does not set the classification and does not delay the report.

The assessment considers the sensitivity of the information, including combinations that can reveal a person's movements, the number of people affected, the confidentiality, integrity and availability impact, whether a recipient is known, whether information may have left an authorized environment, the likelihood of misuse, the actual or potential harm, the jurisdictions involved, and whether the event is still underway.

One affected person can be material. The absence of financial data or of a government identity number does not, by itself, make an incident low severity. An AI system may help organize the facts. It does not decide the severity and it does not decide whether anyone outside YT24 is notified.

14. Containment

Containment limits ongoing exposure and protects evidence. It is not delayed until a legal notice decision is finished, and it is not used as a reason to skip the report.

The user carries out the containment steps the user can take safely under section 9, and then follows the instructions of the incident process. Those instructions may include isolating an account, revoking a credential or a token, stopping a communication, recovering a message where the system can do so, or preserving a device.

The user must not take a containment step that destroys evidence, expands access, or creates a new disclosure, unless the incident process has directed that step. A promise by an unauthorized recipient to delete information is not containment.

15. Jurisdictional Assessment

The central process evaluates the affected jurisdictions, the data categories, the sensitivity, the scale, the likelihood of misuse, the actual and potential harm, any duty to notify a regulator, any duty to notify an individual, any contractual duty, any insurer duty that applies, and whether law enforcement should be contacted.

Each law is applied on its own terms. A deadline, a threshold or a definition from one jurisdiction is not used as the rule for another. The user's location does not select the law, and it does not lower the internal report. The paragraphs below state the rules the central process applies where that law actually covers the event. They are not a checklist the user completes.

15.1 European Economic Area

Where the GDPR applies, a personal-data breach is a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to, personal data. Article 32 requires security appropriate to the risk. That duty is continuous. It is not the user's test for whether to report.

Where notification is required, the controller notifies the competent supervisory authority without undue delay and, where feasible, not later than 72 hours after YourTransfer24 becomes aware of the breach. The duty does not apply if the breach is unlikely to result in a risk to the rights and freedoms of natural persons. A later notice states the reasons for the delay. Information that is not yet known may follow in phases, without further undue delay. Where the breach is likely to result in a high risk to those rights and freedoms, the affected person is informed without undue delay, unless Article 34 provides an exception.

Every personal-data breach is documented, including the facts, the effects and the remedial action, whether or not a supervisory authority or a person is notified. Becoming aware is determined by the central process when there is a reasonable degree of certainty that a security incident has compromised personal data. The internal report is made before that certainty exists. The process must not treat the reporting user's uncertainty as a reason to postpone the determination.

15.2 United Kingdom

Where the UK GDPR applies, the same structure is used with the Information Commissioner's Office as the supervisory authority. A notifiable breach is reported without undue delay and, where feasible, not later than 72 hours after YourTransfer24 becomes aware of it. If the breach is unlikely to result in a risk to the rights and freedoms of individuals, that report is not required. Where the breach is likely to result in a high risk, the affected individuals are informed without undue delay, subject to the exceptions in the UK GDPR. The breach is documented whether or not it is notified. The 72 hours are not the internal reporting deadline.

15.3 Canada

Where PIPEDA applies, a breach of security safeguards that it is reasonable to believe creates a real risk of significant harm is reported to the Office of the Privacy Commissioner of Canada, and the affected individual is notified, as soon as feasible after YourTransfer24 determines that the breach has occurred. The assessment considers the sensitivity of the information and the probability that it has been, is being, or will be misused. Another organization is notified where the Act requires that notice in order to reduce the risk.

A record is kept of every breach of security safeguards involving personal information under YourTransfer24's control, including a breach that does not meet the real-risk threshold. Where PIPEDA applies, that record is kept for 24 months after the day YourTransfer24 determines that the breach occurred, and longer if this Policy, a hold or another law requires it. Where a provincial statute applies, that statute is applied on its own terms. A determination under PIPEDA does not replace it.

15.4 United States

There is no single United States notification deadline and no single national definition of the information that triggers notice. The central process applies the statute of each affected state to that statute's own data elements, its own harm or acquisition test, its own encryption rule, and its own clock. A clock measured in days in one state is not borrowed for a state that uses a different standard.

Where California Civil Code section 1798.82 applies to a breach of the security of the system involving personal information as that statute defines it, notice to an affected California resident is given within 30 calendar days of discovery or notification of the breach. That period yields to the statute's exceptions for the legitimate needs of law enforcement and for the time necessary to determine the scope of the breach and restore the reasonable integrity of the data system. Any notice to the California Attorney General that the same statute requires, in the circumstances it defines, is made by the central process. A disclosure that does not meet the statute's definition of personal information is still reported internally.

A federal duty that applies only to a defined kind of entity, a defined data element, or a defined harm is assessed on those conditions. It is not assumed from the fact that an incident occurred, and it is not used as a nationwide deadline.

15.5 Dominican Republic

Ley 172-13 requires the controller of a personal-data file, and where applicable the processor, to adopt the technical, organizational and security measures needed to safeguard personal data against alteration, loss, unauthorized processing, consultation or access, and it imposes a duty of secrecy. That law does not itself set a numeric deadline for notice of a personal-data incident to a data-protection authority. YourTransfer24 does not import the GDPR period of 72 hours into the Dominican Republic by default.

Decreto 685-22 requires public entities of the Executive Branch to notify a cybersecurity incident within 24 hours of detection. That decree is not applied to YourTransfer24 as if YourTransfer24 were one of those public entities. A Dominican sector rule, a contract, or a criminal-law duty is assessed only when it actually binds YourTransfer24. None of these limits changes the user's duty to report internally at once.

15.6 Brazil

Where the LGPD and ANPD Resolution CD/ANPD No. 15 of 24 April 2024 apply, the central process uses that resolution's own criteria for relevant risk or damage to data subjects. Communication is not made for every security event.

Where the resolution requires communication, YourTransfer24 communicates with the ANPD and with the data subjects within three business days from knowledge that the incident affected personal data, unless the resolution assigns the controller a different period. Further information may be supplied, with reasons, within the additional period the resolution allows. Those business days are not the internal reporting deadline, and they are not applied outside the events the resolution covers.

15.7 Singapore

Where the PDPA applies, a data breach is notifiable if it is, or is likely to be, a breach that results in significant harm to an affected individual, including harm deemed by the Personal Data Protection (Notification of Data Breaches) Regulations 2021, or if it affects 500 or more individuals. The central process makes that assessment in a reasonable and expeditious way.

Once the breach is assessed as notifiable, the Personal Data Protection Commission is notified as soon as practicable and no later than three calendar days after the day of that assessment. Each affected individual is notified of a significant-harm breach as soon as practicable, on or after notice to the Commission, unless the Act provides an exception. A breach that is notifiable only because of its scale is not given the same individual notice unless the Act requires it. The three calendar days are not the internal reporting deadline.

15.8 Australia

Where the Privacy Act's Notifiable Data Breaches scheme applies, an eligible data breach is unauthorized access to, unauthorized disclosure of, or loss of personal information that a reasonable person would conclude is likely to result in serious harm, and that remedial action has not prevented. If there are reasonable grounds to believe an eligible data breach has occurred, a statement is given to the Australian Information Commissioner, and the affected individuals are notified, as soon as practicable.

If YourTransfer24 only suspects an eligible data breach, it carries out a reasonable and expeditious assessment and takes all reasonable steps to complete that assessment within 30 days after becoming aware of the grounds for the suspicion. Remedial action that prevents the likely risk of serious harm can mean the scheme does not require external notice. The incident is still recorded. The 30 days are an assessment limit where the scheme applies. They are not the internal reporting deadline, and they are not a global rule.

15.9 Contracts, insurers and law enforcement

A contract may require notice to a customer, a partner or a processor on a clock that is shorter than a statute. The central process meets the duty that is actually binding. A statute is not waived because a contract is silent, and a contract is not waived because a statute allows more time.

Notice to an insurer, where an insurance arrangement requires it, is given by the central process. The user does not contact the insurer about the incident unless instructed.

Contact with law enforcement is decided by the central process, except for the immediate personal-safety contact section 10 allows. A request by law enforcement to delay an external notice is honored only through that process, and only to the extent the applicable statute permits the delay.

16. Escalation

Escalation follows function. It does not depend on a job title the user must discover before reporting. The user reports through the designated channel.

Incidents are escalated to the appropriate internal security, privacy, compliance, legal, and management functions according to their nature, severity, risk, and applicable obligations.

A function that receives an incident must not hold it because the event looks small.

The user does not skip the channel and write directly to an executive in order to shape the outcome. Protected reporting under section 10 remains available.

17. External Notification Authority

External communication about an incident is made only through the authorized incident-response workflow. The authorized internal legal and privacy function directs communication with a regulator, an affected person, the public, an insurer, or law enforcement, except for the emergency contact section 10 allows.

A user who is instructed to send an approved notice sends that notice, without adding an apology that admits liability, a promise of compensation, or facts the notice does not contain.

No user decides that a customer already knows, that a recipient has agreed to delete the information, or that silence is safer. Those are not grounds to withhold a notice the central process has authorized, and they are not grounds for the user to send one it has not.

18. Evidence Preservation

The user preserves logs, messages, emails, files, devices, screenshots that already exist, and any other record that shows what happened. The user does not create a new screenshot of customer information in order to illustrate the incident if a safer reference, such as a record identifier and a time, will do.

The authorized Legal function may direct preservation, a legal hold, a privileged investigation where the law recognizes privilege for that work, external communications, and the response to a regulator or a customer. A legal hold overrides ordinary deletion for the records it names, for as long as it remains in force.

Not every investigation is privileged. Marking a message confidential does not make it privileged. The user must not assume that a conversation with a coworker, or with an AI system, is protected. The user must not destroy a record because the user hopes it will be privileged, and must not describe facts differently because a hold is in place.

19. Investigation Cooperation

The user gives 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. Cooperation includes a prompt, complete and truthful account, access to a company device when instructed, and identification of other people who may have facts.

The user must not coach another person to hide facts, must not obstruct the investigation, and must not retaliate against a person who reported or who participated. A good-faith report that later proves mistaken remains protected, as the Internal Use Terms & Employee Responsibilities provide. A report the user knows to be false is not protected.

20. Recovery and Remediation

Incident handling follows preparation, detection, response, containment, recovery, and lessons learned that improve the risk. That sequence aligns with NIST Special Publication 800-61 Revision 3, which places incident response inside cybersecurity risk management rather than in a single linear script. A later step does not wait for a perfect earlier step while people or systems are still exposed.

Recovery restores the affected service or data to a trusted state under the incident process. The user returns to ordinary work only when told that the user's part of the recovery is complete. Finishing a task, recalling a message, or resetting a password does not by itself close the incident.

Remediation includes the steps that reduce the chance of the same event, and the steps that reduce harm to the people affected. Both are recorded. An AI system may help summarize evidence. It does not declare the incident closed and it does not invent a fact that the record does not contain.

21. Root Cause and Corrective Action

After the immediate risk is contained, YourTransfer24 identifies the root cause to the extent the evidence supports it, and records the corrective action. Corrective action may change a control, a workflow, a permission, a template, or training. It is tracked to completion.

The root cause may be a control gap, a process gap, a mistake, or misconduct. Naming a cause is not a finding that the reporting user is at fault. Lessons learned are fed back into the controls. They are not stored only as a closing remark, and they are not used to discourage the next report.

22. Good-Faith Reporting

A good-faith error that the user reports promptly is what this Policy requires. Prompt self-reporting supports containment and mitigation. It must not be discouraged, and it must not be treated as serious misconduct merely because the user was the person who made the error.

The user reports the user's own mistake in the same way, and with the same speed, as a mistake the user observes in someone else's work. Waiting to see whether the customer complains is a failure to report.

23. Concealment / Failure to Report

The following are distinct from a good-faith error that is reported promptly, and they remain misconduct even if the user reports the event later:

  • intentional concealment;
  • recklessness toward an incident the user knows or reasonably suspects;
  • a deliberate failure to report, including a decision that the event is too small;
  • destruction or alteration of evidence; and
  • a knowingly false report, or a knowingly incomplete report made to hide a material fact.

Asking another person to do any of those things is the same misconduct. A late report does not erase it. The central process may still use a late report to reduce harm, and the user must still make it.

24. 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 concealment, destruction of evidence, malicious access, and a deliberate failure to report are serious misconduct. Recklessness may also be serious, depending on the harm and the user's role.

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.

25. 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 where YourTransfer24 authorizes access.

Nationality does not decide which incident law applies. The user's work location does not reduce the duty to report internally, and it does not reduce the protection of customer or traveler information. A lighter local rule, where one exists, does not license silence.

Section 15 is applied only to the extent the named law covers the event. Where that law, or a contract, requires more than this baseline, YourTransfer24 follows the stricter requirement. Where a provision of this Policy cannot lawfully be applied to a particular user, the remainder continues, as section 26 provides.

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

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

27.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 acknowledging this Policy, the user confirms receipt, understanding and the obligation to comply with YT24 incident-reporting and escalation requirements as a condition of authorized system access, 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.

27.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 Security & Incident Escalation Policy as part of that recurring sign-in control.

By acknowledging this Policy, the user confirms receipt, understanding and the obligation to comply with YT24 incident-reporting and escalation requirements as a condition of authorized system access, subject to applicable law.

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.

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