Privacy notice

Optional notifications

If you choose notifications, we store an encrypted notification address for this app installation, your language and your notification choices. Messages contain a short reminder and an internal reference, not your name, session title, recording, transcript or feedback. You can change your choices in Settings. Turning off the future-session default does not cancel notifications you selected separately.

For Android delivery, Expo and Google’s Firebase Cloud Messaging (FCM) process notification identifiers and message data, potentially outside your country. Their retention differs from our app records: disabling alerts does not immediately erase provider records.

We clear our routing token when you disable notifications for the device, sign out, revoke the device or the provider reports that the token is unusable. Saved choices may remain so you do not have to choose again. Operational session-notification events, delivery records and exam-reminder receipts are removed after 30 days by scheduled cleanup, which also runs while delivery is off. Account deletion removes the associated device-notification records and session-ready events. Cleanup can be delayed by an outage; encrypted backups follow their separate expiry.

What we collect

We collect the account details you provide, your learning activity, session intentions and reflections, permission records, and technical information needed to keep the service secure.

• The app keeps an app-scoped installation identifier, device name or model, platform and app version when supplied, plus recent-use and security details such as last-seen time, protected network reference and browser or app information. This helps you recognise devices and helps us protect your account.
• If you use Google, Facebook, or LinkedIn to sign in, we keep the provider name, its stable account identifier, the email it returns, and whether the provider confirmed that email. We do not retain the provider access token or raw profile response.
• If you add a recording, we process the recording, transcript, language information, AI feedback, and evidence links created from it.
• If you report a concern about AI feedback, we keep the concern category and any optional details you choose to add so an authorised person can review it. The app does not include session content in the submission automatically.
• If you connect Zoom, we store the connection and selected meeting details needed to discover recordings. For an eligible discovered recording, we store limited recording metadata to create the review item; no media is imported until you approve it and any applicable participant or client permission is valid. We do not import video, chat, participant files, or meeting summaries.

Access enquiries

When you ask about access, we store your email and any optional name, organisation or message in encrypted form. We also keep a keyed fingerprint of your email to identify duplicate requests without exposing the address, your selected path and focus, language, request status and timestamps, and minimal security and audit information.

We use this information only to understand the access setup that may fit you and to reply about availability, inclusions and any cost. Sending an enquiry does not create an account, enrol you or take payment.

You may ask support to correct or delete eligible access-enquiry information. We may retain limited security, legal or audit records where necessary.

Bridge registrations

For a registration abandoned before payment, we keep encrypted contact details while the payment outcome is checked. Once an unpaid reservation is verified as expired, eligible contact details are removed after 90 days. An issued bank invoice, uncertain payment or other financial exception needs manual review and is not automatically erased. Paid enrolments and financial evidence follow separate record-keeping rules.

Website Guide conversations

If you use the Guide on our home page or The Bridge page, we keep your questions, the Guide’s replies, language, page, timestamps and limited technical and safety records. The conversation is separated by page and organisation. Your name and email are encrypted when you choose to ask a person for help, and we verify the email before sending a personal reply.

The Guide may use an automated service to answer from information we have reviewed for that page. If it cannot give a supported answer—or you ask for a person—the conversation is passed to an authorised programme team member. A personal reply does not become a reusable public answer unless it is separately reviewed and approved.

We keep Guide enquiries so they can be connected to your account if you later join, but only after your ownership of the email is verified. We do not delete them on a fixed schedule. You may ask support to delete eligible information. Limited security, delivery, legal or audit records may be retained where necessary, and encrypted backups follow their separate expiry.

Why we use it

We use this information to provide your learning journey, prepare source-linked developmental feedback, remember useful themes across sessions, support you, prevent misuse, and keep an auditable record of permission and important actions.

Permission comes first

Recordings may be used only with permission from both coach and client or practice participant. Real-client processing waits for the client’s recorded agreement. Permission can be declined or withdrawn without affecting access to unrelated parts of the service.

AI and service providers

AI services help create transcripts, translations, and formative feedback. We send these requests with response storage disabled. Under standard controls, an AI provider may still keep limited request data for abuse monitoring for up to 30 days; stronger approved data controls can reduce this period. API data is not used to train public models unless the account owner explicitly opts in. Our hosting, email, security, AI, and connected-meeting providers process only the information needed to deliver their part of the service.

• AI output can be incomplete or mistaken and remains a developmental hypothesis.
• A connected meeting provider remains responsible for its own copy of a cloud recording under your account settings.

Storage and retention

Recordings are encrypted in private storage and normally scheduled for deletion after 30 days. Verified transcripts, consent receipts, structured findings, reflections, audit records, and deletion receipts may be retained to preserve the integrity of your learning record. If Zoom verifies that you removed The Coaching Map, we delete the Zoom connection, content, identifiers, imported session, and learning data derived from it in active product systems, regardless of that normal schedule. To prevent an authorization already in progress from restoring access, we temporarily use only keyed, non-reversible identity and event digests plus lifecycle timing records. They contain no raw Zoom account or user identifier, credential, meeting detail, recording, transcript, or client information. These markers expire and stop being used within 24 hours. Automated cleanup removes expired rows; if infrastructure is unavailable, physical row removal completes when normal processing resumes. The recording in your Zoom account is not deleted. Encrypted server backups may retain a deleted item until the normal backup cycle expires.

Your choices and rights

You can delete an imported recording, withdraw client permission while the recording is retained, disconnect Zoom, or ask us to access, correct, export, restrict, or delete eligible personal information. Some records may need to be retained for security, legal obligations, or evidence integrity.

International processing and security

The service and its providers may process information in more than one country. We use access controls, encryption, signed requests, least-privilege permissions, audit trails, and tested recovery procedures to reduce risk. No online service can promise absolute security.