Acceptable Use Policy

1. Scope

This Acceptable Use Policy applies to every QueueTempo Account, Organization, Brand profile, Knowledge source, prompt, draft, uploaded asset, Link, Tempo, Connection, Channel, publication, invitation, support request, and related use of the Service.

You must follow applicable law, the rights of others, provider developer and automation rules, the QueueTempo Terms, and this policy. Permission from QueueTempo does not override a destination platform’s restrictions.

2. Prohibited use

You may not use or attempt to use QueueTempo for:

• bulk spam or unsolicited repetitive publishing;
• deceptive impersonation or misrepresentation of identity or authority;
• coordinated inauthentic behavior or deceptive political influence operations;
• automated replies, mentions, comments, likes, follows, or engagement farming;
• harassment, threats, hateful abuse, or targeted intimidation;
• sexual exploitation content or content involving abuse of minors;
• illegal goods or services, or prohibited regulated-goods promotion;
• malicious links, phishing, credential theft, malware, or evasion techniques;
• fraudulent, fabricated, or materially deceptive claims;
• copyrighted, trademarked, private, or confidential material without rights;
• repeated near-duplicate posts across many accounts to manipulate distribution;
• evasion of platform enforcement, quotas, rate limits, review, or account restrictions;
• buying, selling, requesting, storing, or sharing social passwords or credentials;
• scraping authenticated sites or hidden browser control as an API substitute;
• accessing another Organization or person’s data without authorization.

3. Sensitive industries and decisions

Health, finance, legal, political, employment, housing, education, and regulated-goods content can create heightened risk. QueueTempo may require Review required, verified facts and disclaimers, stricter moderation, disabled Auto-publish, administrative approval, or jurisdiction-specific legal review.

QueueTempo does not certify that an automated classifier or AI-generated draft is legally compliant, professionally appropriate, or accurate. Do not use the Service to make eligibility, credit, employment, housing, medical, legal, or other high-impact decisions about a person.

4. Honest automation consent

Before enabling Auto-publish, QueueTempo shows the action, destination, cadence, and policy. An authorized member must provide express consent. OAuth consent is not a substitute for QueueTempo Auto-publish consent.

You may not conceal that a process is automated where law, platform policy, or context requires disclosure. You must honor pause, disconnect, opt-out, and revocation promptly.

5. Content and destination safety

Before an automatic post is eligible, QueueTempo may check:

1. active Organization and Tempo;
2. valid plan entitlement and allowance;
3. recorded automation consent;
4. healthy Connection and required scopes;
5. current approved content and Content recipe versions;
6. format, link, and media validity;
7. moderation and prohibited claims or topics;
8. duplication and spam signals;
9. due time, posting window, and exclusion rules.

A failed check creates a visible blocked or skipped state. You may not attempt to bypass, disable, or obscure these controls.

6. Rate limits and abuse prevention

QueueTempo may rate-limit or restrict activity by IP address, Account, Organization, Connection, provider, action type, or plan. Protected actions include authentication, invitations, OAuth, generation, URL ingestion, uploads, previews, publishing retries, support forms, and exports.

Creating multiple Accounts or Organizations to evade a limit, suspension, cost, or enforcement action is prohibited.

7. Enforcement

Depending on severity, history, risk, law, and provider obligations, QueueTempo may issue a warning, restrict generation, disable Auto-publish, disable publishing, restrict an Organization, suspend an Account, or terminate use.

QueueTempo may preserve evidence, cooperate with lawful process, report urgent harm, or withhold details when necessary for security or abuse prevention. Where appropriate, QueueTempo will provide a reason and support or appeal route.

8. Reporting concerns

Use the security or privacy support categoryto report suspected abuse. Provide a safe description and relevant public link or opaque request ID when available. Do not send passwords, OAuth tokens, authentication cookies, payment details, or exploit code through an unsecured channel.