Your data and sharing

Optional Travel app

Travel stores your saved roads and bus-stop choices privately against your account. Stop searches use a shared local copy of the Department for Transport's public NaPTAN directory. Public road reports are cached for all users. Requesting a departure update sends the selected public stop identifier to TransportAPI; it does not send your MindMesh identity or GPS coordinates. The provider processes that request under its own privacy terms. Stop choices are removed when your account is deleted.

Optional sign-in on custom-domain websites

A verified MindMesh Profile or Business website can recognise you using a separate sign-in session if you approve it on MindMesh. This shares your current display name, username and signed-in status with that website. It does not share your password, email address, main-site session cookie, private records or account permissions. Editing and private actions remain on MindMesh. You can continue browsing public pages without approving website sign-in.

The hand-off uses a short-lived, single-use code bound to your browser and the verified website. Website cookies are host-only, Secure and HttpOnly. Website identity sessions last up to 30 minutes and cannot outlive the source session's current deadline. Approval lasts 30 days; Website sign-ins lets you revoke it and its sessions. Signing out of MindMesh revokes website sessions linked to that browser's sign-in. Account security changes and invalid website ownership also prevent reuse.

MindMesh stores hashed hand-off identifiers, account/domain references, approval and expiry times for these checks. Expired hand-off records are removed in bounded batches during subsequent hand-offs after a one-day retention buffer; approvals expire after 30 days. Existing backups follow the site's normal retention policy.

Optional Google sign-in

You can choose Google to sign in after linking it in Settings > Account. Approved beta invitees can also choose Google when creating an account. MindMesh receives your Google account identifier, email address and email-verification status. It stores the identifier and email to recognize your linked account. Google sign-in does not grant access to your Google Drive, contacts, email messages or Self Care exports.

Existing accounts are not linked automatically by matching email addresses: you must sign in and confirm your MindMesh password first. Beta approval, age and consent requirements, MindMesh email verification and any required authenticator step still apply. Signing in with Google does not change your MindMesh email address. Google processes the sign-in under its privacy policy.

Google login tokens are checked during sign-in and are not retained for background access. Disconnecting Google in Account settings removes the live sign-in link and signs out your browser sessions; it does not disconnect Calendar connections or Google Sheets exports. Confirm a MindMesh password to disconnect. If you created your account with Google, you can use password reset to set a backup password first. Sign-in identifiers are removed when the account is deleted; previous backups expire under the site's backup retention schedule.

Optional food barcode lookup

If you look up a product barcode, MindMesh requests public product information from Open Food Facts and caches it separately from the curated food catalogue. Only the barcode is sent: your account, food diary, chosen portion and camera images are not sent. Camera barcode decoding runs on your device; scanning stops when closed or after a short timeout. Product results may be incomplete or inaccurate, so check the packaging before logging. Nothing is logged until you press Add.

Public product data comes from Open Food Facts under the Open Database License. A source label is retained with logged nutrition. Barcode lookup does not use an AI service or upload meal photos.

Optional browser notifications

Browser notifications are off until you enable them on a device and grant browser permission. You can choose chat messages and other notifications separately. MindMesh stores a device subscription endpoint, its encryption keys, your choices and delivery status so it can send alerts without an open MindMesh page. These subscription credentials are kept in the database; the server signing key and delivery library are outside the public website directory.

Push delivery uses your browser provider's service, such as Apple, Google, Microsoft or Mozilla. The provider receives delivery metadata and an encrypted alert payload. By default, MindMesh sends generic alert text and a MindMesh destination link. If you explicitly enable private message previews on a device, the encrypted alert includes a shortened preview of the latest unread message. This text may appear on the lock screen or in notification history, including anything sensitive written in that message. Sender names, Self Care records and other notification details are not added. You can turn previews off independently on each device; doing so cannot remove alerts already delivered. Notification clicks open MindMesh, where normal sign-in and access checks apply. The service worker does not cache private pages for offline use.

Disable notifications in Settings > Notifications on each device or revoke permission in your browser. Logging out removes that device's live subscription from MindMesh. Password resets and other account-wide session revocations invalidate existing subscriptions. Expired subscriptions are removed when reported by the provider. Earlier copies may remain in production backups for up to 30 days. Delivery is not guaranteed and these alerts are not intended for emergencies.

Optional connected calendars and booking sync

You can connect Google Calendar from Bookings Calendar > Calendar settings > Calendar sync. This is separate from Google sign-in and Self Care's Google Sheets export. Each person connects their own provider account. Microsoft / Outlook controls are also available where that provider has been configured; it is not currently enabled on MindMesh.

What MindMesh accesses and why

Viewing asks for permission to list calendars you can access and read their events, including calendars shared with your Google account. Google grants this permission at account level; within MindMesh, only calendars you select are imported. MindMesh uses their names, identifiers, timezones and display colours for the calendar chooser, and selected event titles, locations, start/end times, all-day and busy/free status for your private Dashboard calendar. It also processes event identifiers, versions and sync markers to recognise updates and avoid duplicate booking copies.

You can separately choose to use a selected calendar's busy times to prevent overlapping MindMesh bookings. Other visitors and people sharing your MindMesh calendar do not receive imported event titles, locations or provider account details. Availability may be unavailable or a time may be blocked without revealing the external event. If blocking is enabled and the external cache is too old, unavailable or does not cover a requested date, new bookings pause rather than treating unknown availability as free.

Optional permission to send bookings

Allow booking sync is a separate permission request. Google's event-write permission allows viewing, creating, changing and deleting events on calendars your Google account can edit; MindMesh uses it only for the booking copies it manages in calendars you explicitly enable. Viewing calendars does not enable outgoing writes. New busy-time blocking, booking export, external-change review and address-sharing options start off.

When you enable outgoing sync for a MindMesh calendar, confirmed bookings hosted by that calendar can be sent to the selected external calendar. Copies contain their time, a title based on the host's configured booking name, an optional Business service name and a short explanation that they are managed by MindMesh. Booker email addresses and phone numbers are not added as attendees, and the sync does not send Google Calendar invitations. Booking addresses are excluded unless you separately enable Include confirmed booking addresses. An address sent to an external calendar may be visible to people who can already access that calendar under the provider's sharing settings.

An external time edit does not immediately move the MindMesh appointment. If external-change review is enabled, it can become a suggestion that the other party must accept. Deleting an external copy does not silently cancel the MindMesh booking: cancellation requires explicit confirmation in MindMesh. Choosing to keep the MindMesh booking can restore its managed fields or recreate a deleted external copy.

Storage, refresh and retention

MindMesh stores encrypted connection tokens, provider account and calendar identifiers, calendar names and imported event details on its server. The encryption key is outside the public website directory. It also stores selected-calendar preferences, sync status, busy-time indexes, event-version information, managed-copy identifiers and change-review records. Times and busy/free status are indexed in the database for availability checks. This is server-side encryption of the protected connection and event fields, not end-to-end encryption of every booking record.

The importer uses a rolling window from 30 days before the current date to 120 days ahead. Events outside that window are removed from the active cache on a successful refresh. External-change review records and old booking-copy snapshots are pruned after 30 days by connection sync. With automatic updates disabled, refresh and this cleanup require Sync now. Automatic updates are currently disabled on MindMesh; if enabled later, they will run periodically and remain subject to provider limits, retries and outages. Updates are not instant or guaranteed.

Disconnecting and removing data

Turning off Use this calendar removes its imported event cache and disables its sync and busy-time mappings. Disconnect removes the live connection tokens, imported event cache and external-change review data, and disables its mappings. Limited encrypted account/calendar/event identifiers and connection metadata can remain to support reconnection and prevent duplicate copies. Contact support@mindmesh.cc to request removal of retained connection metadata. Previous backup copies expire under MindMesh's 30-day backup retention policy.

Calendar disconnect removes MindMesh's local tokens; it does not itself revoke Google's grant. You can also remove permission in your Google account connections. Provider permissions can cover more than one MindMesh feature, so review the services listed before removing a grant. Disconnecting does not delete existing external booking copies or your original MindMesh appointments. Turning address sharing off removes the address on the next successful update; provider version history, copies or earlier downloads may retain it.

Private subscription links

The separate subscription options provide a one-way feed of confirmed appointments you attend or host, including supported Business bookings. Anyone with a private subscription link can read that feed; keep the link secret and reset or disable it if exposed. Each feed's address inclusion starts off. External calendar services decide when to refresh subscriptions. Resetting or disabling a feed stops future access through that link, but does not erase copies already downloaded by a provider.

How provider data is used

Information received through Google Calendar APIs is used to provide these visible calendar, availability and booking-sync features. It is not sold, used for advertising, passed to ChatGPT or another AI service, or used to train general-purpose AI models. Imported provider details are not made public or shared with other MindMesh users. MindMesh's use and transfer of information received through Google APIs will comply with the Google API Services User Data Policy and Google Workspace API User Data and Developer Policy, including their Limited Use requirements. Google processes information under its own privacy policy.

Connected calendar information updated: 25 October 2026.

Optional Google Sheets exports

Where this feature is available, you can connect your own Google account from Self Care settings. Connecting alone does not start an export. You choose the measures and history range, then explicitly confirm that MindMesh may send those records to Google and keep the spreadsheet updated.

What is sent to Google

Your selected measures may include health and wellbeing records such as weight, sleep, water intake, mood, resting heart rate, bowel movements, supplements and other available Timeline measures. Daily summaries include dates, measure names, values, units and your account timezone. You can choose a rolling 30, 90 or 365 days. Cycle data is a separate opt-in, with independent choices for period dates, daily flow, symptoms and ratings, and private Cycle notes. Cycle notes require an additional explicit confirmation and include their associated dates. They go to a separate Cycle log tab; Notes and symptoms can also be exported through a separate option, but only entries individually marked for Google Sheets are included, with their date/time, title, text and symptom severity. All other private notes are excluded. Cycle data remains off in existing exports unless you select it.

Detailed food records require a separate selection. If enabled, these include food names, meal times, quantities, kcal, recorded nutrition and food sources. Separately selected detailed sleep records include times, hours, quality and awakenings, but exclude private sleep notes. Detailed supplement records include names and log times, not verified doses or adherence. You can separately select current units/timezone, food and water targets, and configured supplement entry targets for a Goals and settings tab. These settings are current, not historical or medical recommendations. Selecting food energy alone sends daily kcal totals, not the detailed food log.

Google access and stored connection details

MindMesh requests Google's file-only permission (drive.file) to create and maintain the export spreadsheet. This permission covers files MindMesh creates or files you explicitly select for it; it does not grant access to your entire Google Drive. This export feature does not browse unrelated Drive files or make your spreadsheet public.

MindMesh stores encrypted Google authorization tokens on its server outside the public website directory, so scheduled updates can run without you being signed in. It also stores your export selections, consent time, spreadsheet identifier and sync status. Disconnecting removes the live stored tokens; export preferences and sync metadata remain so your settings are retained. Encryption of these tokens does not mean that all Self Care records or the exported spreadsheet are end-to-end encrypted.

Information received through Google APIs is used to provide and maintain this export feature. It is not used for advertising, sold, or used to train general-purpose AI models. MindMesh's use and transfer of information received through Google APIs will comply with the Google API Services User Data Policy and the Google Workspace API User Data and Developer Policy, including their Limited Use requirements.

Updates, pausing and disconnecting

While exporting is enabled, MindMesh checks for changes approximately every five minutes. Changes to your selected measures, corrections and deleted source entries are reflected in MindMesh's managed spreadsheet tabs after the next successful update. Older records leave those tabs as the selected rolling range advances. Pausing stops further updates but keeps your connection. Disconnecting stops updates, removes the live stored Google tokens and asks Google to revoke access. If Google cannot confirm revocation, MindMesh tells you to remove its access in your Google account as well.

You can also revoke access through your Google account connections. Pausing, disconnecting or revoking access does not delete the existing spreadsheet, remove your original MindMesh records, or erase copies already made. You can delete the spreadsheet and manage its sharing in Google Drive. Google version history, downloads, backups and copies held by other services may retain earlier data even after the current export changes.

Using the Sheet with ChatGPT or other services

MindMesh sends your selected export to Google. It does not connect ChatGPT on your behalf. If you separately authorize ChatGPT or another service to read your Google Drive, that service may access the spreadsheet under the permissions you grant it. Review its data controls and privacy terms before sharing health information. Disconnecting Google from MindMesh does not disconnect those other services or delete information they have already received.

Google processes exported information under its own privacy policy. For questions about MindMesh's handling of your data or to request removal of retained export metadata, contact support@mindmesh.cc.

Google Sheets export information updated: 17 October 2026.

Optional Business maps

A business can choose to show a map of its published public address using Google Maps or Geoapify with OpenStreetMap. The map loads only when you choose View map. MindMesh sends that public address to the selected supplier to display the location; private booking addresses and unpublished business information are not used.

When a map opens, your browser connects to that supplier for the map and related location or tile requests. The supplier receives connection information such as your IP address and browser details and processes it under its own privacy policy. Google maps may also use Google's cookies. Geoapify coordinates can be reused in your browser session for up to 90 days for the same public address. MindMesh records admitted map openings for usage limits and uses temporary rate-limit information to reduce misuse. You can use Get directions instead of opening the embedded map.