Cryptage Letter
Cryptage Letter prepares the HTML letter for mail servers. When it is on, non-ASCII letters can be written as numeric HTML references and the message is serialized as standard MIME. The preview stays readable, and the letter you edit is not replaced. This is not end-to-end encryption, and it does not hide text or try to evade a filter.
- Included on every pack
- Readable preview, encoded source when on
- UTF-8 HTML and a plain-text copy
- Original letter stays editable
- No public key is required
Cryptage Sender Name
Cryptage Sender Name prepares an international display name for mail servers. The mailbox address stays visible and stays on the account you connected. Diagnostics still read the SPF, DKIM, and DMARC records you publish. The product does not spoof a brand or send as a domain you do not control.
- Display-name management and previews
- Consistency checks across a campaign
- SPF, DKIM, and DMARC diagnostics
- Sender-domain alignment guidance
Cryptage Subject
Cryptage Subject prepares an international subject for mail servers. The words stay the same. A separate review can still flag length, clarity, and whether the subject matches the body. It is not a claim about where the message will land.
- Subject suggestions and previews
- Length and mobile inbox preview
- Misleading-language and spam-risk indicators
- Subject and body consistency
Deliverability Risk Analyzer
Run a preflight on the message you are about to send: HTML structure, links, authentication, and whether the subject agrees with the body. Findings are estimated diagnostic indicators with a recommended next step. They are not a spam score you can treat as a guarantee, and they are not an inbox prediction.
- HTML and URL analysis
- Authentication and sender configuration warnings
- Bounce-risk explanations
- Recommendations you can act on before sending
Link Tracking
Click tracking, when a workspace is entitled, would count a measured request to a disclosed link and show it beside campaign analytics. It would not estimate human engagement, and it would not disguise the destination. Operator is the first plan that includes it. Signal does not. Array, which sits above Operator in the catalog, includes it as well. The preview workspace has no catalog subscription, so the control refuses the request on the server. Click collection itself is not built yet: an entitled plan would receive a clear placeholder rather than invented numbers.
- Included from Operator upward
- Consent, unsubscribe, and privacy copy stay visible
- HTTPS destinations only, with credential links rejected
- No open redirect and no stored clicks in this preview