Your operation. Your data. Protected.
How Kresynt protects customer information — written so your IT and security teams can review it directly.
Powered by a modern technology stack, not legacy software.
Kresynt connects people, workflows and operational information on a modern platform. Layered security controls help protect customer data across the application and database.
Practices by area
Layered controls protect customer information. Additional documentation is available on request for your security review.
Customer separation
- Customer isolation enforced in both the application and database
- Account membership checked on each request
- Automated cross-account access tests before each release
Sign-in protection
- Two-step verification using a one-time email code
- Password checks against common and breached passwords
- Salted, one-way password hashing with Argon2
Encryption and hosting
- TLS 1.2 or higher for connections
- Encryption at rest for databases, stored files and backups
- Microsoft Azure hosting in US data centers
Controlled access
- Records visible to their owners or explicitly authorized recipients
- Private, expiring links for authorized file access
- Production access limited to named administrators
Backups and recovery
- Daily backups with daily, weekly and monthly retention for up to one year
- Copies replicated to a second Azure region
- Database backups in locked, immutable storage
Security operations
- Automated tests for access, customer isolation, sign-in and file handling
- Security reviews informed by the OWASP Top 10
- Security advisories monitored and fixes applied promptly
Audit and monitoring
- Record changes logged with who made the change and when
- Passwords and access tokens excluded from audit logs
- Backup health, service availability and storage activity monitored
Customer data
- Customer-supplied content rights remain with customers and their licensors
- Structured-data export and retention governed by the Terms
- No model training without separate express written customer opt-in
Security across the platform
Customer separation, controlled access and recovery practices work together to protect operational records.
Access
Two-step verification, account membership and permissions
Application
Customer separation checked on every request
Database
Independent enforcement of customer separation
Recovery
Encrypted backups replicated to a second Azure region
Security questions
How does Kresynt protect customer information?
Kresynt uses layered controls: customer separation in both the application and database, encryption in transit and at rest, two-step verification, encrypted backups, automated security tests and monitoring.
Where is Kresynt hosted?
Kresynt runs on Microsoft Azure in US data centers. Provider processing can occur in other countries as described in the Privacy Policy; US hosting is not a promise that every processing operation stays in the United States.
Is our data used to train AI models?
Kresynt does not use customer content to train or fine-tune AI models, or authorize its providers to do so, without the customer's separate express written opt-in. Processing a requested AI output, search or translation is service processing, not model training.
Can we export our data?
Authorized administrators may request a standard JSON export of stored structured data under the Terms. Standard exports exclude attachment files; the Terms describe limited assisted attachment retrieval after an unexpected cutoff and applicable retention protections.
How do you support a security review?
Contact [email protected] to request additional documentation or discuss your vendor security questionnaire.
What technology foundation does Kresynt use?
Powered by a modern technology stack, not legacy software. Kresynt connects operational workflows on a modern platform, supported by the security controls described here.
How do we report a security concern?
Email [email protected]. Report the concern without including passwords or verification codes. Kresynt investigates security incidents and notifies affected customers without undue delay, consistent with applicable law and its agreements.
Security contact
Email [email protected] for questionnaires, documentation requests and vulnerability reports.