Privacy

Who is responsible for your data

ANDERSSEN, a sole proprietorship (enkeltpersonforetak) registered in Norway, organisation number 936 664 792, runs The Leverage Club and is the data controller for everything described here. In this policy "we" means ANDERSSEN and "you" means the person using the site or holding an account.

This policy covers theleverageclub.ai, the member area and the emails we send. It follows the EU General Data Protection Regulation (GDPR) as it applies in Norway through the personopplysningsloven. We apply the same standard to every member, wherever you live.

What we collect

Account

Email address, display name, password (stored only as a hash by Supabase Auth; we can't read it) and sign-in timestamps. From you, when you sign up and log in.

Membership and billing

Membership status, seat number, plan (monthly or annual), the price you joined at, when the current period ends, and Stripe's customer and subscription ids. Card numbers, expiry dates and billing addresses are collected by Stripe on Stripe's pages and stay with Stripe. From the join flow, where we pass Stripe your email address and account id so the payment can be matched to you, and from verified provider payment facts. Purchase records include the offered price and interval, exact accepted Terms edition, separate Terms and immediate-start selections, server timestamps, verified totals, renewal and refund facts, and the immutable contract confirmation. We retain the verified recipient and confirmation-delivery status separately from optional notices and tracking choices. These records support the contract, account recovery and accounting.

Learning

Lessons you've completed, notes you write on lessons, your class preference and display mode, private mission checklists and evidence, and your points and level. Mission evidence is visible only to you through the member interface; administrators may access stored data where necessary to operate the service or handle your requests. From what you do in the classroom.

Community

Posts, comments, helpful marks, saves, and whether you're online while you have the member area open. From what you do in Community and in the member area.

Member profile

Optional location text, what you're building and your chosen tracks, supplied by you for your member card. This is profile text, not GPS tracking or a member map.

Private communications

Messages between your account and the founder, sender and conversation references, timestamps and internal read markers for each recipient. We also store your activity notifications, their read state, and separate message-email and discussion-email preferences. Both email preferences default off.

Email delivery operations

Queued optional notices, recipient addresses and prepared email content, delivery status, attempt times, provider acceptance references, suppression records and operator action records. Minimal identifiers prevent duplicate sends. Optional notification emails contain a generic summary and an account link, not private message text.

Live calls

If you join a live call, your display name, your voice and video (if you turn them on) and what you say or type are in the recording, which is posted inside the club for members. From you, when you join a call.

Technical

IP address, browser (user agent) and request logs, kept by our hosting and database providers for security. From your browser, automatically.

Browser consent

Independent analytics and marketing choices, policy version, action, random request and receipt identifiers, and timestamps. The receipt body excludes email, account ID, browsing history and raw page URLs or referrers. The server and hosting provider still receive connection metadata when handling requests. A separate consent session remembers permission or refusal and, with current marketing consent, can associate an owned checkout with that permission.

Optional advertising measurement

After recorded marketing consent and verified activation, reviewed public-page events can go to Meta. Server events cover owned checkout starts, verified initial purchases, including the actual amount and currency, and a single free sign-up event when a confirmed free account first enters the club. Matching uses the normalized SHA-256 hash of your verified checkout or account email, bounded request browser information, and optional validated Meta click/browser identifiers (_fbc and _fbp). Hashed email is pseudonymous, not anonymous, and may be matched by Meta. We do not add names, phone numbers, addresses, card details, client IP addresses or private content to server advertising events. Direct browser connections to Meta necessarily reveal connection metadata, including IP addresses. No browser email matching, renewal conversions or historical imports are included.

To have a free account you need to give us an email address and confirm it, then choose a password; to be a member you also need to pay through Stripe. Without those we can't create the account or the membership. Profile details, notes, posts, comments, helpful marks, private messages, optional email alerts and joining calls are optional.

Your browser's time zone is used to show call times in your local time; it's read on the spot and not stored. We do not collect GPS location, contacts, device fingerprints or behavioural profiles. You can choose to write a location on your member card.

What we use it for, and the legal basis

Where we rely on legitimate interests, we've weighed them against yours and kept the use to what a member would expect. You can object; see Your rights below. We don't make automated decisions about you that have legal or similarly significant effects.

What other members can see

The club is a community, so some of your data is visible to other members by design:

• Your display name and chosen class, to other members, and your points and level wherever the club shows who did something.
• Your posts, comments and helpful marks in Community.
• The location, building description and tracks you choose for your member card.
• That someone is online: while you have the member area open, your account id is in the presence channel and other members see a count of members online, not your name.
• Your name, voice and video in a call recording, if you join a call. If your camera or microphone is on, other members on the call see and hear you, and you appear in the recording.

Private conversations are between your account and the founder; other members cannot read them. The founder can read and reply to these conversations. Read markers and notification read states are internal to each recipient, not read receipts shown to the other participant. Your notifications and email preferences are private to your account in the member interface. The founder can see operational delivery counts and statuses; these do not prove that an email reached your inbox.

Your email address, billing details, lesson progress and lesson notes are never shown to other members. The founder can see what's needed to run the club, including your email and membership status, and, because the founder runs the database, could technically open your lesson notes, though we don't as a matter of course; but never your password or your card.

Cookies, local storage and trackers

Meta configured for reviewed production public pages, subject to separate consent and clean-document checks. This does not establish server conversion delivery or provider reception. Local, editor and sample measurement stays inert. Cookie settings let you accept, reject or choose these purposes independently, and withdraw later. Rejecting optional purposes does not block signup, payment, learning or support. Global Privacy Control suppresses marketing without enabling analytics. Cookie settings

Necessary local storage includes your sign-in session, display and learning preferences, and the consent-owned key family: tlc.consent.v1 and keys under tlc.consent.v1. for receipts, retries and revocation evidence. Your browser choice lasts 90 days. Superseded consent evidence is cleaned in bounded batches while the site is active; unrelated storage is left alone. Sign-out clears the sign-in session; cookie choices are independent of your account. A separate Secure, HttpOnly consent capability cookie starts denied and lasts at most 90 days. With marketing consent it supports the checkout association described above; the receipt body itself does not contain account identity.

YouTube, Vimeo and Loom players contact the provider only after you choose “Load this video”. The provider then receives your IP address, browser details and this site's origin, and may use cookies under its own policy. The iframe's referrer policy sends the origin without a private lesson path or query. Loading a video does not grant advertising permission. A new lesson requires a new request. Fonts are self-hosted. Stripe's checkout and billing portal run on Stripe's pages under its cookies and privacy policy. See Cookies for retention, provider activation gates and withdrawal limits.

Emails we send

Supabase Auth creates authentication emails, including sign-up confirmations, invitations, sign-in links, email changes, password resets and verification codes. Resend transports these through our configured SMTP service. Receipts and billing notices come from Stripe. These account and billing emails are separate from optional alerts.

Message emails and discussion emails have separate preferences, both off by default. Optional dispatch is currently paused. When enabled, Resend will deliver eligible notices from The Leverage Club <hello@theleverageclub.ai>, with replies directed to support@theleverageclub.ai. These notices contain a generic summary and a link to your account, where sign-in is required, never the private message text. You can switch either preference off in your account. This is not newsletter consent. Lesson discussions and automated discussion or billing-event notices are not part of this release.

Google Workspace hosts our hello, support, marius and privacy mailboxes at theleverageclub.ai. Email replies go to those mailboxes and do not automatically appear in your club inbox. To continue a private club conversation there, use your account's Messages page.

We don't currently send marketing emails. If we start, we'll ask for your consent first, every message will have an unsubscribe link, and withdrawing consent stops them without affecting anything else.

Who handles your data for us

Supabase (Supabase Inc., US)

Database, authentication, private communications, consent receipts and delivery records, and realtime updates for Community and presence. Creates authentication emails for transport by Resend. Project hosted in the EU (AWS eu-west-1, Ireland); Supabase Inc. is a US company. Account-specific processing terms and transfer safeguards remain to be verified.

Resend (Plus Five Five, Inc., US)

Transports authentication emails and, once dispatch is enabled, optional notification emails. Processes recipient addresses, email content and delivery metadata. Authentication emails include their sign-in links or verification codes; optional notices exclude private message text. Resend discloses processing in the US in its privacy policy.

Stripe (Stripe Payments Europe Ltd, Ireland, and Stripe Inc., US)

Checkout, subscriptions, invoices, the billing portal and tax calculation. Ireland and the US.

Lovable ([Lovable legal entity, country]) hosting on Cloudflare's network (Cloudflare Inc., US)

Serves the website, runs the server side of the app and keeps request logs. A global network. Account-specific hosting terms, log retention and transfer safeguards remain to be verified.

[Live-call platform, legal entity, country]

Runs the weekly live calls; joining one is under that platform's terms and privacy policy.

[Video host, legal entity, country]

Hosts lesson videos and call recordings, which play inside the club through its embedded player.

Google Workspace

Hosts our business mailboxes, including general enquiries, member support and privacy requests. Processes the sender address, message content and attachments you email us.

Google Analytics, Google Ads and Meta — optional

Meta configured for reviewed production public pages, subject to separate consent and clean-document checks. This does not establish server conversion delivery or provider reception. Local, editor and sample measurement stays inert. Intended recipients of separately consented public-page analytics or advertising measurement after activation checks. Meta can also receive the server-confirmed conversions and pseudonymous matching data described above. Google destinations remain unconfigured. Meta's destination is dataset 2241123776677595. For EEA measurement, Meta Platforms Ireland Limited processes data under its Business Tools Terms and Data Processing Terms. Its European Data Transfer Addendum describes transfers to the United States. Meta may retain event data for up to two years; withdrawal here stops future sharing, not deletion of information already sent. We reviewed these terms and this dataset's settings on 15 September 2026. Automatic advanced matching, automatic events and extra page/product collection are off. Server conversion delivery has separate controls and has not been verified for launch. Signup conversions remain excluded. Consent alone does not activate these services, and browser configuration is not proof of provider reception.

Providers processing data on our behalf require appropriate data processing terms. Account-specific Resend and Google Workspace agreements and transfer safeguards remain to be verified; this provider list is not confirmation that those checks are complete. Stripe, or a video or call platform, may act as an independent controller for its own limited purposes, such as fraud prevention and legal obligations. We don't share your data with anyone else, unless the law requires it, we need to enforce our terms, or you ask us to.

Where your data goes

The club's database, including your account, progress, notes, posts and private conversations, is in the EU, in Supabase's Ireland region. Email processing is separate: Resend discloses US processing, and Google Workspace's data processing terms allow processing where Google or its subprocessors have facilities, subject to those terms. Stripe, our hosting provider, the live-call platform and the video host may also process data in the United States. Transfers outside the EEA require an applicable legal safeguard, such as an adequacy decision or standard contractual clauses. The safeguards and settings for our Resend and Workspace accounts have not yet been verified; we do not claim that all email data stays in the EU. Contact us for the current transfer details.

How long we keep it

Account, membership, learning and community data

While your account exists, then deleted within 30 days of a deletion request.

Private conversations, read markers, notifications and preferences

While your account exists, including after paid membership ends. The account deletion process removes conversations owned by your account and their messages and read markers, together with your recipient notifications and preferences. Where another account owns a conversation, deleting a sender account can remove the sender link without deleting that conversation. A remaining notification may show that its source is no longer available.

Optional email payloads and delivery attempts

Our cleanup command removes prepared and frozen email payloads from finished delivery records once 30 days have passed since the first attempt, and attempt records once 90 days have passed since each attempt began. It does not delete private conversations. Scheduled cleanup is not enabled yet: these are cleanup thresholds, not a claim that automatic deletion is already running. Until scheduling is enabled, cleanup requires an operator to run the command.

Limited operational records

Minimal delivery identifiers, status, timestamps and attempt counts remain after payload cleanup to prevent duplicate sends and reconcile failures. Suppression and operator action records also have no automatic expiry in this release. Account and notification deletion removes linked records where deletion rules apply; remaining operational records are reviewed through the deletion-request process. These limits describe our database, not retention in Resend or Workspace.

Posts and comments

May be kept in anonymised form, with your name removed and no link back to you, so that threads other members are part of stay readable.

Call recordings

While the recording is in the club library. Ask us if you want your contribution cut.

Purchase, contract and accounting records

We generally keep primary accounting evidence for five years after the relevant financial year ends, and secondary accounting evidence for three years and six months after that year ends. An agreement needed to substantiate an invoice is kept with the primary evidence. Contracts needed to administer an ongoing subscription remain available while it runs. A specific legal obligation, dispute or audit may require selected records to be kept longer; this does not extend retention of every account field. Required evidence can remain after account deletion, including purchase confirmations and payment records. Retention, holds and deletion requests are reviewed manually, with a monthly review of due records. No automatic financial-record purge is running. Removing expired financial records requires a scoped maintenance review to protect linked accounting evidence and check any applicable holds. Contact us about access to or deletion of your records.

Technical logs

Provider-specific log retention has not yet been verified; contact us for current details.

Browser choices and consent receipts

Browser choices last 90 days. First-party receipts become eligible for cleanup after 180 days. Consent receipt cleanup is not scheduled; eligibility does not promise deletion on that day. An operator must run and verify cleanup. Receipts are held by us through our database provider, separately from account records. Unverified optional vendor retention and transfer settings must be resolved before activation.

Optional marketing sessions and conversion records

Marketing permission lasts at most 90 days. Revocation or observed expiry suppresses undelivered events and clears matching identifiers and checkout associations. Pending events are limited to 24 hours. Completed or terminal events retain only operational identifiers and status, eligible for cleanup after 90 days. No marketing cleanup schedule has been verified; eligibility is not a promise of deletion that day. Withdrawal cannot recall an event already sent or a request already in flight, or delete a provider's existing records. If the service is unreachable, local refusal takes effect immediately but server revocation requires a successful request; retry through Cookie settings. Contact us about provider data or deletion.

Email with us

As long as we need it to deal with the matter and to show that we did.

How we protect it

Data travels over HTTPS. Passwords are hashed by Supabase Auth and we never see them. Card details are collected and stored by Stripe and never reach our systems. Access to the database is limited to the founder, to the app itself and to Lovable, the development platform the site is built and hosted on, and the database enforces per-account rules so that members reach only their own data and the community content meant to be shared.

No system is perfectly secure. If we discover a breach affecting your data, we'll tell you and the supervisory authority as the law requires.

Your rights

Under the GDPR you can:

• Access: ask what we hold about you and get a copy.
• Rectification: have anything wrong corrected.
• Erasure: have your account and data deleted; see the next section.
• Restriction: ask us to pause processing while a disagreement is sorted out.
• Portability: get the data you gave us in a machine-readable format.
• Objection: object to processing based on legitimate interests, and to direct marketing at any time.
• Withdrawal of consent: for anything based on consent, such as marketing emails, at any time. Withdrawing doesn't affect what happened before.

Send requests to privacy@theleverageclub.ai from the address on your account. We may ask you to confirm your identity before acting, usually by replying from that address. We answer within a month; if a request is complex we may take longer, and we'll tell you.

If you're unhappy with how we've handled your data, you can complain to Datatilsynet, the Norwegian data protection authority, or to the supervisory authority where you live. We'd rather you told us first, so we can fix it.

Deleting your account

There is no self-service delete button yet. Send a deletion request to privacy@theleverageclub.ai from the address on your account. Before we delete the account we cancel any active Stripe subscription, so nothing more is charged. Then the founder deletes the account, which removes your profile, lesson progress, notes, helpful marks and points. Your posts and comments are anonymised or deleted. Our accounting records and required purchase evidence may be retained separately under applicable obligations, as described in the retention section. Stripe keeps its own invoice history.

Your private inbox and its messages and read markers are removed when the founder deletes the account that owns it. Your recipient notifications and preferences are also removed. This is a request handled by the founder, not immediate automatic deletion. Other accounts' conversations, limited operational records and email correspondence may remain as described in How long we keep it; deletion is not a promise that every record in every provider disappears at once.

Deleting your account ends your membership, and there's no refund for the remaining period. If you have paid-for time left, cancel first and ask for deletion when it runs out.

Under-18s

The club is for adults. We don't knowingly hold data about anyone under 18, and we delete the account of any minor we discover. If you think a minor has an account, tell us.

Changes to this document

We update this policy when the club, our providers or the law change. Small changes take effect when we publish them. If a change affects how we use your data in a way you wouldn't expect, we'll email members before it applies, and where a new use needs your consent we'll ask for it rather than assume it. The version and effective date at the top tell you which one you're reading; the Terms describe the membership itself.

Contact

ANDERSSEN, Nedre Åsvei 36, 1341 Slependen, Norway. Organisation number 936 664 792.

Privacy and data requests: privacy@theleverageclub.ai.