Your reflection answers never leave your browser
The answers you give on the children, teens, parents and adults pages are held in the memory of the browser tab you are using. They are not sent over the network, not written to a database, not included in the booking form and not passed to any analytics tool. Closing or refreshing the tab discards them permanently. We never see them, which means we cannot read them back to you later, and no one can request them.
This is a deliberate design decision, and it has a trade-off: because we do not store your answers, we also cannot show you a saved report or track change over time. If that changes, this page will be updated before it happens.
What a booking request contains
Booking is a separate, deliberate step. The form collects only the following, and only if you submit it yourself.
| Field | Why it is collected |
|---|---|
| Confirmation reference | Identifies your request when you call or email. |
| Audience and age band | Suggests who the conversation is for. |
| Online or in person | Arranges the call link or the room. |
| Preferred date and time | Proposes a slot. Not a confirmed appointment. |
| Name, email, mobile number | To confirm the session and reach you about it. |
| Parent or guardian name, email, mobile (under 18 only) | Required point of contact for a safeguarding check. |
| Transactional contact consent | Records that you agreed we may reply about this session. |
| Research consent (optional) | Records a yes or a no, separately from the booking itself. |
There is no free-text box asking you to describe what is going on. Context is gathered in a session, where the right protections apply, rather than in an unprotected form field.
This build does not store booking requests yet
The booking API validates requests and generates a reference, then hands them to a placeholder storage adapter that is clearly marked as unfinished. The current adapter is supabase, so nothing a booking form submits is durably stored. The confirmation screen tells you this.
The planned destination is a separate Supabase project area using the wellbeing schema. It will not share tables, credentials or a database with the Jignyasa shop.
Research contact is optional and separate
On the reflection pages and on the booking form there is a separate, unticked checkbox about optional research conversations. It is never pre-selected, it is never required, and it does not change what you can see or book. Declining is the default and has no consequence.
Because your reflection answers are never transmitted, a research conversation can only be about the experience of using the site. It cannot include the content of your answers.
Cookies
- Admin session cookie. Only staff who type the admin password receive a cookie, named
jy_wellbeing_admin. It is httpOnly, expires automatically and is never set for visitors. - No tracking cookies for visitors. The reflection pages set none at all.
- Analytics. No analytics tool is configured on this deployment, so none is loaded.
Who else sees your information
In this build, no one. There is no advertising network, no third-party tracker and no marketing tool connected to the wellbeing hub. Your booking details are not added to the shop’s customer list, and shop activity is never used to personalise the wellbeing site.
If that changes, the change will be described here first.
Law, retention and your rights
We intend to handle personal data in line with the Digital Personal Data Protection Act, 2023. A published retention period, a data controller registration and a working deletion process are not yet in place, which is one reason the booking service is deliberately not storing anything yet.
When storage is switched on, this page will state the retention period, how to request access, correction, export or erasure, and who to contact. You will not be asked to accept a change retroactively.
Questions and complaints
Email hello@jywellbeing.com with any privacy question, and you will get a human answer.