Privacy Policy

1. Introduction

At Klyr, we prioritize the privacy and security of our users' data. This Privacy Policy outlines how Klyr, operated by YOKR SASU, collects, uses, and protects personal information when users access or interact with our platform. It also explains users' rights regarding their data and our commitments to transparency and compliance with data protection laws.

1.1 Purpose

The purpose of this Privacy Policy is to provide users with a clear understanding of:

  • The types of data we collect.
  • How and why we process that data.
  • The measures we take to protect data privacy.

By using Klyr, users consent to the practices described in this Privacy Policy. If users do not agree with any part of this policy, they are advised to discontinue using our platform.

1.2 Our Commitment to Privacy

YOKR SASU is committed to:

  • Complying with applicable data protection regulations, including the General Data Protection Regulation (GDPR) in the European Union.
  • Ensuring that user data is handled responsibly and securely.
  • Providing users with control over their personal information.

1.3 Applicability

This Privacy Policy applies to:

  • All users of Klyr, regardless of their location.
  • Data collected through Klyr's platform, integrations (e.g., Telegram), and related services.
  • Information shared directly with Klyr (e.g., during registration) and indirectly collected through cookies or other tracking technologies.

2. Data We Collect

Klyr collects and processes various types of data to deliver its services, enhance user experience, and maintain platform security. Below is an overview of the data we collect and why it is necessary.

2.1 Personal Information

We collect personal information directly from users when they interact with Klyr, including but not limited to:

  1. Contact Information:
    • Examples: Name, email address, phone number.
    • Purpose: Used for account creation, communication, and customer support.
  2. Payment Details:
    • Examples: Credit card information, billing address.
    • Purpose: Required for processing payments and issuing invoices for Klyr's services.

2.2 Usage Data

Usage data is collected automatically when users interact with Klyr to monitor platform performance and improve functionality:

  1. Log Information:
    • Examples: IP addresses, browser type, operating system.
    • Purpose: Used to analyze platform usage, detect and prevent fraud, and optimize user experience.
  2. Interaction Logs:
    • Examples: Messages processed by Klyr's AI, timestamps of interactions.
    • Purpose: Necessary for providing AI-driven services and enhancing response accuracy.

2.3 Cookies and Tracking Technologies

Klyr uses cookies and similar tracking technologies to collect data about user interactions:

  1. Cookies:
    • Types: Essential cookies, analytical cookies, and marketing cookies.
    • Purpose: Enable platform functionality, analyze usage trends, and deliver personalized experiences.
  2. Third-Party Tracking:
    • Examples: Google Analytics for user behavior analysis.
    • Purpose: Used to improve platform performance and inform product development.

2.4 Special Data Categories

Klyr does not intentionally collect sensitive personal data (e.g., health information, political opinions). Users are advised not to share such information through the platform.

3. How We Use Collected Data

Klyr processes collected data to provide its services, ensure platform security, and improve the overall user experience. This section details the purposes for which data is used and the corresponding legal bases under GDPR.

3.1 Service Delivery

The primary purpose of data collection is to enable Klyr to provide its services efficiently and effectively:

  1. Account Management:
    • Data such as usernames, email addresses, and passwords is used to create and manage user accounts.
  2. AI Functionality:
    • Interaction logs and usage data allow Klyr's AI to respond to queries, manage community discussions, and improve contextual accuracy.
  3. Payment Processing:
    • Financial information is processed securely to complete transactions and maintain compliance with legal accounting requirements.

3.2 Communication

Klyr uses collected data to communicate with users:

  1. Service Updates:
    • Notifications about feature changes, maintenance schedules, or platform developments.
  2. Support:
    • Responding to user inquiries and resolving issues related to the platform.

3.3 Personalization

To enhance user experience, Klyr may use data to:

  1. Customize AI Responses:
    • Tailoring responses based on past interactions or user preferences.
  2. Improve Recommendations:
    • Suggesting features or tools based on user activity patterns.

3.4 Security and Fraud Prevention

Klyr prioritizes the security of its platform and users' data:

  1. Fraud Detection:
    • Usage data and log files are analyzed to identify suspicious activity or unauthorized access.
  2. Platform Monitoring:
    • Continuous monitoring ensures the integrity of Klyr's systems and prevents misuse.

3.5 Analytics and Improvement

Klyr uses data to understand how the platform is used and to identify opportunities for improvement:

  1. Usage Trends:
    • Analyzing aggregate data to identify popular features or pain points.
  2. Development Insights:
    • Using feedback to inform product updates and optimize platform performance.

3.6 Compliance with Legal Obligations

Klyr processes certain data to comply with:

  1. Regulatory Requirements:
    • Examples: Tax reporting, accounting standards.
  2. Legal Requests:
    • Data may be shared with authorities if required by law or court orders.

4. Legal Basis for Data Processing

Under the General Data Protection Regulation (GDPR), Klyr processes user data based on specific legal bases. This section explains the principles guiding our data processing activities and how they align with regulatory requirements.

4.1 User Consent

  1. Explicit Consent:
    • Users provide explicit consent during account registration, agreeing to the collection and processing of their personal data as described in this Privacy Policy.
    • Examples:
      • Accepting terms when creating an account.
      • Opting in to cookies or marketing communications.
  2. Revocation of Consent:
    • Users can withdraw consent at any time without affecting the lawfulness of prior processing.
    • Example: Disabling cookies through browser settings or managing consent preferences in the user dashboard.

4.2 Contractual Obligations

  1. Service Fulfillment:
    • Data processing is necessary to deliver Klyr's services as described in the Terms of Service.
    • Examples:
      • Using user details to create accounts and process payments.
      • Logging interactions for accurate AI responses.
  2. Account Management:
    • Personal information is processed to enable core functionalities, such as password recovery or personalized settings.

4.3 Legal Compliance

  1. Regulatory Requirements:
    • Data processing ensures compliance with laws and regulations, including:
      • Tax reporting and financial audits.
      • Responding to legal requests or court orders.
  2. Data Retention for Legal Purposes:
    • Certain data may be retained for a legally required period, such as financial records for tax compliance.

4.4 Legitimate Interests

  1. Improving Services:
    • Klyr processes data to enhance platform performance, functionality, and user satisfaction.
    • Example: Analyzing usage patterns to optimize features or fix issues.
  2. Security Measures:
    • Processing usage logs and interaction data helps detect fraud, prevent abuse, and maintain the integrity of the platform.

5. Data Sharing and Disclosure

Klyr values user trust and takes a transparent approach to sharing data with third parties. This section outlines the circumstances under which data may be shared and the safeguards in place to protect user privacy.

5.1 Internal Use

  1. YOKR SASU Operations:
    • Data is shared within YOKR SASU to support essential operations, including platform development, customer support, and compliance monitoring.
  2. Team Access:
    • Access to user data is restricted to authorized personnel based on their role and responsibilities.

5.2 Third-Party Service Providers

  1. Partnerships:
    • Klyr works with reputable third-party service providers to deliver specific functionalities, such as:
      • Payment processing (e.g., Stripe, PayPal).
      • Cloud storage and hosting (e.g., RENDER, potential future Filecoin integration).
      • Analytics tools (e.g., Google Analytics) to monitor platform performance.
  2. Safeguards:
    • These providers are required to adhere to strict data protection standards and process data only as instructed by Klyr.
    • Example: Encryption during payment transactions to protect financial data.

5.3 Legal Obligations

  1. Compliance with Laws:
    • User data may be disclosed to comply with legal obligations, such as:
      • Responding to valid court orders or law enforcement requests.
      • Addressing claims of intellectual property infringement or other legal disputes.
  2. Protection of Rights:
    • Klyr may disclose data if necessary to:
      • Protect its legal rights or the safety of its users.
      • Investigate and respond to fraudulent or harmful activities.

5.4 Business Transactions

  1. Mergers and Acquisitions:
    • In the event of a merger, acquisition, or sale of YOKR SASU, user data may be transferred to the acquiring entity as part of the transaction.
  2. User Notification:
    • Users will be informed of such transfers and any significant changes to data handling practices.

6. Data Storage and Retention

Klyr ensures that user data is securely stored and retained only for as long as necessary to fulfill its purposes. This section explains where data is stored, how long it is retained, and how users can manage their data.

6.1 Storage Location

  1. Current Infrastructure:
    • Data is stored on secure servers hosted by RENDER, ensuring compliance with GDPR and other applicable standards.
  2. Future Decentralization:
    • Plans to integrate decentralized storage solutions (e.g., Filecoin) aim to provide enhanced user control and transparency in data management.

6.2 Data Retention Periods

  1. Retention Guidelines:
    • Personal data is retained based on its purpose:
      • Account Information: Retained as long as the user account is active.
      • Payment Data: Retained for the duration of the transaction and as required for financial records (e.g., seven years for tax compliance).
      • Interaction Logs: Retained temporarily to optimize AI functionality, then anonymized or deleted.
  2. Archived Data:
    • Certain data may be archived for legal or research purposes, provided it is anonymized to protect user identities.

6.3 User Data Management

  1. Access and Portability:
    • Users can request a copy of their data, formatted for easy transfer to another service.
    • Example: Downloading interaction logs or account details.
  2. Correction and Deletion:
    • Users can request corrections to inaccurate data or deletion of their data through the user dashboard or by contacting support.
    • Exceptions: Data required for legal or regulatory compliance cannot be deleted immediately.
  3. Deactivation:
    • When users deactivate their accounts, their personal data is anonymized or deleted unless retention is required by law.

6.4 Security Measures

  1. Encryption:
    • Data is encrypted during transmission and storage to protect against unauthorized access.
  2. Access Restrictions:
    • Data access is limited to authorized personnel and governed by strict access control policies.
  3. Regular Audits:
    • Klyr conducts regular security audits to identify and address vulnerabilities in its systems.

 

7. User Rights

Klyr is committed to empowering users with control over their personal data. This section outlines the rights users have under GDPR and how they can exercise those rights.

7.1 Access to Data

  1. Right to Know:
    • Users have the right to request confirmation about whether Klyr processes their personal data.
    • Upon request, users will be provided with a copy of their personal data, including:
      • Categories of data processed.
      • Purpose of data processing.
      • Recipients of the data, if shared.
  2. How to Request:
    • Users can submit data access requests through Klyr's user dashboard or by contacting support at the provided email address.

7.2 Correction or Deletion

  1. Right to Rectification:
    • Users can request corrections to inaccurate or incomplete personal data.
    • Example: Updating a misspelled name or incorrect contact information.
  2. Right to Erasure ("Right to Be Forgotten"):
    • Users can request the deletion of their personal data under the following conditions:
      • The data is no longer necessary for the purpose for which it was collected.
      • The user withdraws consent, and there are no overriding legal grounds for processing.
      • The data was unlawfully processed.
  3. Exceptions:
    • Deletion requests may be denied if data must be retained for legal compliance, dispute resolution, or security purposes.

7.3 Data Portability

  1. Right to Transfer:
    • Users can request their data in a structured, commonly used, and machine-readable format to transfer to another service.
    • Example: Exporting data for integration with a different community management platform.
  2. Scope of Portability:
    • This right applies to data provided by the user and processed with their consent or based on contractual obligations.

7.4 Withdrawal of Consent

  1. Revocation Options:
    • Users can withdraw consent for specific data processing activities, such as:
      • Marketing communications.
      • Use of analytical cookies.
  2. Impact of Withdrawal:
    • Revoking consent may limit the availability of certain services or features.

7.5 Right to Object

  1. Scope of Objection:
    • Users can object to data processing based on legitimate interests, such as analytics or personalization.
    • Example: Opting out of data being used for platform performance analysis.
  2. How to Exercise:
    • Objections can be submitted through the user dashboard or by contacting Klyr support.

7.6 Right to Complain

  1. Filing Complaints:
    • Users can lodge complaints with their local data protection authority if they believe their rights have been violated.
  2. France's Supervisory Authority:
    • Users in the European Union can contact the French Data Protection Authority (CNIL) for escalated concerns.

8. Security Measures

The security of user data is a top priority for Klyr. This section outlines the measures YOKR SASU has implemented to protect data from unauthorized access, loss, or misuse.

8.1 Data Encryption

  1. During Transmission:
    • All data transmitted between users and Klyr servers is encrypted using industry-standard HTTPS protocols.
  2. At Rest:
    • Sensitive data stored on Klyr's servers is encrypted to protect against unauthorized access.

8.2 Access Control

  1. Role-Based Access:
    • Data access is restricted to authorized personnel based on their roles and responsibilities.
  2. Authentication:
    • Secure authentication mechanisms, such as multi-factor authentication (MFA), are implemented to prevent unauthorized account access.

8.3 Monitoring and Audits

  1. Continuous Monitoring:
    • Klyr's systems are monitored for suspicious activity or potential breaches.
  2. Regular Audits:
    • Security audits are conducted periodically to assess vulnerabilities and ensure compliance with security standards.

8.4 User Responsibilities

  1. Account Security:
    • Users are responsible for securing their account credentials. Klyr recommends using strong, unique passwords and enabling two-factor authentication where available.
  2. Reporting Issues:
    • Users must notify Klyr immediately if they suspect unauthorized access or notice unusual account activity.

8.5 Incident Response

  1. Data Breach Protocol:
    • In the event of a data breach, affected users will be notified within 72 hours of discovery, in compliance with GDPR requirements.
  2. Mitigation Measures:
    • Steps will be taken to contain the breach, assess its impact, and prevent future incidents.

9. Cookies and Tracking Policy

Klyr uses cookies and similar tracking technologies to enhance user experience and gather valuable insights into platform usage. This section details the types of cookies used, their purpose, and how users can manage them.

9.1 Types of Cookies

  1. Essential Cookies:
    • Purpose: Enable core functionality, such as user authentication and access to secure areas of the platform.
    • Example: Remembering login credentials for session continuity.
  2. Analytical Cookies:
    • Purpose: Track usage patterns and identify areas for improvement.
    • Example: Collecting anonymized data on page views or feature interactions.
  3. Marketing Cookies:
    • Purpose: Deliver personalized advertisements or promotional content.
    • Example: Retargeting users with ads based on their activity on Klyr.

9.2 Third-Party Tracking

  1. Analytics Tools:
    • Klyr uses tools like Google Analytics to analyze user behavior and optimize platform performance.
    • Data shared with third-party tools is anonymized and used solely for improving services.
  2. Advertising Platforms:
    • If applicable, marketing data may be shared with advertising platforms to deliver targeted ads.

9.3 User Control

  1. Managing Preferences:
    • Users can manage cookie preferences through:
      • Klyr's cookie consent banner.
      • Browser settings to block or delete cookies.
  2. Opt-Out Options:
    • Users can opt out of analytical or marketing cookies without affecting essential platform functionality.

9.4 Retention of Cookie Data

  1. Retention Periods:
    • Cookies are stored for defined periods based on their purpose:
      • Session cookies: Deleted when the browser is closed.
      • Persistent cookies: Retained for up to 12 months unless deleted by the user.
  2. User Rights:
    • Users can delete cookies at any time and adjust browser settings to limit future cookie storage.