Connection requests are the relationship unlock, not the trust event itself. Once a connection is accepted, the same member thread becomes the place where future interactions continue.
Activities such as Practice, Social Dance, Event / Festival, Travelling, Hosting, Private Class, or Collaborate are then started from that accepted thread. Each accepted activity is logged inside the thread history so the relationship timeline remains visible when you scroll.
To keep trust signals clean, the same two members can only log up to 2 accepted activities per month, and those activities must be different types.
References do not come from connection acceptance alone. They become eligible after an activity is accepted by both sides, then unlock 24 hours after the activity ends or 24 hours after acceptance if there is no date range.
Practice and Social Dance share one reference cooldown. Between the same two members, they can only generate one new reference every 120 days. Private Class uses the Classes reference category and can generate one new reference every 90 days.
Travelling, Request Hosting, Offer Hosting, Event / Festival, and Collaborate can each generate one reference per completed activity.
Interaction counts are tracked separately from written references, so repeated real experiences can still show on the profile without inflating public trust with duplicate references.
Once a reference unlocks, each member has 10 days to submit it. Pending references live in your Profile > References area, with a direct link back into the chat if you need to check context before writing.
Need policy-level detail?
Open the Trust & Safety Guidelines for full policy coverage, reporting scope, emergency guidance, and how moderation handles cases.