Security & Privacy

API keys, license keys, permissions, nonces and log redaction.

Backend scope (v0.24.3): Stardetha One is the customer default; legacy mode requires an explicit IST_LICENSE_BACKEND=legacy override. The legacy behavior below does not describe Stardetha One. For One configuration, strict signature checks, a maximum 72-hour signed lifetime, target-language/memory grants, online character authorization, and licensed package updates, see Stardetha One Integration.

Legacy licensing backend

Instant Language Switcher keeps provider credentials and licensing credentials server-side.

Provider API keys

DeepL/Google keys are saved in WordPress settings, never localized to visitor JavaScript and redacted from diagnostic logs.

Stardetha license keys

v0.21.0 sends license keys only to the Stardetha licensing API over HTTPS. The WordPress admin displays a masked key. The saved customer key is encrypted with installation-specific WordPress key material so a raw database export does not contain the key in clear text.

Signed licensing responses

The licensing server signs the entitlement payload. v0.21.0 retrieves and pins the Stardetha public-key identifier and verifies Ed25519/RSA signatures when the required crypto function is available. If the server's pinned key ID changes unexpectedly, the client rejects the signed response and requires the licensing configuration to be checked.

Grace period

The 14-day entitlement grace window applies only when a previously valid site cannot reach/obtain a valid response from the licensing server. Explicit expired, revoked or disabled responses are not treated as connectivity failures.

Visual Editor

Visual Editor requests use administrator permissions, nonces, explicit content IDs and target languages. It does not expose provider/license secrets to the front end.