Privacy Policy
Privacy Policy
How Aika Labs collects, uses, shares and deletes personal data.
Last updated
Effective date: 22 October 2026.
Who we are
Aika Labs is AIKALABS TECHNOLOGIES PRIVATE LIMITED. Our registered office is 703, 7th Floor, Palm Court, MG Road, Sec 16, Industrial Estate (Gurgaon), Industrial Estate, Gurgaon, Haryana, India, 122007. CIN: U62011HR2026PTC151107. We run Aika on +91 9006 81 9006 and this website.
What we collect
Phone calls
We receive your phone number, a code made from it, call reference, start time, duration, language, call status and talk-time use. We process your voice and speech as text to answer during a call, before a recording permission is given. Your questions can contain health, financial or other personal information.
With a yes to the remembering question, we keep recordings, transcripts and memory notes for later calls and improving Aika. We also handle consent answers, caller profiles, voice statistics, inferred gender, reminders, messages, recipient details, safety flags and payment status. We store voice statistics and inferred gender even without a yes. A code made from a phone number still identifies a returning caller; it is not anonymous.
For WhatsApp delivery, we process recipient numbers, requested message or template contents, replies, delivery receipts and message references. For connected Swiggy orders, we process account-linking tokens, saved delivery addresses, order history, cart choices and payment progress. Connecting a shop account is separate from the remembering question.
Aika Family
We handle the parent and family member contact details, relationship, enrolment and sharing permissions, call-derived notes, summaries, facts, commitments and scheduled calls. Information shared with a family member follows the Family sharing permission. The sharing notice also covers a serious-danger exception. The general remembering answer does not replace Family sharing permission.
Aika Living
A society committee supplies resident names, phone numbers, flats, buildings and languages before a resident calls. We store community and membership details, society questions and answers, notices, call summaries, unanswered questions and consent and admin action records. Committee access to resident call information has a separate sharing permission.
For committee sign-in, we handle name, email, password hash or linked Google account details, session tokens, IP address, browser information, invitations and password-reset records. Committee roster views mask phone numbers; the service stores the number needed to recognise and contact a resident.
The website
We automatically receive page and action events, time, language, referrer origin, viewport and device information, cleaned campaign tags, country and bot indicators. Our server makes a daily visitor code from the IP address, browser information, a secret value and the date. The analytics event does not store the raw IP address or browser header in those fields.
Cloudflare receives network requests. Operational records contain request route, status, timing and country. Browser security reports contain the security rule, blocked origin and first path segment. Historical waitlist records contain email, language and a daily visitor code. The current public site has no waitlist form.
If you start the browser voice demo and allow the microphone, your audio reaches the call service. The demo shows conversation text in browser memory and uses a generated session reference. Call-service processing follows the phone-call rules above.
MARS
MARS has its own Privacy Policy. Read it for MARS account and counselling data.
Why we use it
| Data | Purpose |
|---|---|
| Live voice, text and conversation context | Answer your current question |
| Caller identity, consent and saved memory | Recognise you and use permitted context on later calls |
| Consented recordings and transcripts | Review answer quality |
| Consented recordings and transcripts | Improve Aika by training our own models |
| Voice statistics and language or gender observations | Understand speech and choose suitable wording |
| Reminder, message and recipient details | Deliver the reminder or message you requested |
| Family contacts, permissions and summaries | Provide the agreed Family sharing service |
| Living resident, committee and community records | Provide society answers and permitted committee information |
| Linked-shop account, address and order details | Carry out your requested Swiggy order |
| Payment, balance and usage records | Take payment and apply talk time |
| Safety flags and call or service logs | Detect misuse and enforce the Acceptable Use Policy |
| Request and security reports | Diagnose failures and protect the service |
| Website events and campaign tags | Measure website use and campaign response |
| Hashed phone, call reference, time and new or repeat status | Measure advertising through Meta |
| Email and request details | Handle your enquiry, rights request or complaint |
| Records covered by a legal preservation duty | Meet that legal duty |
The consent question
There is 1 general spoken remembering question, rather than separate questions for recording, remembering and training. A yes covers keeping recordings, remembering you and using calls to improve Aika, including training our own models. Saying no does not stop you using Aika. Live speech processing still takes place to answer you.
We ask: “I'd like to remember our conversations, so I can understand you better and help you well. Is that okay with you?”
With no answer or a no, we keep no recording. We keep transcripts with personal details removed for up to 30 days. Service and safety records are separate from the recording choice.
To take back a yes, email the grievance contact or ask Aika for a callback from your own number. A person handles the request within 30 days. Taking back consent stops the uses covered by that consent; it is separate from asking to delete existing data. Taking back consent does not reverse training that has already taken place.
Who we share it with
We share the following data with these providers for the listed purposes. Models receive the conversation context needed for their task.
| Provider | What it receives | Why | Where it is processed |
|---|---|---|---|
| Supabase: phone service | Call, consent, profile, memory and billing records | Store our phone-service records | Mumbai, India |
| Google Cloud | Call-service data, audio (stored in Mumbai, India) and encryption keys | Host the call service, store audio and protect phone numbers | May be processed outside India |
| Exotel | Live call audio and phone numbers | Connect phone calls and requested outbound calls | May be processed outside India |
| Soniox | Live caller audio and speech context | Turn speech into text | India for speech recognition |
| Sarvam | Caller audio and text on speech or model paths | Help recognise speech and generate answers | India |
| Cartesia | Reply text and voice settings | Turn Aika’s replies into speech | May be processed outside India |
| OpenAI via OpenRouter | Conversation text, history and context | Generate answers, redact transcripts and extract relevant information | May be processed outside India |
| DeepSeek via OpenRouter | Conversation text, history and context | Generate answers | May be processed outside India |
| OpenRouter: other routed models | Conversation text, history and context | Generate answers, make safety decisions and process Family information | May be processed outside India |
| TypeSafe | Caller words, questions and conversation state | Understand intent and choices | United States |
| Exa | Search queries derived from your question | Find information for answers | May be processed outside India |
| Octen | Search queries derived from your question | Find current information for answers | May be processed outside India |
| Brave | Search queries derived from your question | Find current information for answers | May be processed outside India |
| Razorpay | Phone number, amount, checkout and payment references and status | Process talk-time payments | May be processed outside India |
| Meta: WhatsApp | Recipient phone number, message or template details, replies and receipts | Deliver requested messages | May be processed outside India |
| Meta: ad measurement | Hashed phone number, call reference, start time and new or repeat status | Measure advertising | May be processed outside India |
| Swiggy | Linked account, delivery address, cart, order and payment-flow details | Carry out requested orders | May be processed outside India |
| Cloudflare | Website requests and network details | Deliver and protect the site | May be processed outside India |
| Supabase: MARS | MARS account and saved counselling data | Store MARS records under its separate Privacy Policy | May be processed outside India |
| Google Workspace | Email content, sender address and request details | Handle correspondence | May be processed outside India |
| Grafana Cloud | Service logs, call text in logs, metrics and website analytics | Operate and measure services | Mumbai, India |
Providers whose location is not shown as India in this table can process your data outside India. We request no-retention endpoints for DeepSeek and a no-training setting for OpenAI safety decisions through OpenRouter; OpenAI does not train on API data by default. Cartesia and Exa allow training under their standard public terms, subject to opt-outs or separate agreements; Brave allows keeping API query records, and Sarvam’s privacy policy allows keeping content and training unless opted out.
Requested message recipients receive the message and sender details needed for delivery. Family members and society committees receive the information covered by their separate sharing permissions. We disclose records to authorities when the law requires disclosure.
Meta ad measurement
For ad measurement, our call system sends Meta a scrambled (hashed) form of the caller phone number, a call reference, the call start time and whether this is a new or repeat caller. It sends no audio or transcript. The hashed number is still personal data. There is no Meta website pixel.
To object, email the grievance contact or ask for a callback from your own number. A person handles the request within 30 days.
How long we keep it
| Record | Retention rule |
|---|---|
| Recordings and transcripts after a yes | Up to 3 years from the call |
| Memory about a caller | Deleted after 1 year with no calls |
| Recordings after no or no answer | No recording kept |
| Transcripts after no or no answer | Personal details removed; kept up to 30 days from the call |
| Payment records | At least 8 years from the end of the financial year they relate to; GST records are kept for at least 72 months from the annual-return due date for that year, and longer where the law requires. |
| Abuse and safety flags | Kept for up to 1 year after the last flagged event |
| Inbound WhatsApp personal contents | Scrubbed after 30 days by daily maintenance; delivery identifiers and receipts are separate |
| Call-contact phone copies | Up to 7 days in the contact database; checkout contact cache expires after 48 hours |
| Swiggy saved-address cache | 24 hours; separate shopping context cache expires after 30 minutes |
| Living admin session | 7 days, renewed during use; password-reset link expires after 1 hour and invitation after 7 days |
| Service and analytics logs | Kept in Mumbai, India, for 30 days |
| Other profile fields, outbound messages, Family records, Living registers and admin history, historical waitlist records | Kept while your Aika account is active; deleted within 30 days of a full deletion request |
| Consent records | Kept as proof of your choice while we hold data under it |
The periods above are distinct from legal preservation. We retain records covered by accounting duties or a legally required preservation order for that duty. A data-deletion response identifies records retained and the reason. We do not keep backups of the call database.
Your rights and how to use them
You can ask to see your data, correct it, delete it, take back consent, complain or nominate someone to act on your behalf after death or incapacity. Email hello@aikalabs.io, or call from your own number and ask for a person to call you back. Include the number you used and the request. A person handles the request and completes it within 30 days. A shorter legal deadline takes priority.
Nomination is a right under the main Digital Personal Data Protection Act provisions when they apply, from 2027-05-13. The request route also accepts nomination enquiries now.
Deleting your data
On a call, ask Aika to forget what you told her and confirm when asked. It clears saved conversation-memory entries, pending memory jobs, memory identity links, name records learned from those entries, prepared memory-search data, unfinished topics and the saved conversation summary. Facts still supported by another caller and other caller-profile fields remain. An erasure boundary stays to stop old work recreating erased memory.
This command does not delete recordings, transcripts, other profile fields, voice statistics, inferred gender, consent records, messages, payments, Family or Living records, shop caches, logs or provider copies. It does not take back a previous yes.
For full deletion, email the grievance contact or request a callback from your own number. A person completes the request within 30 days and confirms what was deleted and what legal records remain. Read the Data Deletion Instructions for the steps.
Children
Aika is for people aged 18 and over. If we learn that a caller is under 18, we delete their data except records the law requires us to keep. Tell the grievance contact if you believe a child has used Aika.
Website storage and tracking
We use first-party analytics through our own website endpoint. The public site has no advertising cookies and no Meta pixel. First-party measurement runs without a visitor setting to turn it off today. Browser storage is also used for the following purposes.
| Category | Browser keys | Purpose and lifetime |
|---|---|---|
| Analytics session | aika_sid | Random tab identifier; session storage ends with the tab session |
| Campaign tags | aika_campaign | Campaign and click-source tags; session storage ends with the tab session or a replacement campaign |
| Test-visit flag | aika-test | Exclude test visits; local storage has no automatic expiry |
| Call cooldown | aika_web_call_last | Last browser-call time for a 90-second cooldown; local storage has no automatic expiry |
| Display and game preferences | sunset-dialled; theme; aika-404-muted; aika-404-best-answer; aika-404-best-deliver; aika-404-best-tune | Loader state lasts for the tab session; admin colour, game sound and best scores use local storage with no automatic expiry |
| Living admin sign-in cookie | __Secure-better-auth.session_token | Admin sign-in only; 7-day session renewed during use |
The sign-in cookie is restricted from script access and uses secure delivery on HTTPS. Optional nonremembered sign-in and configured Google sign-in use authentication state; these are not advertising cookies. You can clear browser storage in your browser. Clearing it does not delete server records.
Security
The call system encrypts stored contact and relay phone-number fields using Google Cloud encryption keys. The public website uses HTTPS. Authorised services and people with the required access can read personal data. Call logs can contain conversation text.
Data breaches
We will tell affected people and the authorities about data breaches as the law requires.
Changes
We post policy changes on this website at least 30 days before they take effect, except changes the law requires sooner. We tell callers on their next call. A change to this page does not replace consent required for a new use of data.
Grievance officer and contact
Ayush Bhattacharya, Chief Executive Officer and Grievance Officer, Aika Labs. Email hello@aikalabs.io. Postal address: 703, 7th Floor, Palm Court, MG Road, Sec 16, Industrial Estate (Gurgaon), Industrial Estate, Gurgaon, Haryana, India, 122007.
We acknowledge complaints within 24 hours and resolve them within 30 days, or within 1 month if that ends sooner. Complaints about relayed messages or Aika Living notices are resolved within 7 days. Legally urgent removals follow the shorter time the law sets. See Grievance Officer for escalation and Contact for company details.