Terms of Service

1. About these Terms

These Terms are intended to govern access to and use of the Helmara public website and the Helmara platform/services once finalised. Helmara is an AI business automation product with six specialists: Content Generation, Email Campaigns, Customer Support, Calling Agent, Lead Generation and Paid Ads.

The Master Proposal describes product architecture and planned commercial behaviour. It is not automatically a customer contract. Product facts below are grounded in that documentation and current public site behaviour; contractual obligations that remain undecided are flagged.

Confirm the contracting legal entity, trading name and how these Terms bind website visitors versus authenticated account holders.

2. Eligibility and accounts

Helmara is designed as a business automation platform. Users access the product through authenticated accounts. Account information should be accurate, and account access should not be shared improperly.

Multi-user client accounts / team collaboration are documented as Wave 2 functionality and are not described here as current launch contractual features.

Confirm minimum age, business-only vs consumer eligibility, authority to bind a business, prohibited jurisdictions and any sanctions/export restrictions.

3. Helmara services

Helmara provides modular AI specialists that can be used independently or together. Public product pages describe workflows for content, email, support, calling, lead generation and paid ads, plus WhatsApp-oriented approval for certain outbound actions.

Homepage pricing is presented for demonstration purposes and may change. Final commercial terms (plans, usage rates, taxes) require confirmation before they become contractual commitments.

Confirm which services are included in the current commercial offering and which remain future/Wave 2–3 (for example team members, API keys, white-label, CRM).

4. AI-powered services

Depending on the module, Helmara may use AI-enabled workflows to generate content, assist with support responses, synthesise or transcribe speech, run Calling Agent conversations, classify intents, process leads/workflows and assist with campaigns.

AI outputs may be incomplete, inaccurate or unsuitable for a particular purpose. Clients should review outputs before relying on them for legal, financial, medical or other consequential decisions.

Approve final disclaimer wording for AI accuracy, uniqueness, non-infringement and fitness for purpose. Define responsibility for client-approved AI outputs.

5. Client responsibilities

Clients may provide or connect business information, brand assets, content, email lists, recipient data, support knowledge, call targets, leads, advertising accounts, social accounts and calendars.

Clients are expected to have appropriate rights and permissions to use the information and connected accounts they supply. Exact warranties and remedies for unlawful client-supplied data require legal drafting.

Lead Generation

Lead Generation may include sourcing, enrichment and list workflows that can feed downstream Email, Calling or Ads. Helmara does not state that scraped or public data is always lawful to contact. Compliance obligations for outreach and data use require legal confirmation.

Email Campaigns

The product design includes safeguards such as validation, authentication readiness (SPF/DKIM/DMARC), unsubscribe/suppression handling and approval before launch. Those features do not guarantee inbox placement, open rates, conversions or revenue.

Calling Agent

Documented calling workflows may involve telephony providers, AI disclosure requirements, DNC scrubbing, calling-hour rules, optional recording (opt-in) and campaign approval. Helmara does not guarantee calling-law compliance in every jurisdiction. Recording is not automatic for all calls.

Paid Ads

Paid Ads may help manage campaigns, budgets, audiences, creatives and reporting on external platforms (for example Meta or Google). Ad platforms remain third-party services; Helmara does not guarantee ROAS, conversions, ad approval or platform acceptance.

Customer Support module

“Customer Support” refers to a Helmara product module for end-customer conversations. It is not, by itself, a contractual SLA for Helmara’s own user support.

Draft client lawful-use obligations for lead sourcing, email outreach, calling and advertising without inventing indemnities until counsel approves them.

6. Connected services

Clients may connect third-party accounts (for example social, email, calendar, messaging or advertising platforms). Those providers process information under their own terms. Helmara processes information needed to operate the connection and requested workflow; it does not claim unrestricted access to an entire external account.

7. Approvals and automated actions

Certain outbound or consequential actions are subject to approval workflows depending on the module. Documented examples include approval before relevant content publishing, email campaign launch, Calling campaign launch and Paid Ads campaign launch. WhatsApp is a primary approval channel in the product design.

Not every AI step requires a human tap. For example, Customer Support may answer automatically when confidence is sufficient, and Lead Generation may run and produce results without a publish-style approval gate.

Define contractual responsibility for client-approved actions (content, email, calls, ads, budgets, audiences and claims in generated material).

8. Subscriptions and billing

The documented commercial model is modular and usage-based. Customers may use one or more modules depending on subscription. Monthly and annual billing frequency are part of the Wave 1 product design. Payment-card handling is delegated to Stripe (or the then-current verified payment provider). Helmara does not claim to store full payment-card numbers.

Documented product behaviour includes plan changes (upgrade access described as immediate; downgrade described as effective next renewal), cancellation via a manage/cancel flow, and end-of-period access retention if cancellation proceeds. Those flows are product specifications until confirmed as contractual terms.

Public pricing figures shown on the marketing site are for demonstration and are not guaranteed contractual rates. Exact billable units, allowances, overages, taxes and dunning/grace rules require commercial confirmation.

Confirm refund policy, renewal, taxes, proration, payment-failure behaviour, grace periods, chargebacks and whether upgrade/downgrade/cancellation product flows become binding contractual promises.

9. Usage and service limits

Modules are designed around metered usage (for example generations, emails, conversations, calling minutes or leads). Exact plan limits and overage rules are commercial terms and must match the live billing configuration when published.

Align published plan limits and overage rules with the live billing product.

10. Client content and data

Clients may upload or generate business content within Helmara. Documented retention and offboarding behaviour is described in the Privacy Policy (including deletion of client-owned business content on tenant offboard, subject to documented retention classes).

Confirm ownership, licence and post-termination handling of client content and generated assets in contractual language.

11. Intellectual property

Define ownership of the Helmara platform/IP, licences granted to customers, and rights in AI-generated outputs. Do not invent licence grants until approved.

12. Acceptable use

Helmara is intended for lawful business automation. Misuse that violates law, third-party rights or platform integrity is expected to be prohibited in the final Terms.

Approve an acceptable-use policy covering spam, unlawful calling/outreach, scraping abuse, security interference and other restricted activities.

13. Service availability and changes

Engineering documents may contain availability targets. Those targets are not automatically contractual SLAs. Helmara will evolve; features, modules and integrations may change over time.

Determine whether any availability SLA applies, and approve language for feature changes and third-party provider changes.

14. Suspension and termination

The product design includes subscription states such as past-due behaviour and a user cancellation / offboarding path. Documented data behaviour on offboard is summarised in the Privacy Policy.

Define suspension and termination rights (customer and Helmara), cure periods, outstanding fees, refunds and data handling after termination.

15. Third-party services

Helmara relies on third-party providers (for example payments, messaging, telephony, AI models, email delivery and advertising platforms). Those services are governed by their own terms. Helmara does not control third-party uptime or policy changes.

16. Privacy and security

Use of Helmara involves processing of information as described in the Privacy Policy. Additional information about the platform’s documented security architecture is available on Security & Trust.

17. Disclaimers

Approve disclaimer wording covering AI output accuracy, business outcomes, campaign results, email deliverability, ad performance, lead conversion and third-party service availability. Do not publish aggressive all-caps boilerplate until counsel/business approves it.

18. Limitation of liability

Set any liability cap, excluded damages and mandatory consumer-law carve-outs. Do not invent a monetary cap or exclusion list.

19. Indemnification

Decide whether mutual or one-way indemnities apply (for example client content, unlawful lists/outreach, IP claims) and draft only after approval.

20. Governing law and disputes

Confirm governing law, venue/jurisdiction and dispute resolution method (courts vs arbitration). Do not invent these.

21. Changes to these Terms

When these Terms are finalised, material updates will be posted on this page with a revised “Last updated” date. Notice methods for material changes require legal review.

22. Contact

For product or website enquiries, use the Contact form.

Insert legal/billing contact channels once the contracting entity and notice addresses are confirmed.