العربية

Security & Trust

Powerful automation.
Control built in.

Helmara’s documented architecture approaches data protection, access, tenant boundaries, approvals and product safeguards as part of how automation is designed - not as an afterthought.

Explore our approach How Helmara works →
  1. User
  2. Authentication
  3. Tenant
  4. Helmara
  5. Approval
  6. Action

Business data stays inside tenant boundaries. Important outbound actions are designed to wait for approval before they run.

Trust summary

Four foundations of control.

How Helmara’s architecture is designed to protect business data while automation stays accountable.

  • Data protection

    Encryption at rest and in transit, with production credentials designed for managed secret storage.

  • Tenant boundaries

    Organisations operate in isolated workspaces, with role-based access as part of the platform design.

  • Human control

    Key outbound actions are designed to require approval - including via WhatsApp - before they execute.

  • Defined lifecycle

    Documented retention defaults, plus export and deletion workflows as part of the specification.

Data protection

Protect data in motion and at rest.

Helmara’s technical specification includes encryption for stored data and TLS 1.2 or later for data in transit. Production secrets are designed to come from managed secret storage rather than application code.

  1. In transit TLS 1.2+

    Client and service traffic is specified to use modern transport encryption.

  2. Platform Encrypted storage

    Architecture specifies encryption for database, object storage and cache where enabled.

  3. Credentials Managed secrets

    AWS Secrets Manager and KMS sit in the documented production credential model, with key rotation in the specification.

Tenant isolation & access

Your workspace. Your boundary.

The platform is designed around tenant isolation so users operate inside their organisation’s data, with role-based access and module entitlements as part of the architecture.

Tenant A

Workspace data

Tenant B

Workspace data

Tenant C

Workspace data

Access is controlled through Client Portal accounts and role-based permissions defined in the platform architecture. Keep credentials limited to people who should manage your workspace.

Automation with control

AI prepares the work.
You approve what matters.

Security is not only encryption. For important outbound actions - such as publishing, campaign launches and similar gated workflows - Helmara is designed so the action waits for client approval, including via WhatsApp, before it executes.

  1. 1 Prepared

    A specialist prepares the action inside your workspace.

  2. 2 WhatsApp

    The request is sent for approval through the documented approval flow.

  3. 3 Decide

    You approve or reject. Approval tokens are designed to be signed so tampered decisions are rejected.

  4. 4 Execute

    Only after approval does the gated action run.

Not every AI step requires a tap. The architecture gates important outbound actions - it does not claim that every internal computation waits for a human.

Auditability

Privileged actions should leave a trail.

The architecture specifies an immutable, append-only audit log for privileged actions, with a documented default retention of 3 years.

  1. Action prepared
  2. Approval requested
  3. Decision recorded
  4. Action executed

Payments

Card data stays with Stripe.

Payment-card handling is delegated to Stripe. Helmara’s design does not store card numbers on its own application infrastructure. Inbound payment webhooks are designed to verify cryptographic signatures before processing.

This describes Stripe delegation of card handling - not a claim that Helmara itself is PCI certified.

Data retention

Documented defaults for how long data lives.

These retention values come from Helmara’s documented data-retention specification. They are defaults - not marketing estimates.

Email events 13 months rolling
Call transcripts 90 days default (configurable)
Call recordings 30 days, opt-in only
Ad metrics 24 months
Support conversations 13 months
Invoices 7 years
Audit log 3 years
Client-owned content & leads Per ownership / offboarding / deletion rules

Data access & control

Export and deletion are part of the specification.

The architecture includes per-tenant export and deletion workflows, with a documented 30-day target for data subject requests. Detailed legal privacy disclosures belong on the Privacy Policy.

  • ExportPer-tenant data export as specified
  • DeletionRight-to-delete workflows in the design
  • DSAR target30 days documented response target

Product safeguards

Controls inside the specialists.

Documented safeguards for Calling, Email and Customer Support - described as architecture, not as guarantees.

Calling Agent

  • Region-appropriate AI disclosure preamble in the specification
  • Do-Not-Call / suppression scrubbing before dialling, as designed
  • Call recording opt-in only (default off), 30-day retention when enabled
Calling Agent →

Email Campaigns

  • SPF, DKIM and DMARC verification specified before production sending
  • Enforced unsubscribe handling in the campaign design
  • Physical address requirements as part of sender readiness
Email Campaigns →

Customer Support

  • Support widget designed for client-allowlisted domains
  • Signed widget key as part of the embedding model
  • Support conversations retained 13 months by documented default
Customer Support →

Connected services

Connected accounts need careful credential handling.

Connected-account sessions are designed to be encrypted at rest. Secrets are not returned to the browser, and disconnect is designed to wipe stored secrets for that connection.

  • Encrypted session storage for connected accounts
  • No secret material returned to the client UI
  • Disconnect wipes stored credentials for that link

Clear boundaries

What this page does not claim.

Helmara documents security architecture and controls. It does not present unsupported certifications or absolute guarantees.

  • No SOC 2, ISO 27001 or HIPAA certification claims
  • No claim that Helmara itself is PCI certified
  • No “100% secure” or unhackable guarantees
  • No invented MFA, SSO, SCIM, pen-test or bug-bounty programs as current public claims
  • No claim that every AI action requires approval
  • No claim that every call is recorded

Security questions

Straight answers. No overclaiming.

How does Helmara handle my data?

The technical specification includes encryption at rest and in transit, tenant isolation, role-based access and audit logging. Payment-card handling is delegated to Stripe rather than storing card details in Helmara’s application infrastructure.

Are calls recorded automatically?

No. Call recording is defined as opt-in rather than automatic, with a default 30-day retention period for recordings when enabled.

Does email include unsubscribe handling?

The Email Campaign specification includes enforced unsubscribe handling and sender-domain readiness requirements such as SPF, DKIM and DMARC before production launch.

Is Helmara SOC 2, HIPAA or similarly certified?

Helmara documents security architecture and controls. External certifications such as SOC 2 or HIPAA are not claimed here.

Who can access my workspace data?

Access is controlled through your Client Portal account and role-based permissions defined in the platform architecture. Restrict credentials to people who should manage your Helmara workspace.

More answers live in the Data & Security FAQ.

Automation you can stay in control of

Put AI to work without giving up the final say.

Explore how Helmara combines six AI specialists with connected workflows, approvals and business-owner control.

See how it works → Contact Helmara →