VelisAds Network

Terms of Service

Effective date: February 17, 2026 | Version: 2026.02-global

These Terms of Service define the legal conditions for using VelisAds Network, including eligibility, account responsibilities, acceptable platform use, enforcement rights, and dispute handling.

This document is a product policy standard and does not replace jurisdiction-specific legal advice.

Scope and Applicability

  1. Applies to all publishers, agencies, delegates, and business users accessing VelisAds Network services.
  2. Applies to websites, mobile apps, ad units, reports, API integrations, and payment workflows.
  3. Applies to trial, staging, and production accounts when real traffic or data is processed.
  4. Applies globally, with local law taking precedence where legal obligations differ.
  5. Applies to all future features unless a stricter feature-specific agreement is published.
  6. Applies to all users acting on behalf of a registered business entity.

Mandatory Requirements

Account Eligibility and Identity

  • Users must have authority to represent and bind the legal entity using the platform.
  • Registration data must remain accurate, complete, and regularly updated.
  • Entity ownership and contact details must be truthful and verifiable.
  • Shared credentials are prohibited unless role-based access controls are in place.

Permitted Service Use

  • Only approved interfaces and documented integration methods may be used.
  • Ad code may not be modified to bypass tracking, policy, or consent controls.
  • Only verified domains and authorized inventory may be monetized.
  • Traffic acquisition methods must be lawful and transparent.

Content and Rights

  • Users must hold rights to all content, creatives, and landing destinations they submit.
  • Trademark, copyright, and licensing conflicts must be resolved promptly after notice.
  • Confidential platform information may not be republished without permission.
  • Users retain content ownership while granting necessary service-operation rights.

Prohibited Practices

  1. Creating fake accounts, forged identities, or shell entities to evade policy controls.
  2. Using bots, click farms, incentivized abuse, or traffic manipulation schemes.
  3. Uploading malicious payloads, hidden redirects, or deceptive scripts.
  4. Reverse engineering systems to bypass limits, anti-fraud checks, or security controls.
  5. Submitting forged domain ownership proof, payment records, or support evidence.
  6. Operating via sanctioned or blocked counterparties without legal authorization.
  7. Interfering with other user accounts, platform services, or reporting integrity.
  8. Misrepresenting platform metrics in commercial or legal communications.

Governance, Monitoring, and Enforcement

  1. Terms acceptance is version-controlled and logged with timestamp evidence.
  2. Material term updates require re-acceptance before restricted actions continue.
  3. Violations may trigger warnings, traffic holds, payout restrictions, or suspension.
  4. Severe abuse can result in immediate termination and evidence preservation.
  5. Appeals require corrective evidence and are evaluated under defined review SLAs.
  6. Legal and compliance teams may request documents to resolve high-risk cases.
  7. Policy exceptions require written approval and expiry-based revalidation.
  8. Records are retained where required for audit, legal, or regulatory obligations.

Global Source Links and Standards

  1. FTC Advertising and Marketing Guidance
  2. FTC COPPA Rule
  3. OFAC Sanctions Programs
  4. IAB Tech Lab ads.txt
  5. IAB Tech Lab app-ads.txt
  6. IAB Tech Lab sellers.json
  7. OECD Consumer Policy Resources
  8. UNCTAD Digital Economy Resources

Operational Interpretation and Regional Mapping

These requirements should be interpreted as global baseline controls for a live ad operations platform. Teams must map each requirement to local legal obligations, contractual duties, and traffic-source constraints before enabling production delivery at scale.

When regional regulations impose stricter standards, the stricter standard applies. Where legal ambiguity exists, operations should default to least-risk handling and documented escalation to legal or compliance owners.

Policy-to-Workflow Mapping

  • Map each policy control to one concrete workflow checkpoint.
  • Define accountable owner, review cadence, and evidence source.
  • Link policy failures to clear remediation and rollback actions.
  • Track policy exceptions with expiry and approval metadata.

Evidence and Audit Quality

  • Keep verifiable logs for approvals, enforcement, and account state changes.
  • Maintain immutable records for policy acceptance and version changes.
  • Preserve incident evidence with timestamp accuracy and actor context.
  • Support regulator and partner audits with structured evidence retrieval.

Release and Change Governance

  • Run policy impact review before major workflow or billing changes.
  • Gate high-risk releases behind compliance and security readiness checks.
  • Document rollback criteria for policy or abuse regressions.
  • Communicate material policy updates with effective-date clarity.

Extended Compliance Checklist

  1. Confirm access controls for admin, publisher, advertiser, and support roles.
  2. Verify domain ownership, sitemap coverage, and install-code integrity before launch.
  3. Validate ad creatives, landing behavior, and category eligibility rules.
  4. Ensure budget, spend, and settlement paths align with billing model selection.
  5. Run fraud and abuse controls for both ad-serving and click attribution pathways.
  6. Confirm user data handling for consent, retention, and rights-response timelines.
  7. Check payout safeguards, webhook integrity, and transaction audit visibility.
  8. Review security events, incident triage flow, and postmortem documentation quality.
  9. Ensure policy pages remain reachable, indexable, and version-consistent in sitemap.
  10. Require periodic policy refresh training for operational and support teams.

Policy FAQ for Operations Teams

How often should this policy be reviewed?

Review before each major release and at recurring governance intervals, especially when billing logic, targeting controls, or verification workflows change.

What happens if live behavior conflicts with policy text?

Live enforcement should default to safer behavior immediately, then trigger incident review and documented correction to either implementation or policy wording.

How should teams handle partner-specific requirements?

Apply partner requirements as stricter overlays where needed, while preserving baseline platform controls and maintaining auditable policy-to-process mapping.