Privacy Notice

WWAIT is a service that models a psychotherapeutic process in timed sessions. It is not healthcare, not a medical device, and not a substitute for treatment. It does not diagnose, does not prescribe and does not make treatment decisions.

The organisation operating WWAIT is the data controller for the personal information described in this notice. Its identity and contact details are in section 3 and section 32.

This notice covers the WWAIT website, the WWAIT account, the session interface (typing and speaking), the process memory, scheduling, payments and the emails WWAIT sends you.

It does not cover services you reach by leaving WWAIT, including crisis and emergency services listed on the safety page, or your own device, browser or network provider.

The controller decides why and how your personal information is processed. For everything described here, that is the organisation operating WWAIT.

Payments are an exception. Purchases are made through Stripe Managed Payments, where Sold through Link, LLC (United States) is the merchant of record and processes the transaction data it needs as seller under its own privacy terms. Stripe also processes payment data to run the payment service; in Europe this is Stripe Payments Europe Limited, which acts as a controller for some purposes (such as fraud prevention and its own legal obligations) and as a processor for others, depending on the purpose.

WWAIT collects only what the service actually needs. In practice this is: account and identity data, the four onboarding basics, your language and interface preferences, your session content and the memory distilled from it, scheduling and entitlement data, payment references, technical and security data, and — for pilot testers — pilot administration data.

Each of these is described in the sections that follow, together with why it exists.

When you create an account, WWAIT receives your email address and your sign-in identity — either a Google account or an email address with a password. Passwords are handled by the authentication service and are never visible to WWAIT.

Before your first session, WWAIT asks four basics once: the name you would like to be called, your age in years, your gender (woman, man, other, or prefer not to say) and your country. Your country determines which local crisis resources WWAIT can point to; it is deliberately kept separate from your interface language and from your conversation language.

WWAIT also stores your interface language, your conversation language, your time zone, whether you prefer to type or speak, and your voice settings for WWAIT's own speech.

• Email address and sign-in identity
• Preferred name, age, gender, country
• Interface language, conversation language, time zone
• Input and output preference, voice settings

During a session, each turn — what you write or what your speech was transcribed into, and what WWAIT replies — is held so the conversation can continue. Turn text is kept: it forms your process's conversation history. Earlier conversations stay in the same conversation view and you can scroll back through them, and they are included in your data copy. It goes when you delete your process or your account, or when you ask for one particular matter to be forgotten.

For each session WWAIT stores structured records: which session it was, whether it was a Regular or Acute session, when it started and ended, how long it actually lasted, counters used for capacity (tokens, seconds of speech recognised, characters spoken), the session's focus and themes, a summary for the process, and whether the session involved a safety concern.

WWAIT also stores a distilled memory per session — the narrative, the situations, the people you mentioned, the thoughts and emotions, the goals and concerns, the insights, the open questions, what to return to next time and what changed. This is written in WWAIT's words, and the conversation itself is kept verbatim alongside it.

• Turn text: kept as conversation history for as long as your process exists
• Session records: type, times, duration, capacity counters, focus, themes, summary
• Session memory: narrative, situations, people, thoughts, emotions, goals, insights, open questions, changes
• Safety signal: whether a session involved a risk or crisis situation

When you speak, your browser captures audio from your microphone and turns it into a compact audio file in memory. That file is sent once, over an encrypted connection, to WWAIT's server, which passes it straight to the speech-to-text provider and waits for the text.

WWAIT does not write your audio to any database, file storage or disk. It is not cached, not queued and not attached to your session. Once the text comes back, the audio is gone from WWAIT.

Only the resulting text enters the process — exactly as if you had typed it. From there it is treated like any other turn: it is kept as part of your conversation history, exactly like a message you type.

When WWAIT speaks, the reply text is sent to the text-to-speech provider and the audio is streamed back to your browser. WWAIT does not store the generated speech.

What WWAIT cannot see is what a provider does inside its own systems. WWAIT can state precisely that it stores no audio itself; it relies on its providers' terms for their side, and does not claim more than it can verify. See section 16.

• No recording of your voice is ever stored by WWAIT
• Audio exists only in memory and in transit, for the length of one transcription
• Only the transcribed text is kept, and only as long as any other turn
• Reply text is sent for speech synthesis; the resulting audio is not stored

Running a web service produces technical data. WWAIT's own server logs record technical events — a request's purpose, a language code, sizes and timings, error messages and identifiers such as a session id — so faults can be found. They are written not to contain what you said or what WWAIT replied.

The hosting, database and network layers WWAIT runs on produce their own operational and security logs, which can include IP addresses, timestamps and request metadata. Those logs exist to keep the service available and to detect abuse.

The voice pipeline produces measurements — sample rates, durations, byte counts, timing, whether the microphone was live — that stay in your browser tab for the lifetime of that tab and are not uploaded.

WWAIT never sees or stores your card number. Checkout and billing run through Stripe Managed Payments, and Sold through Link, LLC is the merchant of record for the purchase.

What WWAIT stores is what it needs to know what you are entitled to: your plan, the price and currency of your plan, the status of the subscription, the identifiers Stripe uses for your customer and subscription record, any one-off first-session purchase, and the payment events Stripe reports, so entitlement can be checked on the server rather than trusted from the browser. To open a checkout, WWAIT gives Stripe only your WWAIT user identifier, your email address and the product you are buying.

If you send feedback, WWAIT stores its category and the message you wrote. Feedback is voluntary; you decide what goes into it.

Pilot testers additionally have a pilot record with the invited email address, the invitation language, the chosen session rhythm, administrative notes and the acceptance of the pilot confidentiality terms, including version and timestamp.

Messages sent to you by an administrator are stored with their subject, body, recipient and whether they were read.

WWAIT uses your information to run your process and nothing beyond it: to hold a session, to keep the conversation coherent, to carry understanding from one session to the next, to schedule your sessions, to know what you are entitled to, to keep the service secure, to answer you when you contact us, and to meet legal obligations such as accounting.

WWAIT does not use your session content for advertising, does not sell it, does not share it for anyone else's marketing, and does not use it to build products for third parties.

Under the GDPR, every purpose needs a legal basis. WWAIT's are:

• Providing the service and running your sessions — performance of a contract (Art. 6(1)(b)).
• Maintaining your account, entitlement, scheduling and process continuity — performance of a contract (Art. 6(1)(b)).
• Sensitive information you share in a session — your explicit consent (Art. 9(2)(a)), on top of the contract basis; see section 13.
• Security, abuse prevention and service integrity — legitimate interests (Art. 6(1)(f)), balanced against the fact that these logs are kept free of session content.
• Accounting and tax records for payments — legal obligation (Art. 6(1)(c)).
• Voluntary feedback — consent (Art. 6(1)(a)), which you give simply by choosing to send it.
• Service emails you need in order to use WWAIT (verification, booking, data-copy links) — performance of a contract (Art. 6(1)(b)). Marketing emails would require separate consent and are never a condition of using WWAIT.
• Analytics and advertising — WWAIT runs no analytics or advertising trackers, so no data is processed for those purposes at all.

WWAIT is not healthcare, and that boundary does not remove its data protection duties. What you bring to a session may reveal your health or mental health, your sexuality, your religion or beliefs, your political opinions, your trade union membership or your ethnic origin. In GDPR terms that is special category data under Article 9, and WWAIT must assume it will occur.

WWAIT does not ask you for it, does not require it and does not infer diagnoses from it. But because it is inherent to the purpose, WWAIT relies on your explicit consent under Article 9(2)(a). That consent is asked for separately from everything else, before your first session, and is recorded with its version, language, and the time you gave it.

You can withdraw it at any time. Withdrawal stops WWAIT from continuing to process that material for your process going forward; it does not by itself erase what is stored, because erasure is a separate decision that stays in your hands. Both actions are available on the Own process page.

You are interacting with an AI system, not a human therapist, and never a human reading along in the background.

What you write or say is sent to a large language model, together with WWAIT's own instructions and the relevant part of your process memory, in order to produce the next response. Your speech is converted to text by a speech recognition model, and WWAIT's replies are converted to audio by a speech synthesis model.

The AI is used to run the process: to listen, to ask, to reflect, to notice patterns and to keep continuity. It is not used to diagnose you, to assess you clinically, to score you, or to decide anything about your rights, your money or your access to anything outside WWAIT.

AI output can be wrong. WWAIT's observations are working hypotheses about a conversation, not findings about you.

Process memory is what makes WWAIT a process rather than a chat. It holds, in WWAIT's own words, the goals you have named, emotional and relational themes, recurring patterns, working hypotheses and hypotheses already dropped, insights, contradictions, what has changed over time, what is unfinished, what is not yet understood, and what to return to next.

It is readable only by you. There is no named viewing right, no sharing link, no administrative route and no emergency override into it. If you want to share it, you share your own copy of your data, outside WWAIT.

You can ask WWAIT to forget a single matter in the process memory. How that works is described in section 22.

WWAIT keeps the list of recipients as short as the service allows. Data is shared only with the providers that make the service work, each acting as a processor on WWAIT's instructions, except the payment parties: Sold through Link, LLC as merchant of record, and Stripe for the purposes for which it is itself a controller.

• Hosting, database and authentication — stores your account, profile, sessions, memory, scheduling and entitlement data.
• AI gateway and the language model behind it — receives your session content and process context in order to produce each response.
• Speech-to-text provider — receives your spoken audio for the length of one transcription.
• Text-to-speech provider — receives WWAIT's reply text in order to produce speech.
• Stripe Managed Payments — Sold through Link, LLC is the merchant of record (payment, indirect tax, receipts, transaction-level disputes and payment support); Stripe (in Europe Stripe Payments Europe Limited) runs the payment service. They receive your payment details directly, not through WWAIT.
• Email delivery — receives your email address and the message content of service emails.
• Professional advisers and authorities — only where legally required, and only what is required.

Some of these providers, or their own subprocessors, process data outside the EU/EEA — the AI, speech recognition and speech synthesis providers in particular.

Where that happens, the transfer relies on the mechanisms recognised by the GDPR: an adequacy decision where one applies, otherwise the European Commission's Standard Contractual Clauses together with the provider's own supplementary measures, as set out in that provider's data processing terms.

WWAIT states the mechanism rather than naming a specific country chain, because a provider may operate in several regions. If you need the current, provider-by-provider position for your own assessment, ask using the contact details in section 32.

WWAIT keeps information for as long as it is needed for the purpose it was collected for, and no longer. In practice:

• Turn text (your conversation history): kept for as long as your process exists, the same as the session memories. Deleted when you delete your process or your account.
• Session records, session memories and process memory: kept for as long as your process exists, because continuity is the point of the service. Deleted when you delete your process.
• Account and profile: kept while your account exists.
• Scheduling data: kept with your process and deleted with it.
• Payment and accounting data: kept as long as accounting law requires, which is longer than your process, and cannot be deleted on request while that obligation lasts.
• Data-rights audit events: metadata only — which action happened and when, never its content — kept as evidence that your requests were carried out.
• Data copy links: single use and valid for one hour, after which the link is dead.
• Voice audio: not retained at all.
• Technical and security logs: kept for a short operational period by the hosting and network layers under their own retention settings.
• Backups: your deletion applies to live data immediately; encrypted backups roll over on the hosting provider's own cycle and are not searched for individual records.

On the public website and in the purchase flow WWAIT may use Google Analytics 4 and Google Ads conversion measurement (Google Ireland Ltd / Google LLC as recipient). The purpose is to measure where visitors come from and whether advertising leads to sign-ups, purchases and a first session. Only a fixed list of events is sent (pricing page viewed, sign-up started/completed, purchase started/completed, first session started), with page address without query parameters, purchase amount and currency, and technical data that Google's tags collect, such as device and approximate location. Session content, anything you write or say, your process data, your name or email address are never sent to Google. There is no remarketing and no ad personalisation. In the EU/EEA, the UK and Switzerland — and wherever your location cannot be determined — nothing is measured until you accept in the cookie banner; declining is as easy as accepting, and you can change or withdraw your choice at any time under Cookie settings in the footer. Your choice, its time and the banner version are stored in your browser. Elsewhere this measurement runs by default; the legal basis in consent regions is your consent.

What the service stores in your browser is strictly functional — it is what makes signing in and your own settings work. Apart from the measurement choice above, everything is necessary for the service you asked for. In full, the browser holds:

• the authentication session that keeps you signed in, and the technical values needed to refresh it;
• your chosen interface language;
• your chosen currency on the pricing page;
• your voice and input preferences as they are applied in the interface;
• a measured microphone noise-floor value, used only to decide when your speech has started on your own device;
• the open or closed state of a panel, and an acknowledgement that a notice has been shown in this browser tab;
• an optional debug flag you can switch on yourself if you are helping diagnose a voice problem.
• only while the payment window is open: cookies and similar technologies that Stripe and Link set themselves, for fraud prevention, authentication and Link services, under Stripe's own cookie policy (https://stripe.com/legal/cookies-policy).

All traffic between your device, WWAIT and its providers runs over encrypted connections. Data stored in the database is encrypted at rest by the hosting platform.

Access to your process data is enforced at the database level, per row, against your own signed-in identity — not merely hidden in the interface. Administrative accounts are a separate, server-checked role and are limited to operational data: they can see usage counters, entitlements, invited pilot emails and feedback you chose to send. They cannot read your session content, your session memories or your process memory.

WWAIT applies data minimisation deliberately: logs are written not to contain session content, diagnostics are numeric, and audio is never stored.

You have the right to access your personal information, to receive a copy of it, to have inaccurate information corrected, to have information erased, to restrict or object to certain processing, to data portability where it applies, to withdraw a consent you have given, and to complain to a supervisory authority.

Four of these are built into the product and need no request at all: forgetting a single matter, deleting your whole stored process, downloading a copy of your data, and closing your account entirely. They are on the Own process page.

For anything else — correction of profile details you cannot edit yourself, restriction, or objection — contact us using section 32. WWAIT answers within one month, and tells you if the request needs longer or cannot be met in full, and why.

You can tell WWAIT, in the session itself, to forget a specific matter. You do not have to justify it and you will not be asked why.

WWAIT confirms what it understood you to mean, then removes that matter from the process memory and from your session memories, deletes matching turn text, and stores a deletion mark so the matter is not raised again. The deletion mark records the subject in your own words, and nothing else about it.

The list of what has been forgotten is visible to you on the Own process page.

You can delete your whole stored process at any time, from the Own process page. Deletion is confirmed once and then carried out on the server. Nothing is questioned, and no reason is asked for.

This deletes your turn text, all session memories, your process memory, your session records and your appointments.

It deliberately does not delete: your account and profile, your subscription or entitlement record, payment and accounting records subject to legal retention, and the metadata-only audit trail showing that a deletion happened. Keeping the entitlement record is what stops a deletion from being read as a new customer starting fresh; keeping the audit trail is what proves your request was honoured.

If you want the account itself closed and the remaining account data erased, ask using section 32. That is handled as an erasure request, not as a self-service button, because it also ends any live subscription.

You can request a copy of your data on the Own process page. WWAIT creates a single-use link valid for one hour and also emails it to you as a notification. The email never contains your data.

The copy itself is generated only when you, signed in, actually download it, and is handed straight to your browser as a PDF. No export file is stored anywhere.

The copy contains your profile, subscription record, session records, session memories, process memory, appointments, the list of matters you have had forgotten, your data-rights events, any feedback you sent and any pilot terms acceptance. It does not include the temporary turn text of a session that has not been consolidated yet, and it does not include payment records held by Stripe or Sold through Link, LLC — those you can request from Stripe.

Two consents are asked for, separately, before your first session: an acknowledgement that you have been shown this privacy information, and an explicit consent to the processing of sensitive information you may share in sessions.

Each is recorded with the document version, the language you saw it in and the time. They are never bundled into one vague checkbox, because they rest on different legal grounds.

You can withdraw the explicit consent at any time on the Own process page. Withdrawal is recorded as a new event; the earlier record stays as evidence of what was true at the time.

WWAIT is intended for people aged 18 and over. We do not knowingly offer the service to anyone under 18 and we do not seek to collect their personal data. Your age is asked once during onboarding, where you also confirm that you are at least 18.

If we learn that someone under 18 has used the service, we will handle the situation in line with applicable law and our data protection obligations. If you believe a minor has created an account, contact us using section 32.

WWAIT does not make decisions about you that produce legal effects or similarly significant effects, based solely on automated processing, within the meaning of GDPR Article 22.

The AI generates conversation and maintains process memory. It does not decide your entitlements, your price, your access to the service, your creditworthiness, or anything about you outside WWAIT. Entitlement and scheduling are rule-based checks against your plan and your bookings, not model judgements.

WWAIT does not produce diagnoses, clinical risk assessments or treatment decisions, and does not report anything about you to any outside party automatically.

WWAIT sends you the emails you need in order to use the service: address verification, booking and session matters, data-copy links, and pilot administration if you are a pilot tester.

Marketing email is never a condition of using WWAIT. If marketing is ever introduced, it will be based on separate, freely given consent, and it will be withdrawable in one step.

Purchases are made through Stripe Managed Payments. Sold through Link, LLC (United States) is the merchant of record: it sells the purchase to you, handles the payment and indirect tax such as VAT, issues receipts, and handles transaction-level disputes and payment support. Your card statement shows LINK.COM* followed by WWAIT's name.

Your card and billing details are collected by Stripe directly, never by WWAIT. Sold through Link, LLC processes the transaction data it needs as seller, and Stripe processes payment data to run the payment service, in each case under their own privacy terms; Stripe acts as a controller or a processor depending on the purpose. Sold through Link, LLC is in the United States, and Stripe describes how international transfers are protected in its privacy policy. More information: https://stripe.com/privacy and https://link.com/privacy.

When this notice changes materially, its version is raised and you are shown the updated information the next time you sign in, before your next session.

Editorial corrections that do not change meaning are made without interrupting you. The version and effective date at the end of this notice always tell you which wording is current.

If you think WWAIT has handled your personal information wrongly, tell us first — it is usually the fastest way to fix it.

You also have the right to complain to a data protection supervisory authority. In the EU/EEA you may complain to the authority in the country where you live or work, or where the issue arose. In the United Kingdom this is the Information Commissioner's Office. Other jurisdictions are covered in the supplements below.

For any privacy question, or to exercise a right that is not built into the product, use the contact details below.

This is the current version of the WWAIT Privacy Notice. Earlier versions are retained internally, together with the record of which version each person was shown.