Unsubscribe Footer
Broadcasts sent via Onsite automatically include an unsubscribe footer. This is a platform-level requirement and cannot be removed for individual accounts.
Here's why it's there - and why it's actually a good thing for your building.
It's a legal requirement
Anti-spam laws in Australia (the Spam Act 2003) require every commercial electronic message to include a functional unsubscribe mechanism. Similar laws exist in the US (CAN-SPAM), Canada (CASL), and the EU/UK (ePrivacy regulations). Penalties for non-compliance in Australia can reach up to $2.22 million per day.
Because Onsite sends messages on behalf of buildings and estates across multiple jurisdictions, the unsubscribe link ensures compliance with the broadest set of requirements.
It protects your email deliverability
Gmail, Outlook, and Yahoo now require bulk senders to include an unsubscribe option. Senders without one risk having their messages flagged as spam or blocked entirely. Since Onsite uses shared sending infrastructure, this protects deliverability for all customers on the platform - not just yours.
It keeps your sender reputation healthy
If a recipient can't unsubscribe, their only option is to mark the message as spam. Spam complaints damage sender reputation, which directly impacts whether your future emails land in inboxes or junk folders. An unsubscribe click is always better than a spam complaint.
It improves your communications
A clean mailing list means your broadcasts reach people who actually want to receive them. This leads to better open rates, fewer complaints, and more effective communication with your residents and owners.
What happens when a resident unsubscribes?
When a resident clicks the unsubscribe link, they will no longer receive broadcast emails from your building. If they change their mind, they can resubscribe at any time by visiting their profile and clicking the Resubscribe button.
Can I remove it?
No. The unsubscribe footer is enforced at the platform level and cannot be disabled. This is standard practice across all email platforms - Mailchimp, HubSpot, SendGrid, and others all enforce the same requirement for the same reasons.