A short document, because there is very little to describe. No analytics, no advertising, no tracking — and a precise account of the few things that are stored.
The public Tephlo sites — marketing, documentation and this legal site — set no tracking cookies of any kind. There is no advertising pixel and no third-party script at all: the sites’ security policy blocks them outright. The sites count their own page views, without cookies or identifiers (section 1).
Visiting the marketing site, the documentation site or this legal site sets no cookies at all unless you take the action described in section 2. There is nothing to opt out of, because:
Our hosting provider processes ordinary connection data — IP address, request time, user agent — in server logs to deliver the page and protect against abuse, as any web host does. That is described in the Privacy Policy, and the provider is on the sub-processor list.
The pricing page shows prices in a market currency. If you switch markets, that choice is stored so the page keeps showing your currency next time.
| Name | What it holds | Set when | Lifetime |
|---|---|---|---|
| tephlo_market | A short market code such as a country or region identifier — nothing about you. | Only when you pick a market on the pricing page. Simply visiting the page sets nothing. | One year, first-party, SameSite=Lax. |
An older cookie named xephlo_market, from before the product was renamed, is actively cleared when you set a market. Deleting either one simply returns the pricing page to its default currency. Your choice is never used to identify you, and the page never guesses your market from your IP address.
The marketing site also keeps two values in the browser’s local storage, neither of them a cookie: tephlo-billing, your monthly-or-yearly choice on the pricing page, and tephlo.ref, a partner’s code kept for 90 days when you arrive through a partner’s link so that a signup can credit that partner. The code identifies the partner, not you, and clearing site data removes both.
The agent console and the operator console are private applications you sign into. They set strictly necessary cookies — without them there is no way to know you are signed in.
| Cookie | Purpose | Lifetime |
|---|---|---|
| __Host-dash_access / __Host-op_access | Holds the short-lived access token that authorises each request. | Minutes — it is refreshed automatically while you work. |
| __Host-dash_refresh / __Host-op_refresh | Lets the console get a new access token without asking you to sign in again. Rotated on every use; replaying an old one revokes the whole session family. | Until it expires or you sign out. |
| __Host-dash_mfa_enrollment / __Host-op_mfa_enrollment | Marks that you are part-way through setting up multi-factor authentication, so the console knows where to send you. It contains no credential. | The enrolment step, and at most thirty days. |
| __Host-dash_password_change | Marks that you must change your password before going on, so the tenant console sends you there. It contains no credential. | As long as the sign-in session. |
| tephlo_suspension | Set when someone signs in to a suspended workspace, so the tenant console can show the suspension and the appeal route. It is a short-lived token, not a session. | Thirty minutes. |
All of these are httpOnly — JavaScript cannot read them, which is what stops a script on the page from stealing a session. In production all but the suspension cookie carry the __Host- prefix, meaning the browser refuses to accept them from any other host or path, and are marked Secure and SameSite=Lax.
The consoles also store display preferences locally: light or dark theme under theme, and sidebar state under console:sidebar-collapsed. The tenant console uses kb-layout for its knowledge-page layout and tephlo.phoneAppNudge.dismissedAt to remember that you dismissed the phone-app prompt. These preferences are not session credentials.
The phone app, the partner portal and the desktop app follow the same pattern. The phone app signs you in with __Host-mob_access and __Host-mob_refresh, keeps unsent reply drafts in local storage under tephlo.drafts.v1:acct-<id>, remembers a dismissed install prompt under tephlo.install.dismissedAt, caches its app shell and your latest Today screen in the browser’s service worker cache so it opens offline, and holds a push subscription if you turn notifications on. The partner portal signs you in with __Host-pt_access and remembers your theme. The desktop app keeps its window size and notification preferences in its own settings file.
If a business puts the Tephlo chat widget on its own website, the widget stores a value in the local storage of its own frame, which is served from our platform rather than from the business’s site, under xw_visitor: a random string the widget generates in your browser. It exists so that reloading the page does not start a new conversation from scratch.
Conversations on WhatsApp and Telegram happen inside those apps, and nothing in this document applies to them. What those apps store on your device is governed by their own policies.
Consent is required for storage that is not strictly necessary for a service the visitor asked for. On these sites there is almost none: no advertising, no profiling, and a page-view count that stores nothing in your browser. The currency and billing choices are set only by your own explicit action, the console cookies are necessary for a service you signed into, and the partner code is stored only when you follow a partner’s link and names the partner rather than you. A banner asking permission for nothing would be theatre, and would train people to click through the ones that matter.
General questions about this document go to hello@tephlo.com. Questions about personal data, including requests from individuals, should go to the data protection contact at hello@tephlo.com. A request about your own data — access, erasure, correction, objection or a complaint — can also be sent through the privacy request form, which puts it in front of the team as a tracked request rather than a message in a mailbox.
Postal address: TEPHLO AI VANGUARD SYSTEMS LTD, 9A Kenneth Lekara Luka Street, Lokogoma, FCT, Nigeria.