Acceptable Use Policy

Send business messages to business people about something plausibly relevant to their job, honour every stop request immediately, and do not use the product to reach consumers about consumer things.

• Consumer marketing. Anything aimed at people in a personal capacity.
• Regulated verticals that carry their own consent regimes: adult content, gambling, firearms, controlled substances, payday and high-interest lending, debt relief, multi-level marketing, cryptocurrency investment solicitation.
• Deception of any kind: forged headers, misleading subject lines, false claims about who you are or what you sell, and implying a prior relationship that does not exist.
• Phishing, credential harvesting, malware, or anything that pretends to be someone else.
• Harassment, threats, or repeat contact after somebody has asked you to stop, on any channel.
• Purchased or scraped lists you cannot account for the origin of.
• Reselling access, sharing a seat, or using the product to build a competing lead database.

Some of these are policy and some are architecture, and it is worth knowing which:

• Send without an unsubscribe link and a postal address. Both are injected by the sending layer, and the database refuses a message reaching sent without them. This is not a setting.
• Contact a suppressed address or profile. Suppression is checked at sourcing, again at the reveal, and again at the gate.
• Continue a sequence after a reply. Any inbound message skips every pending step for that contact, before anything is classified.
• Ignore a stop request written in prose. The keyword pass runs before classification and without a model, because a missed opt-out is a regulatory event rather than a wrong label.

Automating LinkedIn breaches their user agreement and there is no compliant API. The consequence. A restricted account. Lands on your profile rather than on ours, which is why the age ramp is on by default and why every limit is yours to lower rather than only to raise.

Turning the ramp off on a young account, or setting a daily limit well above the platform norm, is something you can do and something we will not do for you.

Sending domains you attach are yours, but they sit behind an email provider whose acceptable-use policy restricts unsolicited mail. A workspace generating sustained complaints puts that relationship at risk for everybody on the platform.

So: complaint and bounce rates are monitored per sender, a spike re-anchors your ramp automatically, and a sustained one is a conversation. We would rather have it early.

In rough order: an automated ramp reduction, then an email from a person, then a pause on sending, then termination. We skip to the end for phishing, malware and impersonation, and for anything that puts other customers’ deliverability at risk immediately.

If you think a pause was wrong, reply to it. A human reads those, and being wrong about a customer is worse for us than being slow about a bad one.

If you received a message through GTM that should not have been sent, forward it to support@trygtm.com. Include the headers if you can. We will suppress you at platform scope, which is exempt from every retention purge, so it holds, and we will look at the workspace that sent it.