About Accordial · The company

Built on a single,
stubborn decision.

A relationship platform should not know who its users are. Everything else followed from that, the product, the pricing, the team, the way we talk on this very page.


They start with an account, an email, a credit card, a phone number, then add privacy promises on top. Once a company holds your identity, no policy can fully undo that. Not against subpoenas. Not against breaches. Not against the slow drift of how data ends up getting used over time.

We wanted to build something a person could use during the worst week of their marriage, or while quietly figuring out whether to leave, or while co-parenting with someone they no longer trust, without leaving a trail.

The only way to make that promise honestly was to build a company that couldn't break it. So we did.
The founding decision

Accordial doesn't store your name. We don't have your email. We don't see your card. Your partner is paired with you through an opaque code, not a contact. Practitioners meet you without knowing who you are, working from a brief our AI generates from your sessions.

The anonymity isn't a setting. It's the architecture.

Architecture, inverted

Same product. Two starting points.

The usual way
Identity first, privacy on top.
emailphonecardproductpolicy
Once identity is in the database, every later choice is downstream of it.
Accordial
No identity. Product around what's left.
refuseopaque tokenpair by inviteproduct
We chose not to be the company that holds those things. The product had to fit that shape.
02 · What we believe

Five lines you can quote back at us.

These are the principles the product is built around. We've kept them short on purpose so they're impossible to drift from quietly.

01

The relationship is the customer, not the user.

No engagement metrics

A couple who needs us less over time is a success, not a churn problem. We don't optimize for engagement. We don't measure ourselves on minutes-spent. The good outcome here looks like quieter Sundays, not heavier app usage.

02

Privacy is a structural decision, not a marketing one.

Architecture · not policy

We made architectural choices that cost us growth tactics other companies rely on. Referral graphs, contact-import, retargeting, lookalike audiences, partner-of-partner suggestions. Those tactics required knowing you. We chose not to.

03

Our AI sounds human, not performing empathy.

Plain voice

It speaks plainly. It doesn't validate everything. It's honest when honest is what helps. If the model wrote the line "I hear that this must be very difficult for you," we'd rewrite it. Or scrap it.

04

We don't gamify pain.

No streaks · no nudges

No streaks. No badges. No notifications designed to pull you back. The mechanics are calm on purpose. If you don't open Accordial for a week because things are good, that's the point.

05

We say what we can't do.

Edges, said out loud

Some situations need a human. Some need a crisis line. We tell you when we see it instead of pretending we can handle everything. Honesty about edges is part of trust. Pretending otherwise is how products quietly become dangerous.

03 · What anonymous actually means here

We try not to overclaim.

Apple knows you bought something on Apple's platform. A subpoena to Apple can produce that record. What we can tell you is what we hold, because that's what we control.

The short version

We don't have any of these.

None of them exist in our systems, because we never asked for them.

  • N/AYour name. No legal-name field exists. Not even nullable.
  • N/AYour email. Not requested, not stored.
  • N/AYour phone number. No SMS, no SIM lookup.
  • N/AYour card. The App Store handles every cent.
  • N/AYour partner's contact info. An opaque pairing code, not an address book entry.
The long version

Every choice we made, and why.

Lives on our Privacy page. We update it whenever the architecture changes, not just when the legal copy changes.

That document is the source of truth. Anything you read elsewhere on this site, including the page you're on, is meant to reflect it. If it ever doesn't, the Privacy page wins.

Read the architecture in full
04 · Who Accordial is for

Couples across three stages.
And the professionals who support them.

Stage 01

Whether you're building something real

Two people working out what fits and what doesn't. Soft enough for early days, honest enough to surface what shouldn't get glossed over.

What the platform does for them
  • Translate hard things gently
  • Notice the recurring rough edges
  • Spot the things worth saying out loud
Pairing illustration
Two people · No accounts shared
A
B
stage = "dating"
pair = tok_a ↔ tok_b
shared_history = on-device
05 · The team

A small team. No founder profiles.

Accordial is a small team working across product, engineering, design, and clinical advising. We don't list everyone here, and we don't run founder profiles. The product asks users to trust a company that doesn't know who they are. It would be strange to spend the rest of our marketing surface making the company about us.

ProductEngineeringDesignClinical advisingTrust & safety
support@tryaccordial.com
Product
Eng
Design
Clinical
Eng
"We built a company that can't know you."Founding line
Trust
Eng

If any of this sounds like the kind of company you'd want in your corner,

we built it for you.