Mihe
Draft. This page is being reviewed by a lawyer and may change before it takes effect.

Privacy policy

What Mihe collects, why, who else sees it, how long it is kept, and how to ask for it back. The Security page says how it is protected.

Last updated 30 September 2026

Who we are

Mihe is run by Neek Digital Solutions Ltd, Lagos, Nigeria. For anything on this page, email support@mihe.dev.

Two kinds of data

About you and your team, and about visitors to this site. We decide what is collected and why, so for this data we are the controller.

About the users of your app, which passes through Mihe when they talk to the assistant you embedded. You decide what your app sends and why, so for this data you are the controller and we process it on your behalf, only to run the assistant for you.

About you and your team

Name and email address
Why: To sign you in, send you verification and reset links, and invite your team.
Password
Why: Kept only as an argon2id hash. We cannot read it.
Two-factor secret, if you turn it on
Why: Kept encrypted, to check your codes.
Sessions: browser and IP address
Why: To keep you signed in, and to show you where you are signed in.
Your organisations, apps and settings
Why: They are the service.
Billing contact, country and payment history
Why: To take payment, charge the right tax and give you receipts.
Card details
Why: The card number is held by the payment provider, never by us. We keep its last four digits, brand and expiry date, and an encrypted token from the provider that lets a saved card be charged.
Feedback you send
Why: What you type, plus the page you were on, your role, browser and screen size, to act on it.

We use it to run Mihe and to tell you about your account. We do not sell it, and we do not use it for advertising.

About your app's users

What your app’s users send the assistant, and what your app tells us about them:

  • Their user id and permissions, from the token your backend signs. Mihe never handles their password.
  • Their conversations with the assistant, both sides, including transcripts of voice.
  • What is on their screen that your app chooses to share with the assistant.
  • Every action the assistant attempted for them, with its input and outcome.
  • Documents you upload for the assistant to search.

Voice audio is relayed to the model provider as it happens and never written to disk. Its transcript is kept with the conversation.

We use this data only to run the assistant for you and to show you what it did. You are responsible for telling your users about it, and for having a lawful basis to send it.

Who else sees it

OpenAI
What for: Running the model, typed and spoken
What it sees: Conversations, screen context your app shares, action results, and voice audio.
DigitalOcean
What for: Hosting the runtime and database, and storing launcher icons
What it sees: Everything we store. Icons are public, and loading one tells it the visitor's IP address.
Vercel
What for: Hosting the dashboard and this site
What it sees: Your team's dashboard traffic, and visits to this site.
Resend
What for: Sending account email
What it sees: Recipient addresses and the messages, which are sign-in, reset and invitation links.
SeerBit, or Paystack
What for: Taking payment
What it sees: Your billing contact, country and card.

Where it goes

Neek Digital Solutions Ltd is in Nigeria, and some of our subprocessors are in the United States and elsewhere, so your data is processed outside the country you are in. Each subprocessor is bound to protect it, and we move it only as far as the service needs.

How long it is kept

What we keep, for as long as your organisation exists

Your account, your organisations, their settings, and your apps’ conversations, action logs and documents. Keeping conversations and action logs is deliberate: they are the record of what the assistant did, and you need that record to review it.

What goes sooner

  • Signed-in sessions expire after thirty days.
  • Verification, reset and invitation links stop working once used, and expire.
  • Voice audio is never stored at all.

Deleting it

Closing an organisation stops its apps and keeps its data, so it can be opened again. To have data deleted, whether yours, an organisation’s, or one of your users’, email us from an owner’s address. We delete it within 30 days, except what we must keep by law, such as payment records.

Cookies

This site sets no cookies and runs no analytics. It remembers whether you chose light or dark in your own browser, and nothing else.

The dashboard sets three, all needed to sign you in: your session, the token that renews it, and a short-lived one between your password and your two-factor code. They are sent only to the dashboard, never to this site, and no script can read them.

The widget in your app sets none of its own.

Your rights

Wherever you are, you can ask what we hold about you, ask us to correct it, to delete it, or to send you a copy. Email support@mihe.dev and we reply within 30 days. The Nigeria Data Protection Act, the GDPR and similar laws give you these rights, and the right to complain to your data protection authority.

If you use an app that has Mihe inside it, the app’s owner controls your data. Ask them first, and we will help them answer.

Mihe is for businesses. It is not meant for anyone under 18.

Changes

When this policy changes in a way that matters, we email the owners of every organisation before it takes effect, and the date at the top of this page changes.