Privacy Policy
Informative translation. The Bahasa Indonesia version prevails.
Last updated: October 12, 2026. Applies to the Maira Sales platform (web app, browser extension, and API).
This document follows the framework of Law No. 27 of 2022 on Personal Data Protection. We avoid generic wording: each section states what data this system actually processes, on which legal basis, and through what mechanism you can object. One point we state up front, because it is often misunderstood: publicly available data is still personal data as long as it points to an identifiable individual. A WhatsApp number displayed on a shopfront, an owner’s name on a business profile, or a social media username doesn’t stop being personal data just because anyone can access it. That is why every search activity below runs on a processing basis we state explicitly, not on the assumption that public data is free to use.
1. Who we are
Maira Sales is an AI-based sales platform for the Indonesian market (WhatsApp-focused). In data processing activities, we may act as the Data Controller (for your account data) and as the Data Processor (for customer/prospect data you manage within the platform, where you are its Controller).
2. Data we collect
- Account data: name, email, company, password (hashed), 2FA settings.
- CRM/prospect data you enter or collect: name, job title, company, phone/WhatsApp number, email, and other public professional information — whether from manual/CSV import or from the search (crawl) feature over public sources (e.g. LinkedIn, Google Maps, social media, marketplaces).
- Conversation data: the content of incoming/outgoing WhatsApp messages you manage through the Inbox, with metadata (time, status, recipient).
- Usage & AI data: feature logs, AI tokens/costs, activity for security & billing.
- Payment data: processed by third-party providers (Midtrans/Xendit/Tripay). We don’t store card details; we store the transaction status + reference.
3. Prospect search and its legal basis
The search feature collects business contact details from sources open to the public — web search results, Google Maps, business directories, and social media profiles. The processing basis differs depending on who is targeted, and we record that difference on every data row:
- Business-entity prospects (B2B). Processed on the basis of legitimate interest (Article 20(2) of the PDP Law). Offers are aimed at a person’s role within their business, not their private life; reach is limited to details actually published for prospective customers to make contact; and an objection can be given with a one-word reply. Each such contact is marked
legitimate_interestwhen created, so its legal basis can be shown again at any time rather than compiled after the fact. - Individual prospects (B2C). We don’t consider these covered by legitimate interest. Such rows are marked
unknownand stay so until the person agrees through the consent link in the first message. We deliberately don’t hide that marking, so the gap stays visible to platform users and to us.
The first message to any contact always includes the sender’s identity, a note that the message is sent through Maira, and two ways out. Replying STOP (or BERHENTI) stops messages from the user who contacted you; their automated assistant also stops replying, and you can reply MULAI at any time to hear from that user again. A digitally signed link records the objection without needing an account, and an objection through the link applies across every platform user — once a number or email is on the do-not-contact list, matching contacts are flagged in every tenant account and their offers are withdrawn from the marketplace.
As the platform provider, we process prospect data on the instructions of the users who use it. The obligation to determine the purpose of use, keep it relevant, and respond to data subjects’ objections rests with those users as Controllers; we explain that role in section 1.
3a. Browser extension (Maira Sales — Discovery & WhatsApp)
Our Chrome extension is optional and works as a collector: it runs using your own login session on the channels you choose (LinkedIn, Google, Google Maps, Tokopedia, Shopee, Instagram, TikTok, WhatsApp Web) to collect business prospect data you see, then sends it to your Maira Sales account.
- What is collected: public prospect data on the pages you open (business name, listed contacts, profile links) and — for the WhatsApp bridge — conversation metadata so replies can be monitored.
- What we do NOT do: the extension does not store your login credentials , does not read sites outside the channels you choose, and does not run in the background without your action.
- Local storage: only the connection token + preferences, stored on your device.
- Permissions: site access is limited to the channel list above plus the Maira app domain (to detect installation). You can remove the extension at any time.
Data coming in through the extension is subject to the same section 3 (search) and section 8 (data subject rights).
3b. Social media profile assessment
For individual customer searches, the system may read the bio and a number of recent posts on a public profile to assess how close the owner’s interests are to the target set by the user. What you should know is the storage limit: we only store the follower count, interaction ratio, interest category tags (e.g. “coffee”, “touring”), and a single 0–100 fit number.
Post content, image captions, and bios are not stored. Narrative descriptions about a person — such as a one-sentence summary describing them — were previously generated and have now been removed from the system, because they added nothing beyond the existing numbers and tags while being far more intrusive. You have the right to object to such automated assessment and request deletion of its results (section 8).
3c. Location of field app users
The field visits feature records a coordinate point (latitude and longitude) with its time each time a user presses check-in or check-out on a visit. The point is recorded only when the button is pressed — the app doesn’t track position in the background, doesn’t record the journey between two points, and doesn’t turn on location without the user’s action.
This data is the personal data of employees, not prospect data. That is why access is restricted within one workspace: a salesperson sees their own visits and check-ins, while the account owner/admin sees the whole team for visit verification. Its legal basis is the employer’s legitimate interest in making sure reported visits really happened, and its scope is therefore deliberately narrowed to just that.
You have the right to request a copy or deletion of your location points through the channel in section 8. An honest note on retention: today coordinates follow the account’s general retention period and do not yet have a destruction schedule shorter than the visit data itself — that is still in progress, and we write it here rather than promising something not yet running.
4. How we use data
- Providing & running the service (CRM, AI message drafting, outreach, quotes, payments).
- Personalization & product improvement, customer support, and security.
- Billing, abuse prevention, and legal compliance.
Processing bases: consent, performance of a contract, and legitimate interest balanced against your rights.
5. AI & automated processing
We use AI models to draft messages, classify prospects, and for analytics. Relevant content is sent to model providers (e.g. Deepseek/Anthropic/OpenAI/Google) only to generate output for you. You can use your own keys/models (BYOK/BYOA). You can always review AI drafts before they are sent.
6. Who data is shared with
- Infrastructure providers: hosting & databases (e.g. Vercel, Neon).
- AI providers: to generate output (see section 5).
- Payment providers: Midtrans/Xendit/Tripay (when you enable payments).
- Message transport: WhatsApp/gateway providers when you send/receive messages.
- Consent management: a consent partner (Privasimu) when enabled.
We do not sell your personal data. The data marketplace only operates on data you consciously choose to share.
7. Security, storage, and retention
Separation of data between customers is enforced at the application layer: every database query runs in the context of a single customer and is filtered by that customer’s identity. An additional database-level safeguard (row-level security) is not yet in force across the board, so we don’t claim it as an active control today; its rollout is in progress and this page will be updated when it is done. Passwords are stored hashed, customers’ third-party keys are encrypted at rest, two-factor authentication is available, and access within an account is restricted by role. Every cross-tenant administrative action is recorded in an audit trail.
The retention period is set by each customer in their account’s compliance settings. Prospect data past that period, or whose deletion was requested by its data subject, is deleted from the active database; a record that an objection was once made is kept as minimally as possible precisely to make sure that objection keeps being respected. Account data is kept while the account is active and as long as it is needed for tax obligations or dispute resolution.
8. Your rights as a data subject
The PDP Law gives you the right to obtain information about processing, access and obtain a copy of your data, correct inaccurate data, end processing and delete data, withdraw consent, object to decisions based solely on automated processing including profiling, and request that your data be transferred. These rights apply whether you are a paying user or a person whose data entered the system because one of our users collected it.
There are three ways, and you don’t need an account to use them:
- Reply STOP to the WhatsApp message you received. That reply immediately stops further messages from the user who contacted you, including scheduled ones. Reply MULAI if you later want to hear from them again.
- Open the consent link included in the first message. The link is digitally signed and records your objection to the do-not-contact list that applies to every platform user.
- Open the Data Rights page — enter your WhatsApp number or email, choose delete my data or don’t contact me. The request applies to every platform user at once, not only the party that contacted you.
- Send a request to the address in section 12 — for anything not covered above, such as requesting a copy of data, a correction, or objecting to a profile assessment. State the phone number, email, or profile link you use so we can find the data.
We forward deletion requests to the user acting as Controller of that data and execute them on the system. If a request is refused, we will give the reason in writing. You also have the right to complain about handling you consider inadequate to the authority responsible for personal data protection.
10. Children
The service is intended for business use and is not meant for individuals under 18.
11. Policy changes
We may update this policy. Material changes will be announced in the app or by email, and the “last updated” date above will be adjusted.
12. Contact us
Requests about personal data — access, correction, deletion, objection to profiling — go to privasi@maira.id. We respond within at most 3 × 24 hours for requests to stop contact, and within 14 working days for other requests.
Publication note: before this policy is published as an official document, complete the Controller’s identity — legal entity name, business identification number, registered address — in section 1, and make sure the email address above is actually monitored. If processing runs at large scale and systematically, the appointment of a data protection officer with their contact channel needs to be stated here.