Six answers,
before any of the jargon.
You do not need an IT person to read this part. If you own the business and you are the one who would have to explain this to a worried customer, these six sentences are the whole story.
Not in a shared pile with a label on it — separated. And we don’t take that on trust: an automatic check runs before every update we release, and the update does not ship if one business’s records can be reached from another’s.
Everything moving between your customers, your screen and us is scrambled on the way, so it cannot be read in transit. An unlocked connection is refused rather than allowed through.
Answering, booking, quoting, writing the customer record — on your instructions, for no other purpose. Inside our own team, reaching the live system needs a second login step, is limited to the people whose job requires it, and is written to a log.
We do not use one business’s conversations to train the AI serving another. Using yours to improve the model at all is off unless you turn it on in writing — and you never have to.
You decide how long things are kept. Ask for an export or a deletion and we carry it out — that is a written obligation in the agreement, not a favour you have to argue for.
Every call and chat opens by saying so, with a way to reach a person in the same breath. You can reword it; where the law requires it you cannot switch it off. Recording follows your country’s consent rule automatically.
Same six facts in the vocabulary a security questionnaire uses? The technical version is directly below — unchanged, and written for whoever your insurer or your lawyer sends.
A name, a number,
and why they called.
Security questionnaires talk about records. Your pipeline calls the same thing a new inquiry. Either way, what is actually in it is a patient who rang after hours, a couple asking about a Saturday, a tenant with a burst pipe. That is the material this page is about — and it stays yours.
Photography is illustrative — the kind of business Saleringo is built for, not named customers and not testimonials.
Your data.
Your instructions.
Clear roles make every other security question easier to answer. Here is who controls what when your front desk runs on Saleringo.
What we do —
and only what we do.
Each item below reflects the current implementation. When something changes, this page changes with it.
Every customer's data is separated with row-level security at the database layer. Cross-tenant isolation tests run in CI on every release. Two exceptions today: dated migration snapshots kept for rollback — which we are closing — and shared reference data that belongs to no customer. We name them here rather than let a pen test find them.
All traffic between your browser, your customers' channels, and our APIs is encrypted with TLS. Plaintext connections are not accepted.
Multi-factor authentication for administrators, least-privilege roles by default, and audit logs of administrative access to production systems.
Choose where your end-customer data is stored: production runs in Seoul (ap-northeast-2) today. EU, US and APAC are available by contract — we stand the region up for you and name it in the order. Storing is not processing: whichever region you pick, the model that composes an answer runs on US servers. If your organisation cannot accept that transfer, say so before you buy.
Retention policies are set per organization. We honor export and deletion requests for your data — the controls a DPA and privacy regulations expect.
A defined incident process: detection, severity classification, containment, and notification without undue delay. Two cases, because the roles differ. Data we control ourselves — your account, your order, your inquiry — we notify the people affected and Korea's Personal Information Protection Commission within 72 hours, as the Personal Information Protection Act requires. Your customers' data, where you are the controller and we are the processor: we notify you within 72 hours of learning of a breach, with what we know and what we have contained; whether and how your customers are told is your decision as controller, and we help you make it. Both standards apply to every customer, wherever you are.
The database host (Supabase, on AWS ap-northeast-2) takes the backups; a record you delete leaves them within 90 days. Not yet: a rehearsed restore with a measured recovery time. We do not print a recovery-time promise until a restore has actually been run against a clock.
The list below changes the day a subprocessor does, and the review date on this page moves with it. Not yet fixed: how many days' notice you get before a change, and a right to cancel without charge if you object. When the DPA sets those, the numbers go here — we would rather say “not decided” than print a notice period the contract does not back.
Each seat on your plan is its own login; there is no shared password to pass around. Not yet: roles inside your account, enforced two-factor for your staff, and single sign-on. The multi-factor requirement above is for our administrators on production, not for your users — this card says so rather than let the two be confused.
Dependencies and the runtime are updated with each release, and every release runs the cross-tenant tests first. Not yet: a fixed patch window or a published time-to-fix for critical vulnerabilities. A small team can promise “we patch as we release”; it cannot honestly promise a 24-hour SLA, so we don't.
If you are a healthcare, legal or financial business, read this before you go further.
Regulated industries have one specific question — HIPAA and a Business Associate Agreement in US healthcare, or your jurisdiction's equivalent. It must be settled in writing before a single patient or client record reaches us. We put no badge on this page, for the same reason we do not publish certifications before the audit report exists.
So raise it in your first email, not your last. Tell us a BAA is a condition of purchase, and you get a written answer before you pay us anything. If it is not the answer you need, you will know early enough to go elsewhere — we would rather lose the deal than sell around the question.
Where that stands today: we cannot sign a BAA yet. A BAA from us would have to rest on BAAs with every subprocessor that would see patient data — the model providers and the database host — and we do not yet have those in place with them. Until we do, the written answer to a HIPAA-covered use is no. The day that changes, the date and the subprocessors covered go here before anywhere else.
Everything above this box is true without a certificate: per-customer isolation tested on every release, encryption in transit, multi-factor authentication on production access, no training that serves another business, and export or deletion on any day. Separately, the AI refuses clinical questions outright — diagnosis, medication, suitability and symptom assessment go to your staff, never to an answer. See exactly where that line sits →
The question
every buyer asks in 2026.
Who knows they're talking to AI, what gets recorded, and what your data trains. Here are the answers, in full.
How Saleringo discloses AI
Every conversation begins with a clear statement that the customer is talking to an AI assistant, with a visible way to reach a human. You can change the wording. You cannot turn it off in countries where disclosure is required.
Call recording
Recording rules differ by country — some require all parties to consent. Saleringo applies your country's rule automatically and records the disclosure and consent basis with every call.
How your data is used for AI
Your business knowledge and conversations are used to answer your customers. We do not use one customer's data to train models that serve another customer. Model improvement using your data is off by default and requires your written opt-in. The answer itself is drafted by a model we reach through OpenAI's and xAI's APIs, in the United States; under the API terms we use, what we send is not used to train their models. How long they retain it on their side, and whether our account is on zero-data-retention, are contract terms recorded in the DPA — we do not quote a number here that we have not confirmed.
Nobody finds out later.
Disclosure is the opening line on every channel, in the caller’s language, with a way to reach a person in the same breath. You can reword it; you cannot switch it off where the law requires it.
One tenant, one wall.
Recording follows your country’s consent rule automatically, and the consent basis is stored with the call. Your conversations never train a model that serves another business.
Every company in the chain,
by name.
A security page that says “we use industry-leading providers” is telling you nothing. These are the actual companies that process some part of your data, what each one does, and where the data physically sits while they hold it — not where the company is registered. If one changes, this list changes with it.
Payment provider: none yet. Card registration starts only after we have contracted a payment provider, and that provider is named in this table before it takes a card. Until then an order is a request and nothing is charged at that stage.
Conversation content is processed on servers in the United States. If your organisation cannot accept that transfer, say so before you buy — not after — and we will tell you plainly whether we can serve you.
Retention, per object.
Not one blanket number. Different records have different legal lives, so they are listed separately.
You set the period as controller; if you never set one, the default is 24 months, and when it lapses they go.
Your window to export. After it, deletion.
Then destroyed, including from backups.
A record you delete is purged from backups within 90 days of the deletion.
Held to meet South Korean telecoms record-keeping duties.
Security forensics only, never marketing.
Required by consumer-protection law.
The floor, on every object above.
Every company on that list can see some part of your data, which is why each is named individually rather than described as “industry-standard infrastructure partners”.
Paperwork,
ready for review.
The documents your legal and procurement teams need are prepared and current. Each is available on request during evaluation — email hello@saleringo.com and ask; you do not need an account or a sales contact first.
Ask for any of these during evaluation and you get the document, not a sales call. They are sent on request rather than published because each one is issued to a named party — not because they do not exist. The version and date beside each one is what you will receive.
In the product now. You can see it in your own account during your first 14 days (the refund window).
- Tenant isolationRow-level security at the database layer, with cross-tenant tests in CI on every release.
- EncryptionTLS 1.2+ in transit, AES-256 at rest, on every object listed in retention.
- DeletionDelete a conversation or a whole customer record from the dashboard; it leaves the knowledge base with it.
- No training on your dataYour conversations are not used to train a model that serves anyone else.
- Answer provenanceEvery answer traces to a fact you approved, with a source and an expiry.
Real documents with version numbers, sent to a named party. Not published, because each one is issued to you.
- DPA, with the SCCsController/processor roles under UK & EU GDPR. v1.2, 12 Aug 2026.
- Subprocessor listThe same companies as the table above, in a form you can attach to a contract. v1.4.
- Security overviewArchitecture, data flows and controls, written for questionnaires. v1.1.
- RetentionThe periods on this page are the ones the DPA commits us to.
Depends on your country, your channels and your regulator. Ask and you get a written answer, not a maybe.
- Where the data sitsThe operational database runs in South Korea (Seoul); other regions are available by contract. The model that drafts the answer runs on US servers either way.
- Recording and consentThe rule differs by country and by state. We set yours at onboarding and store the consent basis with each call — but which rule applies to you is confirmed for your market, not assumed.
- Telephony carriageWhich carrier serves your numbers, and under whose licence.
- Regulated tradesClinics, legal and financial work carry refusal rules we agree with you in writing first.
And what is not here. No SOC 2 report, no ISO 27001 certificate, no third-party penetration-test letter exists for Saleringo yet. Nothing on this page is independently attested; it is our own statement, written to be checked line by line. If your process requires an auditor’s report, we are not ready for you yet.
- OwnerFounder and data-protection contact — reached through the request form, which is the route that reaches a person today. Saleringo is a small company; there is no security department to point at, and the person accountable for every statement on this page reads what arrives there.
- Statement version2.1, published 3 September 2026 — subprocessor table, retention, incident roles and the BAA position restated
- Last reviewed12 August 2026, against the live configuration and the subprocessor contracts
- Next review12 February 2027, or the day a subprocessor changes — whichever comes first
- Independent auditNone yet. There is no SOC 2 report and no ISO 27001 certificate for Saleringo today. Everything on this page is our own attestation, written to be checked rather than believed. If a third-party report is a condition of your purchase, we are not ready for you yet — which is a more useful answer than a badge.
Found something?
Tell us first.
We welcome good-faith security research. If you believe you've found a vulnerability in Saleringo, tell us before disclosing it anywhere else — through the request form, which is the route that reaches a person today.
Report it through the request form →Published, not on request: the same statement is machine-readable at /.well-known/security.txt — the contact route, the expiry, the languages and a link back to this policy, at the location a researcher’s tooling checks first. It is the one piece of security evidence we can honestly publish rather than send to a named party.
Please include steps to reproduce, and don't access data that isn't yours while testing. We won't pursue action against good-faith research that follows this process.
We have not had to run this process yet. It is written down so that the first time is not also the first time we think about it.
Named companies, per-object retention, and where the data physically sits. If your organisation cannot accept a US transfer, that is a conversation to have before you pay, not after.
Ask us the awkward
question first.
Twenty minutes, a person, and whatever you are worried about — where your customers’ records live, what the AI is allowed to say, what your pipeline and reports look like on a Monday morning. Bring the security questionnaire too if you have one.
New here? Start with the two-step tour — about a minute →