Privacy Policy

Last updated: 26 August 2026

This policy covers coaching.idamayer.com and the scheduling and billing that runs behind it, operated by Ida Mayer Coaching & Consulting LLC. It describes what is actually collected and stored, not what a generic template says might be. For the terms of the coaching service itself, see the legal disclaimer.

If you only visit the site

Google Tag Manager and Google Analytics run on every page. They record page views and a small set of interactions — which "book a call" button was clicked, which FAQ was opened, whether the scheduler came into view. None of that is tied to your name or email, but Google sets cookies and receives your IP address as part of it. You can block this with browser settings, a content blocker, or Google's own analytics opt-out add-on.

The cal.com booking widget's script loads on every page so that booking links work anywhere on the site. It comes from app.cal.com and is covered by cal.com's own privacy policy.

If you get in touch

The contact form is a Google Form, so whatever you put in it — typically your name, email and message — is stored in Google Drive under my account. Emailing me directly does the same thing in Gmail.

If you book a session

Booking a session creates three things:

• A calendar event on my bookings calendar, with you as an attendee and a Google Meet link. The event also carries private billing metadata — why the session exists and whether it has been paid for. That metadata is not visible to attendees.
• A row in my session ledger, a private spreadsheet: a session id, your email as the identifier, the scheduled start and end, the actual duration once the session has happened, what it cost or how many prepaid hours it drew down, its payment status, and the ids of the matching calendar event and payment records.
• A client record, also in that spreadsheet: your email, your payment processor customer id, whether you are on a package or invoiced monthly, your rate, your remaining hours balance if you have a package, and whether you hold a standing weekly slot.

Booking through cal.com sends your name and email to cal.com directly. Once booking moves into my own client portal, cal.com is only asked which times are open and never learns who is booking.

None of this stores what we talk about. The system above holds scheduling and payment data only. It has no field for session content, and nothing said in a session goes into it.

If you pay me

Payments run through Stripe. I never see or store your card number — card details go straight to Stripe and stay there. What I hold is a Stripe customer id, your invoices and their amounts, dates and session line items, and — if you have agreed to it — a record that Stripe is holding a saved payment method for you so a future invoice can be charged. You can withdraw that at any time by telling me, and I will remove it in Stripe.

Nothing is ever charged automatically without approval. Every invoice passes a manual approval step before it is billed.

If you use the client portal

The portal signs you in with a link emailed to you — there is no password, so there is no password to be leaked. The sign-in link is single-use and expires shortly after it is issued. Your email address is what identifies you.

Where it lives, and who else can see it

• Google — Calendar, Sheets, Gmail and Apps Script, under my own account.
• Stripe — payment processing, invoicing, and any saved payment method.
• cal.com — works out which times are free by reading my calendars. It sees the contents of my calendars, which include your name on the events you have booked.
• Google Analytics and Tag Manager — site usage, as described above.

The session ledger spreadsheet is shared with nobody. Not one additional viewer or editor: it is reachable only by my own account.

I do not sell your data and I do not share it with anyone beyond the processors above, except where I am legally required to.

How long it is kept

• Billing records — invoices, payments, and the ledger rows behind them — for as long as tax and accounting rules require, which in practice means several years.
• Calendar events and session records — for the length of our working relationship, and beyond that where they carry billing information covered above.
• Sign-in links — minutes. They expire and are single-use.
• Analytics — for Google Analytics' configured retention period.
• Contact form messages and email — until they are no longer needed.

Your choices

You can ask me what I hold about you, ask me to correct it, or ask me to delete it. Deletion can't extend to records I am required to keep for tax and accounting, or to Stripe's own record of payments you have made — but everything outside that can go.

To make any of those requests, or to ask anything about this policy, usethe contact form.

Children

This service is not directed at anyone under 18, and I don't knowingly collect their data.

Changes to this policy

If what the system stores changes, this page changes with it and the date at the top is updated.