Privacy Policy

Last updated: 25 July 2026

STAMNR is a confidence and wellbeing app for men. Because of what it does, the information you log in it is personal and often sensitive - it can concern your health and your sex life. We take that seriously, and this policy explains, in plain English, exactly what we collect, why, where it goes, and the control you have over it.

The short version:

• Your logs are private to your account. Nobody else using STAMNR can see them.
• We do not sell your data. We never have and we never will.
• There is no advertising in STAMNR, no ad SDKs, no third-party analytics or tracking tools, and no cross-app tracking.
• Sensitive logs (your check-ins, firmness readings and wellbeing answers) are processed only with your explicit consent, which you can withdraw at any time.
• You can delete your account and its data whenever you want.

STAMNR is a self-improvement and wellbeing app. It does not provide medical advice, diagnosis, or treatment, and it is not a medical device. Nothing in this policy changes that.

1. Who we are

STAMNR (the app and the website at stamnr.com) is operated by:

STAMNR (a sole trader; not currently a registered company)

Email: support@stamnr.com

For the purposes of UK data protection law (the UK GDPR and the Data Protection Act 2018) and, where it applies, the EU GDPR, the sole trader operating STAMNR is the data controller of the personal data described in this policy.

2. What this policy covers

This policy covers:

• The STAMNR mobile app (iOS bundle com.stamnr.app; Android package com.stamnr.app).
• The STAMNR website at stamnr.com.

It does not cover services you interact with directly under their own terms, such as Apple's App Store, Google's sign-in pages, or Apple Health, each of which has its own privacy policy.

3. The data we collect, why, and our lawful basis

We collect only what the app needs to work. For each category below we explain what it is, why we process it, and the lawful basis we rely on under Article 6 (and, for sensitive data, Article 9) of the UK GDPR and EU GDPR.

3.1 Account data

What: your email address, a display name if you set one, your sign-up date, and a random account identifier (a UUID) that keys your records. If you sign in with Google or Apple, we receive the basic profile your provider shares (email address and name; with Apple this may be a private relay email address if you choose to hide yours). Passwords are handled by our authentication provider (Supabase) and stored only in hashed form - we never see or store your plain password.

Why: to create and secure your account, sign you in, and let you recover access.

Lawful basis: performance of our contract with you (Article 6(1)(b)).

3.2 Self-reported wellbeing logs - sensitive data, handled with explicit consent

This is the heart of the app, and we name it plainly. If you choose to use these features, we collect and store, in your private account record:

• Daily check-ins: your self-rated sleep, energy and training, and related habit factors such as stress, anxiety, alcohol and nicotine derived from your answers.
• The daily questionnaire: answers about your day. These can include:
• whether a sexual opportunity arose and its context, and how an attempt went;
• self-rated erection hardness, and firmness readings you log (a 0 to 100 self-rating);
• morning and spontaneous erections, and desire;
• mood, performance anxiety, general stress, tiredness, and feeling unwell;
• alcohol and nicotine use;
• missed or changed medication, and whether you took an erection medication (a PDE5 inhibitor) and when.
• Onboarding answers: your quiz responses, confidence score, goals, and questions about when your difficulties started.
• Baseline details (optional): age, height, weight, waist measurement, whether you have been told you have certain conditions (such as diabetes, high blood pressure, high cholesterol or a heart condition), smoking status, family history of early heart disease, certain long-term medications, and your answers to the SHIM (IIEF-5) questionnaire, a standard self-assessment.
• Practice and progress records: practice sessions and their self-ratings (calmness and firmness), lessons completed, streaks, and programme progress.
• Journal entries: any free-text reflections you write against lessons.
• Stories you choose to submit (see section 3.3).

This information is data concerning health and data concerning your sex life - "special category" data under Article 9 of the UK GDPR and EU GDPR. We process it only with your explicit consent (Article 9(2)(a), together with Article 6(1)(a)), which you give when you choose to complete the onboarding questions and start logging. Every one of these inputs is optional: you can skip questions, skip days, and stop logging at any time.

You can withdraw this consent at any time by stopping logging, by deleting your account in Settings, or by emailing support@stamnr.com. Withdrawing consent does not affect the lawfulness of processing before you withdrew it. If you withdraw consent but keep your account, the logs you have already saved are retained only so you can still see your own history; you can have any or all of them erased at any time (see section 9).

Why we process it: to show you your own history, compute your Charge/Firmness readiness index (see section 5), surface which of your logged habits appears linked to your logged firmness, and adapt the programme to you. We use it for nothing else. It is never used for advertising and never shared with third parties for their own purposes.

3.3 Stories

You can submit a short written story about your experience. Stories are reviewed before anything is published, and approved stories are shown to other signed-in users without your name, email or account identifier attached. Because a story about your experience with STAMNR is likely to describe your health or sex life, we treat submitted stories as special category data processed with your explicit consent, which you give by choosing to submit. If you want a submitted story removed, email us at support@stamnr.com and we will remove it (see also section 9).

3.4 Apple Health data (optional, iOS only)

If a version of the app offers an Apple Health connection and you choose to grant it, STAMNR asks for read-only access to the following metrics recorded by your device:

• Sleep, and breathing during sleep: sleep duration and stages, respiratory rate, blood oxygen, sleep apnoea notifications, and sleeping wrist temperature.
• Activity and fitness: exercise time, workouts, steps, active energy, VO2 max, heart rate recovery, and walking heart rate.
• Heart: heart rate variability, resting heart rate, and heart-rhythm safety records (irregular-rhythm notifications, high heart rate notifications, AFib history, and ECG records).
• Wellbeing extras: mindfulness minutes, time in daylight, and Apple's state-of-mind log if you use those features.

STAMNR never writes anything to Apple Health.

How it is used and stored: the values derived from these readings - daily and recent summary values, and the heart-rhythm safety flags - are stored in your private account record on our database (see section 6 on Supabase) so the app can factor measured sleep, exercise, and a small heart-fitness signal (heart rate variability, resting heart rate, and VO2 max, compared only against your own baseline) into your readiness index and show you your own trends. Heart-rhythm safety notifications are used for one purpose only: to suggest, calmly, that you speak to a doctor. They are stored in your account record like the other values, but they are never fed into any score.

Your Apple Health data is used only to provide these features to you. It is never used for advertising or marketing, never used to build profiles for anyone else, never sold, and never shared with any third party for that third party's own purposes. The derived values are stored only with Supabase, our database processor (section 6), which holds them solely on our instructions to run the app for you - consistent with Apple's Health app rules, which forbid using Health data for advertising, data mining or disclosure to third parties for their own use. You can disconnect Apple Health at any time in your device's Health settings, and deleting your account deletes the stored values.

Lawful basis: your explicit consent (Article 9(2)(a) with Article 6(1)(a)), given when you grant Health access, withdrawable at any time as above.

3.5 Usage events (first-party telemetry)

The app records first-party usage events in our own database for two purposes: so we can tell whether core features actually work, and, if you use the Read feature (section 3.9), so your Read can reflect how you actually use the app. Examples: app opened, which screens you open, check-in saved or left partway, practice completed, kegel session completed, an in-the-moment session opened or completed, a library article opened and roughly how long you spent reading it, a story opened or bookmarked, the tier page opened, a missed day filled in, a journal entry written (we record that one was written and its length, never its text), lever reveal seen, paywall shown or converted, tour done or skipped. Event payloads are minimal; they never contain your log values, firmness readings or journal text. Events are linked to your account identifier and are visible only to us, never to other users.

No third-party analytics service receives these events - they go only to our own database. Because even the fact that you completed a practice says something about your use of a wellbeing app, we treat events that reflect your wellbeing activity as covered by the same explicit consent as your logs (section 3.2). For purely operational events (such as whether the intro tour was skipped), we rely on our legitimate interest in understanding and improving the app (Article 6(1)(f)), an interest we have balanced against your rights by keeping the events few, minimal and first-party only.

3.6 Subscription and purchase data

If you subscribe to STAMNR Premium, the purchase is made through Apple's App Store and managed through RevenueCat, our subscription-management provider:

• Apple processes your payment. We never see or store your full payment card details - Apple does not share them with us.
• RevenueCat receives your STAMNR account identifier (the UUID, not your email or name), your App Store transaction and receipt data, subscription status, and standard device and app metadata its software collects (such as app version and locale). We use this to know whether your subscription is active, to restore purchases, and to handle renewals and expirations.

Lawful basis: performance of our contract with you (Article 6(1)(b)) and, for transaction records, compliance with legal obligations (Article 6(1)(c)).

3.7 Data that stays on your device

Some data is stored only in the app's local storage on your phone and is not sent to our servers:

• your session tokens (which keep you signed in),
• an unsaved check-in draft (deleted when you save; stale drafts are pruned),
• your reminder time preference, rest-mode flag, daily-path preferences, tour-completed flag, and whether Apple Health is connected.

Saved story bookmarks are stored in your account record (so they survive a new phone), with a copy kept on the device.

Reminders are local notifications scheduled on your device. Most use fixed, generic wording ("Two minutes. Log your last 24 hours."). The optional personal note reminder carries a short line written from your own logs by the Read feature (section 3.9); every such line is screened before scheduling so it never contains health terms, scores, or anything a stranger glancing at your lock screen could connect to this app's subject. We do not use push notifications - no push token is collected or sent to any server.

3.8 App delivery and updates (Expo)

The app is built on Expo, and release builds check Expo's update service (EAS Update) at launch to fetch bug fixes. That check sends Expo your IP address, platform, app runtime version and a random installation identifier - not your account identity. Our password-reset and sign-in redirect pages are served from Expo hosting (stamnr.expo.app), where standard web-server access logs (including IP addresses) may apply.

Lawful basis: our legitimate interest in delivering a working, up-to-date app (Article 6(1)(f)).

3.9 Your Read (AI-written insights)

The Read feature writes you a short personal narrative - what your own recent logs and app use looked like, what stood out, and one thing worth focusing on - plus the optional personal-note reminder lines. It is written by an AI model (Claude, provided by Anthropic).

How it works: when a new Read is due, our server builds a compact summary of your recent data - your logged habits and outcomes, your practice activity, which library topics you read, aggregate usage events (section 3.5), and, only if you connect Apple Health, derived measured values - and sends that summary to Anthropic's API to generate the text. The result is stored in your account record and shown only to you.

What is deliberately kept out of that summary:

• your name, email address and account identifier - the summary is identity-stripped before it leaves our systems;
• all heart-rhythm and cardiac safety data from Apple Health - it is never sent to any AI model, ever;
• your journal text, unless you switch on "Let your Read use your journal" in Settings. That switch is off by default; with it off, no journal entry ever reaches the AI.

Anthropic processes the summary as our processor, does not use API data to train its models under its commercial API terms, and does not retain it beyond short-term operational handling. Generated text passes a filter on our server before it is stored, and it is education, never a diagnosis or a prediction.

Nothing is generated before you act: the first Read is only built when you explicitly tap to build it in the app, and the ongoing quiet updates that keep your Read and personal notes fresh run only after that first choice.

Lawful basis: your explicit consent to the processing of your wellbeing data (Article 9(2)(a), as in section 3.2), given when you choose to build your first Read; the journal toggle is a separate, additional consent you can withdraw at any time in Settings.

3.10 Website visitors (stamnr.com)

Our website is a static page. It sets no cookies, runs no analytics, and has no tracking of any kind. It makes one third-party request: your browser loads our typefaces from Google Fonts (fonts.googleapis.com and fonts.gstatic.com), which transmits your IP address to Google as part of the request. Our hosting provider may also keep standard server access logs. That is the whole list.

Lawful basis: our legitimate interest in operating a functioning website (Article 6(1)(f)).

4. What we do NOT do

• We do not sell your personal data, and we do not license or rent it to anyone.
• We do not show ads and we embed no advertising SDKs.
• We use no third-party analytics or tracking SDKs (no Google Analytics, no Meta pixel, no Amplitude, Mixpanel or similar) in the app or on the website.
• We do not track you across other apps or websites, and we do not participate in cross-app or cross-site advertising ecosystems.
• We currently use no crash-reporting service; crashes are handled inside the app and nothing leaves your device. If we ever add one, we will update this policy first.
• We never use your wellbeing logs or Apple Health data for advertising or marketing of any kind.

5. About the Charge/Firmness readiness index

The app shows you the Charge/Firmness readiness index. It is computed from the habits you log (things like sleep, stress, alcohol and training), from how things actually went when you choose to log that (only clean, unconfounded entries count), and, if you connect Apple Health, from measured values (section 3.4). It is not a prediction, probability or forecast of anything, it is not a diagnosis, and it is not medical information about you beyond what you yourself logged or connected. The same calculation applies to every user; we never re-weight it per person. We describe it here so you know exactly what is computed from your data and why.

6. Who we share data with (our processors)

We share personal data only with service providers who process it on our instructions to run STAMNR, under contracts that bind them to protect it. They are:

1. Supabase - our database, backend and authentication provider. All account data and app content described above is stored with Supabase, hosted on AWS in the eu-west-3 region (Paris, France, in the EU). 2. RevenueCat - subscription management, as described in section 3.6. Receives your account UUID and purchase data, not your email, name or logs. 3. Apple - App Store payment processing, and Sign in with Apple if you use it. Apple also enforces its own rules on us regarding Health data (section 3.4). 4. Google - only if you use Sign in with Google, in which case Google knows you signed in to STAMNR and shares your basic profile with our authentication provider. 5. Expo - app build, update delivery and web hosting, as described in section 3.8. 6. Anthropic - the AI provider that writes your Read (section 3.9). Receives only the identity-stripped summary described there (never your name, email, account identifier, cardiac data, or - unless you opt in - journal text), uses it solely to generate your Read, and does not train models on it under its commercial API terms.

We do not share your personal data with anyone else, except if we are legally required to (for example by a court order), or, should the business ever be sold or reorganised, with a successor who would remain bound by this policy (we would notify you first).

7. International transfers

Your app data is stored in the European Union (AWS eu-west-3, Paris). For users in the UK, transfers of personal data to the EU are covered by the UK's adequacy regulations for the EEA.

Some of our providers (RevenueCat, Apple, Google, Expo, Anthropic) are based in or operate from the United States, so limited data (as described in section 3) may be transferred there. Where that happens, we rely on recognised safeguards: the UK-US Data Bridge / EU-US Data Privacy Framework where the provider is certified, or standard contractual clauses with the UK Addendum or International Data Transfer Agreement. You can contact us for more detail on the safeguard applying to a specific provider.

8. How long we keep your data

We keep your data for as long as you have a STAMNR account, because the app's purpose is to show you your own history over time. We do not run automated expiry on your logs - they are yours to keep until you delete them.

When your account is deleted (section 9), your data is permanently deleted from our systems. Transaction records held by Apple and RevenueCat are retained by them as required for accounting and legal purposes under their own policies. Standard server logs held by our hosting providers expire on their normal schedules.

9. Deleting your account and your data

You can delete your account and its data at any time, directly in the app: Settings, then Delete account. This permanently deletes your account and the data held against it. Deletion is permanent and cannot be undone.

You can also ask us to delete your account, your submitted stories, or specific data by emailing support@stamnr.com from the email address on your account. We will act on verified requests within one month.

Two honest notes:

• Individual usage events (section 3.5) and submitted stories cannot currently be deleted one-by-one from inside the app. They are covered by account deletion, and we will delete a specific story on request by email.
• Deleting the app from your phone does not delete your account. Use the in-app deletion or email us.

10. Your rights (UK and EU/EEA)

Under the UK GDPR and EU GDPR you have the right to:

• Access: get a copy of the personal data we hold about you.
• Rectification: have inaccurate data corrected and incomplete data completed.
• Erasure: have your data deleted (see section 9).
• Restriction: ask us to limit how we process your data in certain circumstances.
• Portability: receive the data you provided to us in a structured, commonly used, machine-readable format, and have it transmitted to another controller where technically feasible.
• Object: object to processing based on our legitimate interests.
• Withdraw consent: at any time, for anything processed on the basis of consent, including all your wellbeing logs and Apple Health data - without affecting processing that happened before withdrawal.

We do not make any decisions about you based solely on automated processing that produce legal or similarly significant effects.

To exercise any right, email support@stamnr.com. We will respond within one month and will never charge you for a reasonable request. We may ask you to verify that you control the account first.

If you are unhappy with how we handle your data, you have the right to complain to the Information Commissioner's Office (ICO) in the UK: ico.org.uk, or 0303 123 1113. If you are in the EU/EEA, you can complain to your national data protection authority. We would appreciate the chance to resolve your concern first, but you do not have to give us one.

11. California and other US residents

If you are a California resident, the California Consumer Privacy Act (CCPA, as amended by the CPRA) gives you rights over your personal information. The categories of personal information we collect are those described in section 3: identifiers (email, account UUID), commercial information (subscription status), internet activity (first-party usage events), and sensitive personal information (the wellbeing logs described in section 3.2, which include health and sex-life information you choose to log).

• We do not sell personal information, and we do not "share" personal information for cross-context behavioural advertising. We never have. Because of this, there is no "sell or share" opt-out to offer - there is nothing to opt out of.
• We use sensitive personal information only to provide the services you request, so no separate limit-use right needs to be exercised.
• You have the right to know what we collect, the right to access it, the right to correct it, the right to delete it, and the right not to be discriminated against for exercising your rights.

Exercise these rights in the app (Settings, Delete account) or by emailing support@stamnr.com. We do not respond differently based on how a request arrives, and an authorised agent may act for you with proof of authorisation.

12. Users elsewhere

Wherever you are, the substance of this policy applies to you: your logs are private, processed with your consent, never sold, never used for advertising, and deletable at will. If your local law grants you additional rights over your personal data, contact us at support@stamnr.com and we will honour them to the extent they apply.

13. Age limit: 18 and over

STAMNR is for adults. You must be 18 or over to create an account. The app is not directed at children or teenagers, and we do not knowingly collect personal data from anyone under 18. If we learn an account belongs to someone under 18, we will delete it. If you believe someone under 18 is using STAMNR, please tell us at support@stamnr.com.

14. How we protect your data

• Owner-only access rules: every record in our database is protected by row-level security, so your data is readable and writable only by your own authenticated account. This is enforced at the database level, not just in the app.
• Encryption in transit: all traffic between the app and our servers uses TLS (HTTPS).
• Hashed passwords: handled by our authentication provider; we never store plain passwords.
• Minimal footprint: no third-party analytics, ad or tracking code means fewer places your data could go.

No system is perfectly secure, but if a breach ever affects your personal data in a way that puts your rights at risk, we will notify you and the relevant authority as the law requires.

15. Governing law

This policy, and any dispute about it, is governed by the law of England and Wales, and the courts of England and Wales have jurisdiction - without limiting any mandatory consumer or data protection rights you have where you live.

16. Changes to this policy

If we change this policy, we will update the date at the top and, for any material change (especially anything touching your wellbeing logs or new data sharing), tell you in the app before the change takes effect and, where the law requires it, ask for your consent again. Earlier versions will be available on request.

17. Contact us

Questions, requests, or concerns about your data:

STAMNR

Email: support@stamnr.com

We read everything, and we will reply like humans.