Akintu

Akintu connects a WordPress site to the site owner’s Akintu dashboard and renders the Akintu Embed

chat surface. An Akintu account is required to use the hosted service. If you do not have one, you

io/.

What you can do from WordPress

After the guided connection verifies the exact site origin, administrators can:

• monitor conversations, messages, outcomes, ratings, bookings, and knowledge gaps;

• search conversations and export the site’s data to CSV;

• upload PDF or DOCX files and add source text;

• scan website pages and control which pages remain in the knowledge base;

• configure the assistant’s instructions, tone, guardrails, and conversion objective; and

• customize the Embed appearance and accessibility features.

io.

The installation management credential stays on the WordPress server. Browser administration

requests use WordPress capabilities and REST nonces.

Add Akintu Embed anywhere

You can place Embed in four ways:

• the “Akintu Embed” Gutenberg block;

• the [akintu_embed] shortcode;

• the akintu_render_embed() PHP template helper; or

• the optional “Akintu Embed” Elementor widget.

The plugin registers Embed only. Akintu Inline is intentionally unavailable in this WordPress

release.

The browser runtime is bundled locally with the plugin. No executable code is downloaded from

Akintu. 1 removes the previous custom

update channel.

Privacy-aware contact handling

When the connected website enables contact collection, visitors can provide their first name,

last name, email address, and optionally a phone number before continuing a configured action.

Akintu encrypts these contact fields in the hosted service and applies the retention period selected

for that website. Site owners remain responsible for selecting a lawful basis, publishing an

appropriate privacy notice, and configuring a retention period suitable for their use case.

External services

Akintu hosted service

io to connect a site and provide chat.

When a WordPress administrator explicitly starts the connection, the plugin sends the site’s home

URL, plugin version, a client-key prefix, and one-way hashes of locally generated connection,

verification, management, and client credentials. It subsequently sends the connection identifier

and the appropriate locally stored credential when checking approval, verifying the site, or

revoking the connection. When an administrator uses the Akintu pages in WordPress, the WordPress

server sends the scoped installation identifier and management credential to request this site’s

analytics, conversations, sources, scans, and assistant settings.

When an administrator explicitly uploads a PDF or DOCX file, the WordPress server first requests a

short-lived, single-use upload grant. The administrator’s browser then sends the selected file,

filename, file size, site origin, and that temporary grant directly to the Akintu API. When source

text or settings are saved, that content is sent through the WordPress server to Akintu. These

operations are required to update the hosted knowledge base and assistant configuration.

When a visitor opens or uses an Embed, the bundled runtime contacts the Akintu API. Requests can

include the dedicated browser client key, a random versioned conversation identifier, chat

messages, feedback, confirmed actions, booking details, and contact details explicitly entered by

the visitor. Standard HTTP metadata such as IP address, origin, referrer, and user agent can also be

received by the service.

These requests are required to load configuration, retrieve conversation history, generate answers,

execute explicitly confirmed actions, and submit feedback.

io/termini

io/privacy

Calendly

If the connected Akintu tenant enables Calendly booking and a visitor chooses to continue a

booking, Embed loads a Calendly scheduling page in an iframe. The URL can receive the visitor’s

name, email address, selected appointment context, the WordPress site’s host name, and Akintu

campaign parameters so that the booking can be completed. Calendly is not contacted during normal

chat use when no booking is opened.

com/legal/participant-terms-conditions

com/legal/privacy-notice

Privacy

The plugin itself does not add analytics or advertising trackers. The browser runtime stores one

random, versioned conversation identifier in the visitor’s localStorage to preserve chat

continuity. It does not store the Akintu client key or chat messages in browser storage.

Site owners should describe their use of Akintu, and Calendly when enabled, in their own privacy

policy and select a lawful basis and retention policy appropriate to their site and jurisdiction.

Contact fields collected through configured Akintu actions are encrypted by the hosted service and

are automatically anonymized after the website’s configured retention period.

Source code and build instructions

4. Its human-readable TypeScript source, package

manifest, license, and build configuration are included under assets/widget/source/.

To rebuild the runtime, run pnpm install and pnpm build inside that directory. The generated

js, its source map, and the accessibility

subdirectory into assets/widget/. These are build-time steps only: the published plugin has no

js or Composer runtime dependency.