Check-in responses
Radio selections and preparation notes are handled in the current page. They have no form action, are not posted to the server, and disappear when the document is reloaded or closed.
Reflection tools run entirely in your browser and are not sent to or saved by Yourself.
| Reflection answers | Processed in browser memory; not submitted to the Yourself server. |
|---|---|
| Accounts and profiles | No user account or longitudinal mental-health profile is created by this build. |
| Contact | A mailto link opens your email provider; there is no website contact-form database. |
| Browser notifications | SDK4Push may process device, network, subscription, and click_id information under its own terms when the integration loads. |
| Server logs | The hosting layer may record technical request data; the operator should document retention and access controls. |
Your answers and on-screen summary are calculated in browser memory. Yourself does not create an account, transmit responses, or store them. Reloading or leaving the page clears the current summary.
This site does not use a contact form. Selecting the email link opens your own email application; any message is then handled by you and your email providers. Do not include medical records or sensitive health details.
This build includes SDK4Push to offer browser notifications. The SDK receives the page’s click_id parameter when one is present and may process browser, device, network, and subscription information under its own terms. Notifications require browser permission and can be revoked in browser settings.
This build includes the Stay22 script, which can attach travel and accommodation booking suggestions to relevant links and may process page, browser, device, and network information under Stay22’s own terms. Yourself may earn a commission on bookings made through it. This build otherwise includes no analytics, display-advertising scripts, or non-essential cookies. Standard server access logs may still record technical request details such as time, requested URL, IP address, and user agent.
Links to outside services are clearly identified. Their privacy practices apply after you leave Yourself.
Privacy becomes clearer when each interaction is traced from the page to the systems that may receive it.
Radio selections and preparation notes are handled in the current page. They have no form action, are not posted to the server, and disappear when the document is reloaded or closed.
Browser-notification permission belongs to the browser profile and can persist after leaving the page. Clearing a check-in does not revoke it; use browser site settings for that choice.
Selecting the contact link transfers the interaction to your email application and providers. Their storage, security, and retention apply, so minimize sensitive information before sending.
Crisis services, institutional sources, regulators, and provider directories operate independently. Review their location, identity requirements, cookies, and privacy terms before sharing information.
Each private self-check explains that answers remain in browser memory and clear when the page is reloaded or left.
For editorial questions, the contact page opens your own email application and reminds you not to include health records or urgent disclosures.
The legal and clinical limits of using the material are described separately in the terms of use .
Privacy is partly architectural and partly controlled by your browser, device, email provider, and the external sites you choose to visit.
No. The response summary is calculated in your browser and is not posted to the server.
No. Notification permission is controlled separately by your browser and must be changed in browser settings.
No. Once you open another service, its own privacy terms and technical practices apply.
No. The editorial email address is not a clinical channel. Do not send records, diagnoses, or urgent safety information.