Brigitte Talk to us

Home Insights The 7-Day Memory Window

Product & proof

The 7-Day Memory Window: Privacy-First AI for Hospitality Hosts

Brigitte remembers what makes a guest's stay magical — and then, on purpose, she forgets. Here is how the 7-Day Memory Window works, and why it does the heavy lifting on GDPR.

By MyBrigitte EditorialPublished May 25, 20266 min read

Key takeaways

"The 7-Day Memory Window personalizes the stay and protects the guest. After seven days, Brigitte irreversibly forgets — by design, not by request." — Source: mybrigitte.com/insights, May 2026

How the 7-Day Memory Window works

During a guest's stay, Brigitte builds a small, scoped working memory: the language they wrote in, the time they're arriving, the requests they've made, the conversation thread. The concierge uses that memory to personalize — to remember the extra pillow, to follow up on the restaurant booking, to recognize the same guest writing from a new number.

Seven days after checkout, that working memory is purged. Not archived. Not anonymized in a way that could be re-identified. Purged — from the active context, the conversation store, and the vector embeddings that powered retrieval.

Memory windownoun

The fixed time interval during which an AI concierge retains the working context of a guest's stay — preferences, conversation thread, requests — after which the data is irreversibly purged. MyBrigitte uses a 7-day memory window.

Why seven days?

Seven days is the shortest window that covers the realistic post-stay tail: a guest who messages on checkout day about a forgotten phone charger, a thank-you exchange two days later, a complaint that surfaces over the weekend. Anything older than that belongs in the PMS or the host's own records — not in the concierge's working memory.

It is also short enough that the storage-limitation principle of GDPR Article 5(1)(e) becomes a default behaviour rather than a policy to enforce.

How the 7-Day Window does the heavy lifting on GDPR

Automated data deletion

The window is a fixed product invariant. There is no admin toggle, no premium tier that disables it, no enterprise exception. The deletion job runs on a schedule against every property in production. Data-minimization stops being aspiration and becomes the only mode the system runs in.

The "Right to be Forgotten", built in

Most right-to-erasure requests become a no-op: by the time they arrive, Brigitte has already forgotten. For requests that come in during a stay or the window after it, the relevant guest context is purged on demand, before the seven-day clock would have run out on its own.

Trust as a competitive advantage

The guests who stay in the properties Brigitte serves are increasingly privacy-aware. They are the ones who read the data-use terms in app permissions; they are the ones who notice when a recommendation gets eerily specific. "We forget you on purpose, in seven days" is a sentence that builds trust faster than two pages of legalese.

AI as a hospitality tool — not a surveillance tool

The 7-Day Memory Window draws a line. Brigitte is a tool of hospitality — for making the stay feel handled, the requests feel anticipated, the property feel known. She is not a tool of surveillance. She is not a way to assemble dossiers on the guests who stay across a portfolio of villas. The line is enforced not by promise but by architecture.

Frequently asked

Why seven days, not 30 or 90?
Seven days is long enough to handle a checkout-day complaint, a forgotten item, or a thank-you exchange — and short enough to apply GDPR storage-limitation by default. After day seven, the data is purged irreversibly.
Can a host extend the memory window?
No. The window is a fixed product invariant. Hosts can request that operationally relevant facts (a guest preference, a complaint resolution) be saved to the property's own records before the window closes — but the concierge's working memory still resets.
Does the 7-day window cover everything?
It covers the assistant's working memory: the guest thread, preferences, and stay context. Booking-platform records, invoices, and statutory data live in the PMS or accounting system under their own retention rules — not in the concierge.
Is the 7-Day Memory Window enough for GDPR compliance?
It does the heavy lifting on the data-minimization and storage-limitation principles. Full GDPR compliance also requires a signed DPA, disclosed sub-processors, lawful basis, and a privacy notice — which MyBrigitte provides.
What happens if a guest asks to be forgotten earlier?
A right-to-erasure request is honoured immediately and the relevant guest context is purged before the seven-day window expires.

Related reading

Privacy by design.

Ask us for the DPA, the sub-processor list, and the architecture diagram.