Most conversations with people you have just met exist for one reason: an event, a trip, a project that runs for a weekend. When the reason is done, the conversation has nothing left to do. Yet in most messengers it stays, along with the phone numbers both sides exchanged to have it. FadeTalk starts from the opposite default: a conversation opened for a purpose can end with that purpose.
What lingers after the purpose is gone
A conference group where hundreds of people you met once still have your number. A chat thread with someone you sat next to at one workshop. A number in the phone of a fellow traveller from a trip two years ago. None of these is harmful on its own. Together they form a contact surface that keeps growing and never shrinks, and changing your number is the only way to shrink it.
The end belongs to the person who made the link
A single-use link expires after 24 hours, 3 days or 7 days, and burning it ends its guests' chats. Each chat can run for 1 hour, 1 day, 7 days or a custom time, and the time left is always on screen, so neither side is surprised. A place room opened for an event closes when its time is up. For the people you keep, such as someone you will now work with, there is no timer at all. The point is not that everything should vanish; it is that a conversation should last as long as its purpose.
A promise, not magic
An end on a timer is a schedule, not protection against copying. Reported content is preserved for safety review, backups and legal holds are exceptions, and what the other person has already seen, saved or captured cannot be taken back. That is why FadeTalk speaks of chats scheduled to disappear and a lighter record burden, and does not promise that nothing remains.
Contact that ends when its purpose ends is lighter for both sides. Designing that end with care, and saying plainly where it stops, is FadeTalk's job.