Return after 30 days
Compare the first window with real events and decisions.
Saved spreads
Every completed result is stored with its generation or delivery date, context and type. Compare what you read then with what is visible now.
One chronological archive
The history is designed as an account feature, not an accidental browser page. It keeps the original result connected to the correct profile or order.
How to use the history
The point is not to force every event to fit the cards. Use the archive to check which themes were useful and where your own interpretation changed.
Compare the first window with real events and decisions.
Notice patterns that appear across separate spreads.
Record what was actually present, not only what now looks convenient.
History improves the quality of future context.
FAQ
Availability depends on the current application version and retention rules. Account deletion is handled separately.
A reused identical result may refer to the existing spread rather than create an unnecessary duplicate.
No. A reader should access only the assigned order data required to perform the service.
The final retention period must be set in the operator's privacy policy and application configuration.
Start here
Return after the period and judge the spread with the benefit of actual time.