Peraly

Acceptable Use Policy

Last updated: 17 August 2026

PRE-LAUNCH — NOT YET REVIEWED BY COUNSEL

Peraly is preparing for early access. This policy describes the product as it is built today and the standards we hold customers to; it has not yet been reviewed by counsel, and a small number of items — a notice period, a postal address — are settled once the operating entity is incorporated.

Scope

This policy applies to everyone who uses Peraly — account holders, workspace members, people invited into a workspace, and anyone acting on their behalf. It applies to content you publish through Peraly, messages you send with it, contacts you store in it, automations you build in it, and the social accounts you connect to it.

It sits alongside the Terms of Service and the Privacy Policy. Where a connected platform’s own rules are stricter than this policy, the platform’s rules apply as well — connecting an account does not exempt you from the terms you agreed with that platform.

The Short Version

Use Peraly to talk to people who want to hear from you, on accounts you are entitled to operate, in ways the platforms allow. Everything below is that sentence with the edge cases spelled out.

Spam and Unsolicited Bulk Communication

You may not use Peraly to send unsolicited bulk messages of any kind — by email, by direct message, by comment, or through an automation that fans one trigger out to many recipients.

Purchased, Rented and Scraped Lists

Every address and contact in your workspace must have reached you legitimately: given to you directly, or created by Peraly because that person contacted your connected account.

Peraly Is Not a Sending Service

Peraly sends email about your account and your workspace. It is not, and may not be used as, a general-purpose relay or bulk-email service.

This is a property of how the product is built rather than a rule we ask you to remember: there is no endpoint anywhere in Peraly that accepts an arbitrary subject and body. Every message is a fixed server-side template with a typed context, and its recipients are read from your own account and workspace records.

Credentials, Accounts and Unauthorized Access

You are responsible for the accounts you connect and the people you let into your workspace.

Impersonation, Fraud and Deception

People are entitled to know who they are talking to.

Automation and Malicious Use

Automation is most of what Peraly is for. These are the uses of it that are not acceptable.

Illegal, Harmful and Deceptive Content

You may not use Peraly to create, store, publish or send content that is unlawful, or that causes the kinds of harm below. This applies to content you publish to a connected channel, content you send to a contact, and content you store in Peraly, including in a knowledge base used by AI features.

Connected Platform Policies

Peraly reaches Instagram, Facebook, YouTube, TikTok and LinkedIn through their official APIs, under developer terms that bind us and, through us, you. Breaking a platform’s rules puts every Peraly customer’s access to that platform at risk, not only yours.

AI Features

Peraly’s AI features draft captions, replies, summaries, translations and thumbnails for you to review. They suggest; they do not publish or send on their own.

You remain responsible for anything you publish or send, whether or not a model wrote the first version of it. Review AI output before it goes out, do not use these features to generate content prohibited by this policy, and do not submit other people’s personal data to them without a lawful basis for doing so.

Your Responsibilities to Your Contacts

When you store and message contacts through Peraly, you decide why and how — which makes you the controller of that data and Peraly your processor.

You are responsible for having a lawful basis to hold and contact those people, for telling them who you are, and for honouring their requests. Deleting a contact in Peraly removes it from our systems; nothing else in the product does that for you automatically.

Enforcement

Some of this policy enforces itself. The messaging window, the suppression list, the refusal of multi-recipient addresses and the absence of any arbitrary send path are properties of the software: an attempt to cross those lines fails rather than being noticed later.

The rest we enforce by hand, in proportion to what happened. Depending on severity we may contact you, limit or pause a feature, suspend sending for a workspace, suspend or terminate an account, or preserve and disclose records where the law requires it. A first-time misconfiguration and a deliberate campaign are not the same thing and are not treated the same way.

We may act without prior notice where a delay would cause harm to a recipient, to a connected platform, or to the deliverability of every other customer’s account-critical mail. Where we do, we will tell you what happened and why as soon as we reasonably can.

Reporting Abuse

If you have received something from a Peraly account that breaks this policy, or you believe an account is being used to break it, email [email protected]. Include the message or a screenshot with its headers if you have them, the account or channel involved, and roughly when it happened — that is usually enough for us to identify the workspace responsible.

Suspected security vulnerabilities go to the same address. Please describe what you did, what happened and what you expected; a reproduction is worth more than a scanner’s output. Do not test against other people’s workspaces or data.

Changes to This Policy

We will update this policy as the product grows and as the platforms we connect to change their own rules. The date at the top shows when it last changed, and we will give notice in the product before a material change takes effect.

Contact

Questions about this policy, or about whether something you want to do is allowed, can go to [email protected]. Asking first is always cheaper than being suspended afterwards, and we would rather answer the question.