Privacy Policy
Last updated: October 25, 2026
Who we are
withclaude is an independent project run by Phil Rivard, based in Quebec, Canada. If you have questions about this policy or your data, email .
What we collect and why
On the course form (“Save my spot”)
| Data | Why | Basis |
|---|---|---|
| First name, last name and email | To reply to you, take your payment if you pay now, send updates, and enroll you | Your consent (form submission) |
| Your answer to “What are you looking to get out of a course like this?” (optional) | To shape the class around the people who sign up | Your consent (form submission) |
| Whether you ask for a late spot after registration has closed (I approve each request by hand) | To know whether to send you a payment link or only updates | Your consent (form submission) |
| The language of the page you signed up on (English or French) | To send you emails in that language | Your consent (form submission) |
| Newsletter consent (the box you tick) | To keep a record that you agreed to receive the newsletter | Your consent (form submission) |
| How you found us: the referring page, plus the UTM source, UTM medium and UTM campaign tags on the link | To understand which channels bring sign-ups | Your consent (form submission) |
On the advisory form
| Data | Why | Basis |
|---|---|---|
| Name and email | To contact you about your application | Your consent (form submission) |
| Your answers (3 questions) and the time you submitted | To evaluate fit for the program | Your consent (form submission) |
| Approximate location (country, region, city) | To understand where interest comes from | Your consent (form submission) |
| Newsletter consent (the box you tick) | To keep a record that you agreed to receive the newsletter | Your consent (form submission) |
The advisory form works out your location from your IP address when you submit. We store the city, region and country, not the IP address itself. All three forms send your IP address to Cloudflare Turnstile, which checks that you are not a bot. Until you send the setup questions, your answers are saved only in your own browser. We don't receive them before you send.
On the setup questions and participant agreement (enrolled students only)
| Data | Why | Basis |
|---|---|---|
| Your computer (personal or work, its system, and whether installs need IT's OK), the language your apps run in, your Claude plan, which accounts you already have (Claude, Claude API, GitHub, ElevenLabs), your starter build pick, the tools you plan to connect, and anything else you tell us | To prepare setup week and fit the class to your setup | Your consent (form submission) |
| Your answers to the participant agreement (the recordings, and the optional promotion release), the version you saw and when you answered | To keep a record of what you agreed to | Your consent (the boxes you tick) |
If you join the class
| Data | Why | Basis |
|---|---|---|
| Card details and billing address for tax, which Stripe collects when you pay (we never see your full card number) | To take your payment | Needed to take your payment |
| Payment status, payment date and the Stripe session reference, which we keep in Airtable | To confirm that you paid and to enroll you | Needed to take your payment |
| Every session is recorded with Zoom (video, plus a separate audio file for each participant) and Fathom (its own recording and notes), and transcribed with ElevenLabs: what you say and show in the session, including anything on screen | So the cohort and Phil Rivard can watch the recordings and read the transcripts | Needed to run the class sessions |
| The questions you ask Zoom AI Companion about a session, the notes you take with its My Notes feature, and the notes Zoom's AI writes there from the transcript | So you can ask about what was said in a session and keep your own notes of it | Needed to run the class sessions |
| The AI chapter summaries Zoom makes of each recording (the recording highlights) | So you can find the part of a session you need | Needed to run the class sessions |
| The participation statistics Zoom AI Companion shows the host for each participant (Meeting Coach) | So Phil Rivard can see how each participant takes part in a session | Needed to run the class sessions |
| What is shared on screen and the meeting chat messages, which Zoom AI Companion uses as input for its features | So its answers, notes and summaries can draw on what was shown and typed in a session | Needed to run the class sessions |
| Your Slack profile, and the messages and files you post in the cohort channel | To run the cohort community | Needed to run the cohort channel |
On every page
| Data | Why | Basis |
|---|---|---|
| Page views (anonymous) | To understand site traffic | Not applicable: aggregate, cookieless page-view counts; no personal information is retained |
Your own data stays yours
In the class you connect Claude to your own inbox, calendar, notes and meeting transcripts. You authorize each connection yourself, from your own accounts. What you connect stays in your accounts: we have no access to those connections and receive no copy. Phil Rivard sees it only if you show it, for example when you share your screen in a session or post in Slack. Anything shared on screen ends up in the session recording, so close what you don't want the cohort to see. What Anthropic and your other providers do with your data falls under your agreement with them, not this page.
This policy does not let us use a participant's name, face, screenshots or photos publicly. That needs your yes to the optional promotion release in the participant agreement.
The newsletter
Both forms have a box you tick to agree to receive the withclaude newsletter. It is sent by withclaude (Phil Rivard) and carries news of the live cohort or the cofounder experiment. You can ask us to stop at any time, at the address in the Contact section. We will name the service that sends the newsletter on this page before the first send.
What we don't do
- We never sell your data to anyone.
- We don't run ads or share data with advertisers.
- We don't use your data for AI model training.
- We don't track you across other websites.
Who has access to your data
Only Phil Rivard reviews form submissions and payment records. Your cohort can see the session recordings, the transcripts and the cohort Slack channel. The sessions also use three Zoom AI features, which work from the session transcript: meeting questions, where a participant asks about what was said; My Notes, where a participant takes notes and Zoom's AI also writes notes of its own; and recording highlights, which split each recording into chapters with a short AI summary. Two more are on: Meeting Coach, which shows Phil Rivard, as host, participation statistics for each participant, and Catch up with AI, which gives a participant who joins late a summary of what they missed. Zoom AI also uses what is shared on screen and the meeting chat messages as input for its features. Your notes are yours, and Phil Rivard, as the Zoom account administrator, can view them in Zoom's admin portal. AI answers can be wrong, so check them against the recording. Your data is stored using the following services:
- Airtable (United States) — stores form submissions, newsletter consent and payment status
- Vercel (United States) — hosts the website and processes form submissions
- Vercel Analytics (United States) — anonymous, aggregate page view counting without third-party cookies
- Cloudflare Turnstile — bot protection on the forms, no tracking cookies
- Stripe — processes your payment
- Slack — hosts the cohort channel
- Zoom (United States) — hosts and records the sessions, with a separate audio file for each participant; the recordings are stored in Zoom's cloud. Zoom AI Companion, Zoom's AI assistant, runs in the sessions and may use AI models from Zoom and its providers, so your session data may be processed in the United States. Zoom's terms say it does not use meeting content to train its own or third parties' AI models
- Fathom (United States) — its notetaker joins the sessions and keeps its own recording and notes
- ElevenLabs (United States) — transcribes the recordings
- Google Drive — stores course material, and may hold copies of the session recordings and transcripts shared with the cohort
- AWS (Canada, Montreal) — stores the session video and audio recordings in a private, encrypted archive
- GitHub (United States) — stores the session transcripts and the course notes in a private repository
Some of these services are based in the United States, so your data may be transferred outside of Canada or the European Union. By submitting a form or joining the class, you acknowledge this transfer.
Cookies
Our analytics, Vercel Web Analytics, counts page views without third-party cookies. Instead of a cookie, a visit is identified by a hash created from the incoming request, and that visitor session is automatically discarded after 24 hours. It collects no personal identifiers that track you across different applications or websites. Page views are recorded anonymously without being tied to any individual or IP address, and the data is used for aggregated statistics only. Because of that, it loads for every visitor, with no banner to accept.
Cloudflare Turnstile may set a functional cookie for its bot check. It is used only to protect the form from bots, never for tracking.
Your rights
Regardless of where you live, you have the right to:
- Access — request a copy of your data
- Correct — fix any inaccurate information
- Delete — ask us to remove your data (recordings and transcripts follow the rule in Data retention)
- Withdraw consent — you can ask us to stop processing at any time
To exercise any of these rights, email . We'll respond within 30 days.
Data retention
- Newsletter list (everyone who submits either form): the data you gave on the form stays until you ask us to stop or to delete it. After you ask us to stop, only your email address stays, on a do-not-contact list so that you are not added again.
- Course form sign-ups: if you enroll, we keep your contact and enrolment data and your setup answers for 12 months after the cohort ends, and your agreement record for as long as we use anything it covers. If you also subscribed to the newsletter, the data you gave on the form follows the newsletter rule above until you ask us to stop, and only your email address follows it after that.
- Advisory applications: up to 12 months after the program concludes.
- Payment records: the status, date and Stripe session reference we keep in Airtable are kept for 6 years from the end of the tax year they relate to, as Canada Revenue Agency record-keeping rules require. Stripe keeps its own payment records under its own rules.
- Recordings and transcripts: available while the community runs, with 30 days' notice before it closes. We don't delete a recording or transcript because one person asks, since it holds other participants' voices and words. We look at each request on its own and, where we can, offer to cut your own contributions. We reply in writing within 30 days, with our reasons and where you can complain or ask for a review: the Commission d'accès à l'information du Québec if you live in Quebec, or the Office of the Privacy Commissioner of Canada if you live anywhere else.
- Slack: the messages and files you post stay in the cohort channel, which is archived when the community closes.
For data not covered above, if you request deletion, we'll remove it within 30 days.
Security
All data is transmitted over HTTPS. Access to the form database is restricted to Phil Rivard. We don't store passwords: Slack handles its own sign-in.
Changes to this policy
If we make significant changes, we'll update the date at the top of this page. For a simple landing page, that's the most honest approach — no one reads update emails about privacy policies.
Contact
Phil Rivard
Quebec, Canada