ShakaPrivacy policy
Last updated 9 October 2026. Shaka is operated by Luminos Ventures Technologies Ltd (Hoteleak, hoteleak.com). Contact: the bot's WhatsApp chat.
What Shaka collects
- From WhatsApp: your phone number, profile name, the messages, voice notes, photos and locations you send to the bot, and your reactions to its messages.
- What you tell it to keep: your home spot, level, alerts, reminders, schedules and the facts you ask it to remember.
- From Google, only if you connect your account (you may connect more than one): your Google account email address; the title, start and end time of your calendar events for the next 7 days; your mail, incoming and sent: sender, recipients, date, subject, Google's preview, the text of the message and the names, sizes and types of attachments, for about the last 90 days and then as it arrives. The attachments themselves are not indexed: one is opened only when you ask a question that needs it (see below). Shaka never reads contacts or Drive files.
How Google user data is used
- Calendar events are used to find the free surf window in your day, to name your first meeting in the briefing you asked for, and to hold back an alert when you are busy. They are kept in memory for up to 5 minutes and are not written to the database.
- When you approve a suggested session, Shaka creates that one event in your primary calendar. It does not change or delete other events.
- Your mail is stored in an index on Shaka's server (Google Cloud, United States) so it can answer questions about it ("did the invoice go to the accountant?", "when did X last reply?") and notice what needs you: a confirmation, a flight, a bill, an answer you were waiting for. It then offers one reminder, hold or draft. Nothing is created or sent until you say yes.
- An attachment (a PDF invoice, a ticket, a photo) is opened only when you ask a question whose answer is inside the file. At that moment the file is fetched from Gmail and sent to Anthropic (Claude) to be transcribed to text, and the answer is written from that text. The file is not stored on Shaka's server.
- OAuth tokens are stored encrypted on the same server until you disconnect.
- Messages the bot sends you, which may mention a meeting time, remain in your conversation history with it.
Sharing and AI processing
Shaka does not sell your data and does not use it for advertising. To write its answers, the text of your conversation, and the calendar times, the mail or the attachment needed for the feature you are using, are sent to AI model providers acting as processors: Anthropic (Claude; it receives the mail text and, when you ask about one, the attachment itself, unmasked), Google (Gemini API) and TypeSafe (Jev, for short yes/no judgments such as whether a new mail is worth a message; it receives headers and previews with addresses and numbers masked, never mail bodies or attachments). If you turn on the morning voice note, the text of your morning brief (which can include your first meeting's time; never the "waiting on" line from your mail or other surfers' reports) is also sent to Google (Gemini API) to be rewritten for speech and spoken; the audio goes to you on WhatsApp and is not kept on Shaka's server. Before Shaka asks for your approval, adds a calendar hold, types or confirms on a website for you, or delivers a message it started on its own, it checks that the names and figures in it come from what it was told or read: numbers, amounts and addresses are compared by code, and when a name, or an amount, date or time, needs a closer look, the message and short excerpts of what that step read (a few hundred characters around each place the name or figure appears in the conversation, your saved facts, or the mail, calendar entries or web pages it used; never whole mails or pages) are sent to Google (Gemini API), or to Anthropic on a server set up without Gemini, to judge it. They process the data only to return the answer, under API terms that exclude training on it. Google user data is never used to develop, improve or train generalized AI or machine-learning models, and no human at Shaka reads it, unless you ask for support and agree, or where the law requires it. WhatsApp messages travel through Meta's WhatsApp Business Platform.
The use of information received from Google Workspace scopes will adhere to the Google User Data Policy, including the Limited Use requirements.
Retention and deletion
- Write "disconnect Google" to the bot: the grant is revoked at Google and the stored tokens and the indexed mail of that account are deleted immediately. You can also remove access at myaccount.google.com/permissions.
- Write "STOP" to end all proactive messages.
- Write "delete my data" to the bot: after you confirm, the Google grant is revoked and everything Shaka holds about you (profile, alerts, reminders, memories, conversation history, indexed mail, photos you sent) is erased immediately from the live database. Server logs (which contain no message text, except the browser agent's step log: each step's name, the page or button it used and a short result, never what it types for you) and the nightly database backup are kept for 14 days and then deleted, so a copy of your data can exist for up to 14 days after a deletion. You can also ask at the bot's WhatsApp chat.
Security
Traffic is encrypted with TLS. The server accepts only web traffic, administrative access is restricted, and WhatsApp webhooks are signature-verified. Tokens and the contents of your mail are never written to logs.
Children
Shaka is not directed at children under 13.
Changes
Changes to this policy are posted on this page with a new date.