Secure SMS delivery.
Zero compliance risk.
Flowora carries application-to-person messaging for licensed operators across 164 markets, on connections we hold in our own name. Consent, sender registration and quiet hours are settled before a message leaves, not explained after one is refused.
- Bulletproof compliance tools
- Direct carrier connections
- Automated opt-in management
- Data residency options
- ISO 27001Certified
- SOC 2Type II
- RegisteredProcessor
- Sender IDRegistrar
- PCI DSSAligned
- Pen TestedTwice Yearly
reachable on a connection we hold ourselves, not resold
messages accepted without a content or sender rejection
from documents submitted to a sender identity approved
Dublin, Frankfurt and Toronto, chosen per customer
Six things we settle before you send
Delivery is the easy half. What separates a route that survives a regulator from one that does not is everything that happens in the two seconds before a message leaves the platform.
Routes we own the relationship on
Every market is reached over a connection we hold in our own name. When a network changes a rule we hear it from the network, not from a rejected batch two days later.
One consent record per player
Opt-in, its source, its timestamp and every subsequent change live in one register. A send checks it, an opt-out writes to it, and an auditor can read it without our help.
Residency you choose
Message bodies and recipient numbers stay in the region you nominate. Dublin, Frankfurt or Toronto, set per customer and enforced at the storage layer rather than by policy.
Quiet hours from the recipient
The window is read from the country the destination number belongs to, never from where the campaign was scheduled. Anything landing inside a closed one waits with a visible release time, and a held message is never counted as sent.
The stricter rule always wins
Where our own policy and a local rule disagree, the local rule takes precedence. Anything failing either test comes back as an error naming the test it failed, and nothing is queued in the hope it passes later.
Filtering visible while it happens
Silent carrier filtering is the hardest failure to see. Content-class rejections surface as their own event so a blocked template is obvious inside the hour rather than at month end.
Every market keeps its own paperwork
Six of the one hundred and sixty four, written the way our rule set stores them: the consent basis, the sender identity a network will accept, the hours a marketing message may not arrive, and the local detail that catches people out.
- Basis
- Explicit opt-in, ePrivacy Art. 13
- Sender
- Alphanumeric, pre-registered
- Quiet hours
- 21:00 to 08:00 local
Responsible-play wording required in the body of every marketing message.
- Basis
- Express consent, CASL
- Sender
- Long code or short code
- Quiet hours
- 21:00 to 09:00 local
Sender must identify the licensed entity, not the brand alone, in the first message.
- Basis
- Explicit opt-in, marketing act
- Sender
- Alphanumeric, pre-registered
- Quiet hours
- 20:00 to 09:00 local
Bonus terms may not be abbreviated below a stated minimum in the message body.
- Basis
- Explicit opt-in, GDPR Art. 6
- Sender
- Alphanumeric, registered per brand
- Quiet hours
- 22:00 to 08:00 local
A registered brand name must match the operating licence exactly, not the trading style.
- Basis
- Opt-in, POPIA s.69
- Sender
- Alphanumeric or short code
- Quiet hours
- 20:00 to 08:00 local
Opt-out must be free to the recipient and honoured inside the same working day.
- Basis
- Prior consent, personal data law
- Sender
- Alphanumeric, per-network
- Quiet hours
- 21:00 to 07:00 local
Registration is per network rather than per market, so one refusal does not block the rest.
From first call to first route
Licence and entity check
We read the licences you hold and the entity names printed on them, because half of all registration refusals are a mismatch between the two.
Sender identity filed
Registration goes in per market under your own entity. We chase it, and you watch the state of every submission as it moves.
Consent imported
Whatever the opt-in evidence looks like today, it arrives in the register with its original source and timestamp intact.
First route opened
One market goes live, we read the first week of delivery events together, then the rest follow at whatever pace suits you.
Three problems that arrived as emergencies
Nordics
6 weeks
to a compliant launch across four markets
A group that had been told Sweden would take a quarter
Four brands, four sender identities, four sets of documents that did not match the licences they were filed against. We refiled them, corrected the entity names, and had all four approved inside six weeks.
- Markets
- 4
- Sender identities
- 12
- Rejections after refiling
- 0
Latin America
34%
more messages reaching a handset
The same list, the same offer, a different route
An operator was losing a third of its Peru traffic to silent filtering and reporting it as delivered. Moving to a per-network registration and rewriting two templates recovered it without adding a single contact.
- Delivery before
- 63%
- Delivery after
- 97%
- Extra spend
- None
Regulated Europe
1 query
to answer a regulator's consent request
An audit that used to take three weeks
Consent evidence lived in a CRM, a support desk and two spreadsheets. Consolidating it into one register meant the next request for proof of opt-in on 40,000 players was answered the same afternoon.
- Players evidenced
- 40,000
- Systems queried
- 1
- Response time
- Same day
What the people who sign it off say about it
We chose them because they were the only ones who answered the residency question with a region rather than a paragraph. Two years later that is still the reason we stay.
Amaia ZubiriHead of compliance, operator group, Iberia and Latin AmericaThe register is the whole product as far as I am concerned. Our last audit took an afternoon instead of a fortnight.
Piotr WodnickiData protection officer, platform supplier, Central EuropeThey refused a send of ours once and told us exactly which rule did it. Nobody had ever done that before, they just let it fail quietly.
Lorcan WhyteMessaging lead, multi-brand operator, IrelandAsked on most first calls
- Must we be licensed everywhere you can deliver?
- Only where you actually send. The licences attached to your account are checked against each destination, so a lapse or a newly added territory stops traffic until the paperwork catches up. That wait is the usual reason a launch slips.
- Whose sender identity does traffic go out on?
- Yours. We file the registration on your behalf and maintain it, but the identity belongs to your licensed entity and so does the reputation it builds. If you leave, it goes with you.
- A network moves the goalposts. When do we find out?
- Before it bites, in almost every case. The connection is in our name, so the notice arrives here first, and your account gets the affected templates and identities listed against the new revision while the old one is still in force.
- Can you prove consent if a regulator asks?
- That is what the register is for. Opt-in state, its source, its timestamp and every change since are one query, exportable in a form a regulator will accept, without us being in the room.
- Where does our message data physically sit?
- In the region you nominate at the start of the engagement: Dublin, Frankfurt or Toronto. It is enforced in the storage layer rather than promised in a policy, and delivery to a network outside that region necessarily transfers only the number and the body.
- How quickly can we open somewhere we have never sent?
- Our median is eleven days from documents submitted to an approved identity. At one end sit the markets with no pre-registration at all, where it is same day; at the other, the ones that want a local entity behind the filing, which runs to about five weeks.
Something more specific? compliance@flowora.media reaches the compliance desk directly.
Tell us the market that is refusing you
Bring the rejection message, the sender identity and the licence it sits under. Most first calls end with the reason named and a filing date agreed.