This notice describes how the KAUSYN website and application handle information. Customer deployments may include additional contractual or jurisdiction-specific terms.
Demo requests may include your name, work email, organization, role, use case and non-sensitive deployment context. Do not send passwords, customer datasets, health records, financial account data or other sensitive records through the public contact form.
Authenticated KAUSYN deployments may process account, organization, project, dataset metadata, audit events and private customer files. Customer data handling is governed by the deployment configuration and applicable customer agreement.
Information is used to operate the service, respond to requests, secure the platform, support users, investigate incidents and improve product reliability. KAUSYN does not need raw customer rows for public-site demo requests.
The public marketing pages do not require advertising cookies. The authenticated application uses security-related cookies for server-side sessions, CSRF protection and sign-in flows.
Information may be processed by infrastructure, identity, security, support or communication providers configured for a deployment. KAUSYN does not sell user data to advertisers.
Retention depends on the data category, deployment needs, security obligations and customer agreements. Data should be kept only as long as necessary for those purposes, subject to legal or security requirements.
KAUSYN is designed around tenant isolation, least-privilege database roles, server-side sessions, private file storage boundaries and auditable events. No system can guarantee absolute security, and production deployments require environment-specific security validation.
Depending on applicable law and the relationship with KAUSYN, you may have rights concerning access, correction, deletion, restriction or objection. Use the contact page to submit a privacy-related request without including sensitive records.
This notice may change as KAUSYN moves from staging to commercial deployment, adds processors or enters new jurisdictions. Material changes should be reflected by updating this page and its effective date.