Privacy Policy
Effective date: October 27, 2026
Last updated: October 27, 2026
Boloma (“Boloma,” “we,” “us,” or “our”) provides an Android app that lets you speak with an AI assistant and, when you choose to share your screen, receive spoken guidance about what is displayed. This policy explains what information we handle, why we handle it, and the choices available to you.
Service provider: Boloma
Contact: contact@boloma.in
Address: TC 28/2786, KRA C-18, Chettikulangara, Thiruvananthapuram, Kerala, India
Account deletion: In the app under account settings → Delete account.
Information we handle
Account information. When you sign in with Google, we receive account identifiers and profile information made available through the sign-in flow, such as your Google email address, Firebase user ID, display name, and profile photo URL. We use Firebase Authentication to sign you in. If enabled, the app may fetch your profile photo from Google’s image-hosting service.
Live call content. When you start a help session and grant the relevant Android permissions, the app sends your microphone audio and the screen frames you choose to share to Microsoft Azure OpenAI Realtime so it can generate spoken responses and guidance. Screen frames may show information from other apps, including messages, contacts, or financial information. Some apps or screens may be blanked or unavailable because of Android or app protections. The AI may also receive and return text and tool instructions needed to operate the session.
Boloma does not store call audio, screen images, or transcripts. We store a short call title, start time, duration, end reason, and token counts so we can show call history and enforce quotas. Server logs may include error text from a session. They do not include the audio or the screen images. Microsoft processes the live audio and screen frames to run the session.
Microsoft processes live call content to provide the AI service. Microsoft’s Azure documentation says prompts and completions are not used to train foundation models, but Azure’s abuse-monitoring practices may involve automated processing and may include review of content flagged for potential abuse. These practices depend on the Azure service, deployment, and configuration used by Boloma. Microsoft Azure AI data privacy
Service and usage information. Our API and Azure infrastructure may process your Firebase user ID, account/profile data, call timestamps and duration, quota and subscription state, app diagnostics, and request metadata. We use Azure Container Apps, Azure Database for PostgreSQL, Azure Key Vault, Azure Container Registry, and Azure AI services to run the service. We use Google Cloud service-account infrastructure to verify Google Play purchases and process subscription notifications.
Purchases. Google Play handles subscription purchases. We receive and process purchase tokens and subscription status information, including renewal, cancellation, and expiration status, to verify access and manage your plan. We do not receive your full payment-card details through the app.
Fraud prevention. If you delete your account, we may retain a one-way hashed email identifier to help prevent trial or promotion abuse. We do not use this remnant to sign you in.
How we use information
We use information to:
- authenticate you and maintain your account;
- provide live AI voice and screen-guidance sessions;
- track usage quotas and subscription entitlements;
- verify purchases and manage subscription access;
- secure, maintain, and troubleshoot the app and backend;
- prevent fraud, abuse, and violations of our terms; and
- comply with applicable legal obligations.
How information is shared
We share information with service providers only as needed to operate Boloma:
- Google provides Google sign-in and Firebase Authentication, may host profile photos, and processes Google Play purchases and subscription status.
- Microsoft Azure hosts our backend and processes live call audio, screen frames, and AI request/response traffic through Azure OpenAI Realtime.
- Google Cloud supports our server-side Google Play purchase-verification and notification workflow.
We do not sell personal information. We do not share live call content with your family members or other users through Boloma. [Confirm that no analytics, crash-reporting, support, or advertising SDKs transmit data; disclose any that do.]
Permissions and your choices
You control whether to start a session and grant microphone, screen-capture, notification, and overlay permissions. Android displays its own consent flow for screen capture. You can end a session at any time and revoke permissions through Android settings. If you deny or revoke a permission, the related feature may not work.
You can review or change your Google account permissions through your Google Account settings. You can manage or cancel a Google Play subscription through Google Play’s subscription settings.
Retention and deletion
Account, profile, call-history, and usage records are kept until you delete the account. Live audio and screen frames are not kept by Boloma after the session. The hashed email used to limit repeat free trials is kept after deletion and is not deleted on a schedule. Google may keep purchase records under its own policies.
You can delete your account in the app under Settings → Delete account, or by emailing contact@boloma.in from the Google address you used to sign in. We then delete the account, profile, call history, and usage records. We keep the hashed email described above. We may also keep records required for legal, security, billing, or dispute-resolution purposes.
Google Play requires an in-app account deletion path and a discoverable web resource for deletion requests when an app allows account creation. Google Play account deletion requirements
Children’s privacy
Boloma is intended for adults and is not designed for children under 18. If you believe a child has provided personal information to Boloma, contact us at contact@boloma.in.
Security and international processing
We use reasonable safeguards designed to protect information. No method of transmission or storage is completely secure. The API and the Azure OpenAI deployment run in Azure South India. The database runs in Azure Central India. Google processes sign-in, profile photos, and Play billing on Google’s systems, which may be outside India.
Changes and contact
We may update this policy as Boloma changes. We will post the updated version with a new “Last updated” date and provide additional notice when required.
For privacy questions or requests, contact contact@boloma.in.
