Ramtro AuraAI

Privacy Policy

This explains what AuraAI collects when you use the app to chat, set reminders, and connect services like Google Calendar and Swiggy — and what we do with it.

Effective 12 September 2026 Applies to AuraAI for Android (com.auraai.mobile) Contact hello@ramtro.com

At a glance

The short version — the sections below cover each row in full.

DataCollectedShared withWhy
Phone number Required Our SMS delivery provider Signing in, via one-time SMS code
Chat messages Required Our AI model providers Generating the assistant's replies
Reminders you create Required Not shared Notifying you when they're due
Push notification token Required Google (Firebase Cloud Messaging) Delivering reminder notifications
Google Calendar Only if connected Google Reading and creating events via chat
Swiggy account & orders Only if connected Swiggy Ordering food, groceries, table bookings via chat
Precise location Not collected — Maps directions open in your Google Maps app instead
§01

What we collect

Account information

Your mobile phone number, to create your account and sign you in with a one-time SMS code. We don't ask for a name, email, or password.

Conversations and content

The messages you send AuraAI and the assistant's replies, so your conversation history is there when you come back, and so the assistant has context across a conversation. This includes any reminders you ask it to set — the reminder text and the time you asked for.

Device and notification data

A push notification token issued by your device, so we can deliver reminder notifications through Google's Firebase Cloud Messaging service. This token identifies your device for notifications only — it isn't tied to your identity beyond your account.

Connected third-party accounts

If you choose to connect Google or Swiggy from Settings, we store an encrypted access credential that lets AuraAI act on that account on your behalf when you ask it to — see §04.

What we don't collect

  • Location — AuraAI never reads your device's GPS or network location. When you ask for directions, we hand off to your phone's own Google Maps app, which has its own separate location permission.
  • Analytics or crash tracking — there is no analytics or crash-reporting software in the app.
  • Contacts, camera, microphone, SMS, or files — the app does not request or use any of these permissions.
§02

How we use it

  • To run the assistant — understanding your messages, holding context across a conversation, and generating a reply.
  • To act on connected accounts when you ask — creating a calendar event, searching a restaurant, adding an item to a Swiggy cart, only when you've connected that account and only for the specific request you made.
  • To notify you when a reminder you set becomes due.
  • To keep your account secure — detecting suspicious sign-in activity and letting you sign out of all devices at once.

We do not use your conversations, orders, or calendar data to build advertising profiles, and we do not sell personal data.

§03

Who it's shared with

We share only what's needed to do what you asked, and only with these parties:

SMS providerDelivers the one-time SMS code when you sign in. Receives your phone number for that purpose only. We may change SMS providers from time to time; whichever we use is bound by the same purpose limitation.
AI providersYour message text is sent to the AI model generating that reply. No account identifiers beyond what's needed to process the request are included.
GoogleIf you connect Google, calendar actions you request are sent to Google's Calendar API. Also delivers push notifications via Firebase.
SwiggyIf you connect Swiggy, order and cart actions you request — restaurant, dish, delivery address, order details — are sent to Swiggy to place or manage that order.

We do not share data with data brokers, and we do not permit any of these providers to use what we send them to advertise to you.

§04

Connected accounts

Connecting Google or Swiggy is always your choice — every feature that doesn't need them (chat, reminders) works without connecting anything.

When you connect one, you authorize it directly with that provider (you sign in on Google's or Swiggy's own page — AuraAI never sees your password there). We receive back an access credential, which we store encrypted and use only when you ask the assistant to do something on that account.

You can disconnect either account at any time from Settings → Connected Accounts. Disconnecting immediately deletes the stored credential from our systems.

§05

Security

  • All traffic between the app and our servers is encrypted (HTTPS).
  • Connected-account credentials (Google, Swiggy) are encrypted at rest in our database.
  • Your session credentials are stored using your device's secure storage (Android Keystore) — never in plain text.
  • Signing out clears your credentials and cached conversations from the device.
§06

Retention & deletion

We keep your conversations and reminders for as long as your account is active, so your history stays available to you. Connected-account credentials are kept only until you disconnect that account or delete your AuraAI account.

To delete your account and all associated data, email hello@ramtro.com from your registered number's associated contact, or ask us in-app. We'll confirm once it's done, and aim to complete deletion within 30 days.

§07

Your rights

If you're in India, the Digital Personal Data Protection Act, 2023 gives you the right to:

  • Access a copy of the personal data we hold about you.
  • Correct or update inaccurate or incomplete data.
  • Erase data we no longer need for the purpose you gave it to us for.
  • Withdraw consent for any connected account, at any time, without affecting anything you did before withdrawing it.
  • File a grievance with our Grievance Officer (§10) if you believe we've mishandled your data.
§08

Children

AuraAI is not directed at children, and we don't knowingly collect data from anyone under 18. If you believe a child has created an account, contact us at the address in §10 and we'll remove it.

§09

Changes to this policy

If we make a material change to what we collect or how we use it, we'll update the effective date above and notify you in the app before the change takes effect.

§10

Contact & grievance officer

Questions about this policy, or a request under §07, can go to either address below.

General privacy contact
hello@ramtro.com

Grievance Officer (Digital Personal Data Protection Act, 2023)
Aman deep
hello@ramtro.com