There is no record of your session, because none is made.

Your conversation is held in the browser tab you have open. When you send a message, that message and the exchange so far travel to our application, which uses them to find relevant passages from TGGR’s library and to write a reply. Then they are gone. Nothing is written to a database, a file, or a log on the way through.

This is why the conversation has to travel with each message: the application has nowhere to keep it between one message and the next. What looks like an inefficiency is the mechanism.

It also means there is no session history to return to. Close the tab and the conversation is gone, not deleted, but never recorded. There is nothing to delete because there was never a record to begin with.

A passkey is an access code issued to one person. When you enter it, the system checks it against a list of valid codes and lets you in. That is the whole of what it does.

What it is not: it is not an account, it carries no name, no email address and no employer, and it is not attached to anything you go on to say. We store passkeys as one-way hashes, which means the database holds enough to recognise a valid code and not enough to reconstruct one.

The system records, once, that a code has been redeemed. That is a single yes-or-no so a code can be managed, not a record of when or how often you have visited.

At the end of a session you can download a transcript. Because nothing is retained on our side, that file is the only copy that will exist anywhere, and it belongs entirely to you.

We suggest password-protecting it before you save it. It contains everything you said, and once it is on your device its safety is a matter of where you put it.

If you want continuity between sessions, you can upload that file at the start of a future session to restore the context. That is the only mechanism for continuity, and it stays in your hands throughout.

Being clear about the exceptions matters more than the headline. Here is everything the database holds. None of it is conversation content.

Passkeys, as one-way hashes

Enough to recognise that a code is valid, never enough to reproduce it. The plaintext exists only at the moment it is issued to you.

Whether a passkey has been used at all

A single yes-or-no, recorded the first time it is redeemed. Not how often, not when since, not from where.

Administrator accounts

For TGGR staff who manage the library. Passwords are stored as one-way hashes. A second factor is supported and can be switched on by TGGR.

The Foundational Library

The documents TGGR uploads and the search index built from them. This is TGGR's own material, not yours.

Sign-in counters

To slow down anyone guessing at codes. The identifier is itself stored as a hash, enough to recognise a repeat attempt, not enough to know whose.

Feedback you choose to submit

Only if you complete the questionnaire at the end, and only what you put in it. It is not linked to your session.

Anything you send through the contact form

Your message, its subject and the address to reply to, so the Development Administrator can answer you. That page is outside the confidential space and says so: nothing from a mentoring session reaches it, and a contact message is never linked to a passkey or a session.

A log of administrator actions

Who changed what in the library, and when. It contains no user and no conversation content, there is nothing of yours for it to record.

There is no conversation table, no message table and no session table anywhere in the database. That is a design decision, not a setting that could be changed by accident.

Three organisations are involved in running this service. Each account belongs to TGGR Ltd.

Of these, only OpenRouter ever sees the words of a conversation, and only for as long as it takes to write a reply, with one addition if you choose voice, when Deepgram also sees them in order to write down what you said and to read the reply back. No analytics service, advertising network or tracking script runs on this site.

A small number of cookies, set when you sign in, which together tell the site you are allowed to be here and keep the sign-in itself safe from tampering. None of them carries your name or anything you have said, and they expire on their own. There are no analytics, advertising or tracking cookies of any kind.

Your choice of light or dark appearance is remembered in your own browser and never sent to us.

This is a reflective space and it is not an emergency service. It does not monitor what you write and no one is watching a screen at the other end. If you are in danger or in crisis, please contact the emergency services or a crisis line in your country.

If you have a question about any of this, or about a feedback submission you have made, please get in touch through the contact page.

TGGR Ltd is responsible for this service and for the accounts described above. Formal data protection contact details will be published here before the service opens beyond Stage 1 testing.