Terms & Conditions
1. Company principles and scope
Bytesbooster Consulting presents this product under the Bytes Booster brand. Our company terms protect original company materials, respect customer ownership of their business data, preserve confidentiality and explain that external infrastructure and market outcomes have limits. See the company Terms of Use. For this software product, the explicit product subscription terms and any signed order take priority over general website descriptions; mandatory consumer and privacy rights are preserved.
A subscription is access to hosted software, not a transfer of ownership of the shared platform source code. Ownership of any separately commissioned deliverable is determined by its written agreement. No blanket security certification or encryption claim from a marketing page is adopted here without implementation evidence.
2. Current preview and future contract
The current demo and sandbox make no live WhatsApp calls and collect no subscription payment. Published prices are the confirmed monthly platform subscription rates for launch. The final seller identity, registered address, tax treatment, order summary and applicable contractual jurisdiction must be disclosed before checkout. Do not upload customer lists or credentials to this preview.
Free account access
Free registration requires a valid email, a password of 12–128 characters and acceptance of these Terms. Verification is required before login. All public registrations receive a client role and Free plan; no administrator permission, paid entitlement or message credit is granted. Keep credentials private. Login is rate-limited, and sessions expire after 30 minutes of inactivity. This account foundation has not yet undergone an independent security audit.
3. Subscription, billing and usage limits
Platform subscriptions and Meta message usage are separate. The intended default is your own Meta account and billing method, with no Bytes Booster message-rate markup on that direct-billing route. Taxes, bank conversion costs and optional provider charges remain separate. Plans do not include Meta message credit. Additional seats and capacity are opt-in; unused allowances do not roll over. Plan and spending limits must be enforced server-side before execution, including retries and scheduled jobs.
Recurring payment is off unless expressly authorised. A downgrade takes effect at the next renewal unless agreed otherwise. Lower limits must be shown before confirmation and excess records offered for export; downgrading must not silently delete data. Cancelling a renewal retains access until the paid period ends. Provider-approved message categories and the account’s current rate card control billing.
4. Renewal, recovery and deletion
| When | Access & data handling at paid launch |
|---|---|
| Before expiry | Renewal reminders targeted at 7 days and 1 day before expiry, plus an expiry notice. No automatic debit without an explicit recurring mandate. |
| At expiry · Day 0 | Outbound sends, API sends, campaign queues, paid AI calls and workflows pause immediately. Pending jobs do not silently restart or back-send on renewal. |
| Days 1–30 | Read-only workspace and self-service export for the verified account owner. No paid sending. Renewal restores eligible data and settings after checks. |
| Days 31–90 | Restricted recovery archive; ordinary workspace access ends. A verified owner may request export or paid reactivation before day 90. No new message capture. Reminder targets: days 23, 60 and 83. |
| After day 90 | Primary customer contacts, conversations, media and flow data are scheduled for permanent deletion within 7 days. Recovery is not promised after day 90. |
| Backup expiry | Deleted customer content ages out of rotating backups within 30 days after primary deletion. Backups are restricted, not a customer recovery service. Restoration must reapply deletion records. |
The clock starts at the paid subscription’s effective expiry, not the day a reminder is read. An earlier verified deletion request overrides the ordinary recovery window where legally permitted. Fraud investigations, litigation holds or mandatory records may require narrowly scoped retention; access is restricted and retention is reviewed. Data held separately by Meta, an AI provider or a downloaded export is governed by that holder.
5. Acceptable use and immediate protective suspension
The platform must not be used for unsolicited bulk messaging, lists without valid consent, repeated contact after opt-out, phishing, scams, impersonation, malware, credential theft, harassment, threats, hate or incitement to violence. Sending-rate and quality controls are mandatory; a paid subscription never grants permission to spam.
Explicit sexual or pornographic content, adult entertainment or sexual services, escort/solicitation services, non-consensual intimate material and sexual exploitation are prohibited. Child sexual exploitation material, trafficking and exploitation are strictly prohibited and may be reported as legally required. Other illegal goods, services or uses, and activities prohibited by Meta’s current policies, are also restricted.
Credible signs of serious misuse trigger immediate protective suspension of sending, affected workflows and tokens, without advance warning where necessary. Evidence is preserved proportionately; an account notice and reason are provided unless legally or operationally unsafe. An authorised reviewer decides reinstatement or termination; AI flags alone do not make an irreversible deletion decision. Appeal through bytesbooster@gmail.com, normally within 14 days of notice. No fees buy reinstatement. Proven severe or repeated misuse may lead to permanent termination, subject to applicable law and fair review.
6. Consent, suppression and security
Keep auditable opt-in evidence, identify the sender accurately, use approved templates where required, and honour opt-out immediately. Maintain a suppression list so a later contact import does not re-enable opted-out recipients. Stop requests, complaint spikes, low quality ratings and abnormal traffic must be able to pause campaigns. Store tokens securely; never share passwords or OTPs with support. No recursive workflow loops or unauthorised access attempts are allowed.
7. Support and onboarding
AI-first guidance. Human accountability.
Planned support combines a searchable knowledge base, guided setup checks and a clearly labelled AI assistant. AI explains setup, templates, billing categories and common errors from approved product documentation. It cannot guarantee Meta approval, change account ownership, promise refunds, bypass a suspension or request passwords, OTPs, card details or full API secrets.
| Support layer | What is included at launch |
|---|---|
| Free Sandbox | Guided templates and knowledge base. No externally billed AI or live onboarding. No guaranteed human response SLA. |
| Every paid module | Self-service setup checklist, connection diagnostics and 50 product-support AI replies per workspace/month. |
| Growth / Scale | 100 / 200 product-support AI replies per workspace/month. These help users operate the platform; they are not customer-facing bot messages. |
| Human escalation | Product faults, billing disputes, privacy/security incidents, misuse appeals and cases the AI cannot resolve. AI quotas never block these escalation routes. |
AI replies stop at their quota; the knowledge base and ticket route remain available. There is no automatic AI overage or paid upgrade. Vendor cost controls and maximum answer length must be implemented before paid support AI is enabled.
Response targets, not invented guarantees.
Planned human support hours: Monday–Friday, 10:00–18:00 India time, excluding published Indian public holidays. Standard first-response target: within one business day. Verified account-wide sending outages and suspected security incidents are prioritised, with a four-business-hour initial review target during those hours. These are response targets, not guaranteed resolution times or a contractual 24/7 human SLA. The future AI help interface may be available outside those hours.
Setup without a surprise service bill.
Standard guided API onboarding, starter templates and in-product diagnostic steps have no separate setup fee on paid plans. Customers supply their own business information, number ownership and Meta access. Manual migrations, bespoke integrations, custom-built flows and done-for-you implementation require a separate written scope and price before work begins. Human assistance for product defects and billing concerns is not a paid add-on.
8. Refunds, liability and dispute handling
Read the product Returns & Refunds Policy before purchase. No guaranteed sales, message delivery, Meta verification or uninterrupted third-party availability is promised. Nothing excludes liability or remedies that applicable law does not allow us to exclude. AI outputs require appropriate checking. Customers can request review of disputed charges or suspension through the published support channel.
Business location: Barrackpore, Kolkata, India.
Product support, privacy, misuse reports and refund requests: bytesbooster@gmail.com
WhatsApp: +91 87774 38845 ↗