Acceptable Use
Acceptable Use Policy
This policy describes prohibited uses of the Odd Latent Service, Customer Content, and Outputs.
Version date: 15 June 2026
Overview
Customer and Authorized Users must not use the Service, Customer Content, or Outputs in violation of this Acceptable Use Policy.
S2.1 Illegal or Harmful Use
Customer must not use the Service to create, upload, process, distribute, or facilitate:
- illegal content or illegal activity;
- malware, exploit code, credential theft, phishing, spam, botnets, or cyber abuse;
- instructions for evading security controls or committing cyber abuse;
- content that infringes intellectual property, privacy, publicity, confidentiality, or other third-party rights;
- content that violates platform rules, app-store rules, ad-network rules, publisher requirements, or workspace rules;
- deceptive, fraudulent, or misleading content;
- sexually explicit or pornographic content, including explicit nudity or sexual content intended primarily for sexual arousal, whether photorealistic, illustrated, animated, stylized, fictional, or AI-generated.
S2.2 AI-Specific Prohibited Content
Customer must not use the Service to generate or assist with:
- non-consensual intimate imagery or sexualized private images;
- child sexual abuse material or sexual content involving minors;
- hateful, harassing, threatening, or abusive content targeting protected classes or individuals;
- content that encourages self-harm, violence, exploitation, or abuse;
- biometric identification, face recognition, or sensitive-attribute inference unless expressly approved in writing and lawful;
- impersonation of real people without rights or clear lawful basis;
- deceptive synthetic media intended to mislead people about real events, statements, identity, or endorsements;
- political persuasion, voter targeting, or election manipulation where restricted by law or platform policy;
- automated decisions with legal or similarly significant effects in employment, credit, housing, education, healthcare, insurance, or similar regulated contexts.
S2.3 Sensitive and Regulated Data
Customer must not submit or process the following unless Provider expressly agrees in writing:
- special-category personal data under GDPR or similar law;
- health data, biometric data, genetic data, criminal-offense data, or children's data;
- payment card data, bank credentials, private keys, passwords, API keys, production secrets, or authentication tokens;
- government identifiers, passport data, national identity numbers, or tax identifiers;
- customer lists, employee data, or consumer data not necessary for the pilot;
- trade-secret materials or confidential third-party materials Customer has no right to use;
- regulated financial, medical, legal, insurance, employment, or education decision data.
S2.4 Rights and Clearance
Customer must not submit Customer Content or use Outputs unless Customer has the required rights, licenses, permissions, consents, notices, and legal bases.
Customer must not use the Service to imitate, copy, or closely replicate third-party brands, characters, games, celebrities, artists, protected styles, UI, assets, trademarks, or trade dress in a way that violates rights or creates misleading association.
S2.5 Operational Abuse
Customer must not:
- scrape, crawl, extract, or harvest the Service or Provider Technology;
- overload, load test, stress test, or benchmark the Service without written approval;
- bypass rate limits, queues, safety systems, usage limits, permissions, or access controls;
- reverse engineer, decompile, reconstruct, or extract prompts, flows, system instructions, model routing, tools, source code, or internal logic;
- use automated high-volume requests outside approved interfaces;
- resell, sublicense, white-label, or provide bureau access without written approval;
- use the Service to build, train, benchmark, distill, or improve a competing product or service;
- use the Service, Outputs, or workflow behavior to extract model weights, replicate model behavior, create training datasets for competing AI systems, or systematically approximate Provider Technology;
- use prompt injection, adversarial inputs, jailbreaks, hidden instructions, tool-manipulation attempts, or similar techniques to bypass safety systems, extract confidential instructions, corrupt Service behavior, or obtain unauthorized access;
- misrepresent identity, affiliation, rights ownership, consent, source, or endorsement.
S2.6 Node and Concurrency Abuse
Customer must not exploit Nodes, concurrency limits, queue behavior, rate-limit recovery windows, throttles, duplicate accounts, parallel workspaces, shared credentials, automations, schedulers, headless clients, scripts, channel splitting, artificial project splitting, or similar mechanisms to obtain project capacity, workflow concurrency, or generation volume materially beyond Customer's plan, Order Form, or approved usage limits.
Provider may treat sustained usage materially above Node allocation, especially when combined with automation, duplicated access channels, or project-splitting patterns, as evidence of abuse. Provider may queue, throttle, pause, or suspend access, require additional Nodes or a plan upgrade, invoice excess usage at then-current rates, or terminate access.
S2.7 Advertising, Games, and Public Distribution
Customer must not publish, distribute, submit, or run Outputs in ads, app stores, paid media, public websites, games, or customer campaigns unless Customer has completed appropriate human review and clearance.
Customer is responsible for advertising claims substantiation, platform-policy compliance, app-store and ad-network compliance, age rating, consumer protection, audience suitability, IP review, likeness review, publicity review, privacy review, trademark review, technical QA, and security review for prototypes, games, code, and playable ads.
S2.8 Enforcement
Provider may remove content, refuse generation, throttle usage, suspend access, terminate access, or notify affected parties if Provider reasonably believes Customer has violated this AUP or that continued use creates legal, security, platform, third-party, reputational, or service-integrity risk.
Provider may update this AUP as needed for law, security, platform policy, third-party service requirements, product safety, or abuse prevention.
If content is removed or access is suspended under this AUP, Customer may request review by contacting Provider's support or notice contact and explaining why Customer believes the action was mistaken. Provider will review reasonable requests in good faith, but Provider's decision is final unless an Order Form states otherwise.
Customer may report suspected violations, vulnerabilities, abuse, or rights issues through Provider's support or notice contact.