Legal

Personal Information Collection List

Last updated: 2026-10-05

Collection triggers, information, purposes and the effect of declining, by feature. Local-only editing does not upload maps.

Collection details

Account — when you register, sign in or edit your profile: email, name, avatar, password hash where password sign-in is used, verification status, authorized Apple/Google identity fields, sessions and consent records. Required for account services; declining does not prevent local editing.
Cloud sync — when you enable sync for a map: title, nodes, text, structure, appearance, revisions and referenced attachments. Used to store and sync the selected map; subsequent edits are uploaded while sync is active. Local-only maps are not uploaded.
Read-only sharing — when you create or manage a link: selected map content and attachments, link identifier, access settings and password hash if set. Viewers generate request and access-session data. Revoking a link prevents subsequent access but cannot retrieve copies already saved.
Purchases — when you buy, restore or manage Pro: product, period, amount/currency, order or transaction identifiers, subscription status, store validation data and account-linked entitlements. Stripe or the store processes payment details; HMind does not store full card numbers.
Support — when you send feedback or email: contact details, message, selected attachments and diagnostics you choose to include. Used to respond and troubleshoot; avoid sending unrelated personal information.
Online requests — IP address, time, browser/app/OS information, session and security metadata, including account-linked device/session records where used. Required for delivery, sign-in security and abuse prevention; this is separate from optional analytics.
Desktop first launch — release builds send a randomly generated local installation identifier, OS, distribution channel and initial app version to HMind to count first-observed launches. Retries reuse the identifier; it is not linked to your account, maps, email or hardware identifiers, and is not sent to Google Analytics. Previously installed users upgrading to this version may be counted on first observation. Requests are subject to network security processing.
Website analytics — enabled by default: sanitized page paths/referrers, fixed page title, browser/device data, cookie identifiers and limited event labels. First-party daily measurement records random event IDs, download/store-click platform, interface language and a coarse 30-minute acquisition channel; optional checkout attribution is carried to billing records. Raw campaign values and referrer URLs are not retained in these first-party events. Used to measure website usage. Cookie settings lets you reject or withdraw; HMind events exclude map text, email, share tokens and payment details.
Files and system access — only for your selected import, attachment, avatar, export or paste action: selected files, photos/videos, clipboard content or destination. These are processed locally unless you choose sync, sharing, profile upload or feedback. Refusing access affects the related action, not ordinary local editing.

Your control

Keep maps local-only, revoke sharing, reject website analytics or request account deletion. Stopping sync does not erase cloud copies; revoking a share does not retrieve saved copies. Manage file/photo permissions in system settings; declining affects the related action. Email support@hmind.app for rights requests.

Collection triggers, information, purposes and the effect of declining, by feature. Local-only editing does not upload maps.

Collection details

Account — when you register, sign in or edit your profile: email, name, avatar, password hash where password sign-in is used, verification status, authorized Apple/Google identity fields, sessions and consent records. Required for account services; declining does not prevent local editing.
Cloud sync — when you enable sync for a map: title, nodes, text, structure, appearance, revisions and referenced attachments. Used to store and sync the selected map; subsequent edits are uploaded while sync is active. Local-only maps are not uploaded.
Read-only sharing — when you create or manage a link: selected map content and attachments, link identifier, access settings and password hash if set. Viewers generate request and access-session data. Revoking a link prevents subsequent access but cannot retrieve copies already saved.
Purchases — when you buy, restore or manage Pro: product, period, amount/currency, order or transaction identifiers, subscription status, store validation data and account-linked entitlements. Stripe or the store processes payment details; HMind does not store full card numbers.
Support — when you send feedback or email: contact details, message, selected attachments and diagnostics you choose to include. Used to respond and troubleshoot; avoid sending unrelated personal information.
Online requests — IP address, time, browser/app/OS information, session and security metadata, including account-linked device/session records where used. Required for delivery, sign-in security and abuse prevention; this is separate from optional analytics.
Desktop first launch — release builds send a randomly generated local installation identifier, OS, distribution channel and initial app version to HMind to count first-observed launches. Retries reuse the identifier; it is not linked to your account, maps, email or hardware identifiers, and is not sent to Google Analytics. Previously installed users upgrading to this version may be counted on first observation. Requests are subject to network security processing.
Website analytics — enabled by default: sanitized page paths/referrers, fixed page title, browser/device data, cookie identifiers and limited event labels. First-party daily measurement records random event IDs, download/store-click platform, interface language and a coarse 30-minute acquisition channel; optional checkout attribution is carried to billing records. Raw campaign values and referrer URLs are not retained in these first-party events. Used to measure website usage. Cookie settings lets you reject or withdraw; HMind events exclude map text, email, share tokens and payment details.
Files and system access — only for your selected import, attachment, avatar, export or paste action: selected files, photos/videos, clipboard content or destination. These are processed locally unless you choose sync, sharing, profile upload or feedback. Refusing access affects the related action, not ordinary local editing.

Your control

Collection triggers, information, purposes and the effect of declining, by feature. Local-only editing does not upload maps.

Collection details

Account — when you register, sign in or edit your profile: email, name, avatar, password hash where password sign-in is used, verification status, authorized Apple/Google identity fields, sessions and consent records. Required for account services; declining does not prevent local editing.
Cloud sync — when you enable sync for a map: title, nodes, text, structure, appearance, revisions and referenced attachments. Used to store and sync the selected map; subsequent edits are uploaded while sync is active. Local-only maps are not uploaded.
Read-only sharing — when you create or manage a link: selected map content and attachments, link identifier, access settings and password hash if set. Viewers generate request and access-session data. Revoking a link prevents subsequent access but cannot retrieve copies already saved.
Purchases — when you buy, restore or manage Pro: product, period, amount/currency, order or transaction identifiers, subscription status, store validation data and account-linked entitlements. Stripe or the store processes payment details; HMind does not store full card numbers.
Support — when you send feedback or email: contact details, message, selected attachments and diagnostics you choose to include. Used to respond and troubleshoot; avoid sending unrelated personal information.
Online requests — IP address, time, browser/app/OS information, session and security metadata, including account-linked device/session records where used. Required for delivery, sign-in security and abuse prevention; this is separate from optional analytics.
Desktop first launch — release builds send a randomly generated local installation identifier, OS, distribution channel and initial app version to HMind to count first-observed launches. Retries reuse the identifier; it is not linked to your account, maps, email or hardware identifiers, and is not sent to Google Analytics. Previously installed users upgrading to this version may be counted on first observation. Requests are subject to network security processing.
Website analytics — enabled by default: sanitized page paths/referrers, fixed page title, browser/device data, cookie identifiers and limited event labels. First-party daily measurement records random event IDs, download/store-click platform, interface language and a coarse 30-minute acquisition channel; optional checkout attribution is carried to billing records. Raw campaign values and referrer URLs are not retained in these first-party events. Used to measure website usage. Cookie settings lets you reject or withdraw; HMind events exclude map text, email, share tokens and payment details.
Files and system access — only for your selected import, attachment, avatar, export or paste action: selected files, photos/videos, clipboard content or destination. These are processed locally unless you choose sync, sharing, profile upload or feedback. Refusing access affects the related action, not ordinary local editing.