Communi­cation & Consent Policy

1. Scope

This policy covers two kinds of communication:

• PulseForge's own messages — marketing emails or other electronic messages we send to prospective and current clients.
• Automated messages in client workflows — any email or SMS that a workflow we build sends on a client's behalf. Most of our workflows are internal and send no external messages; customer-facing messages are added only where a workflow genuinely needs them.

It applies to any electronic communication that may fall under the Spam Act 2003, the Do Not Call Register Act 2006 or the Australian Privacy Principles.

2. Consent — express and inferred

Under the Spam Act 2003, a commercial electronic message can only be sent with the recipient's consent. The Act recognises two types of consent:

• Express consent — the recipient has clearly agreed to receive messages, e.g. by ticking an unticked checkbox or signing up to a list.
• Inferred consent — consent that can reasonably be inferred from the recipient's conduct and an existing business or other relationship (for example, an existing client receiving information related to the services they already use), or, in limited circumstances, from the conspicuous publication of a work email address where the message is relevant to the recipient's role.

Certain designated commercial electronic messages — for example, messages from government bodies, registered charities, or educational institutions to their current or former students — are exempt from the consent requirement, but must still accurately identify the sender.

We don't send, and don't configure workflows to send, commercial messages without a lawful basis under Australian law.

3. Sender identification

Every commercial message includes accurate sender identification and contact details. For email, the From address and signature identify the sending business. For SMS, the sender ID or number identifies the sending business. On messages a client workflow sends, the client's business — not PulseForge — is the identified sender.

4. Unsubscribe handling

Every commercial message includes a functional unsubscribe mechanism:

• Email — an unsubscribe link or a clear instruction to reply to opt out.
• SMS (only where a client workflow sends SMS) — a clear way to opt out, such as replying STOP.

Unsubscribe requests are honoured within 5 working days, as required by the Spam Act, and the recipient is added to a suppression list.

5. Our own marketing messages

PulseForge sends marketing emails only to people who have given express consent or where consent can reasonably be inferred from an existing business relationship. Every marketing email identifies PulseForge Pty Ltd and includes a way to unsubscribe. We don't buy, rent or scrape contact lists. Messages you need as part of an engagement — such as replies to your enquiry, your Website Review, assessment reports, project updates and invoices — are service communications rather than marketing.

If we make telephone calls for marketing purposes, we check the Do Not Call Register where required.

6. Automated messages in client workflows

Where a workflow we build sends automated email or SMS on a client's behalf (for example, a confirmation that a request has been received, or a reminder about a document the client needs):

• The message template is approved by the client before go-live
• The client's business is identified as the sender, with contact details
• Commercial messages include a working unsubscribe or opt-out
• Opt-outs are added to a suppression list that the workflow checks before sending
• Any AI-drafted message is reviewed by the client's staff before it is sent (see our AI Use Policy)

7. Client responsibility

The client (the business on whose behalf the messages are sent) is responsible for:

• Having a lawful basis (consent) for every commercial message the workflow sends
• Using correct sender identification and contact details
• Honouring unsubscribe requests within 5 working days, including requests received outside the automated channels
• Maintaining suppression lists and keeping records of consent where required
• Not uploading purchased or scraped contact data
• Checking the Do Not Call Register before making telemarketing calls, where required
• Responding appropriately to complaints about communications

PulseForge configures workflows to support compliance by default, but cannot verify the lawful basis of every contact in your systems. If you're unsure whether a list can be lawfully contacted, ask us before launch and we'll help you think it through, or refer you to a legal adviser.

8. Logging opt-outs

Where a workflow we build handles opt-outs, it records the date, channel and recipient identifier in a suppression list held in the client's own systems. Suppression lists are checked by every workflow for the same client. Suppression is not shared between businesses — each business maintains its own list.

9. Prohibited use

PulseForge will not configure or operate workflows that:

• Send unsolicited bulk marketing to purchased or scraped lists
• Spoof or mislead about the sender's identity
• Omit unsubscribe options from commercial messages
• Continue messaging after opt-out
• Use deceptive or misleading content
• Target numbers on the Do Not Call Register without an exemption

Where we identify a breach, we will pause the relevant workflow and discuss remediation with the client. Persistent breaches may result in termination of the engagement.

Questions: hello@pulseforge.com.au. This policy is general — for specific legal questions, consult a qualified Australian legal professional. The ACMA website (acma.gov.au) has authoritative guidance on the Spam Act and electronic marketing.