Skip to content

Privacy policy: plan explanations and feedback on them - #62

Merged
naltatis merged 1 commit into
mainfrom
optimizer-explain-privacy
Oct 16, 2026
Merged

naltatis merged 1 commit into
mainfrom
optimizer-explain-privacy

Conversation

@naltatis

@naltatis naltatis commented Oct 16, 2026 •

Copy link
Copy Markdown
Member

pairs with evcc-io/optimizer#215, evcc-io/optimizer#214, evcc-io/evcc#34920, evcc-io/evcc#34926

The optimizer section of the privacy policy still says the service stores nothing. Plan explanations and feedback on them change that, so the section now describes both.

  • Optimisation requests: unchanged, not stored. The absolute "no data is permanently stored" is narrowed to them.
  • Plan explanation: the plan, device names and UI language go through optimizer.evcc.io to Azure OpenAI, processed only in the EU data zone, Microsoft as processor, no training, not stored by us. Abuse monitoring as Microsoft documents it today: stored only when abuse is suspected, reviewed within the EEA.
  • Feedback on explanations: stored only when someone votes, in a German data centre, deleted after 12 months, consent as legal basis, withdrawal via the account pseudonym.
  • Running the optimizer locally: explanations then need your own Azure OpenAI access.

Matches the target state of evcc-io/optimizer#215, store on vote with a 12 month cleanup, and should go live with it.

🤖 Generated with Claude Code

The optimizer section describes the plan explanation, written by Azure OpenAI
in the EU data zone and not stored, and the feedback on it, stored for 12
months only when someone votes. Optimisation requests themselves stay
unstored.
@naltatis
naltatis merged commit 9e4b78a into main Oct 16, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant