Legal documents

Service Level

States plainly what we commit to and — more importantly — what we do not commit to yet.

Last updated: 28 July 2026 · Data controller / service provider: Bildirim.io service operator

This English text is an informational translation. The agreement is concluded in Turkish and governed by Turkish law; in case of any discrepancy, the Turkish version prevails.
Uptime is NOT measured by the system itself: a server that has crashed cannot count its own availability. Measurement is left to an independent monitoring service running outside our infrastructure, and we publish the result at bildirim.io/durum. That figure is FOR INFORMATION: it is not a committed target and does not enter the service-credit calculation. The performance targets below, by contrast, are committed, and anyone can verify them at bildirim.io/durum and api.bildirim.io/v1/slo.

Measured performance targets

The targets below rest on real load measurements, not estimates. How each row is measured and where its target comes from is written in the api.bildirim.io/v1/slo response, where you can also see the current values.

IndicatorTargetMeasured baseline
Queueing a campaignUnder 5 seconds≈0.16 s at 200,000 subscribers
Start of delivery (p95)Under 60 secondsMeasured continuously from live traffic
Resolving the target audienceUnder 2 seconds97 ms at 200,000 subscribers
Worker livenessUnder 5 minutes without a heartbeatHeartbeat every 60 seconds
Send error rateBelow 5%Calculated over the last 7 days
Baseline measurements were taken on a single-server setup and are not a capacity commitment. The targets sit deliberately well above the measured values: a target is not “the number we hit at our best” but “the threshold at which we intervene”.

What we commit to today

ItemCommitment
Support response time (free plan)Within 3 business days
Support response time (paid plans)Within 1 business day
Acknowledging a security report3 business days
Data breach notificationWithin 72 hours of becoming aware
KVKK requestsWithin 30 days
Planned maintenance announcementBy email, as far in advance as possible
Price change noticeAt least 30 days in advance

Out of scope

Whether a notification reaches the end user’s device depends on the push services run by browser and operating-system vendors. Delays, throttling or outages in those services are outside our control. Likewise, a device being switched off, having no network connection, or notification permission having been withdrawn will prevent delivery.

For that reason no push provider — us included — can guarantee delivery. The “sent” count you see in the panel means the notification was accepted by the push service.

Service credits

If the performance targets above are persistently missed within a calendar month, service credits apply on paid plans at the rates below. The credit is deducted from the next billing period.

Time the target was missed (per month)Service credit
More than 4 hours10% of the monthly fee
More than 12 hours25% of the monthly fee
More than 24 hours50% of the monthly fee
More than 72 hoursThe full monthly fee and a right to withdraw
A service credit is the sole remedy for a missed target, and our total liability is bound by the limit in the Terms of Service. Credits are calculated on targets marked as committed and measurable; indicators reported for information only (e.g. monthly API availability — measured by an independent probe and published on the status page, but not committed) are excluded from the calculation.

Enterprise SLA

If you need higher commitments, a bespoke measurement method or a contractual service level, write to [email protected]. In enterprise agreements the scope, measurement method and credit rates are agreed separately.

Bildirim

For questions about this document, write to [email protected] .

All legal documents