Historical-Data Sessions

Session purpose

Historical-data sessions are for user-requested data access during setup, testing, or export preparation.

Intended retention posture

Stockey should avoid permanent broker-secret storage by default and avoid permanent raw market-data storage by default.

Session lifecycle

1. User selects broker and instrument.
2. Broker authorization occurs under broker rules.
3. Stockey fetches requested historical data.
4. User runs historical testing.
5. Session tokens are removed after the user-requested workflow or explicit disconnect.
6. Temporary raw historical data is removed after the test/export workflow unless a saved report needs derived results.

User checks

• Broker terms allow the requested use.
• Instrument and segment are supported.
• Rate limits are understood.
• Data gaps are visible before testing.

Retention boundaries

Item	Default posture
Broker credentials	No permanent storage by default.
Session tokens	Temporary and workflow-limited.
Raw broker data	Temporary by default.
Saved reports	May retain derived metrics and summaries when the user saves or exports.