Security · privacy · trust

Your fragments are
never anyone's training data.

Krytz reads everything you put into it — voice notes, contracts, half-finished thoughts. That sets a higher bar for how it's stored, transmitted, and processed than most productivity tools live up to.

E2E
Six commitments

Designed, not promised. Auditable in code.

🔐

Encryption in transit and at rest

Krytz uses standard transport security and encrypted storage for user data. Detailed controls are shared during customer security review.

🚫

Model training controls

Your workspace content is handled according to product privacy settings and contractual commitments. We avoid publishing provider-specific internals on the public site.

📤

Export anytime, anything

One-click export to Markdown + JSON. Bring it all over to a competitor in under 60 seconds if Krytz isn't for you.

Deletion requests

Users can request deletion of account data. Retention and deletion timelines are described in the Privacy Policy and customer agreements.

📍

Regional hosting options

Workspace hosting options may vary by plan and deployment. We confirm available regions during onboarding.

🔍

Decision activity history

Every priority change, every connected app write, every retention event — append-only log you can replay at any timestamp.

Data handling

How Krytz talks about trust
without exposing operating details.

Capture

User controlled input

You choose what to add to Krytz and which connected apps are allowed to contribute signal.

Transit

Protected movement

Data is protected while moving between your device, Krytz, and approved service providers.

Storage

Account-scoped records

Workspace records are scoped to your account and governed by access controls, retention settings, and deletion requests.

Review

Customer security review

Detailed controls, provider lists, and contractual terms are shared through the security review process rather than public marketing pages.

Security roadmap

Clear commitments. No inflated claims.

R

Security review

Formal review materials are provided to customers and partners during onboarding.

P

Privacy requests

Access, export, and deletion workflows are handled through documented support channels.

D

Data handling

Workspace data is processed only for product operation and user-requested workflows.

!

Responsible disclosure

Security reports are reviewed through a dedicated disclosure channel.

Service providers

The service categories behind Krytz.
High level by design.

Category Purpose Data class Notes
Cloud hosting Application delivery Account and workspace records Reviewed during customer onboarding
Email delivery Transactional messages Email address and message metadata Used for account workflows
Payment processing Billing Billing records only No workspace content
Product diagnostics Reliability and error review Technical metadata Content is minimized where possible

Detailed provider information is shared through security review and customer agreements.

Responsible disclosure

Found a vulnerability?
Tell us. We'll listen.

If you've found a security issue in any Krytz surface, please reach out before posting publicly.

We review reports through the security contact below and coordinate fixes based on severity.

↳ PGP key: 9F4E 2B3D 8C1A · fingerprint at /security/pgp.asc