Acceptable Use Policy

This policy says what you may and may not do with TACENZA Chat, TACENZA bots and the Bot API, and TACENZA Mail. It expands on the acceptable use section of the Terms of Service. The Community Guidelines cover groups and Discover.

Everywhere

• Don’t use TACENZA to break the law, to harm children, or to harass, threaten or defraud people.
• Don’t try to overload, probe or get around the service’s limits, or to access accounts that aren’t yours.
• Don’t send spam.

TACENZA Chat

Every account has limits on how often it can do things: send messages, start conversations, create groups and invite links, upload files, sign in. They count only how often something happens, never what anyone writes. They are the same on every plan.

• Don’t work around the limits, for example by spreading the same activity over many accounts, networks or bots.
• Don’t mass-create accounts. Sign-up asks your device for a small proof of work, and is limited per network, for this reason.
• Don’t send unwanted messages to strangers. A first message to someone you haven’t written to lands in their message requests. If people decline your requests, your account’s limits go down for a while.
• Don’t try to guess passwords or lock others out.

Bots and the Bot API

Bots are accounts too, with their own keys, and they are created and run by an owner account.

• Say what the bot does in its description.
• Don’t use bots to spam.
• Stay within the Bot API limits. Every Bot API call counts against the bot’s own budget and its owner’s shared one, so more bots don’t add capacity. When you get a “slow down” answer (HTTP 429), wait for the time it gives before trying again. The @tacenza/bot SDK does this for you.
• Webhooks must be https:// addresses on the public internet. Addresses on private or local networks are refused.

TACENZA Mail

Email reaches people at other providers, and spam from one account can hurt delivery for everyone. So Mail has rules of its own.

• No spam, phishing or bulk mail people didn’t ask for.

• Sending limits. Accounts made through sign-up can send to a limited number of people at first. The limits grow with the account’s age:

  Account age	People per message	People per 24 hours
  First day	10	20
  First week	25	100
  After that	50	500

  Every recipient counts, including Cc and Bcc. Accounts added by a company’s own admin don’t have these limits.

• Only your own From address. You can send only from your own address, your aliases, and the shared addresses you have been given. Mail with anyone else’s address in From or Sender is refused, from the web app and from mail apps alike.

• Don’t get around sign-up limits. Sign-up asks your browser for a small proof of work, and a network can only create a few accounts an hour.

Reporting and suspension in Mail

Every message in Mail has a Report button. We only act on a report when the message carries our own server’s signature for the sender, so nobody can get someone suspended with a forged or made-up message.

A suspended account can’t send mail, but can still sign in, read and save its mail, and sees the reason. Accounts can be suspended:

• by the abuse team, after looking at reports;
• automatically, when three different people report a sign-up account within a week. Reports from accounts less than a day old don’t count. Company accounts are never suspended automatically.

The abuse team can lift a suspension.

What we can see, and what we do

Chat messages are end-to-end encrypted, so we can’t read them and don’t scan them. In Chat we act on reports people send us, on what is public (Discover listings and usernames), and on behaviour such as breaking limits.

Depending on what happened, we may lower an account’s limits, remove a Discover listing, or suspend an account or a bot.