Arino One
Arino One Trust Centre
How your platform is built, secured and operated. Review the controls, follow the evidence and get the documents your team needs.
Video Guide
GDPR Native by Design
01
Security & Privacy
Security controls, consent and data residency.
Security
Security controls stated plainly, not badged
Arino Core is built on Lovable and inherits its platform security model. Arino One configures and operates the controls on each platform. We describe the controls that are enabled; we do not publish certification claims.
- Encryption in transit (TLS) for all channel, API and dashboard traffic; encryption at rest on the managed database layer.
- Role-based access to each platform, with access limited to named Arino One engineers on the customer's account.
- Secrets and provider credentials are stored in the platform secret store, never in application code.
- Per-platform isolation means a security question is answered for one customer, not for a shared population.
Compliance
GDPR-aligned controls and documentation for review
Arino One is an Irish company operating under EU law. We provide the documentation procurement and legal teams ask for, and we describe how data subject rights are handled per platform rather than asserting compliance outcomes.
- Data processing agreement, sub-processor list and completed security questionnaires supplied on request.
- Regional hosting options (EU, North America, APAC) selected at provisioning time.
- Per-workspace erasure so a data subject request can be satisfied without touching other customers.
- Consent and opt-out state is held with the contact record and enforced on outbound sends.
Infrastructure
Known infrastructure, in a region you choose
Arino One does not run its own data centres. Platforms run on Lovable's managed cloud infrastructure, with connectivity through Infobip's carrier network — both assessable by your team.
- Managed cloud hosting through Lovable, with regional placement chosen at provisioning.
- Carrier and channel connectivity through Infobip's global network.
- Managed database and storage layer per platform, with automatic backup.
- EU, North America and APAC deployment routes for data residency requirements.
02
Platform & Operations
Architecture, deployment and ongoing support.
Architecture
Single-tenant architecture you can draw on a whiteboard
Each customer runs a dedicated Arino Core platform rather than a shared tenant on a multi-customer platform. The data path is short and inspectable: channel provider, your platform, your connected systems.
- One dedicated Arino Core platform per customer — no shared application database between customers.
- Channels reach the platform through Infobip or Meta; the platform holds conversation state and business logic.
- Connectors to your systems (CRM, commerce, workspace) are configured per platform, not shared across customers.
- The WhatsApp Business Account and the platform remain the customer's assets.
Deployment
A deployment method with defined steps and owners
Provisioning follows the same sequence on every engagement, so a buyer can plan around it. Arino One performs the work; the customer supplies approvals and business rules.
- Architecture review — channels, systems, region, data flows and success measures agreed in writing before build.
- Provisioning — dedicated platform created on Arino Core, typically in about fifteen minutes.
- Channel enablement — WhatsApp Business Account verification, sender and template setup with Infobip or Meta.
- Integration and handover — connectors, automations, dashboards, team training, then ongoing managed support.
Managed service
Arino One operates the platform, not just delivers it
Every deployment described on this site is provisioned, configured and supported by Arino One. There is no expectation that the customer runs the platform.
- Provisioning, channel verification, connector setup and template governance handled by Arino One.
- Named contacts for operational and security questions at hello@arino.one.
- Change requests, new automations and additional channels delivered inside the same platform.
- Support for extending the platform with Lovable, as a Lovable Solution Partner.
Monitoring
Operational visibility on the platform we run on
Arino Core runs on Lovable's managed hosting. Application, delivery and channel health are monitored through the platform's own tooling and the provider consoles, and Arino One acts on what they report.
- Application and function-level logging on each platform, retained on Lovable.
- Message delivery, failure and sender-quality signals monitored through Infobip and the WhatsApp Business Platform.
- Automation runs and conversation state are visible in the platform dashboards your team uses.
- Incidents and channel-quality issues are raised to your named contact by Arino One.
Performance
Performance characteristics of a dedicated platform
Because each customer has their own platform, throughput and responsiveness are not shared with other tenants. Message throughput itself is governed by your WhatsApp Business Account quality rating and provider limits, which we manage with you.
- No noisy-neighbour contention from other customers on the application layer.
- Sending capacity is governed by Meta messaging limits and sender quality, which Arino One monitors and works to raise.
- Regional deployment reduces round-trip latency between the platform and your users.
- Volume growth is handled inside the same platform rather than by migrating provider.
03
Evidence & Responsibilities
Partners, documentation and commercial clarity.
Partners
Named platform relationships, not anonymous infrastructure
Arino One does not operate a messaging network. We build on platforms an enterprise buyer can already assess independently, and we say which one does what.
- Lovable Solution Partner — Arino Core is built and operated on Lovable.
- Infobip — carrier and WhatsApp Business Platform connectivity, at wholesale rates passed through without markup.
- Meta Business Partner and member of Meta's Business Messaging Accelerator — WhatsApp Business Platform sender verification and template governance.
- ElevenLabs for AI voice where a deployment includes it.
Documentation
Public documentation, not a sales deck
The behaviour of the platform is documented publicly and can be read before any commercial conversation. Buyers can hand it to their own technical reviewers.
- Product documentation covering setup, channels, automations, account services and troubleshooting.
- Infobip connection guide with the exact provisioning and webhook steps.
- Enterprise guides on pricing mechanics, channel selection, residency and build-versus-buy decisions.
- Design, content and SEO standards published as a living design system.
Customer stories
Deployments described in engineering terms
Each customer story states the architecture, the channels, the automations and the operating model — enough for a reviewer to judge whether it resembles their own problem.
- Global HR communications for more than 25,000 contributors on a single governed platform.
- Six dedicated WhatsApp Business Platform environments run for one education publisher.
- Healthcare deployment combining WhatsApp, workflow automation and AI voice.
- Retail and hospitality deployments covering commerce, concierge and guest journeys.
Technical validation
Claims a technical reviewer can test
Nothing on this site requires you to take our word for it. The platforms are public, the documentation is public, and the deployment can be reviewed before contract.
- Architecture review before commitment, conducted with your engineers.
- Lovable, Infobip and Meta platform documentation can be assessed independently of Arino One.
- Platform behaviour, dashboards and automation logic are demonstrated on a working platform, not in slides.
- The platform is yours: it can be inspected, extended and audited by your own team.
Transparency
Costs, limits and responsibilities in the open
The parts of a messaging programme that usually surprise buyers — conversation pricing, sender quality, template approval, provider limits — are documented rather than discovered after signature.
- Infobip and Meta usage is billed at cost, with no per-message Arino markup.
- Build and connection fees are published rather than quoted case by case.
- Where a capability is planned rather than live, it is labelled as planned.
- Where responsibility sits with the customer — content, consent, business rules — that is stated.
This page is maintained by Arino One to answer common security, privacy and architecture questions about Arino Core. It describes controls that are in place and services we operate — it is not an independent audit, certification or assurance report. Lovable and Infobip provide the underlying platform capabilities, Arino One configures and operates each platform, and the customer remains responsible for message content, consent and their own business rules.
For Your Review Team
Request the Review Pack
Get the data processing agreement, sub-processor list, data residency detail and security questionnaire for your security and procurement teams.