Role separation
In the gift scenario there is giver, recipient, payment, and private scroll. These roles must not be mixed.
- Payment receipt: giver.
- Question and answer: recipient.
- Support case: only for needed context.
boundaries
private gift rules
Private gift rules
A gift scroll must protect the recipient even more than a normal purchase because a second person is involved.
The giver buys access; the recipient owns the question, answer, and choice to share or not.
Gift flow
- The giver chooses format and pays.
- The recipient activates access and asks their own question.
- The system separates receipt, delivery status, and private content.
Privacy rules
- The giver does not see the recipient's private question.
- Public sharing must not show name, email, question, or the full answer.
- The gift must not feel like pressure: the recipient decides whether to open the scroll.
Commercial notes
- Gift email to the giver should be operational, not intimate.
- Gift email to recipient should explain rights and boundaries.
- Support must not forward answer content to the giver.
Recipient rights
The recipient should be able to not activate immediately, delete data, and not share the result.
- Delay opening.
- Request data deletion.
- Open without notifying the giver about content.
Pre-launch QA
- Support macros do not reveal recipient content.
- Gift code is not guessable.
- There is clear consent before share-card.