Screen 2 of 6
Support Assistant
Automated · available 24/7
This conversation has ended.
Scene 02 · Oct 8, 09:05 UTC — after the notice, before your appeal
Triage Assistant
Explains · gathers · briefs. Never decides.
Handoff brief — rides with your appeal
prepared for the Trust & Safety reviewer on duty · visible to Patrice
- Summary
- Indie developer, account since Mar 2023. Deactivated Oct 8 after the production key answered from 300+ IPs in 48 h — the Elonovo Remote 2.0 release grew the traffic that same week.
- The signals
- 300+ source IPs · 34 countries · one shared production key · no prior flags in 2+ years
- Evidence on file
- Architecture note: all customer requests proxy through one server-side key · request sample: identical app user-agent on every “suspicious” IP · launch changelog
- User statement
- “Every customer talks to the API through my server, so the one key legitimately appears from many IPs. The launch grew the fleet that week — that’s the whole story.”
- Why a human
- Leaked-key shape with a documented, innocent cause: one proxied key, one app, one launch. Confidence sits between thresholds. Context resolves it — automation can’t read an architecture note.