Storing & Loading Strategies
What It Is
There are two types of saved state on Strateda, and understanding the distinction matters for your workflow:
- Job results (temporary) — Every time you click Run, the platform creates a job. Completed job results are stored in the job table and accessible for 7 days, then automatically purged. This includes backtests, optimizations, and walk-forward analyses.
- Stored strategies (permanent) — When you explicitly save a strategy configuration with a name, it is stored permanently in your account until you manually delete it. Stored strategies are independent of the job table.
The connection between the two: you run a job, review the results, and if you find a configuration worth keeping, you store it as a named strategy. The job result may expire after 7 days, but the stored strategy persists indefinitely.
Job results are automatically purged after 7 days. If you find a parameter combination or strategy configuration worth keeping, store it as a named strategy before the job expires. Stored strategies are retained until you manually delete them.
Result lifecycle
| State | How to get there | Retention |
|---|---|---|
| Job result | Click Run | 7 days, then auto-purged |
| Loaded result | Click a job row in the job table | Active in current session |
| Stored strategy | Click Store and name it | Until manually deleted |
How to Access It
Strategy storage is available on all plans through the Strategy tab at app.strateda.com.
- Store — Save the current strategy configuration permanently with a name of your choice.
- Store All — Save multiple strategies as a named group. Whether you are applying the same strategy to different instruments or different strategies to a single instrument, you can save them together for easy access and management.
- Load — Browse your stored strategies. Click a name to load the full configuration into the builder.
What You See
- Store dialog — Enter a name for your strategy. Choose a descriptive name that captures the key parameters (e.g., "AAPL RSI-30 H1 TP2" or "EURCHF DEMA-EMA M30 Buy").
- Store All dialog — Enter a group name. All active strategies in the current view are saved together under this name for easy access and management.
- Strategy list — Your stored strategies and strategy groups appear at the top of the strategy panel. Click a strategy name to automatically populate all strategy fields with its parameters. Stored strategies are private and accessible only by you.
- Loaded configuration — All fields in the strategy builder populate with the stored values. You can modify any parameter after loading.
How to Interpret It
Naming Conventions
There is no enforced naming standard, but a consistent convention saves time as your strategy library grows. Consider including:
- The instrument (e.g., AAPL, EURCHF)
- The primary indicator or logic (e.g., RSI, DEMA-EMA)
- The timeframe (e.g., H1, M30)
- The direction (e.g., Buy, Sell)
- A version or variant label (e.g., v2, optimized)
Data Security and Retention
Strateda treats your strategy parameters as sensitive data:
- Encrypted at rest — All strategy data — both job results and stored strategies — is encrypted at every storage layer using AES-128 encryption. Your indicator settings, entry and exit conditions, and position sizing are not stored in plaintext.
- Job results (7-day retention) — Temporary job data (backtests, optimizations, walk-forward results) is automatically purged from the servers after 7 days. See Job System for details on job tracking and result reloading.
- Stored strategies (permanent) — Explicitly stored strategy configurations persist in your account until you manually delete them. They are not affected by the 7-day job purge.
- Process-level protection — When strategies run live, parameters are never visible in plaintext in the system process list.
This means your strategy logic — your edge — is protected against database exposure. A database snapshot does not reveal your parameters without the platform encryption key.
Workflow Tips
- Store before optimizing — Store your baseline strategy before running optimization so you can return to the original configuration.
- Store optimized variants — After optimization identifies better parameters, load the job result from the job table, then store the updated strategy as a new entry rather than overwriting the original. This preserves your iteration history.
- Load and modify — Loading a strategy does not lock it. Use a stored strategy as a starting template and adjust parameters for a new instrument or timeframe.
- Store before job expiry — If a job produced results you want to keep, store the strategy configuration within the 7-day retention window. The stored strategy will persist even after the job result is purged.
Example
You design a DEMA/EMA crossover strategy on EURCHF M30 and store it as "EURCHF DEMA-EMA M30 Buy v1". You then run a parameter optimization — the job completes and the results appear in the job table.
Three days later, you reload the optimization results from the job table and find that DEMA(14)/EMA(12) outperforms your original DEMA(21)/EMA(21). You update the periods in the builder and store the new configuration as "EURCHF DEMA-EMA M30 Buy v2 optimized". The optimization job result will be purged after 7 days, but both stored strategies persist permanently.
Later, you want to test the same logic on EURGBP. You load v2, change the instrument to EURGBP, and store it as "EURGBP DEMA-EMA M30 Buy". Your original EURCHF strategies remain untouched.