Privacy policy
For organisations in India, in effect from 31 October 2026. Other countries: Australia, Canada, Singapore, United Arab Emirates, United Kingdom, United States, Vietnam.
This policy covers Marro: the web application, its mobile app, and its WhatsApp features. Marro is provided by STAGIONE MEDIA LLP (“Marro”, “we”).
Who decides what happens to your data
Businesses (“organizations”) subscribe to the CRM to manage their leads, their team and their conversations. For the information an organization puts into the CRM, such as its leads, their messages and its staff’s records, the organization is responsible for it and we process it on the organization’s behalf and on its instructions. For the accounts of people who sign in, and for running and securing the service, we are responsible.
What we collect
- Accounts: name, email address, phone number, role, and sign-in records (time, device, IP address). If someone signs in with Google, we receive their Google account name and email address; we ask Google for nothing else.
- Sign-in security: if you set up two-step sign-in, we keep an encrypted authenticator secret, passkey public credentials and their use, backup-code hashes and trusted-device records. Your device keeps its passkey private key and any fingerprint, face or PIN used to unlock it.
- Leads and customers: the contact details and notes an organization records, and the activity on each lead (calls logged, stage changes, follow-ups).
- WhatsApp messages: when an organization connects its WhatsApp Business number, the messages sent and received on it, who sent them, delivery and read status, and the photos, videos, audio and documents in them. We keep a copy of each file in our private file store, so it stays available after Meta deletes its own copy (Meta keeps files for up to 30 days). Files are kept and deleted with the organization’s other data.
- WhatsApp Business app history: if an organization connects a number it also uses on the WhatsApp Business app and agrees in Meta’s window to share its chat history and contacts, we receive them. We add past chats only for people who are already leads in the CRM; the rest is kept for 30 days and then deleted. Contacts shared by the WhatsApp Business app are kept only in these raw notifications, for 30 days, and are not added to the CRM as leads.
- Booking links, forms and the chat widget: when someone books an appointment, fills in a form or writes in the chat widget of an organization that uses the CRM, the name, phone number, email address, the time they chose and the answers they give. The organization decides about this information (see above).
- Calendars (optional): when a team member connects their Google or Outlook calendar, the information described in the next section.
- Emails: the emails the CRM sends on an organization’s behalf, and whether they were delivered.
- HR (when an organization uses it): attendance check-ins with the time, location and a selfie, leave requests, and timesheets.
- Mobile app: a notification token so we can send alerts. On Android, if a user turns on caller identification, the phone numbers of incoming calls are matched against their organization’s leads on the device.
- Call log (Android, optional): if a user allows it, the app reads the phone’s call log to add calls with leads to the lead’s timeline. It reads each call’s number, time, direction and length. Only calls whose number matches a lead the user can see are saved to the organization’s CRM; all other calls are ignored and not stored, and a number that is not a lead is never added. Calls are never recorded. This information is used only to show call history on leads, and is never shared or used for advertising. A user can switch it off at any time in the phone’s settings.
- Assistant (when an organization turns it on): the questions people ask and the answers, voice notes they send, which are transcribed, and the business information an organization adds for it to answer from.
Information from Meta
When an organization connects WhatsApp through the CRM, Meta gives us an access token for that organization’s WhatsApp Business account, and its business, account and phone number IDs. We use them only to send and receive that organization’s messages, manage its message templates, and show its number’s status. We keep the token encrypted. We do not use data from Meta for advertising, sell it, or share it with anyone except as described in this policy.
If an organization has the assistant turned on, the text of a WhatsApp conversation is sent to our AI service providers only when a staff member asks for suggested replies or asks the assistant about that conversation. It is used only to produce that answer. We do not use it to train AI models, and under their business terms our AI providers do not use it to train theirs.
Marro advertising measurement
If you allow optional advertising cookies on the Marro website, we use campaign tags and click or browser identifiers to link an ad visit to workspace signup and a first subscription payment. Where enabled, we send Meta the identifiers, event details and, for a purchase, the amount and currency. We do not send CRM customer records for this purpose. Change your browser choice in Cookie preferences on Marro’s website. To ask us to remove measurement information linked to your account, contact us.
If you allow optional analytics cookies on Marro’s website, Google Analytics also receives an analytics browser identifier and confirmation of a workspace signup or first subscription payment, including the amount and currency for purchases. Marro also saves campaign labels for up to 30 days and uses recent Google session context to link a signup to its visit. You can change the browser choice in Analytics preferences on the Marro website.
Google Calendar and Outlook calendars
A team member can connect their own Google Calendar or Outlook (Microsoft 365) calendar to Marro. This is optional, each person connects only their own calendar, and they can disconnect it at any time in the app or on the web.
- What we access. The times they are busy (never the titles, descriptions or guests of their other events), so that nobody books them when they are busy. We also create, move and cancel the calendar events for appointments booked in Marro, add a Google Meet or Microsoft Teams link when asked, and invite the lead by email. And we read the email address of the connected account, to show which account it is.
- The permissions we ask for. From Google: calendar.events (to write those appointments), calendar.freebusy (to read busy times only), and the account’s email address. From Microsoft: Calendars.ReadWrite, User.Read and offline_access, used the same way. We ask for nothing else, and we use them for nothing else.
- What we keep. The connected account’s email address, the calendar it uses, and the access that lets us keep working without asking again, which is stored encrypted. We do not keep copies of a person’s busy times or of other events in their calendar. The events we create keep the appointment’s details, as in the calendar itself.
- Who sees it. Only the person who connected it and our service providers who run the CRM (listed below). Calendar data is not sold, not used for advertising, and not used to train AI models, ours or anyone’s. If the assistant is turned on and a person asks it about their availability, the busy times are sent to our AI providers only to answer that question.
- Disconnecting. When someone disconnects a calendar, we revoke our access with Google or Microsoft and delete what we stored for it. If an organization’s data is deleted, the stored calendar access is deleted with it. Someone can also remove Marro’s access in their Google account’s security settings or their Microsoft account’s privacy settings.
Marro’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Why we use it
- To provide the CRM: storing an organization’s data, sending the messages and alerts it asks for, and showing its reports.
- To keep the service secure: sign-in checks, audit logs, and detecting abuse.
- To support organizations when they ask for help, with their permission.
- To bill organizations for their subscription and messages.
We do not sell personal data, and we do not use an organization’s data to train AI models.
Who we share it with
Only the service providers that run parts of the CRM for us, each for that purpose alone:
- Vercel (hosting) and Neon (database), where the CRM runs and its data is stored.
- Cloudflare (R2), which stores files such as WhatsApp attachments, content task images and logos.
- Meta (WhatsApp Business Platform), which delivers WhatsApp messages.
- Brevo, which delivers email.
- Upstash, which schedules reminders.
- Google Firebase, which delivers mobile notifications, Google Maps, which shows attendance locations, and Google Sign-In, for people who sign in with Google.
- Google Calendar and Microsoft (Outlook, Microsoft Graph), only for the team members who connect a calendar, as described above.
- Razorpay, which takes payments when an organization pays for its subscription or messages.
- AI service providers, which power the assistant, the AI agents, AI calls, suggested replies and voice transcription, only for organizations that have AI. They act only on our instructions, under data-processing terms. Organizations can ask us for the current list.
We may also disclose data where the law requires it.
The database and the file store are in the Asia-Pacific region; the database is in Singapore. Some providers above, such as our AI providers, process data in other countries, including the United States. We use them only for the purposes above and only where their terms protect the data.
How long we keep it
- Cancelling a subscription and closing an organization are separate actions. Normal owner-requested closure suspends ordinary access and starts a 30-day owner recovery and export window. The exact deadline is shown in the owner workflow. We schedule an email to the recorded owner 15 days before deletion and another one day before deletion, showing the exact deadline. Restoring cancels pending reminders. Export your data or restore your organisation within 30 days of closure; after that deadline, data recovery is unavailable and permanent deletion begins. Verified erasure requests can bypass or shorten that window. We target active-system deletion within seven days after the window ends, subject to shorter applicable legal deadlines; failures and record-specific legal retention are reported separately.
- The raw notifications Meta sends us about WhatsApp messages are kept for 30 days.
- When an organization disconnects its WhatsApp number, we delete the access token at once.
- Backups and third-party copies follow their verified retention and deletion processes. Their status remains pending until supported by evidence; deleting tenant records is not proof every copy is gone. Deletion records must be reapplied before restored data serves traffic. Offline devices and customer-controlled exports cannot be remotely erased.
Necessary Marro accounting evidence and accepted contracts are retained separately under an eight-year accounting baseline, extended only for a later applicable tax deadline or specific legal hold. This does not retain your whole CRM for collection.
Security
Data travels encrypted. Access tokens and other credentials are encrypted at rest. Each organization’s data is kept separate, and people see only what their role allows. Changes to settings and access are recorded in an audit log.
Your rights
You can ask to see, correct or delete your personal data, and withdraw consent where we rely on it. If you are a lead or customer of an organization that uses the CRM, contact that organization first, since it decides about your data; you can also write to us and we will pass your request on. People in India have these rights under the Digital Personal Data Protection Act, 2023. How to delete your data.
Questions and complaints
Write to our grievance contact for data protection at hello@marro.si or call +91 88853 33635. If you are in India and are not satisfied with our answer, you can complain to the Data Protection Board of India once it is operating.
Children
The CRM is for businesses and their staff, not for children.
Changes
We will update this page when the way we handle data changes, and tell organizations about significant changes by email.
Contact
Marro (STAGIONE MEDIA LLP), WorkFlo Hitex, Units 405–411, 4th Floor, Bizness Square, Jubilee Enclave, Madhapur, Hyderabad, Telangana 500081, India. Email hello@marro.si or call +91 88853 33635.