Consent Compliance
Commercial-message compliance, out of the box.
Turkish law (no. 6563) requires that consent for commercial email and SMS is registered with İYS, the national consent registry. Signalbird keeps the ledger, checks it before sending, and blocks messages without consent.
Why it exists
One message without consent, a six-figure fine
A single marketing email sent without consent, or without registering that consent, is enough for an administrative fine. Most teams know this, but their systems are not built for it: consent is a spreadsheet column and the check is a step nobody performs.
What it does
6 capabilities, one screen.
A gate before sending
Every commercial message checks the recipient's consent status. A recipient who opted out drops from the batch and appears in the report, nothing disappears silently.
The system sets the class
Anything leaving the campaign screen is commercial by definition. You cannot mark a commercial message "transactional" to skip the check; "the customer flagged it wrong" is not a defence in an audit.
Opt-out becomes a rejection
Someone who unsubscribes is written into the ledger as a rejection and forwarded to İYS. The law says three business days; the system aims for minutes.
Compliant without the API module
The İYS integration module is priced separately. Without it you can export consents to a file, upload them from the İYS panel and pull the rejection list back, the system still runs compliantly.
Your brand or ours
Connect your own İYS brand if you have one; otherwise send under the shared brand. The second route comes with an undertaking, a monthly volume ceiling and a complaint-rate threshold.
Proof of consent is kept
An "approved" flag is not enough: the source, date and IP of the consent are stored. The burden of proof is on the sender.
How it works
In 3 steps.
Connect the account
İYS code, brand code and credentials.
Move your consents
Via API or by file.
Send
The gate runs automatically on every commercial message.
Specifications
Does it really do that?
- Channels
- Email (EPOSTA) · SMS (MESAJ)
- Sync
- Push every 15 min · pull hourly
- File route
- İYS bulk upload format (CSV)
- Out of scope
- Transactional messages and app notifications
Questions
Things you might wonder.
I have no İYS registration, can I send at all?
Transactional messages (password reset, order updates, invoices) may legally be sent without consent and are never blocked. Consent is required only for commercial messages.
Is the İYS API module mandatory?
No. Without it there is a file-based route: export consents, upload them from the İYS panel. Once a day is enough.
Works well with