SECURITY
Built for executive trust.
Crafted Virtue handles voice, reputation, content, social publishing, and enterprise approval data. Security is treated as a product requirement, not a back-office concern.
Last updated: May 2026
SECURITY
Crafted Virtue handles voice, reputation, content, social publishing, and enterprise approval data. Security is treated as a product requirement, not a back-office concern.
Last updated: May 2026
Your drafts, your voice model, your data — isolated to you. Your voice data trains only your model, and drafts are visible to no one until you approve them.
Crafted Virtue should protect sensitive information at rest and in transit. User content, writing samples, connected-channel metadata, analytics, and approval logs should be handled according to appropriate security controls.
Connected publishing channels are sensitive. Tokens and channel permissions should be stored securely, never displayed in the UI, and revocable by the user or administrator.
Publishing workflows should enforce approval state before content can be scheduled or sent to connected channels. High-risk, failed, or enterprise-governed content should route through additional review.
Important actions should be logged, including sign-ins, content creation, content edits, approvals, publishing attempts, failed jobs, billing events, role changes, and enterprise compliance actions.
Security and reliability incidents should be triaged, investigated, remediated, and documented. Users or enterprise administrators should be notified when incidents materially affect their workspace or data.
If you believe you have discovered a vulnerability, contact the Crafted Virtue team through the security contact channel. Please avoid accessing, modifying, or disclosing user data.
Questions about how Crafted Virtue handles trust, data, or AI?