Privacy when creating and sharing a personalized meditation

Start with the detail the practice needs

“I want to stay present during a difficult work conversation” may be a complete starting point. You can describe a pattern, a desired response, and familiar imagery without supplying colleagues’ full names or a confidential account of the meeting.

Our view is that good personalization depends on relevant meaning. More identifying information does not automatically produce more useful guidance.

Original illustrative request:

Create a practice for listening when I feel criticized at work. Use general role descriptions. Do not include names, the company, or details of the dispute in the script. Help me pause and ask one clarifying question.

Before producing or sharing audio, check that the resulting script follows your request.

Separate creation, Memory, and sharing

Creating a practice produces saved content for your account. Memory can carry selected context into later chats when enabled; its controls let you review or remove notes. Turning it off is a personalization choice, not an account-deletion action.

Sharing a personal practice creates access through a link. A signed-in recipient with an active general link can open it, and the link can be forwarded. The recipient receives the shared experience, not your complete private profile or creation conversation. Personal details written into the experience itself can still be heard or seen.

The owner can stop sharing to revoke the link and associated access. That does not recover information someone already copied elsewhere. See the sharing guide for the full personal-link workflow.

Understand service processing

The current policy explains that Manai collects submitted content, preferences, and service data, and uses third-party providers to deliver features. Access-controlled content is not a promise of on-device-only processing. The policy also describes analytics, retention, deletion, and requests for a copy of available personal data. Read the Manai Privacy Policy for the current terms and contact route.

If you connect another AI client, that provider processes its surrounding conversation under its own policy. Manai receives task-specific inputs for the requested action. You can revoke the client’s future Manai access through Connected agents in Manai Web; revocation does not delete the provider’s retained copy. These boundaries are described in the connected-client section of the policy.

Treat public demonstrations separately

A public demonstration has a different audience from a practice for yourself. Use invented details and review its title, artwork, script, and audio together. A photograph can reveal information the words omit.

Frequently asked questions

Does personalization require real names?

No. Describe the situation, response, and preferences that matter. General role descriptions can be enough to make the practice relevant.

Does turning Memory off erase my recordings?

No. Memory controls and deletion of saved content or account data are different actions. Review the current policy and the relevant account controls for deletion choices.

Who can access a personal shared practice?

Signed-in Manai users who receive its active general link can open it. The link can be forwarded; access is not limited to the first recipient.

Is connecting an AI client the same as publishing my practice?

No. Connecting a client does not make saved scripts or generated audio public. Information used in that client’s conversation remains subject to its own privacy terms.

Create your personal practice with Manai →