Three fair questions
What a buyer is entitled to ask
Who answers, what happens when they're away, and what happens if we stop — each answered with the thing itself.
Who replies when something breaks?
The person who wrote the code. Not a tier-one script, not a bot, and not a queue that reaches an engineer three days later.
- One inbox, read by the builder
- Request logs are searchable — a workspace and a time is usually enough
- A fix doesn't wait for a release committee
What happens if that person is away?
Nothing, for the running service — it doesn't need anyone present. Support slows down, and saying otherwise would be the one thing this page exists to avoid.
- Assistants, bookings and alerts run unattended
- Billing runs through a merchant of record
- No 24/7 on-call rota — stated, not implied
What happens if the company stops?
Your data leaves on the same API it arrived on — the real one the dashboard uses, not an export button bolted onto a summary.
- Every conversation and contact, over the public API
- Documented operation by operation
- Nothing held back behind a plan
# Every conversation, as JSON
curl https://api.integrable.cloud/api/bots/$BOT_ID/conversations \
-H "Authorization: Bearer $INTEGRABLE_API_KEY"
# Every captured contact
curl https://api.integrable.cloud/api/bots/$BOT_ID/contacts/export \
-H "Authorization: Bearer $INTEGRABLE_API_KEY"Division of labour
One builder doesn't mean everything is hand-made
Where being small would be a liability, the work is bought from people who aren't small.
Written here
The product, the API, the widget, the integrations, this website and every word on it.
Bought from specialists
Payments, the database, the models, email and hosting — none of them worth being worse at.
Not done at all
No sales team, no SOC 2 audit, no 24/7 rota. Each is stated on the page where it matters.
Always in the path
- Neon
- Oracle Cloud Infrastructure
- Vercel
- Cloudflare R2
- Cloudflare Turnstile
- Groq
- Anthropic
- Resend
- Brevo
- Dodo Payments
What each one receives is listed at subprocessors.
Getting hold of someone
Separate addresses, the same person
They're separate so the subject is obvious before the message is opened — not because there are departments.
Something's broken
Include the workspace and roughly when it happened.
hello@integrable.cloud
A security issue
Scope and next steps are in the disclosure policy.
security@integrable.cloud
A data request
Access, correction or deletion — under the DPA.
privacy@integrable.cloud
Anything else
Sales, press, partnerships — and response times.
/contact
The registered company details are being finalised. Once registered, the legal entity behind the service is published in the terms and on the legal index — the version that matters if you ever need to enforce something.
