Privacy in plain language

Mindara uses the information needed to provide care, protect accounts, process bookings, and meet legal obligations. Read the Privacy page for categories and retention details. Ask support before putting sensitive health information in a general ticket. Privacy and safety choices are easier when you know which record you are changing and who needs to verify it. Mindara may retain limited records for legal, safety, fraud-prevention, or financial obligations even after an account request. This article focuses on “Privacy in plain language” and gives you a safe next step even when the normal path is unavailable.

What to do now

1. Use Account, Security, Privacy, or the Report action that matches the problem. Describe the minimum necessary facts and keep the original confirmation.
2. For account access concerns, change the password from a trusted device, sign out other sessions, and enable two-factor authentication before discussing details.
3. For data export, deletion, or content reports, submit one request and watch the signed-in notification or verified email for the next step.

If the usual path fails

• A request involving another person requires additional checks; do not upload their identity or health information to prove a point.
• If a message, post, or account activity suggests immediate harm, use emergency or crisis services first; moderation and support queues are not emergency monitoring.
• Recovery codes, passwords, session cookies, and identity documents belong only in the secure flow explicitly named by Mindara.

When to contact Mindara

Support can explain platform records, security steps, and report status. A clinician or emergency service handles clinical or immediate safety decisions. Include the page or booking reference, the exact error text, the time it happened, and the device/browser you used. Never send a password, one-time code, full card number, or another person’s private health information.

For this situation

Different records have different purposes: account details enable sign-in, booking records coordinate care, and security events protect the service. The privacy notice explains categories and retention; a support agent should not ask for a complete health history to answer a login question.

Why the result may look different

Mindara shows a status only after the relevant service has recorded it. A browser can keep an older page in memory, an email can arrive before a database update, and a bank, employer, provider, or identity check may have its own processing time. Read the status words and the timestamp together. “Pending”, “confirmed”, “cancelled”, “failed”, and “under review” are different outcomes, even when a colour or a short notification makes them look similar. If you are helping somebody else, ask them to sign in themselves rather than sharing credentials or screenshots with private details.

Before you try again

• Check the dashboard record first so a successful action is not repeated.
• Confirm the account, country, language, time zone, and role shown in the header.
• Close an old duplicate tab, then refresh once; repeated clicks can create holds or duplicate requests.
• Use a supported, updated browser with cookies, pop-ups, microphone, or accessibility settings enabled as the task requires.
• Write down the exact button label and status before changing anything.

If your circumstances are unusual

A normal step may not fit if you use an employer invitation, share a device, travel between countries, need an interpreter or assistive technology, care for someone during a session, or have lost access to an old email or phone. Say which constraint matters and ask for an accessible or safer route. Do not work around a check by choosing a false country, opening a second account, borrowing a payment method, or sending documents through an ordinary chat. Those shortcuts can make a genuine problem harder to untangle.

Keep a useful record

Make one private note with the article title (“Privacy in plain language”), the date and local time, the page address, the status before and after, and what you tried. Redact passwords, recovery codes, full payment numbers, health details, and other people’s names. A short, factual timeline lets support investigate faster and gives you something reliable to refer back to if a session expires or a redirect takes you to the wrong page. If another person is affected, ask them to make their own request so consent and account ownership remain clear. Clear notes also help you notice whether the problem is occasional, tied to one device, or repeating after a particular action.

Keep the note somewhere private and remove it when you no longer need it. The goal is clarity, not surveillance of yourself or another person. If the issue affects care, safety, or access, say that plainly so the right team can prioritise it. A calm record is often the fastest way to get the right answer.