Skip to content
Milvao
Privacy and consent

Numbers stay hidden until both people say yes

A phone number moves only after two yeses: the asker allows it, and the matched member accepts. Milvao never joins, reads or posts in your groups.

Read the privacy policy
Consent model

Three separate yeses, each for one purpose

Consent isn't one checkbox at sign-up. Each yes covers a single purpose, is recorded when it is given, and can be withdrawn.

  1. 1

    Receiving introduction requests

    Every member, once

    A separate yes in the profile form. It is off by default, and nobody is asked to help until they turn it on.

  2. 2

    Sharing my number for this request

    The member who asks, per request

    After confirming the brief, the asker chooses whether their number may be shared if someone accepts. It covers that one request only.

  3. 3

    Accepting this introduction

    The matched member, per introduction

    Accept means: share my contact with this person for this request. Decline or silence means nothing is shared.

The same rules apply whether your community uses automatic matching or approves each match. A contact is sent only when consents 2 and 3 are both in place, and both are checked again at the moment of sending.

Who sees what

Pick a person and a stage

What the asker, the matched member, your team and the rest of the group can see, at each stage of one sample request.

  • Offers are off until a member turns them on, and PAUSE or STOP works any time.
  • Consent is recorded per request, and checked again right before any contact is sent.
  • A contact that has been delivered can't be recalled, which is why it waits for two yeses.
  • The request brief Sees it
  • Aman's original message Hidden
  • Aman's name and number Hidden
  • Harpreet's name and number Their own

She sees the brief, not who asked or their exact words.

Member controls

One word to pause or stop

Members don't need an app or a settings page. They reply with a single word to your community's business number.

Members can also ask your team to delete their profile. That cancels pending introductions, removes their profile and message content, and keeps only counts that can't identify them.

  • PAUSE

    Stops introduction requests and cancels any the member hasn't answered.

  • RESUME

    Starts requests again, if the member turned them on in their profile.

  • STOP

    Turns off requests and other messages. Requests can be turned back on from the profile.

  • PROFILE

    Sends a new private link to edit the profile. HELP shows all the options.

Never

What Milvao never does

  • Join, read or post in your WhatsApp groups
  • Show a matched member who asked, or their exact words, before they accept
  • Share a phone number before both people have said yes
  • Send your member directory or members' numbers to an AI model
  • Sell member data or use it for advertising
  • Put full phone numbers, message text or secrets in its logs
How data is protected

Built so a mistake can't leak a number

Privacy is enforced in the data model, not only in the screens.

Numbers encrypted

Phone numbers are encrypted in the database and shown masked on the dashboard, with only the last digits visible.

Links stored as hashes

Join links and profile links are kept only as one-way hashes, so a database copy doesn't hand out working links.

Profile links expire

A profile link works once and expires after 60 minutes, and link previews can't use it up.

Communities kept apart

Each community's data is tied to its workspace in the database itself, so one community can never see another's members.

Consent kept as a record

Every consent and withdrawal is stored as an event with the wording version shown, and checked again right before a contact is sent.

Actions are audited

Operator and staff actions are written to a separate audit log, kept apart from the app's own data.

Retention defaults

Milvao keeps message content only as long as it needs to run introductions and fix problems. These are the defaults; your community can ask about shorter periods during the pilot.

Raw message data received from WhatsApp
7 days
Message text
90 days
Audit and security logs
1 year
Website visit counts (daily totals that can't identify anyone)
25 months

Who is responsible: your community decides how its members' data is used, and Milvao processes it on your behalf. Milvao is responsible for operator accounts and this website. Our policy is a draft under legal review.

FAQ

Privacy questions

All questions

Only after two yeses. The person asking agrees to share their number for that request, and the matched member accepts that specific introduction. Then each side gets the other's contact privately. Nobody else sees it.

Your community's operators can see requests and briefs on the dashboard. A matched member sees only the brief, not who asked or their exact words, until they accept. Nobody else in your groups sees anything.

Phone numbers are encrypted in the database and masked on the dashboard by default. Join links and profile links are stored only as one-way hashes, and profile links work once and expire after 60 minutes. Each community's data is kept apart from every other community's.

Only to write the brief. Milvao sends the request text, with contact details removed, and your community's list of categories. Your member directory and members' phone numbers are never sent. Matching itself uses Milvao's own ranking rules.

By default, raw message data from WhatsApp is deleted after 7 days and message text after 90 days. Audit and security logs are kept for one year. A member can ask your operators to delete their profile, which also cancels any pending introductions.
30-day pilot

Give your members a private way to ask

Start with two or three groups. Your members keep control of their numbers from the first message.

Talk to us