1. Scope
This Acceptable Use Policy applies to everyone who uses Squiid, and it forms part of the Terms of Service. It applies equally to what you do by hand and to what your agents do with your key: see Terms, Section 10. It also applies to your own end users if you build a product on top of Squiid; you are responsible for them.
2. Provider terms flow down to you
Every connected service has its own terms and usage policies, and they apply to your traffic through Squiid exactly as if you had signed up with that provider directly. That includes model usage policies, sending and messaging rules, fair-use and rate limits, region and residency restrictions, prohibited-content lists, benchmarking and publication restrictions, and any requirement to disclose AI-generated content.
You must not use Squiid to do something a provider forbids: including using Squiid specifically to obscure who you are, to get around a provider's geographic restriction, rate limit, account suspension or ban, or to pool one account across parties who should each have their own. If a provider tells us your traffic breaches its terms, we will act on it.
Where a provider's rule is stricter than this policy, the stricter rule wins. Current provider terms are linked from each service page in the catalogue; it is your job to read the ones you use.
3. Prohibited activities
Do not use Squiid, or let your agents use it, to:
Illegal and harmful
- Break the law, or facilitate someone else breaking it.
- Produce or distribute child sexual abuse material. We report CSAM to NCMEC and to law enforcement, and terminate immediately and permanently.
- Create or distribute non-consensual intimate imagery, or sexual content involving minors in any form.
- Harass, threaten, stalk, dox or incite violence against anyone.
- Generate or spread material that promotes terrorism or violent extremism.
- Develop weapons, including chemical, biological, radiological, nuclear or high-yield explosives, or to build malware, ransomware or exploitation tooling.
Deception and fraud
- Run phishing, scams, fake stores, payment fraud or money laundering.
- Impersonate a person or organisation, or generate synthetic media of a real person presented as genuine without disclosure and consent.
- Generate coordinated inauthentic content: fake reviews, astroturfed comments, bot networks, election disinformation.
- Submit false billing, tax or identity information, or abuse free trials and promotional credit by creating multiple accounts.
Security and integrity
- Probe, scan, penetration-test, overload or disrupt Squiid or any provider without written authorisation.
- Circumvent authentication, rate limits, spend caps or usage metering; tamper with our audit logs; or attempt to extract another customer's data or credentials.
- Reverse engineer the gateway, or use it to scrape or bulk-extract a provider's service in breach of that provider's terms or a site's terms.
- Distribute malware, botnets, credential stuffing tooling, or crypto-mining workloads on provisioned compute.
Privacy and data
- Route personal data you have no lawful basis to process, or route special-category, health, biometric, financial-account or government-ID data into a service that is not contractually cleared for it.
- Build facial recognition or biometric identification databases from scraped material, or run surveillance of individuals without a lawful basis.
- Send data that is subject to HIPAA, PCI DSS cardholder data, or export-controlled technical data through services not covered by an appropriate agreement.
Commercial
- Resell, sublicense or rebrand raw Squiid access as your own key-brokering or aggregation service. Building a product that uses Squiid underneath is fine; reselling the aggregation itself is not.
- Share one Squiid key or seat across separate organisations, or with people outside your account.
- Use Squiid to benchmark or compete against us in breach of the Terms.
4. Rules for autonomous agents
Agents are the point of Squiid, so these are rules for using them responsibly, not for avoiding them:
- Scope the key. Give each agent a key restricted to the services it actually needs, and set a spend cap. Do not hand a production key with unlimited scope to an experimental loop.
- Bound the loop. Put retry limits, timeouts and concurrency limits in your agent. Runaway loops are billable and may be paused by us.
- Keep a human in the loop for irreversible actions: sending money, sending messages to real people, deleting data, deploying to production, or publishing content.
- Guard against prompt injection. If your agent reads untrusted web pages, files or emails, treat that content as data: not as instructions that can redirect its tools or spend.
- Do not use an agent to evade a policy you could not comply with yourself, or to generate volume designed to exhaust a provider's free tier or rate limits.
- Review output before shipping. Generated code may be insecure; generated text may be wrong or infringing.
5. Email, SMS and voice
Messaging services (Resend, Postmark, SendGrid, Mailgun, Loops, Twilio, Telnyx, Vonage and similar) carry extra rules, and abuse there gets accounts terminated fastest: by the provider as well as by us.
- Send only to recipients who gave you permission. No purchased lists, scraped addresses or harvested phone numbers.
- Comply with CAN-SPAM, CASL, the ePrivacy Directive, the TCPA and equivalent local law: accurate sender identity and subject lines, a physical postal address, a working unsubscribe or STOP handling, and prompt suppression.
- Register campaigns and brands where a carrier requires it (US 10DLC, toll-free verification, short codes) and stay within the use case you registered.
- Honour quiet hours, frequency limits and do-not-call obligations. No autodialled or pre-recorded calls without the consent the law requires.
- Keep bounce, complaint and unsubscribe rates within provider thresholds; authenticate your domains with SPF, DKIM and DMARC.
- Never use an agent to generate and send bulk outreach without a human reviewing the list and the content.
6. Fair use of the platform
The gateway applies platform-level rate limits and anomaly detection to keep it healthy for everyone. Do not try to circumvent them, and contact us before launching something that will multiply your normal volume so we can plan for it. Provisioned compute, storage and database resources must be used for your application, not as free general-purpose infrastructure for unrelated workloads.
7. How we enforce
Depending on severity we may warn you, throttle a key, pause a key or connected service, suspend the account, or terminate. Serious harm (CSAM, an active attack, a legal order, a provider demand) gets immediate action without prior notice. Otherwise we try to contact you first and give you a chance to fix it.
We may share information with a provider or with law enforcement where necessary to investigate or stop abuse. Suspension for abuse does not entitle you to a refund of the platform fee or of top-up fees; we will still refund unspent credits where the law requires it and where the balance is not subject to a legal hold.
We may reinstate an account once you show the problem is fixed. Repeat or deliberate violations are not reinstated.
8. Reporting abuse
If you see traffic from Squiid that breaks these rules, email abuse@squiid.io with as much detail as you can: timestamps, IPs, message headers, the service involved. Security vulnerabilities go to security@squiid.io; we do not pursue good-faith researchers who follow a responsible disclosure process and stay within the rules above. Copyright notices go to legal@squiid.io, marked for the attention of our designated DMCA agent at 50 Alberigi Drive, Jessup, PA 18434, United States.