Security & trust
Trust is an operational discipline, not a badge
Messaging fraud, grey routes and careless data handling all show up eventually — in delivery rates, in invoices or in regulatory questions. Here is how we work to keep them out of your traffic.
Anti-AIT & fraud prevention
Artificially inflated traffic, caught early
AIT turns an authentication budget into someone else's revenue. We watch OTP flows for the patterns that give it away and act before the invoice does the talking.
Destination range controls
Allow and block rules on country and prefix level, tightened where abuse patterns are known.
Velocity and conversion checks
Spikes in requests to unusual ranges, or codes never converting to logins, trigger review.
Number validation
Optional validation of destination numbers before submission to remove obviously invalid targets.
Joint investigation
When something looks wrong we contact you with the evidence rather than silently absorbing it.
Traffic monitoring
Someone is watching the routes
Platform and route health are monitored continuously, with alerting to our operations team. Delivery anomalies are treated as incidents, not statistics.
Delivery anomaly alerting
Deviations in delivery ratio or latency per destination raise alerts for investigation.
Sender ID misuse checks
Monitoring for unauthorised or spoofed sender identities on traffic passing our platform.
Volume shift detection
Unexpected volume changes on an account are flagged and confirmed before they continue.
Incident communication
Named technical contacts and defined escalation for anything affecting your traffic.
GDPR & data protection
An EU company handling EU traffic
PingSMS is a Croatian company operating under EU law. Our processes are designed around collecting less, keeping it for less time and being clear about who processes what. The text below is a starting point — align it with your final legal documentation.
Data minimisation
Message content and destination data are processed for delivery and retained only as long as operationally required.
Processing roles
Clear controller and processor definitions, supported by a data processing agreement.
Access control
Role-based access to platform data, with logging of administrative activity.
Consent and opt-out
Support for opt-out handling and consent evidence requirements in your messaging programmes.
Questions about compliance or fraud controls?
We're happy to walk your security or compliance team through how traffic is handled.