Knowledgebase
Help articles for accounts, billing, licences, and common compiler questions.
Security Best Practices
Security is built into the Pyvorin platform through authentication, rate limiting, and privacy-conscious telemetry. Account securityUse a strong, unique password.Enable two-factor authentication from the Security page.Review active sessions and revoke devices you do not recognize. API tokensCustomer API tokens are hashed in the database. Create tokens with only the abilities you need (read or read-write) and rotate them periodically. Telemetry privacySource code is not uploaded by default.Command text is hashed unless you explicitly opt in.MAC addresses are hashed; IP addresses are retained with limits. Reporting security issuesEmail security@pyvorin.com or open a confidential support ticket. Do not disclose vulnerabilities in public channels.
Updated 1 month ago
API Token Leaked
If you suspect an API token has been leaked, revoke it immediately. Go to API Tokens in the Portal.Find the token.Click Revoke. Create a new token with the minimum required abilities and update your integrations.
Updated 1 month ago
Suspicious Device
If you see a device you do not recognize in your licence list, revoke it immediately. After revoking, change your Portal password and review your API tokens. Contact support if you believe your account was compromised.
Updated 1 month ago
Rotate Tokens
Rotate API tokens and licence keys periodically as part of good security hygiene. Rotating a token invalidates the old one. Update your scripts and CI secrets before removing the old token.
Updated 1 month ago