textRay · relationship text analyzer

evidence-based relationship reads · iOS

the relationship text analyzer that actually read the receipts.

you've re-read the conversation fifteen times. your friends have picked a side. textRay reads both sides of the chat and shows you the patterns with the evidence attached. a second opinion with citations.

fifteen re-reads is not analysis. it's a loop.

the group chat is on your side, which is lovely and useless. a chatbot will agree with whoever's typing. textRay is the second opinion that did the reading. it scans the conversation and comes back with three things, all on file:

  • the verdict. the headline read, 3–8 words. "friction, then actual repair."
  • the receipts. quotes, statistics, timelines. every claim traced to a message.
  • the read. pattern findings, hedged where the evidence is thin. "one-sided effort — 71% pattern match."
themyou're overthinking it, it's not that deep
youyou cancelled twice and went quiet for a week

logged as exhibit 14. counterevidence: searched.

what a relationship shows in its texts

a relationship leaves measurable tracks in a conversation. not vibes. tracks. the scan reads the words and the clock:

what shows up in the receipts
  • who initiates, who makes the plans, who circles back after a fight
  • reply gaps and the warmth trend: is this chat getting colder since february
  • repair quality: the real apology vs "sorry you feel that way"
  • green flags with citations: matched energy, boundaries respected, words that match actions

and the scan reads both sides on purpose. sometimes the nine-hour reply gap was yours. the report will say so, calmly, with the timestamp.

how to analyse a relationship over text

  1. pick the conversation. screenshots, a WhatsApp export, or pasted messages all work.
  2. add it to textRay on iOS. nothing is analysed until you agree to AI processing.
  3. run the scan. one credit gets the verdict and the headline patterns. the full scan opens every exhibit, the trends, and the what now.
verdict: pending

stop re-reading. get the read.

download on the App Store

iOS · 16+ · no subscription · credits from £2.99

a good relationship gets a good report.

this is not a red-flag detector that has to find a red flag to justify itself. healthy patterns are findings too. "steady care, no weird games" is a real verdict, and people screenshot it. real apologies, genuine check-ins, plans that actually happen: all of it gets cited like evidence, because it is.

and where the conversation doesn't support a conclusion, the scan says so instead of inventing one. signals: mixed. literally. the receipts will decide.

The boring bit, on purpose.

textRay never connects to your messaging accounts. You add a conversation yourself, and nothing is analysed until you agree to AI processing. Reports stay in your history until you delete them. Findings describe patterns in a conversation. They are never a diagnosis of a person, and textRay is not therapy or a substitute for it. textRay is for ages 16 and over.

questions, answered plainly

what does a relationship text analyzer actually check?

textRay reads a conversation you add yourself, both sides of it, and looks for patterns: who initiates, who repairs after conflict, reply gaps, warmth over time, and named patterns like breadcrumbing or one-sided effort. every finding cites the messages it came from.

will it just tell me what I want to hear?

no. the scan reads both sides and follows the evidence, including when it cuts against you. counterevidence is shown rather than hidden, and findings describe patterns in a conversation, never verdicts on a person.

what if the relationship is actually fine?

then the report says so, with the same evidence discipline. green flags like real apologies, matched energy, and words matching actions are detected and cited exactly like the concerning patterns are.

what do I need to run a scan, and what does it cost?

screenshots, a WhatsApp export, or pasted text, on iOS. there is no subscription. credits start from £2.99. an initial scan uses one credit, a full scan uses three, and a failed scan does not use the credit.