Skip to main content
Legal

Compliance Policy

Effective Date: January 9, 2026 | Last Revised: January 9, 2026

This Compliance Policy outlines how Cortexvia, operated by Shaik Afrid, trading as Cortexvia Technologies ("Company," "we," "us," or "our") maintains regulatory compliance and fulfills legal obligations in the operation of our AI chatbot platform and related services. Our compliance framework is designed to meet applicable legal requirements while enabling the delivery of innovative AI services. This policy should be read in conjunction with our Terms of Service, Privacy Policy, Data Usage Policy, Security Policy, Cookie Policy, API Policy, Developer Policy, and Refund Policy (collectively, the "Agreement"). The Company reserves the right to modify this policy at any time, and your continued use of the Services constitutes acceptance of any modifications.

1. Security Compliance Framework

1.1. Infrastructure Controls. Cortexvia hosts data on managed cloud infrastructure operated by contracted providers with established security controls and operational safeguards. 1.2. Application Security. At the application level, sensitive user data including passwords, authentication cookies, session tokens, and API keys is protected using industry-standard cryptographic protocols. Passwords are hashed using bcrypt or equivalent algorithms with appropriate work factors. Session tokens employ cryptographic randomness and expiration controls. 1.3. Access Isolation. User data is logically isolated at the application and database levels to prevent unauthorized cross-account access. Access controls are enforced at multiple layers including network, application, and database levels. We implement the principle of least privilege for all system access, including internal administrative access. 1.4. Continuous Assessment. We conduct regular security assessments, vulnerability scanning, and penetration testing to identify and address potential security weaknesses. Findings are prioritized based on risk and addressed according to defined remediation timelines.

2. Data Protection Rights

2.1. Access Rights. Users have the right to access their personal data stored within the Services. Access can be exercised through dashboard features that provide visibility into stored data, or by submitting a formal request to our support team for comprehensive data export. 2.2. Rectification Rights. Users have the right to request correction of inaccurate or incomplete personal data. Corrections to account information can typically be made directly through the dashboard. For corrections to other data, users should submit a request specifying the data to be corrected and the accurate information. 2.3. Erasure Rights. Users have the right to request deletion of their personal data, subject to the retention requirements and limitations described in our Data Usage Policy. Deletion requests result in immediate removal from production systems, though data may persist in encrypted backups for up to seven days. 2.4. Objection Rights. Users have the right to object to certain data processing activities, particularly processing for direct marketing purposes. Objection requests should specify the processing activity being objected to and will be evaluated in accordance with applicable law. 2.5. Portability Rights. Where technically feasible and required by applicable law, users may request their data in a structured, commonly-used, machine-readable format to facilitate transfer to another service provider. 2.6. Request Processing. All rights requests are subject to identity verification to prevent unauthorized access to personal data. Requests are processed within timeframes required by applicable law, typically within thirty (30) days. Complex requests may require additional time with appropriate notification.

3. Legal Jurisdiction and Dispute Resolution

3.1. Governing Law. These terms and all policies within the Agreement are governed by and construed in accordance with the laws of the jurisdiction in which Cortexvia Technologies is established, without regard to its conflict of law provisions. 3.2. Exclusive Jurisdiction. Any legal action or proceeding arising out of or related to the Agreement or the Services shall be brought exclusively in the courts of competent jurisdiction where Cortexvia Technologies is established. Users consent to the personal jurisdiction of such courts and waive any objection to venue. 3.3. Pre-Litigation Notice. Prior to initiating any legal proceedings, the aggrieved party shall provide written notice to the other party describing the dispute and proposed resolution. The parties shall engage in good-faith negotiations for a period of thirty (30) days following receipt of such notice. 3.4. Escalation Process. If initial negotiations do not resolve the dispute, the parties may proceed with formal dispute resolution. The recommended escalation path is: First Notice with response period of thirty (30) days, Second Notice with additional response period of thirty (30) days, Final Notice with final response period of thirty (30) days, then Court Proceedings if unresolved. 3.5. Mutual Legal Rights. Both Cortexvia and users reserve the right to take legal action if the other party materially violates the terms of the Agreement. Legal costs and fees shall be borne according to the determination of the court.

4. Government Data Access

4.1. Legal Process Requirements. Cortexvia will only disclose user data to government authorities in response to valid legal process, such as subpoenas, court orders, or other lawful requests that meet applicable legal standards. We do not voluntarily disclose user data to governments absent valid legal process. 4.2. Request Verification. All government data requests are verified for authenticity and legal validity before any disclosure. Requests that appear to be invalid, overly broad, or inconsistent with applicable law may be challenged. 4.3. Retrieval Limitations. Data retrieval in response to legal process is subject to the technical limitations of our systems. Data that has been deleted from production databases may only be available if the request is received within our seven-day backup retention window. We cannot guarantee successful data retrieval from backups. 4.4. Processing Time. Responding to legal process takes time for verification, legal review, and technical retrieval. Emergency requests will be prioritized, but standard requests are processed in the order received. 4.5. User Notification. Where legally permitted, we will endeavor to notify affected users of government data requests to allow them the opportunity to seek legal protection. However, notification may be prohibited or delayed by law in certain circumstances.

5. Multi-Jurisdictional Service Delivery

5.1. Global Service Architecture. The Services are delivered through a globally distributed infrastructure designed for performance and reliability. This architecture involves multiple data processing locations, content delivery nodes, and computational endpoints across various geographic jurisdictions. 5.2. Data Location Variability. User data may be stored, processed, or transmitted across multiple geographic locations depending on operational requirements, load balancing decisions, and infrastructure availability. Specific data location guarantees are not provided unless explicitly agreed in separate enterprise arrangements. 5.3. Third-Party Processing Locations. Certain service components involve processing by third-party service providers operating their own infrastructure in locations determined by their operational requirements. By using the Services, users acknowledge that their data may be processed in jurisdictions other than their country of residence. 5.4. Compliance Responsibility Allocation. Users are responsible for ensuring their use of the Services complies with applicable laws in their jurisdiction, including any restrictions on cross-border data transfers, data localization requirements, or industry-specific regulations. Cortexvia makes no representations regarding the suitability of the Services for use subject to specific regulatory requirements.

6. Policy Hierarchy and Interpretation

6.1. Document Precedence. In the event of a conflict between provisions of different policy documents within the Agreement, the following precedence applies: Terms of Service provisions take precedence over other policies; Privacy and Data Protection provisions take highest priority among all other policies for matters relating to personal data; subsequently, specific subject-matter policies apply to their respective domains. 6.2. Version Control. Updated policies automatically supersede and replace all previous versions upon posting. The effective date and last revised date at the top of each policy document indicate the currently applicable version. 6.3. Interpretation. Ambiguous provisions shall be interpreted in a manner consistent with the overall intent of the Agreement and standard industry practices for similar services. Provisions shall be interpreted to be enforceable to the maximum extent permitted by applicable law.

7. Legal Severability

7.1. Severability Clause. If any provision of the Agreement is found by a court of competent jurisdiction to be invalid, illegal, or unenforceable, such finding shall not affect the validity, legality, or enforceability of any other provision. The remaining provisions shall continue in full force and effect. 7.2. Reformation. Invalid or unenforceable provisions shall be reformed to the minimum extent necessary to make them valid, legal, and enforceable while preserving the original intent to the maximum extent possible. 7.3. Essential Terms. Notwithstanding the foregoing, if any provision deemed essential to the fundamental bargain of the Agreement is found unenforceable, the parties shall negotiate in good faith to replace such provision with an enforceable provision that achieves the original intent.

8. Regulatory Evolution

8.1. Evolving Requirements. The regulatory landscape for AI services, data protection, and cloud computing continues to evolve. Cortexvia monitors regulatory developments and updates policies and practices as appropriate to maintain compliance with applicable legal requirements. 8.2. User Responsibility. Users are responsible for staying informed about regulatory requirements applicable to their specific use cases, industries, and jurisdictions. The Services are provided as general-purpose tools, and users must determine whether specific uses comply with applicable regulations. 8.3. No Legal Advice. Nothing in the Agreement or these policies constitutes legal advice. Users should consult qualified legal counsel for guidance on specific regulatory compliance questions.

9. Contact Information

If you have any questions about this Compliance Policy, please contact us at:

Cortexvia
General Support: [email protected]
Legal Inquiries: [email protected]

By using the Cortexvia Services, you acknowledge that you have read and understood this Compliance Policy and agree to be bound by its terms.