Questions, answered.
Didn't find what you're looking for? Email support@sendoracloud.com.
Getting started
How long does it take to integrate?+
Most teams send their first event within 5 minutes using the Web SDK. A full lifecycle migration from an existing tool typically takes 1–2 weeks.
Do I need to pick modules up front?+
No. All 22 modules are available on every plan. Turn on what you need, add others later — no migrations required.
Is there a free tier?+
Yes. 10,000 events/month forever, all modules included. No credit card required. The Email module + broadcasts require a verified sending domain (free to add on any tier); system messages like auth, receipts, and support auto-replies run on Sendora without DNS setup.
Pricing & billing
What counts as an event?+
Customer-emitted events count: identify, track, page view, screen view, link click. System lifecycle events (push.send_requested, push.sent, push.delivered, email.delivered, etc.) and webhook deliveries are FREE.
Does a broadcast to 1,000 users count as 1 event or 1,000?+
Zero events against your quota. Broadcasts emit only system lifecycle events (push.send_requested → push.sent → push.delivered per recipient), all of which are free observability signals. You only burn quota when YOUR code calls track() or identify(). So a daily 1,000-user broadcast doesn't move your event meter at all — useful for capacity planning at any scale.
Do I pay per contact?+
No. Profiles are unlimited on every plan. We think per-contact billing punishes growth.
What happens if I exceed my plan limits?+
Nothing breaks. Overage is billed at the end of the cycle at published per-event rates. We'll notify you before it happens.
Can I cancel any time?+
Yes. Monthly plans cancel any time. Annual plans are prepaid and convert to month-to-month at the end.
Delivery & providers
What about email?+
For customer-authored email (the Email module API, workflow email steps, broadcasts) you add a domain you own — one-time DNS setup, DKIM signed by your domain, your reputation stays yours. System messages (auth, billing, support auto-replies) run on Sendora's infrastructure so you can start without any DNS work.
What about SMS?+
Bring your own provider (Twilio, MessageBird, Sinch) and pay the provider directly. The SMS module abstracts the provider API so you can swap without touching application code.
Why is BYOD required for the Email module?+
Sending reputation is tied to the From domain. If every customer sent from Sendora's domain, one bad actor could get Sendora's mail marked as spam everywhere — hurting every other customer. BYOD isolates reputation per customer. It's also how Resend, Postmark, and SendGrid work.
Data & privacy
Where is my data stored?+
US by default. EU region available on request. We do not move data across regions without consent.
Can I export my data?+
Yes, any time. Events export as JSONL to S3/GCS, profiles as CSV. No lock-in.
Are you GDPR and CCPA compliant?+
Yes. Every event carries a consent allowlist. DSAR workflows are built into the platform.