Acceptable Use and Anti-Spam Policy

1. Who this applies to

This Acceptable Use and Anti-Spam Policy ("Policy") is part of the Terms of Service at https://goosybear.ai/terms between you and AI Code That Works LLC, a Texas limited liability company doing business as Goosy Bear ("Goosy Bear," "we," "us," or "our"). It applies to every account and workspace in the Goosy Bear application at https://app.goosybear.ai (the "Application"), to every member you invite, and to every message sent from an address, domain, or phone number we provide or that you connect — whether you write the message, Goosy writes it, or an automation sends it.

You are the sender of the messages you send through the Application. Where this Policy and the Terms differ on messaging, the stricter rule applies.

2. Permission to message

2.1 Verifiable opt-in, per business

Send marketing email or text messages only to people who asked to hear from the business sending them. Each person's permission must have been given to that business — to the brand named in the message — not to a partner, a sister brand, a list owner, or anyone else. An existing customer relationship, a business card, or a public address on a website is not permission.

Keep proof of every opt-in — where and how the person signed up, when, and what they were told they would receive — and produce it to us within 5 business days when we ask. A sender who cannot produce it may be paused until they do.

The Application keeps a consent record for every contact, separately for email and for text messages: whether the person is subscribed, how the consent arrived (a form on a Goosy-hosted page, your connected CRM, an import, or a consent a member recorded), and when. New contacts start as not subscribed unless the way they arrived captured consent. Texts are sent only to people with a recorded text opt-in.

When you import a file that marks people as opted in to email, the import is refused until you confirm that every one of them agreed to hear from you. That confirmation is kept on the import's audit record.

When one sender emails more than 500 people it has never mailed before within 24 hours, the send is held for our review before it continues, because a large new list is how purchased and scraped lists usually arrive.

2.3 Lists you may never use

Do not message any list or contact that you:

2.3.1bought, rented, or leased;
2.3.2borrowed, shared, or received from another business, a partner, or an affiliate;
2.3.3scraped, harvested, or collected from websites, directories, social networks, or public sources;
2.3.4gathered through co-registration, a sweepstakes partner, or a lead-generation service whose sign-up did not name your business;
2.3.5obtained from any third party, however it was described to you; or
2.3.6built by appending or matching email addresses or phone numbers to other data you hold.

3. What every message must carry

3.1Accurate sender identity. The from name, from address, and reply-to must identify the business that is actually sending, and the subject line must reflect what is inside. Never forge headers, impersonate another person or business, or hide where a message came from.
3.2A physical postal address. Every marketing email shows the sending business's valid postal address. The Application adds it to the footer, and it will not send marketing email for a business that has not given us one.
3.3A working unsubscribe. Every marketing email carries a visible unsubscribe link and the one-click unsubscribe headers (List-Unsubscribe and List-Unsubscribe-Post, as RFC 8058 defines them), which the Application adds. Do not remove, hide, or break them, and do not ask the person to sign in, pay, or give anything other than their address to leave.
3.4Opt-outs honored at once, and for good. An unsubscribe takes effect immediately — the Application stops sending to that address before the next message — and it stays in force until the person opts back in themselves. Do not re-add, re-import, or re-subscribe anyone who left. Each business also has its own suppression list: an address that hard-bounces or complains, or that a member adds, is blocked for that business, and the block follows the address, not the contact record, so deleting and re-adding a contact does not lift it.
3.5Texts identify the business and honor STOP. A text names the business sending it, and a STOP reply opts the person out of that business's texts automatically.

4. How you must send

4.1Authenticate your domain. Send from a domain you own or control, with SPF, DKIM, and DMARC set up for it. When you connect your own domain, the Application gives you the records to publish and sends from it only once they verify. Until then, a workspace sends from a capped default address on our sending domain.
4.2Send what people signed up for, at the frequency they expect. A sudden change of topic or volume is the main cause of complaints.
4.3Keep your list clean. Remove addresses that bounce, and stop mailing people who have not engaged in a long time.
4.4Do not try to get around our limits. Splitting sends across workspaces, senders, or domains to stay under a limit, or rotating content to get past screening, is a breach of this Policy.

5. Our limits and what happens when a sender crosses them

We measure every email sender's own results, over each 24 hours, once it has sent at least 100 messages in that window:

Our limits and what happens when a sender crosses them table
Measure	We warn the owner at	We pause the sender at
Hard bounces, over messages sent	1%	2%
Spam complaints, over messages sent	0.05%	0.08%
Unsubscribes, over messages sent	1%	1.4%

These limits are stricter than the review levels our email providers and the major mailbox providers publish, so that one sender's list cannot harm another's delivery. When a sender crosses a pause limit, it stops sending at once and is held until our team reviews it; it does not resume on its own. We tell the workspace owner the reason and what to do next.

New senders start slowly:

5.1The default address on our sending domain sends up to 50 emails a day.
5.2An address on a domain you have just connected starts at 100 emails a day and doubles every 3 days until it reaches 6,400 a day, after which the daily cap is lifted.
5.3Each sender may send up to 20,000 emails a month; sending beyond that is held for our review, and we raise the limit when a sender's results earn it.

For text messages we apply the phone carriers' standards: a sender whose opt-out replies or carrier-filtered messages run high is warned and then paused in the same way. For WhatsApp, we follow the quality ratings and messaging limits Meta sets for each number.

6. Content we screen and content we do not allow

Messages written by Goosy and messages you send through flows are screened for prohibited and harmful content before they go out, and a message that fails is not sent. Screening is a safeguard, not an approval: you remain responsible for every message you send.

6.1 Prohibited

Do not use the Application to send messages that promote, sell, or facilitate:

6.1.1anything illegal where the sender or the recipient is — including illegal drugs, weapons sold unlawfully, counterfeit goods, and stolen data or accounts;
6.1.2sexually explicit material, escort or adult-dating services;
6.1.3gambling, betting, lotteries, or sweepstakes that require payment;
6.1.4cryptocurrency, token, or initial coin offerings, and crypto trading or mining schemes;
6.1.5multi-level marketing, pyramid schemes, and get-rich-quick, work-from-home, or guaranteed-income offers;
6.1.6payday loans, debt relief, debt collection, credit repair, and similar high-interest or debt services;
6.1.7prescription drugs, controlled substances, and dietary supplements or health products that make medical claims;
6.1.8the sale, rental, or brokering of lists, leads, or personal data; or
6.1.9deceptive, misleading, threatening, harassing, hateful, or defamatory content, phishing, malware, or any attempt to obtain someone's credentials or payment details under false pretenses.

6.2 Restricted

Some lawful businesses carry more risk of complaints or legal claims — for example financial services and insurance, real estate investment programs, and alcohol, tobacco, vaping, or cannabis-derived products. We may ask for more information before such a business sends, limit its volume, or decline it.

7. Agencies and multi-brand accounts

If you run Goosy Bear for clients or for several brands, you answer to us for every brand you operate. You must hold each client to this Policy, keep its opt-in records or be able to produce them, and make sure each brand sends only to its own subscribers. A breach by one client is a breach by you, and we may pause that brand's sending, or the account's, as section 8 describes.

8. Enforcement

We may, at our discretion and without prior notice where we reasonably believe it is needed, limit, pause, hold for review, or suspend a sender, a brand's sending, or all of an account's sending; remove content; or suspend or terminate the account under the Terms. We do this when a sender crosses the limits in section 5, when we receive an abuse report, when a message breaks this Policy, or when an email provider, phone carrier, messaging vendor, or Meta acts or asks us to. We will tell the workspace owner the reason and the next step.

Fines, penalties, and surcharges that a carrier, messaging vendor, email provider, or regulator charges because of messages you sent are yours to pay, and we may pass them through to your account, as section 7.1 of the Terms provides.

9. Reporting abuse

If you received a message sent through Goosy Bear that you did not ask for, or you believe a sender is breaking this Policy, report it to abuse@goosymail.com. Questions about messaging compliance go to compliance@goosybear.ai. Include the message with its full headers if you can. We acknowledge every report within 24 hours, match it to the business that sent it, and may pause that sender while we review it.

10. Changes to this Policy

We may update this Policy as the law, our providers' rules, or the Application change. The date at the top shows when the current version took effect. For a material change we give notice as section 19 of the Terms describes.

11. Contact

Questions about this Policy:

compliance@goosybear.ai

AI Code That Works LLC, 2303 Ranch Road 620 S., Suite 160-240, Lakeway, TX 78734, United States.

We use cookies