Acceptable Use Policy | phoneveriflo

1. Purpose & Scope

This Acceptable Use Policy ("AUP") establishes the standards and requirements for all users accessing the phoneveriflo platform, REST API endpoints, SDKs, and data processing tools.

By accessing or using the Service, you agree not to engage in any activity that violates applicable laws, infringes on individual privacy rights, harms our network integrity, or degrades platform reliability for other users.

2. Prohibited Uses & Unlawful Activities

You may not use phoneveriflo for or in connection with any of the following:

Unsolicited Communications & Spam: Generating or validating contact lists for unlawful robocalling, SMS spam, unsolicited promotional outreach, or email phishing campaigns.
Fraud & Impersonation: Facilitating account takeover, credential stuffing, toll fraud, SIM-swap attacks, or social engineering schemes.
Harassment & Surveillance: Stalking, harassing, or conducting unauthorized bulk surveillance on individuals without lawful authority.
Credit Scoring / Underwriting: Utilizing verification signals as a factor in establishing an individual's eligibility for credit, employment, housing, or insurance in violation of the Fair Credit Reporting Act (FCRA) or equivalent consumer statutes.
Circumventing Security Gates: Probing, scanning, or attempting to bypass platform rate limits, commercial authorization gates, or authentication tokens.

3. Regulatory Telecommunication Compliance

Customers are strictly responsible for maintaining compliance with all telecommunication and consumer protection statutes across applicable operating jurisdictions, including:

The US Telephone Consumer Protection Act (TCPA) and National Do Not Call Registry;
CTIA Short Code & 10DLC Messaging Guidelines;
The European ePrivacy Directive (Directive 2002/58/EC) and national telecommunication regulations;
Applicable opt-in, express written consent, and revocation records for all verified recipients.

4. API Rate Limits & Infrastructure Protection

To maintain high availability and predictable response times across our distributed architecture, all API consumers must adhere to published rate limits:

Tiered Rate Limiting: Standard accounts are subject to per-minute and per-day rate limits. Burst limits are enforced automatically via HTTP `429 Too Many Requests` responses.
Idempotency Keys: Critical mutating endpoints require `Idempotency-Key` headers. Replaying requests without distinct idempotency keys is prohibited.
Denial of Service: Executing automated load generation, stress testing, or DoS attacks against phoneveriflo infrastructure without prior written authorization is strictly prohibited.

5. Monitoring & Audit Invariants

phoneveriflo monitors aggregated system telemetry, queue latency, and error rates to detect anomalous or abusive behavior.

We reserve the right to immediately suspend API keys, throttle queue execution, or terminate customer accounts found to be in material breach of this policy.

6. Reporting Abuse & Violations

If you become aware of any security vulnerability, system abuse, or violation of this Acceptable Use Policy, please report it immediately:

Security & Abuse Response Team

Abuse Email: [email protected]

Security Disclosures: [email protected]

General Legal: [email protected]

1. Purpose & Scope

This Acceptable Use Policy ("AUP") establishes the standards and requirements for all users accessing the phoneveriflo platform, REST API endpoints, SDKs, and data processing tools.

2. Prohibited Uses & Unlawful Activities

You may not use phoneveriflo for or in connection with any of the following:

Unsolicited Communications & Spam: Generating or validating contact lists for unlawful robocalling, SMS spam, unsolicited promotional outreach, or email phishing campaigns.

Fraud & Impersonation: Facilitating account takeover, credential stuffing, toll fraud, SIM-swap attacks, or social engineering schemes.

Harassment & Surveillance: Stalking, harassing, or conducting unauthorized bulk surveillance on individuals without lawful authority.

Credit Scoring / Underwriting: Utilizing verification signals as a factor in establishing an individual's eligibility for credit, employment, housing, or insurance in violation of the Fair Credit Reporting Act (FCRA) or equivalent consumer statutes.

Circumventing Security Gates: Probing, scanning, or attempting to bypass platform rate limits, commercial authorization gates, or authentication tokens.

3. Regulatory Telecommunication Compliance

Customers are strictly responsible for maintaining compliance with all telecommunication and consumer protection statutes across applicable operating jurisdictions, including:

The US Telephone Consumer Protection Act (TCPA) and National Do Not Call Registry;

CTIA Short Code & 10DLC Messaging Guidelines;

The European ePrivacy Directive (Directive 2002/58/EC) and national telecommunication regulations;

Applicable opt-in, express written consent, and revocation records for all verified recipients.

4. API Rate Limits & Infrastructure Protection

To maintain high availability and predictable response times across our distributed architecture, all API consumers must adhere to published rate limits:

Tiered Rate Limiting: Standard accounts are subject to per-minute and per-day rate limits. Burst limits are enforced automatically via HTTP `429 Too Many Requests` responses.

Idempotency Keys: Critical mutating endpoints require `Idempotency-Key` headers. Replaying requests without distinct idempotency keys is prohibited.

Denial of Service: Executing automated load generation, stress testing, or DoS attacks against phoneveriflo infrastructure without prior written authorization is strictly prohibited.