This page is here to make expectations easier to understand while Shikem is in active rollout. It keeps the practical terms customers need most: acceptable use, billing, compliance, account responsibility, and platform protection.
Shikem is intended for legitimate business, nonprofit, support, and customer communication workflows. Customers are responsible for obtaining proper consent, following channel rules, and using verified sender identities where required.
You agree not to use the platform for spam, unlawful outreach, deceptive messages, or prohibited content. SMS, email, and voice traffic may require additional review, registration, or policy checks before certain use cases are approved.
Plans may include monthly base pricing plus usage-based overage where applicable. Charges depend on the services, volumes, and sender setup you choose. If something looks off, contact us and we will review it with you.
Shikem is in active production rollout. Early customers can request improvements, workflow changes, and onboarding help while the platform is still being shaped. We reserve the right to protect the platform from abuse, fraud, or harmful use.
You are responsible for activity that happens through your account, users, inboxes, numbers, domains, and sender identities. Keep credentials secure, use authorized senders only, and let us know quickly if you suspect misuse or unauthorized access.
We may pause, limit, or terminate access if we detect fraud, abuse, prohibited traffic, unpaid balances, compliance violations, or activity that threatens platform health, carriers, inbox providers, or other customers.
SMS, MMS, voice, email, carriers, and provider services can have their own rules, fees, filtering, delivery behavior, or approval requirements. Shikem helps manage these workflows, but outside providers may still delay, reject, or block traffic.
We may store operational records such as message metadata, audit logs, submissions, billing activity, and support interactions so we can operate the platform, investigate issues, and improve reliability. Sensitive data should only be used where your workflow and applicable laws allow it.
If you have questions about compliance, permitted use, billing, or rollout expectations, use the contact form in the header and our team will respond directly.