How it works
How SLOWKEPT works.
SLOWKEPT helps someone prepare a real letter, decide what to do with it, and keep a private record of chosen moments around that letter. It does not write the letter for them, and it does not store the full text online.
Step 1
Start with a reason
The letter path begins by naming why this letter exists. This helps the writer choose a clear direction before trying to write everything at once.
Step 2
Use the Guided Printable System
The guide helps with emotion positioning, boundary checks, expression limits, a first sentence, and a physical completion ritual. It guides the process, but it does not write the letter for the user.
Step 3
Decide what should happen next
After the letter is prepared, the writer chooses whether to send it, wait, save it privately, or keep it as part of a future memory archive.
Step 4
Add a Private Thread Code if the letter is sent
One Private Thread Code belongs to one long-term letter timeline between two people. It is not a new code for every letter.
Step 5
Let the recipient add a simple status
The recipient can use the code to add a lightweight update, such as received, needs time, or reply sent. They do not need to create an account first.
Step 6
Keep a private letter timeline
The timeline records chosen moments, dates, and short statuses. It does not contain the full letter text.
What is kept
The timeline keeps moments, not the letter itself.
A private timeline can include dates, statuses, short notes, and whether a moment came from A or B. The full letter stays off the platform.
Example timeline moments
Letter prepared: The sender completed the printable guide.
Letter sent: The letter left the sender's hands.
Letter received: The recipient chose to add a status with the code.
Reply sent: The recipient marked that a reply began its way back.
Product boundaries
What SLOWKEPT does not do.
These boundaries keep SLOWKEPT focused on real letters, private timelines, and careful participation.
SLOWKEPT does not write the full letter for the user.
SLOWKEPT does not store, read, or analyze the full letter text.
The timeline is not a chat, inbox, or social feed.
There are no public profiles, followers, or relationship graphs.
There are no read receipts, seen states, or open-status signals.
The recipient can leave a simple update without being forced to register.
Private Thread Code
One code holds one private letter thread.
The code is the shared entrance to one A/B timeline. If more physical letters are exchanged later, they can belong to the same thread instead of creating a new code each time.
Memory Book
A future archive, not part of V1 production.
Memory Book is a future physical archive for selected letter timelines. V1 only tests whether people want a lasting place for certain private letter histories.
Start with one letter path.
The first step is not to publish, message, or archive anything. It is to prepare the letter clearly enough to decide what should happen next.