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
can register at https://akintu.io/.

After the connection flow verifies the exact site origin, WordPress administrators can use the
native Akintu menu to review this site’s dashboard and conversations, upload PDF or DOCX files,
add source text, scan and manage site pages, and configure instructions, technical settings, and
the widget. Account and billing management remain on akintu.io.

The installation management credential stays on the WordPress server. Browser administration
requests use WordPress capabilities and REST nonces.

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. Plugin updates are delivered by WordPress.org; version 0.2.1 removes the previous custom
update channel.

External services

Akintu hosted service

The plugin requires the Akintu service at https://api.akintu.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, and booking details 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.

Akintu terms: https://akintu.io/termini
Akintu privacy policy: https://akintu.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.

Calendly participant terms: https://calendly.com/legal/participant-terms-conditions
Calendly privacy notice: https://calendly.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.

Source code and build instructions

The bundled minified runtime is @akintu/widget 0.3.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
files are written to dist/loader/v1/; copy loader.js, its source map, and the accessibility
subdirectory into assets/widget/. These are build-time steps only: the published plugin has no
Node.js or Composer runtime dependency.

1. Install and activate Akintu from the WordPress plugin directory.
2. Open Akintu in the WordPress administration menu.
3. Select “Connect to Akintu” and approve the exact domain in the Akintu dashboard.
4. Add the “Akintu Embed” block, use [akintu_embed], call akintu_render_embed(), or select the Elementor widget.

Is an Akintu account required?

Yes. Akintu is a hosted service. You can create an account at https://akintu.io/ before connecting
the site.

Does the plugin support Akintu Inline?

No. This release deliberately registers only Akintu Embed.

Where is the widget configured?

Appearance, knowledge sources, site scans, and assistant behavior can be managed directly from the
connected Akintu pages in WordPress. Account, billing, and advanced integrations remain on akintu.io.

What happens when the plugin is uninstalled?

The plugin automatically revokes its dedicated installation key during uninstall.
It then removes local plugin options without deleting dashboard content or crawled sources.

0.3.4

• Uses WordPress script attributes for the local widget runtime.
• Removes the public frontend credit and external marketing link.

0.3.3

• Corrected the plugin metadata for WordPress.org submission.

0.3.2

• Centered the branded page loader without visible loading copy.
• Revokes the dedicated installation key when WordPress is disconnected or uninstalled.
• Revokes an existing connection before starting a replacement setup.

0.3.1

• Added automatic return to WordPress after approving the site in Akintu.
• Added branded loaders during connection and page data loading.
• Rebuilt the Sources and Instructions forms with responsive field layouts.
• Stacked the Akintu logo, title, and subtitle consistently in admin headers.
• Added direct access to Akintu documentation from the plugin.

0.3.0

• Added a branded native Akintu dashboard to WordPress administration.
• Added site-scoped conversation review, detail, analysis, and CSV export.
• Added PDF, DOCX, and source-text management with direct upload progress.
• Added current-site scanning, page controls, and scan history.
• Added the same Instructions, Technical, and Widget configuration tabs used by Akintu.
• Added site attribution and scoped installation management APIs.

0.2.1

• Released the plugin and bundled widget runtime under GPL-2.0-or-later.
• Removed the custom Akintu updater so future updates use WordPress.org.
• Included human-readable widget source and reproducible build instructions.
• Documented Akintu and optional Calendly external-service data flows.

0.2.0

• First synchronized Embed-only WordPress release.
• Dashboard connection and automatic site verification.
• Gutenberg block, shortcode, PHP helper, and optional Elementor widget.