Skip to content
CallMeCallMe
Menu

Pre-launch: Olorin.ai is in a private pilot. What you see here is built and in daily use by the pilot; public sign-up opens when the launch checklist completes.

Trust & compliance

This page claims only what exists in the product today. Where something is planned rather than shipped, it says so.

Isolation

  • Every account is a tenant of its own: its own carrier subaccount, its own numbers, agents, calls and messages. One account's objects are invisible to another — the API answers 404, never 403, so it does not even confirm they exist.
  • Carrier credentials are stored sealed (AES-GCM) and opened only inside the service at the moment of use. API keys are stored as keyed digests and shown exactly once, at creation; webhook signing secrets are sealed the same way and shown once.
  • Operators can hold an account — calls, sends and provisioning stop — and account holds propagate to a reseller's children, never the other way.

Your data

  • CallMe runs on Google Cloud (Cloud Run, Firestore, Cloud Storage). An audit record is written before every call is dialled and every message is sent.
  • New accounts start in announced mode: calls are recorded and the call opens with a spoken recording notice. You choose off, on, or announced per account, and can change it at any time. Recordings are kept in cloud storage and reached only through signed links minted at read time, valid for at most 15 minutes — a link is never stored anywhere.
  • When recording is off, no transcript of a call is stored: the account keeps the call's metadata (numbers, times, duration and outcome) and, when a hosted agent transfers the call, the short note the agent gave the person it transferred to. A voicemail a caller chooses to leave is the exception: it is recorded and transcribed whatever the mode.
  • Retention is yours: 30 days by default, settable between 7 and 30. Expired recordings and transcripts are purged on a best effort basis: the purge runs when a call on your account closes, so an expired artifact can outlive its retention date until then. You can delete any single call's artifacts at any time.
  • A verified destination is the only number an account can call from its connector — destinations are resolved from the account, never supplied per request.

Messaging compliance (US 10DLC)

CallMe files your brand and each campaign with the US carriers through Twilio, and keeps their status in your account. US texting from a number is blocked — with the exact registration reason — until its campaign is approved.

You warrant that every number you text has given you consent to receive your messages (TCPA), that your message content is truthful, and that you honour opt-outs: a text of STOP suppresses that number on your account automatically, and CallMe refuses to send to it until the person opts back in with START.

Certifications — honestly

CallMe is not SOC 2 certified today, and is not HIPAA-covered. A SOC 2 programme is on the roadmap; until an auditor signs, this page will say exactly that. If your workload needs a certification we do not hold yet, do not put it on CallMe yet.

Abuse controls

Phone service is a fraud target, and CallMe is built like it: per-account daily and per-period caps on call minutes, a daily cap on texts, a daily call window, a verified destination, and an operator hold that stops an account's calls, sends and provisioning at once.

The calls your account places from its connector or the REST API go only to the number you verified by text code. One exception: a hosted agent's transfer tool can bridge a caller to a number you configured on that agent. Those numbers are checked for format and are not verified by text code, so they are your responsibility; the tool refuses any number that is not on the agent's configured list.