Privacy policy
Updated 7 October 2026. This notice covers the public website, optional email list, member accounts, lessons, eligible member chats, call bookings and membership billing when checkout is available. Public registration and new membership purchases are currently closed. This notice explains the prepared paid service without opening it. Group chats do not offer posts, comments or photo uploads.
Who is responsible
EwenFoundry Limited, registered in Scotland (SC732552), at 5 South Charlotte Street, Edinburgh, Scotland, EH2 4AN, is responsible for this website and member service. For privacy questions or rights requests, email daniel@ewenfoundry.com. We may ask for proportionate proof of identity before disclosing or changing account data; you can contact us even if you cannot access the account email.
What we use now
Public website and enquiries. Our hosting and email providers process IP addresses, request times, browser information, security events and delivery records to operate the site, answer enquiries and prevent abuse. We rely on our legitimate interests in a reliable, secure service and in responding to you. We do not use advertising pixels or optional analytics scripts on these pages; fonts and images are served from our website.
Email-list subscribers. The optional public list uses single opt-in with a separate marketing-consent box. Klaviyo holds email addresses, signup source, consent or confirmation records and suppression information for subscribers. We rely on their recorded consent for marketing and keep a minimal record of unsubscribes so we do not email them again. Joining the list does not create a learning account or paid membership. Use the unsubscribe link in a marketing email or contact us to stop marketing.
Member accounts and learning. We use your email address, account ID, verification and sign-in records, unique username, age-16-or-over declaration, accepted account terms, access permissions, chosen profile details, lesson openings and progress to provide your account and learning service. Your username is visible to other eligible members in group chats; use a username that does not reveal your real name if you prefer. We do not require a full date of birth for this declaration. Account email, authentication and required declarations are necessary for registration; without them we cannot create an account. Signing in or accepting an invitation does not subscribe you to marketing.
We rely on the contract to provide the requested account, lessons and paid services, and on legitimate interests in securing and supporting the service, evaluating the private beta and preventing abuse. We do not use beta learning records for employment assessment. Feedback and bug reports include what you submit and the associated account and technical context; authorised owner support uses them to investigate and improve the service. Avoid unnecessary sensitive information in reports or chats.
Paid call bookings
For standalone call purchases, we use your account identifier, email, phone number, topic, questions, availability, accepted terms version, payment references and booking messages to fulfil your contract and arrange the call. Daniel sees these details in the private owner inbox so he can prepare, contact you and manage your booking. Other members and group chats cannot see your private booking information. Please avoid unnecessary sensitive information or another person's private details in your questions.
Stripe processes your payment details and returns payment identifiers, amounts, payment status and any refund or dispute events. We do not receive your full card number. We rely on the contract to deliver the booking, legal obligations for required accounting records and legitimate interests in fraud prevention and resolving complaints or disputes. Buying a call does not subscribe you to marketing.
We retain booking and message information while needed to arrange and fulfil the call and resolve related support or disputes. Relevant payment, tax and accounting records are retained for applicable legal requirements. Some records may need to be retained to establish or defend legal claims; we assess deletion requests against those needs. Contact daniel@ewenfoundry.com for a copy, correction or deletion request, including if you can no longer sign in. There is no automatic deletion promise on a fixed date.
Membership purchases and contract records
Accounts and membership purchases are for people aged 16 or over. Where checkout is available, Stripe handles card and billing details. We receive customer, subscription, invoice and payment identifiers, plan, price, currency, discounts, payment status, refunds and disputes. We do not receive your full card number. These records let us collect payment, grant or stop paid access, provide billing support and fulfil the membership contract. We rely on the contract for these purposes, legal obligations for accounting, and legitimate interests in preventing fraud and resolving disputes.
We retain the exact offer and terms accepted, consent and acknowledgement choices, their version and time, verified first-payment references, and the confirmation supplied to you. A later renewal does not replace the original contract record. If you request cancellation, we retain the original request, received time, acknowledgement, related payment references and the review or refund outcome. These records evidence the contract, consumer-rights requests and our response; a received request or pending review is not proof that a refund has completed. Digital-content supply consent, service-start choices and marketing consent have separate purposes. Buying does not add you to an email-marketing list.
Founder onboarding and any booked HQ visit use your account, booking and attendance details to provide those benefits; HQ booking requires a separate 18-or-over declaration. Only the information needed to arrange and record the visit is used. A membership purchase does not itself book an event. For any separate mentoring or fitness-coaching service, its actual booking and any health-information collection must be explained before that information is requested; do not put medical details into ordinary member chats.
Optional Google sign-in and essential cookies
If you choose Google sign-in, Google supplies our authentication provider, Supabase, with your Google account identifier, verified email and available profile details such as name and profile picture. We use these to authenticate you. Supabase may link Google to an existing account with the same verified email; this does not grant extra permissions. We do not request Gmail, Drive, contacts or your Google password. Google's own privacy policy also applies to its sign-in service.
The member website uses an essential session cookie with a random reference, not a password or Google token. An active session lasts up to eight hours and can end sooner after inactivity. If you choose the optional remembered-device setting, a separate security cookie can resume a session on that device for up to seven days unless you sign out or revoke your sessions. A separate short-lived cookie binds a Google sign-in attempt to the browser for up to ten minutes. These cookies support authentication and security, not advertising. Google and Supabase may set their own sign-in security cookies on their pages.
Chats, owner support and voice notes
Eligible members can see group-chat messages and the usernames attached to them. A group is visible to its eligible members, so do not share another person’s private information without permission. Private Daniel conversations, call bookings and replies are visible to the sender and authorised owner support, not other members. We use message content, sender/account identifiers, time and delivery or quota records to provide the requested service, support members and prevent misuse.
Daniel uses a private local owner dashboard to read and reply to conversations, inspect relevant account email, membership and course information, and handle bug reports, bookings and cancellation requests. A normal website account does not receive access to the owner inbox. Authorised support may also inspect group chats to operate and moderate them.
The owner can send voice notes in eligible private Daniel conversations. Audio and associated message, recipient, file and delivery records are stored privately and served to the intended recipient and authorised owner. Members currently receive playback only; they cannot upload voice notes or files to these chats. We do not transcribe the audio or use it for voice identification. A recipient can still copy audio they receive. Voice notes follow the same support purpose and retention review as their conversation.
Optional marketing and analytics
Account, security, payment, confirmation and cancellation messages are service messages. Any marketing choice is separate, optional and unticked, and can be withdrawn. Terms acceptance, account creation and payment are not marketing consent.
Optional first-party engagement analytics is not a condition of using the service. Where an optional analytics control is offered, it must explain the information collected, retention and withdrawal before collection starts. Optional engagement collection requires your choice; declining it must not prevent account access or purchase. Required authentication, security and provider traffic records are distinct from optional engagement tracking.
Who handles data and where
Cloudflare hosts and protects the website, member sessions and server-side billing and contract processing. Supabase provides authentication, the member database and private voice-note storage; the member database is in its London region. Resend sends account confirmation, invitation, password-reset, contract-confirmation and cancellation-acknowledgement emails and supplies delivery records. Google Workspace handles our contact email; Google supplies optional sign-in; Klaviyo manages the optional marketing list. Stripe handles payments and related subscription, invoice, refund and dispute information. Stripe also acts as a controller for certain purposes, including its own fraud prevention and legal obligations; see Stripe’s privacy policy.
Providers may process information outside the UK, including in the United States, even where the primary database is in London. Their standard terms describe data-processing and international-transfer safeguards, including applicable standard contractual clauses and UK addenda for restricted transfers. You can read the Cloudflare, Supabase, Resend and Stripe processing terms, or contact us for information or a copy of the safeguards applicable to your data. A provider’s published terms do not mean that every activity takes place in the UK.
How long we keep information
Accounts and progress. We keep these while needed to provide your account and lessons. We assess continued need when an account is closed, access ends or you make a privacy request, taking account of outstanding support, security incidents and specific legal duties. Ending a subscription, expiring access or signing out does not itself erase an account.
Chats, voice notes, feedback and bookings. We review these when the related service, enquiry, booking or support case ends and on an erasure request. Retention depends on whether the information is still needed to deliver the service or resolve a specific outstanding complaint, dispute or security incident. We do not treat an accounting duty as a reason to keep every chat or audio file for six years. Unnecessary personal content should be deleted, redacted or anonymised after the review; a limited case-specific legal hold may require some evidence to remain.
Accounting and contract evidence. Company accounting records, including relevant invoices, payments and refunds, are kept for six years from the end of the last company financial year they relate to, or longer where the law requires, such as an HMRC compliance check. We keep the minimum linked order, accepted terms, consent, supply confirmation and cancellation or refund evidence needed to fulfil consumer-law duties, explain the transaction or establish or defend a specific claim. These purposes do not require keeping unrelated conversation content indefinitely. Records kept only for legal obligations or a dispute are restricted to that purpose.
Marketing, security and backups. Marketing records are kept while subscribed, with minimal suppression and consent evidence after withdrawal to honour it and answer compliance questions. Security records are kept only while needed to investigate abuse, protect accounts or address a specific incident. Provider logs, email delivery copies and backups may remain for their configured recovery or legal periods after removal from the active service; we do not promise immediate physical deletion of every backup or a fixed provider period that has not been verified.
Privacy and deletion requests are handled manually through daniel@ewenfoundry.com. We assess each category, explain any lawful refusal or retained evidence, and distinguish removal from the active service from outstanding provider or backup handling. There is no automatic account, message or voice-note deletion schedule. You can request help even if you cannot sign in.
Your rights and changes
You can withdraw marketing consent or object to direct marketing at any time, including by using an unsubscribe link. Depending on the circumstances, you can ask to access, correct, erase, restrict or transfer your information, or object to processing based on legitimate interests. Withdrawing consent does not undo earlier lawful processing. Access checks use account, membership, verified-payment and security records to enforce the service rules. Contact Daniel if you want a person to review an account or billing problem.
You can complain to the Information Commissioner's Office; contacting us first is welcome but not required. We will review this notice and tell people before materially new uses of their data begin, including any new public registration, coaching-data collection, community upload features or advertising tracking.