Privacy policy

Who to contact

HMMART operates HearmemanAI, including this website, PROmpt and the shared account experience. HMMART is responsible for the personal information described here. For privacy questions or requests, email hearmeman@hearmemanai.xyz.

Your shared account

Our account provider, Amazon Cognito, handles Google sign-in. Your sign-in email, password and recovery are managed by Google. We receive an account identifier, your email address, verification status and name. We do not receive your Google password. Your shared account connects PROmpt and LoRA Trainer without linking different people by matching email addresses.

Your profile includes a display name of up to 16 characters, an optional avatar and optional Discord and CivitAI handles. We resize avatars and strip image metadata. Profile handles remain private and unverified. Connecting Discord for paid support is a separate verification step. A verified contact email can receive account messages; changing it does not change your Google identity.

We store communication and analytics preferences, active-session information, verification and privacy requests. We use this information to provide the account features you request, protect access and honour your choices. You can browse public resources without an account.

PROmpt contributions and saved items

We store your starred prompts and packs, submitted images, prompt text, model and category, content declarations, submission dates and review decisions. Each contribution saves your display name and avatar for attribution. Optional social handles are not included in that public credit.

Submitted images are private to you and authorised reviewers while in the queue. Human approval makes a contribution eligible for publication; it does not automatically publish it. Published contributions display the image, prompt, model and creator credit. Updating your profile does not rewrite the attribution saved with an earlier submission.

Purchases and training

LoRA Trainer keeps the inputs, job information and outputs needed to perform your requested training. Your account can show purchase history, available credits and delivery status. Payment providers handle payment details; we retain purchase references, amounts, currency and status rather than full payment-card details. The product and checkout terms describe the work you purchase.

For workflow purchases, we store your account identifier, selected product and payment provider, order and payment references, price, currency, payment status and access entitlement. Fanvue handles card checkout where available; OxaPay handles crypto checkout. Historical card purchase records may reference Dodo Payments. We share your verified contact email, display name where required, and order information with the selected provider. Payment providers collect the billing or payment information entered on their hosted checkout. We do not receive your full card number or security code. Refunds, disputes and account closure may suspend access while the payment is reviewed.

Purchased workflow files are kept in private storage. Downloads require your signed-in account and current access permission. If you connect Discord for included support, we verify and store your Discord account identifier and link it to your HearmemanAI account. We use our Discord bot to manage the relevant product support role and retain access-change status for retries. A profile handle alone does not grant support access.

What we collect and why

When you contact us, we receive your name, email address and message. The Work with us form also has an optional service-interest field. We use these details to answer your inquiry, discuss a proposal and manage work you request. Please leave out passwords, access keys and sensitive personal information.

Providing these details is voluntary, not a legal requirement. The form needs your name, email and message so we can handle the inquiry; without them, we cannot accept a form submission. Service interest is optional.

Our hosting and security services process technical data, such as your IP address and browser information, to deliver the website and prevent abuse. The inquiry service stores keyed hashes of IP addresses and submissions, counters and delivery status to limit spam and prevent duplicate emails.

Where a legal basis is required, we rely on steps you request before entering a contract, our legitimate interests in responding to correspondence and protecting the site, or applicable legal obligations. An inquiry does not subscribe you to marketing.

Who handles your information

Amazon Web Services hosts the website, account records and product services. Cognito manages authentication, DynamoDB stores account and contribution records, and private S3 storage holds submitted images and exports. Our account backend runs in London. Cloudflare provides DNS and Turnstile bot protection. When you submit the form, Resend delivers your message to our Google-hosted inbox. We do not store your name, email address or message body in the website’s anti-abuse database, and we do not sell inquiry details.

Our inquiry service also runs in AWS’s London region. Providers also process data internationally, including in the United States; this is not a promise that all data stays in one country. Read the privacy notices for AWS, Cloudflare, Resend and Google. Resend’s data-processing terms describe its processing and transfer safeguards.

How long information is kept

We keep correspondence as needed to answer your inquiry, follow up on a proposal or manage an agreed project. Relevant records may be retained longer for legal obligations or disputes. You can request deletion at hearmeman@hearmemanai.xyz; we review requests against any continuing need to keep the information.

Anti-abuse records expire within 24 hours and are scheduled for automatic deletion; AWS may take additional days to remove expired records. Application diagnostic logs are retained for 14 days and are not intended to contain message bodies. Email and security providers maintain separate retention schedules.

Account retention and deletion

We keep active profile, preference and product records while needed to provide your account and requested services. From Privacy in your account, you can request an export, correct your information, remove PROmpt data or close your whole HearmemanAI account. You can also delete individual PROmpt contributions, including images waiting for review.

PROmpt-only removal does not delete your shared sign-in or LoRA Trainer account. Whole-account closure covers the shared identity and connected products. Open paid work, purchase records or a legal obligation can require review or limited retention; we explain any restriction when handling your request.

Deletion removes active records and private image versions. Limited recovery backups may retain deleted records for up to 35 days, beyond normal use. If a backup is restored, removal requests are reapplied before that information is made available. Account-service diagnostic logs are kept for 30 days. Prepared exports expire after 24 hours and their private download links after 15 minutes.

We remove published material under our control when applicable, but cannot promise to recall copies another person has already downloaded. Contact us about attribution, rights or removal of published content.

Website analytics

We use PostHog US Cloud to understand how people navigate and use HearmemanAI. Anonymous, cookieless analytics is on by default across the website, PROmpt and LoRA Trainer. You can switch it off using Privacy choices in the footer, without signing in; the choice applies to all three. In PROmpt and LoRA Trainer, anonymous analytics records only page views of canonical pages, plus prompt opens and copies in PROmpt with the selected model, and checkout steps in LoRA Trainer with the payment method, without prompt text or prompt, job, order or account identifiers. We preserve existing browser opt-outs. Account-linked analytics stays off until you explicitly enable it in Account privacy settings. We record canonical page paths, account sections, product openings and successful profile saves, plus selected workflow downloads, JSON copies, outbound clicks, inquiry starts and successful submissions. Call-to-action clicks record which button and page area were used. Sign-in and checkout steps record which product and payment method were involved and whether a step succeeded, with a general reason when it did not. Our servers also count completed and failed sign-ins, opened checkouts and completed purchases anonymously, with a random one-time identifier and no account, order, amount or payment details. Connected products can record selected prompt actions, contribution steps, purchases and training milestones. Referral categories and approved campaign labels help us understand where visits began. We exclude form contents, names, email addresses, handles, filenames, prompts, search text, raw URL query strings and verification tokens. We do not record sessions or use advertising tracking.

For signed-in users who opt in, we attach a stable pseudonymous account identifier created by our server. PostHog uses it for a pseudonymous analytics profile. It lets us connect consented activity across HearmemanAI products and measure return visits and where a process stops. We do not send your Cognito subject, email or display name to PostHog, and we do not merge earlier anonymous visits into your account history. This identifier is personal data even though it does not directly name you.

Analytics does not store tracking cookies or visitor identifiers in your browser. We remember your analytics choice in local browser storage so we can honour it. For visitors who have not opted out and have not enabled account-linked analytics, PostHog uses IP address, browser information and the website domain to calculate an identifier that changes daily. This gives approximate daily visitor counts without connecting that anonymous activity across days. PostHog receives your IP address to handle requests; we disable location enrichment.

PostHog processes analytics in the United States. You can switch anonymous analytics off at any time in the footer and account-linked analytics off in your account settings. An anonymous browser opt-out also stops linked browser events; disable account analytics to stop linked product events sent by our servers. We also keep it off when your browser sends Do Not Track or Global Privacy Control, even if it was previously enabled. Account totals are ordinary service records and do not depend on optional analytics. See PostHog’s privacy notice. For access or removal requests, contact hearmeman@hearmemanai.xyz. We can locate linked account analytics using our pseudonymous identifier; anonymous daily records may not be attributable to you.

Browser storage and external sites

Search and model selections stay in the URL. Essential session cookies keep you signed in, and the account provider uses cookies to complete authentication. Sign-in verification and account-security processing are necessary for the features you request. Turnstile checks browser and device signals to protect the contact form; you can email us directly if you prefer not to use the form.

Runpod, Fanvue, CivitAI, Discord and YouTube are separate services with their own privacy policies. Affiliate links may identify HearmemanAI as the referrer and earn us a commission. We do not send your project inquiry to those platforms for marketing.

Email preferences

Product updates and marketing messages have separate choices in Communications. Marketing is off by default. Optional messages include an unsubscribe route. Verification, security, purchase and training-delivery messages are service communications and cannot be disabled with a marketing preference.

The local account preview creates example messages for review and does not send them. Account delivery through Amazon SES is enabled only when that service is launched. Existing project inquiries continue to use the delivery providers described above.

Your choices

You can ask to access, correct or delete your information at hearmeman@hearmemanai.xyz. Depending on the law that applies, you may also have rights to restrict or object to processing, receive a portable copy, or complain to your local data-protection authority. We may need to verify your request, and some records may need to be kept by law. Where applicable, we respond within one month and explain any permitted extension or reason we cannot fulfil a request. You may complain to the relevant data-protection authority, including the UK Information Commissioner or your EU supervisory authority.

We will update this page when our practices change and provide any additional notice required by law.