Pairing stays one to one
The product model is one person paired with one other person. That keeps permissions, shared context, and expectations easier to understand.
- One active partner pairing at a time
- No group mode
- No adding a third person to the same space
- No public profile attached to the pair
Why BaeMax avoids contacts
A couples app does not need your whole address book to be useful. BaeMax does not request contacts permission to find your partner.
- Pairing happens through a direct invite
- Your contacts are not scanned for matches
- There is no friend discovery graph
- No follower list grows around the relationship
When this is the wrong fit
The narrow model is a strength only if your real need is one to one support. If your life needs more people in the same workspace, use a tool built for that.
- Wrong fit for families managing many schedules
- Wrong fit for friend groups
- Wrong fit for multi-person relationship structures that need shared access
- Right fit for one private pair
When the relationship changes
A two-person app needs an exit. If a relationship ends, support becomes temporary, or the pair was never romantic, use the same rule: unpair when shared access should stop, export or clear what you need, and do not keep someone connected just because they used to be the right person.
Decide whether one-to-one ownership matches the job
Two-person design is useful when each action has an obvious sender and recipient. It can keep a check-in, task, or support preference from becoming a group discussion. But it also means the app should not become the only place for information that a caregiver, clinician, co-parent, or household may need. Keep shared appointments in a calendar others can access when appropriate, and use the pair space for context that belongs between these two people.
- Use a family or team tool for multi-person schedules and care coordination.
- Avoid rotating pairings casually while old shared information remains relevant.
- Confirm who retains a task, note, or export after unpairing.
- Use a direct invitation rather than contact discovery when privacy matters.
- Keep emergency contacts and care instructions outside the pair space if another person may need them.
- A one-to-one design should make re-pairing deliberate: verify the new recipient and review what historical context, if any, will be visible.
- For co-parenting, caregiving, or polyamorous relationships, do not force a two-person tool to represent access needs it cannot express.
- When one person leaves, each participant should understand which local entries, delivered notes, and exported copies remain on their own device.
- Test the invitation with two spare entries and confirm that a mistyped or forwarded code cannot silently connect the wrong person.
- Use separate personal accounts and device locks; one shared phone login undermines a two-person permission model.
- Keep a non-app way to reach each other so account or pairing failure does not block ordinary communication.