Encrypted keys
Keys to models and services are encrypted with AES-256-GCM, bound to their record. Once saved they cannot be read in the dashboard or through the API: only the last characters are shown.
Pennao stores keys to paid services and texts that are not published yet. This page describes how we protect them and where they go.
Keys to models and services are encrypted with AES-256-GCM, bound to their record. Once saved they cannot be read in the dashboard or through the API: only the last characters are shown.
Every request checks that the resource belongs to your organization. Keys, projects and the knowledge base of one organization never reach another organization’s jobs.
Owner, admin, copywriter, viewer and custom roles. API tokens have scopes and work only within the permissions of the person who created them.
Page fetching and customer service addresses go through a filter for private and internal addresses, checked again at every redirect.
Every delivery carries an HMAC-SHA256 signature with a timestamp. Rotate the secret without downtime; private addresses are rejected.
We record who created an order, edited text, added a key or changed permissions, with the date, IP address and type of access.
The content you generate goes through the model behind your key. By choosing a provider, you choose the data processing terms that apply to it.
Pennao does not archive your content or keep backups of it for you. Deleted articles and accounts are removed permanently. Export anything you want to keep: Markdown, HTML and JSON are one click away.
Write to us before you publish anything. We confirm reports within two business days and keep you updated. We take no legal action against people who report vulnerabilities in good faith.
Reporting address
security@pennao.comWe answer security questionnaires and prepare a data processing agreement on request.