Privacy
What we know about you.
Last updated 21 August 2026
Fightless holds the worst sentences of your relationship. So this page is written to be read, not to be survived. It says what we collect, what we genuinely cannot read, and the two moments your words leave your device unencrypted.
Who we are
Fightless is a product of Rupeestack Platform Private Limited, a company registered in Bangalore, Karnataka, India. We decide how the data described here is handled, which makes us the data controller (or, under India’s DPDP Act, the data fiduciary).
You can reach a human at support@fightless.love.
We ask for almost nothing
There is no sign-up form. No email address, no password, no phone number, no social login. When you first open Fightless you type a name and pick a language, and that is your account.
- A display name. Whatever you type — it exists so your partner’s app has something to call you. It does not have to be your real name.
- A language tag. Two letters, like
enorta, so your side of an argument comes back in the language you actually think in. - A random token stored on your device, which is how our server knows the request is yours. We keep only a one-way hash of it, so we cannot read it back out.
The name and language are stored in plain text on our server, because your partner’s phone has to be able to show them. Everything you write inside an argument is not.
What our server holds, and what it can read
Your arguments — the titles, every point, every response, the note you seal with — are encrypted on your two phones before they are sent, using a key that only the two of you hold. The key is generated on the inviter’s phone and travels to the partner inside the invite code. The half of that code we never see is the key itself.
So what sits in our database is ciphertext. Not “access-controlled”, not “staff may not view” — unreadable. We do not have the key, cannot derive it, and cannot be compelled to produce it, because it exists nowhere but on your phones.
What we can see is the shape around it:
- That an argument exists, who opened it and when.
- Whether each point is open, understood, answered, or a kept difference — and when that changed.
- That the two of you are linked, and how many AI assists are left in your shared wallet.
We can see that you had a hard week. We cannot see a single word of what it was about.
The one exception: cooling a note down
Read this one
When you ask Fightless to cool a note down, that raw text is sent to our server in the clear and passed straight to an AI model to be restated. It has to be — nothing can rewrite words it cannot read.
Here is exactly what happens. The raw text, plus the two display names and the two language tags, goes to our server. Our server forwards it to OpenRouter, which routes it to Anthropic’s Claude for inference. The cooled version comes back, and the request ends.
We do not write that raw text to our database. We do not put it in a log file. It exists for the seconds that request is alive and then it is gone. It is never encrypted with your couple key, because at that moment it is not ciphertext — and we would rather say that than pretend otherwise.
If you never want that to happen, you never have to. Sending your words uncooled is free and always available, and an unfilled wallet never blocks a send.
Voice, honestly
Where your voice goes
The audio recording itself stays on your device. It is never uploaded to Fightless and it is never sent to your partner — only text is ever sent, and only after you approve it. But in a web browser, turning speech into text uses your browser’s own speech service, and that service receives your audio while you speak.
This is the same machinery as the dictation key on your keyboard, and it belongs to your browser’s maker, not to us: Google for Chrome, Apple for Safari, Microsoft for Edge. What they do with it is governed by their privacy terms, not by this page. We never receive that audio and we never receive their copy of the transcript — only the text that lands in the box on your screen.
If you would rather nothing at all left your device, type instead of speaking. Typing is fully local until you press send, and it is not a lesser path — it works exactly the same way.
Live transcription is a browser feature; it is what runs today when you use Fightless on the web.
Paying: we never see your card
Checkout is handled by Dodo Payments, who act as the merchant of record. That means Dodo is the seller on that transaction: they run the payment page, they handle your card details, and they collect and remit any sales tax, VAT or GST that applies where you live.
Your card number never touches Fightless. We do not store it, and we could not retrieve it if we wanted to. What Dodo tells us is narrow and boring: that a payment succeeded, and which account to credit. The name, billing address and tax details you give at checkout are held by Dodo under their own privacy policy.
This website
No analytics. No tracking pixels, no ad networks, no session recorders, no third-party scripts of any kind. We do not know how many of you read this page.
One thing does load from elsewhere: the typefaces come from Google Fonts (fonts.googleapis.com and fonts.gstatic.com), which means Google’s servers see your IP address and browser when the page loads. That is the whole third-party surface of this site.
Our web servers keep ordinary access logs — IP address, time, page requested, browser — for security and debugging, and nothing is built on top of them. Our app server counts recent requests per network address in memory to stop abuse; that count is never written to disk.
How long we keep things
- Encrypted arguments stay while the shared space exists, so both phones can sync. They are unreadable to us throughout. When the last person leaves that space, they are deleted; if your partner is still there, their copy of your shared history remains theirs.
- A payment record — the processor’s payment id, what it was for, the amount, and which account or space it credited. We keep it because a refund or a card dispute cannot be answered without it, and it outlives account closure for exactly that reason. It contains no card details; Dodo never gives us any.
- Backups. The database is backed up daily and kept for two weeks, so a disk failure does not erase every couple’s space. A closure takes effect immediately in the live database, and works its way out of the backups as they rotate.
- Raw text sent for cooling is not retained by us at all.
- Invite codes expire after 24 hours. Re-opening the invite screen shows you the same code rather than replacing it, so the one you already sent keeps working; a code is spent the moment it is used.
- Payment records are kept by Dodo Payments for as long as tax and accounting law requires. Our own copy is the payment id, what it bought, the amount, and which account or space it credited — enough to answer a refund or a dispute, and nothing about your card.
- Access logs are short-lived and are not used to build any profile of you.
Deleting your account
Open Space in the app and choose Close my account. It happens immediately, without asking us: closing an account destroys every sign-in token on it and scrubs the display name. Once neither of you is left in the shared space, the space goes too — encrypted arguments included. If you would rather we did it, write to support@fightless.love.
Signing a device out is a different, gentler thing: your space stays on the server and your space key opens it again later. Closing the account does not.
One thing to know first, because it is irreversible: the couple key lives only on your phones. If you delete the app or disconnect, that key is gone, and the encrypted history cannot be recovered by anyone. Not by you, not by your partner, not by us. That is the price of a server that cannot read your fights, and we would rather you knew it up front than discovered it later.
Your rights
You can take a full copy of your own notes at any time from Space → Export my notes, and close your account from the same screen. Beyond that: depending on where you live — the GDPR in Europe and the UK, the DPDP Act in India, and similar laws elsewhere — you have the right to ask for a copy of your data, to have it corrected, to have it deleted, to take it elsewhere, to object to how it is handled, and to withdraw consent. Email support@fightless.love and we will act on it. We do not charge for this and we will not make it difficult.
Two honest limits:
- Because accounts are anonymous, we may need you to prove you control the one you are asking about — otherwise anyone could ask about anyone.
- We cannot give you a readable export of your arguments, because we do not hold a readable copy. We can hand over the ciphertext and the few fields we can read. The readable version lives on your phones — which is why the app has Export my notes in Space, and it is the complete, plain-text copy.
If you think we have handled your data badly, please tell us first — but you can also complain to your local data protection authority, or in India to the Data Protection Board.
Where your data goes
We operate from India, and our providers operate internationally. Text sent for cooling is processed by OpenRouter and Anthropic; payments are processed by Dodo Payments; fonts are served by Google. So your data may be processed outside the country you live in. Where the law requires safeguards for those transfers, we rely on the standard contractual protections those providers offer.
Adults only
Fightless is built for adults in a relationship. You must be 18 or older to use it. We do not knowingly collect anything from anyone under 18, and if we learn that we have, we will delete it. If you are a parent or guardian and think that has happened, email us and we will handle it quickly.
If this page changes
We will update the date at the top. If a change actually matters — if it changes what we collect, or who can see it — we will say so plainly here rather than quietly editing a clause.
Contact
Rupeestack Platform Private Limited
Bangalore, Karnataka, India
support@fightless.love