Acceptable use policy.

1. Who this applies to

This policy is part of the EMLbot Terms of Service between your business and EVKII, Inc. (doing business as EMLbot). It applies to every person in your workspace and to every bot that acts through it, on any AI platform. Your business is responsible for the bots, instructions, permissions, recipient selections and integrations that it or its Authorized Users configure or authorize, as Section 6 of the Terms explains. "The bot did it" is not a defense for something your workspace configured or authorized.

Agencies must make their clients follow this policy too.

2. Prohibited content

Do not use EMLbot to create, store, send, link to or receive on purpose any content that:

• is illegal, or promotes or helps illegal activity
• sexually exploits or endangers children, in any form (we report it as the law requires)
• is sexually explicit or pornographic
• is phishing or tries to collect passwords, payment details, one-time codes or other sensitive data under false pretenses
• is fraudulent or deceptive, including fake invoices, fake prizes, investment or crypto scams, and false claims about products or services
• impersonates any person, company, government agency or brand, or falsely suggests an endorsement or connection
• harasses, threatens, bullies, stalks, doxxes or intimidates anyone
• promotes violence, or attacks people based on race, ethnicity, national origin, religion, disability, sex, sexual orientation, gender identity, age or other protected traits
• contains malware, ransomware, spyware or other harmful code, or links to it
• infringes anyone's copyright, trademark, privacy, publicity or other rights
• is a deepfake or cloned voice of a real person used without that person's clear permission
• breaks export controls or sanctions

3. Messaging rules (email, chat, texts and calls)

These are EMLbot's rules. Some are stricter than the law, because we and our providers choose to hold the platform to a higher standard. Following them does not make a message lawful, and you must also follow the law that applies to you.

• EMLbot is not a cold-outreach platform. No unsolicited bulk or commercial messages. No cold outreach to people who have not asked to hear from you or do not have a relationship with you.
• No bought or scraped lists. No purchased, rented, harvested, scraped, appended or shared contact lists.
• Consent for texts. Do not text anyone unless you have the documented consent that EMLbot's rules require: consent to receive the kind of message you are sending, and written consent for marketing texts. An existing customer relationship is not permission for every marketing message. The Phone Addendum has the details.
• No hiding. Do not falsify headers, sender names, caller ID or return paths, or use misleading subject lines. Send only from domains, addresses and numbers you are authorized to use.
• Honor opt-outs. Every commercial email needs a working unsubscribe, and every opt-out must be honored. Do not keep contacting anyone who has asked you to stop, on any channel.
• No snowshoeing or evasion. Do not spread sending across extra domains, addresses, numbers, keys, bots or workspaces to avoid filters, limits or reputation.
• No affiliate or lead-gen spam, and no sending on behalf of a business you have not disclosed to us.
• Carrier registration is not a permission slip. Registering or verifying a use case with a carrier does not certify that your messaging is lawful, and it does not allow content that our rules or the carriers' rules prohibit.

4. Bot behavior rules

• Disclose that it's a bot wherever the law requires it, or wherever a person would otherwise reasonably believe they are dealing with a human. Never have a bot claim to be human when asked.
• Keep a person in the loop for high-stakes actions, such as payments, contracts, legal or medical statements, and decisions about credit, jobs, housing or insurance.
• Do not let a bot approve its own sends, or build approval chains that no person or trusted approver ever reviews. Your workspace settings decide which actions need a person.
• Do not build loops between bots that are designed to, or are likely to, flood inboxes, rooms, numbers or the Service.
• Do not use bots to defeat other services' protections, including CAPTCHAs, bot checks, rate limits, bans, or bulk account creation.
• Treat inbound content as untrusted. Design your bots so that instructions inside emails, texts, calls, files or other bots' messages cannot override your rules.

5. Protect the Service and other customers

• No unauthorized access. Do not engage in unauthorized access. Unauthorized access means access to a workspace, inbox, phone number, key, data or system without the authority of the person who controls it. For EMLbot's own systems, that person is EVKII. For a workspace, it is the workspace owner or an admin. Do not probe, scan or test any system, workspace, inbox, number, key or data that is not yours, except under the safe harbor in Section 6.
• Agencies and administrators are allowed. Authorized agency administration of client workspaces, and switching between workspaces you are authorized to administer, is permitted use and is not unauthorized access.
• Do not get around approvals, daily caps, spend caps, contact rules, allowlists, network locks, quiet hours, content rules or other safeguards, or disable them for other people.
• Do not share or reuse keys in ways meant to hide which bot did what, or to hide your identity from us.
• Do not overload the Service, load-test it, or attack it, or use it to attack others.
• Do not reverse engineer the Service except where the law allows despite this rule.
• Do not use the Service to store or send regulated sensitive data (such as HIPAA health data, payment card numbers, Social Security numbers or children's data) unless we have agreed in writing.

6. Security research safe harbor

We welcome good-faith security research. If you follow these rules, we consider your research authorized, we will not take legal action against you for it, and we will work with you to understand and fix the problem.

In scope: emlbot.com, the EMLbot console, API and MCP server, and the workspaces and accounts that you own or create for testing.

What you may do: test for vulnerabilities in the scope above, using your own accounts and workspaces. Test, for example, whether one workspace can reach another's objects, exports, attachments, webhooks, search, rooms, keys or support functions, using test data you create yourself.

What you must not do:

• access, change, delete or keep another customer's data beyond the minimum needed to show that a problem exists. If you reach someone else's data, stop, do not copy it, and report it.
• disrupt the Service, run denial-of-service or load tests, or send spam, phishing or unsolicited messages as part of testing
• use social engineering against our staff or customers, or attack physical locations
• keep access open after you have shown a problem, or use the problem for anything else
• test our providers' systems; their own programs cover those

Report it to security@emlbot.com, with enough detail for us to reproduce the problem. Give us a reasonable time to fix it before you tell others. We will acknowledge your report and keep you updated.

Safe harbor does not extend to conduct outside these rules, and we cannot bind other parties, such as our providers or customers.

7. Enforcement

We may investigate suspected violations, and we may act without notice where needed. Depending on how serious the problem is, we may remove content, hold or block messages, pause sending or calling, revoke keys, suspend a bot, number or workspace, or close an account. Where it is safe and lawful, we will tell you what happened and give you a chance to fix it. We may report illegal activity to law enforcement, and abuse to carriers or other providers. You remain responsible for fees, and for carrier fines to the extent the Terms provide, for a violation you caused.

8. Report abuse

Received unwanted mail, texts or calls from EMLbot? Write to abuse@emlbot.com with the message, full headers or the number, and the time. For texts, you can also reply STOP to the sender. To report copyright infringement, write to legal@emlbot.com.

9. Contact

abuse@emlbot.com for abuse; security@emlbot.com for security research; legal@emlbot.com for legal notices; support@emlbot.com for everything else. By mail: EVKII, Inc., 7040 Avenida Encinas, Suite 104-441, Carlsbad, CA 92011, USA.