Large Business API Access Terms
These terms govern enterprise-grade API access to Vibble for large businesses, media organizations, governments, and technology partners. They supplement the core API Terms of Use and apply where dedicated, high-volume, or commercial integrations are provided.
1. Scope & Relationship to Core API Terms
These Large Business API Access Terms (“Enterprise API Terms”) apply to organizations that receive:
- Higher or custom rate limits beyond the standard developer tier
- Dedicated endpoints (firehose, compliance streams, archive access)
- Commercial or paid API plans
- Custom contracts, SLAs, or enterprise support packages
Unless explicitly overridden in a signed enterprise agreement, all provisions in Vibble’s API Terms of Use continue to apply to enterprise integrations.
2. Eligibility & Onboarding
Enterprise API access is granted at Vibble’s discretion and generally restricted to:
- Large businesses, news/media organizations, and public institutions
- Verified brands with compliant use cases
- Trusted partners with a demonstrable need for high-volume data
- Vendors providing analytics, monitoring, or moderation services
Onboarding may require:
- Completion of an enterprise application form
- Company identity and beneficial ownership verification
- Security and compliance review of the proposed integration
- Execution of a written enterprise or data-processing agreement
3. Permitted Use Cases
Enterprise API access must be used only for approved, compliant purposes, including but not limited to:
- Brand monitoring, reputation and safety analytics
- Media and newsroom workflows (publishing, curation, analytics)
- Customer care and support integrations
- Regulatory compliance, risk, and market analysis
- Internal business intelligence and trend analysis
Any change in use case must be disclosed to Vibble and may require additional review or contract amendment.
4. Prohibited Enterprise Uses
Enterprise clients may NOT use the API to:
- Build competing social media platforms using Vibble’s proprietary data
- Create surveillance tools for targeting individuals without a lawful basis
- Construct shadow profiles on non-users or track individuals across services without consent
- Sell raw Vibble data as a primary product unless contractually authorized
- Engage in political, civic, or law-enforcement use without complying with all applicable laws
Violations may result in immediate termination of access and notification to regulators or authorities where appropriate.
5. Data Access, Scope & Minimization
Vibble applies a data-minimization approach to enterprise APIs. Only the minimum necessary data elements for the approved use case will be exposed.
Access may be limited to:
- Public posts, public profile metadata, and public engagement metrics
- Compliance streams (delete notifications, status changes)
- Anonymized or aggregated insights where appropriate
Access to non-public data (e.g., DMs, private accounts) is strictly prohibited unless explicitly authorized by user consent and by law, and separately agreed in writing.
6. Security & Compliance Obligations
Enterprise clients must implement robust technical and organizational measures to protect Vibble data, including:
- Encryption in transit and at rest for all stored Vibble data
- Role-based access controls and least-privilege user permissions
- Audit logs of access to sensitive or high-volume endpoints
- Regular vulnerability scanning and patch management
- Incident response plans for data breaches or misuse
Serious security incidents must be reported to Vibble within 24 hours of detection, including scope, impact, and remediation steps.
7. Rate Limits, Quotas & Performance
Vibble may provide custom rate limits, volume caps, and performance SLAs in enterprise contracts. Clients agree to:
- Respect all assigned rate limits and backoff headers
- Avoid traffic patterns that may destabilize the platform
- Implement internal caching and deduplication where feasible
- Coordinate high-volume tests or bursts with Vibble in advance
Vibble may throttle, suspend, or reconfigure limits if traffic jeopardizes service stability.
8. Data Retention & Deletion
Enterprise clients must comply with Vibble’s Data Retention & Deletion Policy and any contractual retention obligations.
- Data must not be retained longer than necessary for the stated purpose
- Deleted or privatized content must be removed from client systems upon receipt of compliance signals
- Per-user deletion requests must be respected where technically feasible
9. Audit Rights & Compliance Reviews
Vibble may conduct compliance reviews or audits (directly or via qualified third parties) to verify adherence to these terms, including:
- Technical architecture and security controls
- Data flows and storage locations
- Logging and access controls
- Use-case implementation and business logic
Clients must cooperate in good faith with reasonable audit requests and remediation plans.
10. Fees, Billing & Usage-Based Pricing
Enterprise API access may be subject to subscription fees, usage-based pricing, or custom commercial terms. Clients are responsible for:
- Timely payment of invoices
- Monitoring their usage against contracted limits
- Notifying Vibble of suspected billing errors promptly
Vibble reserves the right to adjust pricing upon renewal or with prior notice as specified in the applicable agreement.
11. Suspension & Termination
Vibble may suspend or terminate enterprise API access if:
- There is a material breach of these terms or the master agreement
- Use poses security, legal, or reputational risk to Vibble or users
- Invoices are significantly overdue
- Client fails to remediate identified security or compliance issues
Upon termination, clients must promptly cease all use of Vibble data and delete or anonymize stored datasets, subject to legal retention requirements.
12. Liability & Indemnity
Enterprise clients agree to indemnify and hold Vibble harmless from claims arising from:
- Misuse of API data or violation of user rights
- Security breaches within client-controlled systems
- Non-compliance with applicable laws or regulations
Liability caps and specific indemnity provisions may be further defined in the master enterprise agreement.
13. Contact Information
Enterprise API & Partnerships: enterprise-api@vibble.to
Developer Support: dev@vibble.to
Security & Incidents: security@vibble.to
Legal & Contracts: legal@vibble.to
Enterprise Account Management: enterprise@vibble.to
14. Updates to These Terms
Vibble may update these Enterprise API Terms periodically. Material changes will be communicated to designated enterprise contacts and reflected in the Policy Center with a revised effective date. Continued use of enterprise API access after updates constitutes acceptance of the revised terms.