KeepMyPDIKEEP MYPDI / TRANSPARENCY
Security, without mystery.
What the integration does
KeepMyPDI opens a fresh Chromium session, signs in with a dedicated service user and calls its narrow activity endpoint from that browser session. It appends a timestamp, reads it back, records the result and closes the browser. Optional statistics are fetched only when permitted.
Credentials and permissions
Your account password is hashed with Argon2. PDI service passwords are encrypted with a separate Fernet key, outside the database. Operators with host and key access could decrypt service credentials; encryption does not eliminate the need to trust the operator. The service user receives no admin role and no general property-write permission. The endpoint accepts only that specific interactive service user and writes only this integration’s property family.
Limits that matter
This is an independent community project, not a ServiceNow service. A successful login or property update is not proof that an official inactivity counter has changed. Reclamation and availability remain controlled by ServiceNow. Keep using the Developer Site and maintain backups. CAPTCHA, MFA and external identity-provider challenges require manual intervention.
Removal and history
Each instance provides an inspectable removal script and a JSON export. Activity is split into bounded archive properties as needed. Deleting a local instance deletes its encrypted credential and local history; it does not execute a remote removal script.