API Terms of Use

1. Introduction

The Vexor API allows approved developers to integrate Vexor data, authentication, and platform functionality into their own products, services, or internal tools. Access is a privilege granted at the sole discretion of Vexor and may be limited, suspended, or revoked at any time in order to protect users, the platform, and our infrastructure.

By using the Vexor API, you (“Developer”, “you”) acknowledge that you are entering into a binding agreement with Vexor and that you have the authority to accept these Terms on behalf of yourself or the organization you represent.

2. Developer Account Requirements

To obtain and maintain access to the Vexor API, you must:

• Maintain an active Vexor developer account in good standing.
• Provide accurate and up-to-date contact, identity, and (if applicable) business information.
• Ensure that all information submitted during registration and verification remains correct and complete.
• Keep API keys, client secrets, and OAuth credentials confidential and never share them publicly or embed them in client-side code.
• Promptly notify Vexor if you suspect any compromise of your credentials.

Vexor may require periodic re-verification of developer accounts, including additional documentation about your organization, security practices, and the nature of your integration. Failure to provide requested information may result in suspension or termination of API access.

3. Acceptable Use of the API

You agree to use the Vexor API only for lawful, authorized, and clearly disclosed purposes. You agree NOT to use the API to:

• Scrape, harvest, or export user data without explicit, informed user permission.
• Circumvent platform restrictions, automate abusive behavior, or simulate fake engagement.
• Interfere with or degrade the performance, security, or stability of Vexor services.
• Build services that directly clone core Vexor functionality using proprietary or non-public data.
• Collect personal data for purposes that users have not been clearly informed of or have not consented to.
• Create “shadow profiles” or hidden user dossiers using Vexor data or metadata.
• Engage in profiling, discrimination, or surveillance contrary to privacy and human rights standards.
• Use the API in violation of any applicable law, regulation, or third-party rights.

4. Data Access & Privacy

Developers are responsible for handling all data accessed via the Vexor API in full compliance with applicable privacy and data protection laws, including but not limited to:

• General Data Protection Regulation (GDPR) for EU/EEA data subjects.
• California Consumer Privacy Act (CCPA) and related U.S. state privacy laws where applicable.
• Any local privacy, youth protection, or data localization laws in regions where you operate.

You must also comply with Vexor’s Privacy Policy, Community Guidelines, and any API-specific data access limitations communicated in documentation or separate agreements.

4.1 User Consent & Transparency

You may only access or process user-related data via the API when:

• The user has granted explicit, informed consent to your application.
• You clearly describe what data is being accessed and for what purpose.
• Users are provided with an easy method to revoke access and request deletion of their data.

4.2 Data Handling & Storage

All data obtained via the API must be:

• Stored securely using industry-standard encryption and access controls.
• Retained only for as long as necessary to provide the features users opted into.
• Deleted promptly upon user request or when no longer needed.
• Not resold, repurposed, or shared with third parties without explicit permission from both Vexor and affected users, where applicable.

5. Rate Limits & Quotas

Vexor implements API rate limits, quotas, and concurrency controls to protect platform stability and ensure fair access across developers. Limits may be defined per API key, per IP address, per user, or per application.

Exceeding assigned limits may result in:

• Temporary throttling or HTTP rate-limit responses.
• Automated suspension of your API key(s).
• Permanent termination of access in cases of repeated or egregious abuse.

You must implement appropriate backoff and retry logic and may not attempt to bypass rate limits, including by creating multiple keys, accounts, or using rotating IP addresses.

6. Branding & Attribution

Applications that integrate the Vexor API must comply with Vexor’s Brand Asset Guidelines and any developer branding requirements. Where required by documentation, you must display attribution such as: “Powered by Vexor” or “Integrated with the Vexor API”.

You may not:

• Alter, distort, or misuse Vexor trademarks or logos.
• Imply that Vexor endorses, sponsors, or officially partners with your application without written agreement.
• Use the Vexor name in your application’s primary branding, domain names, or company name without permission.

7. Security Requirements

You are responsible for implementing robust security measures to protect API keys, tokens, and all data accessed through the Vexor API.

• Store API keys and client credentials on secure, server-side environments only.
• Do not embed API keys in client-side code, mobile apps, or public repositories.
• Encrypt OAuth tokens and sensitive data at rest and in transit.
• Use HTTPS (TLS) for all communications with Vexor endpoints.
• Implement proper authentication and authorization checks in your application.
• Maintain logs sufficient to detect unauthorized access or misuse of API privileges.

You must notify Vexor at security@vexor.to within 24 hours of discovering any actual or suspected security incident or data breach involving API data or credentials. Your notification should include relevant technical details, impact assessment, and mitigation steps taken.

8. Prohibited Content & Actions

You may NOT use the Vexor API to build, support, or enable:

• Surveillance tools or user-tracking systems that violate privacy or civil liberties.
• Stalking, harassment, or targeting of individuals or protected groups.
• Deepfake or synthetic media tools that do not clearly disclose synthetic nature to users.
• Applications promoting hate, violence, extremism, or illegal activities.
• Unauthorized scraping, archiving, or bulk export of Vexor content.
• Services designed to bypass user privacy controls, blocking, or safety tools.

Any use of Vexor data in connection with law enforcement, background checks, credit scoring, or employment screening requires explicit, prior written approval from Vexor and must comply with applicable law.

9. Commercial Use & Fees

Access to the Vexor API for commercial or production use may require a paid subscription or a separate enterprise agreement. Vexor may offer various tiers, for example:

• Sandbox / Free Tier: Limited rate limits, restricted datasets, and non-production usage.
• Pro Tier: Higher rate limits, broader feature access, and priority support.
• Enterprise Tier: Custom SLAs, dedicated support, and tailored integrations under a separate contract.

Vexor reserves the right to update pricing, rate limits, or commercial terms at any time. Any such changes will typically be communicated in advance via developer documentation or email.

10. Termination of Access

Vexor may suspend, restrict, or permanently revoke your API access, without liability, if:

• You violate these API Terms, the Vexor Terms of Service, or any applicable law.
• Your application compromises platform performance, user safety, or security.
• You fail to address security vulnerabilities or policy violations after notice.
• Your application becomes malicious, unstable, or is used for harmful purposes.

Upon termination, you must immediately cease all API calls and securely delete any cached or stored Vexor data unless retention is required by law and you have notified Vexor accordingly.

11. Intellectual Property

Access to the Vexor API grants you a limited, revocable, non-exclusive, non-transferable license to call API endpoints in accordance with these Terms. It does not grant you ownership of:

• Any Vexor software, code, or underlying technology.
• User-generated content accessed through the API.
• Vexor trademarks, logos, or brand assets.
• Proprietary algorithms, ranking signals, or recommendation systems.

All rights not expressly granted here are reserved by Vexor and its licensors.

12. Liability Disclaimer

The Vexor API is provided on an “AS IS” and “AS AVAILABLE” basis. To the fullest extent permitted by law, Vexor disclaims all warranties, express or implied, including but not limited to:

• Availability, uptime, or uninterrupted access to the API.
• Accuracy, completeness, or timeliness of data returned by the API.
• Fitness of the API for any particular purpose or integration.

Vexor shall not be liable for any indirect, incidental, consequential, special, or punitive damages arising from or related to your use of the API, including but not limited to loss of profits, revenue, data, or goodwill, even if advised of the possibility of such damages.

13. Changes to the API & Terms

Vexor may modify, deprecate, or discontinue API endpoints, features, or data fields at any time. We aim to provide reasonable notice for breaking changes via developer channels, but we cannot guarantee backward compatibility in all cases.

Vexor may also update these API Terms periodically. Your continued use of the API after changes become effective constitutes acceptance of the updated Terms. If you do not agree to the changes, you must discontinue all use of the API.

14. Contact Information

For API access, technical assistance, or to report misuse of the Vexor API, contact:

Developer Support: dev@vexor.to
Security Issues: security@vexor.to
Legal & Compliance: legal@vexor.to