How we use data
The short version: we keep facts extracted from projects, not your drawings. Your files serve your run, are never shared with another customer, and the originals are deleted after 30 days.
What we receive and what happens to it
| Data | Used for | Kept |
|---|---|---|
| Original files: drawings, AGi32 and IES files, dimensions | Your run only | 30 days after the run |
| Your email and request | Replying to you and doing the run | While we work with you |
| De-identified facts: lot shape (shifted, rotated, scaled), where poles may stand, targets, luminaire light-distribution type, final pole positions, computed results | Improving Runnax Engine and aggregate benchmarks | Until you opt out |
| Removed before anything is kept | Company and person names, addresses, real-world coordinates, title blocks, text layers and file metadata | |
Which part of the engine learns from it
- Finding where poles can stand. Confirmed islands and curbs teach the engine to propose them on new sites.
- Validation. Projects with AGi32 or DIALux results extend what we can call verified.
- Better first layouts. Typical targets, pole heights and spacings make the first proposal closer to the final one.
Who is in, and how to get out
- Free early-access runs: de-identified facts and project content may improve the engine. Opt out for a run or for your account.
- Paid, white-label and enterprise customers: project content is not used to improve the engine unless the contract says so.
- Opting out: write to kyan@runnax.com. Your data is removed from training sets before the next engine update.
What we never do
- Share one customer's files or results with another customer.
- Give project data to third parties to train their models.
- Try to re-identify de-identified data.
- Publish a project as a case study without written permission.
- Apply a new use of data to data we received before announcing it.
Benchmarks
Aggregate figures, such as how many poles lots of a given size typically need, are published only when they combine at least 5 projects and no single customer makes up more than 25 % of them.
Changes
We announce changes to how we use data at least 30 days before they take effect.
- 2026-10-15 · First version of this page.