Privacy Policy

1.Who we are

Reply Hotter is operated by Clarity Decoded, in Austin, Texas. This policy explains what personal information the Service handles, why, and what you can do about it. It forms part of our Terms & Conditions. For privacy questions, write to legal@replyhotter.com.

2.Screenshots: what happens to them

This is the part people actually want to know, so here is the whole sequence:

1. You upload one or more screenshots from your device.
2. They are sent over an encrypted connection to our server, and from there to an AI model provider (Google's Gemini models, or OpenAI as a fallback) so the conversation can be read.
3. The model returns a reconstruction of the conversation as text, plus four suggested replies.
4. We keep the reconstructed text and the suggested replies, so your thread is still there when you come back and so later rounds understand the history.
5. The image files themselves are discarded. They are not written to our database and there is no screenshot archive.

3.What we collect

Account information

Your email address, and — if you sign in with Google — the basic profile Google returns (name, profile picture URL and a Google account identifier). If you sign in with email, we send a one-time code and link to that address; there is no Reply Hotter password. We never see your Google password. We also keep your plan, role, referral code and the date the account was created.

Conversation content

The reconstructed text of the conversations you upload, the suggested replies generated for them, an optional label you give a thread, and your notes on it. This is stored server-side and associated with a per-device identifier your browser generates, and with your account once you sign in. If you use Relationship Mode, the context you choose to record about that relationship is stored on your account too: her name, your relationship status and dates, notes about her, your children's names and birthdays, and the period dates you enter so we can estimate where her cycle is. It is used only to shape the replies written for you, is never shown to anyone else or included in a reply, and is exported and deleted with the rest of your account.

Device and session records

For each signed-in device we keep a session record: a hashed session token, a short device description (such as the browser and operating system), the times it was created and last used, and an approximate location derived from the network connection at city or region level. Location metadata is optional — turn it off in Settings > Privacy and we stop recording it and clear what we already had for your sessions.

Usage and billing

Which plan you are on, how many rounds you have used in the current window, your usage-credit balance, your spend limit and auto-reload settings, a record of each round for metering, your purchase history and receipt links, and identifiers Stripe gives us for your customer and subscription records.

Product analytics

A deliberately content-free event log: the type of event, which model provider served a round, whether it succeeded, which heat level was copied, how long it took, and where people drop off. No screenshots, no message text and no generated replies are written to the analytics store. It records the shape of behaviour, not what was said.

Advertising measurement

We run ads on Meta (Facebook and Instagram), and to know whether they work we use the Meta Pixel on our pages and Meta's Conversions API from our server. What reaches Meta is the same content-free shape as our own analytics: that a page was viewed, an account was created, a plan was looked at, a checkout was started or completed and for how much, a round was generated, a reply was copied (which heat level, never its text), or the support chat was opened. Meta also receives the identifiers it uses to match those events to a person who saw an ad: a hashed version of your email address, your IP address and browser user agent, and the _fbp and _fbc cookies the pixel sets. No screenshot, no message, no generated reply and no name from a conversation is ever sent to Meta. Meta processes this under its own privacy policy; you can limit how Meta uses data from other sites in your Off-Facebook activity settings, and a content blocker that stops the pixel does not affect the Service.

We also run ads on Google, and use the Google Ads tag to count two things and nothing else: that an account was created, and that a plan was bought and for how much. The tag loads only on our own pages and only on replyhotter.com; it loads with each page, so that it can read the ad-click identifier on the page you arrive on, but it reports no page views. Google receives those two events, the page they happened on, your IP address and browser user agent, and the identifier in the click that brought you here from one of our ads, which the tag keeps in its own first-party cookies (_gcl_au, and _gcl_aw when you arrived from an ad). No email address, no screenshot, no message, no generated reply and no name is sent to Google for advertising. Google processes this under its own privacy policy; you can control ad personalisation in My Ad Center, and a content blocker that stops the tag does not affect the Service.

Security signals

Cloudflare, which hosts the Service, processes technical request data such as IP address and user agent to route traffic and to stop attacks, and we use Cloudflare Turnstile to tell humans from bots. This is standard infrastructure logging, handled by Cloudflare as our provider.

4.What we don't collect

• Your screenshots, unless you opt in per round or in Settings.
• Your card number. Card details go straight to Stripe; we see only the last four digits and card brand that Stripe reports back, plus the identifiers it gives us.
• Your contacts, photo library, camera roll or messages. The Service only ever receives the specific images you choose to upload.
• Precise location. We never ask for GPS or device location permission.
• Your browsing elsewhere. The one advertising tag on this site is the Meta Pixel described above, used to measure our own ads. There are no other ad networks, no data brokers and no third-party analytics scripts.
• Special-category data by design. We don't ask for your race, religion, health, politics or sexual orientation. Conversations you upload are personal by nature, which is exactly why images aren't kept and analytics is content-free.

5.How we use it

• To run the Service: read your screenshots, generate replies, keep your threads, remember your settings.
• To keep your account secure: sign you in, show you your active devices, let you revoke them, and detect abuse.
• To bill you correctly: meter rounds, apply plan allowances and credits, process payments and issue receipts.
• To improve the product: using the content-free analytics log, and — only where you opted in — reviewing kept submissions to judge whether the replies are any good.
• To communicate: service messages such as sign-in codes, receipts, and notices about changes to these documents.
• To comply with the law and to enforce our Terms.

We do not sell your personal information, and we do not share it for cross-context behavioural advertising. We don't use your conversations to build advertising profiles.

Where the GDPR or UK GDPR applies, our legal bases are: performance of a contract (running the Service and billing you), legitimate interests (security, abuse prevention, content-free product analytics), consent (the research opt-in and optional location metadata, each withdrawable), and legal obligation.

6.Who we share it with

We share personal information only with the providers that make the Service work, each acting on our behalf and limited to what their job requires:

Content is sent to the AI providers through their APIs. Under the API terms we operate on, data submitted this way is used to serve your request and is not used to train their public models. Those providers may retain data briefly for abuse monitoring under their own policies.

We may also disclose information if the law requires it, in response to a valid legal process, to protect the rights and safety of people or of Clarity Decoded, or in connection with a merger, acquisition or sale of assets — in which case we'll say so before your information becomes subject to a different policy.

7.The research opt-in

There are three ways a submission gets kept, and all three are opt-in:

• The per-round checkbox on the upload card. Off by default. It applies to the round you are about to run.
• The standing permission in Settings > Privacy, if you'd rather not decide each time. Off by default, and switching it off stops future retention.
• A co-founder account, where full visibility is the explicit deal in exchange for rounds at cost, and which is described as such when it's granted.

A kept submission includes the screenshot images, the reconstructed conversation, the replies generated, which reply you copied, and the account it came from. It is reviewed internally by the Reply Hotter team to judge and improve reply quality. It is not published, and it is not sold.

Settings shows how many of your rounds have been kept. Ask us at legal@replyhotter.com to delete them, or delete your account, which removes them automatically.

8.Other people in your screenshots

A screenshot of a conversation contains someone else's words, and often their name and photo. That person is not our user and has no account here, so a few things follow.

Under our Terms, you are responsible for having the right to upload what you upload. We process the other person's information as part of delivering the Service to you. Because their images aren't stored and their text lives inside your thread, the practical way to remove it is for you to delete the thread — or your account.

If you appear in someone else's screenshot and want to raise a concern, write to legal@replyhotter.com. We will need enough detail to identify the material, and we'll do what we reasonably can.

9.Cookies and local storage

Beyond the Meta Pixel and Google Ads cookies described below, we use only what the app needs to work:

• Two Meta Pixel cookies, _fbp and _fbc, set by the Meta Pixel to tell Meta that a visit or purchase came from one of our ads.
• Google Ads cookies, _gcl_au and (after a click on one of our Google ads) _gcl_aw, set by the Google Ads tag to tell Google that a sign-up or purchase came from one of our ads. With the Meta ones, they are the only advertising cookies on the site (see "Advertising measurement" above).
• Two short-lived cookies during Google sign-in, which protect the sign-in round trip against forgery and remember where to send you back to. They are HttpOnly and expire in ten minutes.
• Browser local storage on your own device, holding your session token, a per-device identifier for your threads, and preferences such as calm mode and your research choice. Clearing your browser's site data clears them.
• Cloudflare Turnstile, which may set its own storage to verify you're not a bot.

10.How long we keep things

Deleting your account removes your account record, your conversations and any research submissions tied to your email. Backups and provider logs may take a short time to age out, and we keep the minimum needed for legal, tax and fraud-prevention purposes.

11.Your controls and rights

Most of it you can do yourself, right now, in Settings:

• Export everything. Settings > Account gives you a JSON file with your account, plan, usage, sessions and privacy choices.
• Delete your account. Settings > Account. This deletes your data as described above, and it is not reversible.
• Delete a conversation. The trash icon on the thread bar.
• Turn the research permission on or off. Settings > Privacy, or the checkbox on any upload.
• Turn off location metadata. Settings > Privacy. Existing session locations are cleared when you do.
• Sign out a device. Settings > Devices, revoke any session.
• Cancel billing. Settings > Billing.

Depending on where you live, you may also have the right to access, correct, delete or port your personal information, to object to or restrict certain processing, to withdraw consent, and not to be discriminated against for exercising these rights. Write to legal@replyhotter.com and we'll respond within the time the applicable law allows. We may need to verify your identity — usually by confirming control of the email address on the account — before acting on a request.

12.US state privacy rights

Residents of Texas, California, Colorado, Connecticut, Virginia and other states with comprehensive privacy laws have the rights described above, including the right to know what we collect, to get a copy, to correct it, to delete it, and to appeal a decision we make about a request. To appeal, reply to our decision at legal@replyhotter.com with the word "appeal" and we'll review it again and explain the outcome in writing.

We do not sell personal information, and we do not share it for targeted advertising or cross-context behavioural advertising — under any of these laws' definitions. We do not use personal information for profiling that produces legal or similarly significant effects. We honour browser opt-out preference signals such as Global Privacy Control where they apply, though since we neither sell nor share data for advertising, there is nothing for such a signal to turn off.

You may use an authorized agent to submit a request on your behalf, with proof of their authority.

13.International users

Reply Hotter is operated from the United States, and our infrastructure providers process data on servers in the United States and other countries. If you use the Service from outside the US, your information is transferred to and processed in the US, where privacy law differs from your own. Where required, our providers rely on recognised transfer mechanisms such as the European Commission's Standard Contractual Clauses.

If you are in the EEA or UK, you also have the right to lodge a complaint with your local supervisory authority.

14.Security

Traffic is encrypted in transit. Session tokens are stored hashed, never in the clear. Sign-in codes and links work once, expire after 15 minutes, and are stored only as hashes. Access to stored data is limited to the people who need it to run the Service. Not storing screenshots is itself a security measure: the safest data is the data that was never kept.

No system is perfectly secure, and we can't guarantee absolute security. If a breach affects your personal information, we'll notify you and the relevant authorities as the law requires.

15.Children

Reply Hotter is for adults. It is not directed to anyone under 18, and we do not knowingly collect personal information from children. If you believe a minor has given us information, write to legal@replyhotter.com and we will delete the account and its data.

16.Changes to this policy

We'll update this page as the Service changes. The "last updated" date at the top always reflects the current version, and for material changes we'll give notice in the app or by email before they take effect.