Whenever you suspect the token has leaked — a screenshot leaked, a
URL with ?token= ended up somewhere public, a connector got
shared — rotate it:
openssl rand -hex 32.
OWNSONA_API_TOKEN in
src/main/backend/application.ini.
./bld -v build && ./bld war &&
sudo cp work/Kiss.war /home/ownsona/tomcat/webapps/ROOT.war.
There is no dual-token grace window. Clients see 401 until they update. For a single-user store this is fine; do it after-hours.