Product Constitution · v0.1

Trust is the product.

1. Trust before revenue

Every business decision must preserve the trust between hosts, guests, and Groop.

2. Guests own their participation

Consent is ongoing. Withdrawing it must be as easy as giving it.

3. Hosts own their events

Features should reduce uncertainty and help organizers feel confident.

4. The platform owns neither

Guests participate in events—not in Groop's marketing ecosystem.

5. Privacy is a product feature

People should understand what is shared, with whom, why, and for how long.

6. Events are temporary

Completed events naturally move toward archival and deletion.

7. Simplicity wins

Fewer options, thoughtful defaults, conversational flows, and clear language.

8. Complement existing tools

Groop begins where invitation design ends.

9. Charge for value, not participation

Core coordination remains genuinely useful without ads, credits, or dark patterns.

10. Minimize operator trust

Security and privacy should be architectural properties, not promises alone.

The north star