Privacy Policy.

The Aikebom platform is provided by a sole trader (empresário em nome individual) registered in Portugal (“Aikebom”, “we”). Contact: hello@aikebom.com.

For this website (including the book-a-demo form), Aikebom is the data controller. For a deployed concierge, the client — the event organiser or the hotel — is the controller of their guests’ data, and Aikebom processes it on their behalf under a data-processing agreement (available on request).

No account, no sign-up. Using a concierge creates an anonymous session (an HMAC-signed, httpOnly cookie) holding: the conversation history (including transcripts of voice conversations), the trip preferences you mention (dates, interests, dietary needs), and any itinerary you build. That is what lets you leave and pick up where you stopped.

Two optional additions exist when a client enables them: a verified guest link (a signed link carrying, at most, your name and room/seat so the concierge can greet you and route requests — delivered individually to you, expiring with the stay), and reservation datapushed by the property’s management system (booking dates, room number, moves) so answers stay current.

Events have one published cut-off for everyone: shortly after the event ends (by default about two weeks after the final day), every session — conversations, profiles, itineraries — is deleted automatically.

Hotels & resortsdelete per guest, on the guest’s own clock, triggered by inactivity: once you stop using the concierge, your data is deleted about a week after your last message — and never lives more than 45 days past it, whatever happens. A known checkout date only ever protects a still-in-house guest from early deletion; it is never what triggers deletion. Nothing is kept for the life of the property.

Both schedules are enforced by Aikebom in the engine itself — they are not settings a client can quietly extend. After deletion, only anonymised, aggregate usage statistics remain (counts and costs, never conversation content or personal data). Deleting a session also disables any itinerary share links it created.

Voice conversations are processed in real time: audio is streamed for transcription and replies are synthesized as speech. We do not store the audio. The text transcript joins your conversation history and follows the same retention as chat, above.

No advertising or tracking cookies, no profiling for ads, no selling or renting data — ever. Nothing one client’s guests teach the concierge is used for another client. Our AI providers are used via their APIs, which do not train models on this data.

Strictly functional only: the anonymous concierge session cookie, an admin session cookie for staff who log in, and a language-preference cookie on this website. No third-party or advertising cookies — which is why you don’t see a consent banner.

If you book a demo or join the early-access list, we store what you submit (email, and whatever else you choose to fill in) and use it solely to respond — including a confirmation email. Write to us and we’ll delete it.

Running the service means using specialised providers. Each receives the minimum the feature needs:

Some providers process data outside the EU (notably in the United States) under their standard contractual clauses. Queries sent to search and mapping providers carry the content needed to answer — never your session identity.

Under the GDPR you can request access, correction, deletion, restriction or portability of your data, and complain to a supervisory authority (in Portugal, the CNPD). For a deployed concierge, the event or property you used it at is the controller — you can go to them or directly to us at hello@aikebom.com and we’ll handle or route it. Since sessions are anonymous, we may ask you for the session’s device or share-link details to locate the right data.

We’ll update this page as the service evolves; material changes move the date below. Last updated: 24 July 2026.