Minder Legal
Privacy Policy
What Minder processes, who can see it, and how to ask for help with your information.
Version:
Operator and privacy contact
Minder is currently an unregistered project operating from Armenia. For privacy requests and questions about who operates the service, contact support@minderhealth.app. Your practitioner or organization may have separate responsibilities for the care and records they manage; ask them for their own privacy information.
Information we process
Depending on the features you use, Minder processes your account identifier, password hash, optional contact details, recovery and verification records, professional profile and credential documents, bookings, attendance and consent timestamps, payment receipts and ledger entries, messages, community contributions, and technical security logs. Practitioners and clients may also use clinical notes, assessments, plans, homework, or referral information. Health-related information is sensitive personal data.
Anonymous registration does not require a public real name. Booking, professional verification, or organization services may require further information. Public profiles and community contributions are visible according to their publication settings; avoid posting information you want to keep private.
Purposes and permissions
We process information to create and secure accounts, deliver the features you request, coordinate services, check credentials, handle support and payment disputes, prevent abuse, and meet applicable legal obligations. The appropriate legal basis depends on the data and purpose. Accepting terms or acknowledging this notice is not blanket consent to every use of health data, marketing, analytics, recording, or outcome tracking.
Where consent is required, the responsible operator must explain the specific information, purpose, recipients, duration, and withdrawal process. Contact support to withdraw consent for processing managed by Minder; contact your practitioner for clinical processing they manage. Withdrawal may limit features that need that information and does not override lawful retention obligations.
Access and confidentiality
Access depends on your role and the feature: practitioners can manage their authorized clients, clients can see information shared with them, and organization roles have defined permissions. Technical encryption protects selected sensitive fields but does not mean that data is inaccessible to every authorized system operator. Support or security investigations must use only necessary information under appropriate authorization.
Confidentiality is not absolute: necessary disclosures may be required by law or justified to protect life or health within applicable rules. We do not sell personal data. Public posting makes the information available to others; removing it from Minder cannot guarantee removal of copies already made elsewhere.
Video sessions
Video sessions use MiroTalk and WebRTC. Media transport uses encryption; this notice does not promise independently verified end-to-end encryption for every deployment, device, or call configuration. Minder’s booking workflow does not record call media. Participants and external video infrastructure may have separate capabilities and responsibilities.
The video infrastructure processes connection information such as IP addresses and technical signaling. Minder stores booking, join, consent, attendance, and room-status information for service coordination and disputes. Private room links must not be forwarded. A closed room in Minder prevents joining through its booking flow; it is not a guarantee that an external video provider has invalidated every previously shared link.
Service providers and international transfers
Hosting, database, file-storage, email, and video providers process information needed to operate the service. Minder uses Railway for hosting, Cloudinary for media and access-controlled payment or organization documents, and Google Drive for private professional credential documents. Email and video providers process information needed for their features. Contact support for current provider details and safeguards.
Public interface text and published educational content may be sent to translation services such as DeepL. Public translation tools are not intended for clinical notes or private client information. On eligible public pages, Google Analytics receives cookieless activity measurements even before cookie consent; Microsoft Clarity runs only after acceptance. Transfers outside Armenia require an appropriate legal assessment and safeguards; this notice does not by itself establish transfer authorization.
Retention and account closure
Account deactivation disables access; it does not automatically delete bookings, messages, clinical records, financial records, or backups. Information should be retained only for the service purpose or applicable legal, professional, security, and dispute requirements. Clinical retention can depend on the practitioner and jurisdiction. Contact support and your practitioner for the applicable record category and retention period.
Deletion requests require an identity check appropriate to the risk. Some records may need to be retained or restricted rather than erased; where applicable, we will explain the reason. Backup removal may follow a separate lifecycle. We do not promise immediate deletion from every system.
Requests, complaints, and security concerns
Contact support@minderhealth.app to request information about processing, access, correction, restriction, deletion, or withdrawal of consent where applicable. Identify your account or booking and the request without sending passwords or unnecessary clinical details. You may also raise concerns with the competent personal-data protection authority or seek available legal remedies.
Report suspected unauthorized access to support promptly. No system can guarantee absolute security. This notice is not a HIPAA certification, a data-processing agreement, or a substitute for the safeguards required for a particular practitioner, organization, or jurisdiction.
Notice updates
The version date identifies this notice. Changes in purposes, recipients, or required permissions must be assessed separately; publishing a notice does not create consent to a new use of sensitive information.