Key Information
Y.O.D.O. at a glance: the most important things to know.
Version: 2.1.0 · Last updated: 15 May 2026
This page is a summary only. It highlights key points from our Terms and Conditions in plain language. If there is any conflict between this page and our full Terms, the Terms apply.
What Y.O.D.O. does
- •Y.O.D.O. provides Scheduled Check-ins. The default frequency is monthly on all plans. On Premium and Supreme, you can change this to daily, weekly, or fortnightly.
- •If a Scheduled Check-in is not confirmed within the Response Window (8 hours from your scheduled check-in time), we may send Reminders and may contact Delegates after the Response Window ends, based on the Account Holder's settings.
- •A missed check-in or a Status Check does not mean a Passing.
- •Messages are delivered only after a Passing is reported and verified through the Service.
What Y.O.D.O. is not
- • Y.O.D.O. is not emergency or crisis support
- • Y.O.D.O. is not medical monitoring, medical advice, or legal advice
- • Y.O.D.O. is not a will
Trial and billing
Free Trial: 14 days
No payment details required to start.
- •If you add payment details during the trial: you consent that paid billing starts automatically at trial end unless you cancel before then.
- •If you do not add payment details by trial end: no charge, check-ins stop, Delegates are not contacted.
- •Subscriptions renew automatically unless cancelled.
Cancellation
- •You can cancel online in the Service.
- •Cancellation confirmation: on-screen + email.
- •If you cancel, you keep access until the end of your current paid period unless the Service clearly states otherwise.
- •UK consumers have a 14-day right to cancel a new paid subscription under the Consumer Contracts Regulations. See our full Terms for details.
Key timing concepts
Scheduled check-in time
Your chosen day and time
Response Window
8 hours from your scheduled time
Escalation buffer options
8, 16, 24, or 48 hours
Staged escalation
First, then +24h
Escalation settings
Escalation is enabled while your plan is active. You choose:
Buffer
8, 16, 24 or 48 hours from your scheduled check-in time
Mode
Staged or All at once
Status Check
Delegates can start a Status Check where there is a serious concern. A Status Check does not mean a passing.
During an open Status Check window (72 hours), the Account Holder normally receives up to one reminder per day to log in and respond.
The 72-hour resolution window
When a Concern is raised about a Care Pause, a "They are OK" action, or a Passing report in multi-Delegate accounts:
- •The account is flagged as having an unresolved conflict
- •The Account Holder is prompted to check in
- •We normally send up to one reminder per day during the Status Check window
- •Other Delegates can confirm or dispute the original action
- •If the Account Holder responds, the conflict is resolved
- •Delegates who were notified may receive follow-up updates when action is no longer needed
- •If no resolution occurs within the 72-hour window, you may contact Support for assistance
For single-Delegate accounts, only the Account Holder or our support team can override a Delegate's action.
Passing report disputes
When a Delegate reports a Passing, other Delegates are notified and have 72 hours to respond:
"I can confirm they're OK"
The AH is alive; report may be mistaken
"I dispute this report"
Triggers additional review
"I can confirm this passing"
Corroborates the report
- •If disputes are raised, Message release may be delayed pending additional verification
- •Tie-break rule (Passing disputes): If Delegate responses are evenly split, verification continues (the status quo is maintained) until additional evidence changes the balance, the Account Holder responds, or Support reviews the matter
- •False confirmations intended to delay legitimate verification may result in account suspension
Care Pause tie-break rule: If Delegate responses to a disputed Care Pause are evenly split, the Care Pause continues until (a) the Account Holder records a response, (b) a Delegate submits new evidence that changes the balance, or (c) the 72-hour window expires and check-ins resume. See our full Terms (section 13.8A) for details.
Status Check availability
"Request a Check-in" is unavailable when:
- •A Care Pause is active
- •A dispute is open and unresolved
- •A Passing verification is in progress
"Raise a Concern" and "Report a Passing" remain available to Delegates where applicable, even when "Request a Check-in" is restricted.
Passing verification and Messages
A missed Scheduled Check-in, a Status Check, or a lack of response does not mean a Passing.
Messages are delivered only after a Passing is reported and verified through the Service. Passing verification means the Verification step for a reported Passing.
Recipient access window
Released Messages are available to Recipients for 12 months from the release trigger, unless an extension is granted under the Terms.
After that, Message content is removed from our active systems, with limited retention in backups and logs as described in our Privacy Policy.
Deletion (high level)
- Non-response:Pre-deletion may start 30 days after a missed check-in and deletion may occur after 60 days if there is no Account Holder response and no Delegate Outcome.
- Inactive:Accounts may be deleted after 30 consecutive days Inactive.
- Subscription on deletion:If we delete your account under the T0-based or Inactive deletion rules, we take reasonable steps to stop future subscription renewals.
"Deleted from our active systems" means removed from our live databases and no longer accessible through the Service. Backups/log retention may still apply as described in the Privacy Policy.
Where we serve
Y.O.D.O. is offered to people in the United Kingdom and the European Economic Area. People in other countries can register on their own initiative; the service is operated to UK and EEA standards and is not tailored to local law elsewhere. Access from jurisdictions subject to UK or EU sanctions regimes may be unavailable. UK GDPR applies to all users (Article 3(1) UK GDPR); EU GDPR applies to processing of EEA users (Article 3(2)(a) EU GDPR).