Alfabits · Alfatika

CCP extension privacy

Last updated: 20 September 2026

The Alfatika CCP extension connects a shop’s CCP account to its Alfatika workspace. It checks the connection and imports transactions for review. It does not initiate payments or automatically order paid statements.

Information used

The extension reads the CCP account number and transaction information needed for statements, including dates, descriptions, amounts, balances and any counterparty account details shown by ECCP. It stores the Alfatika website address, a connection token, connection status and import counts in browser storage. Captured transactions waiting for delivery are stored locally (up to 24 snapshots or 2 MB) until Alfatika confirms receipt, you disconnect, or you switch to a different account or website. Pausing retains this queue without sending it. Row fingerprints are retained to detect possible gaps between captures. The website address may be synchronized by the browser; the connection token stays in local extension storage.

Where information goes

Transaction information is sent only to the Alfatika website you connect and authorize. In the current browser connection mode, your ECCP password and session cookies are not sent to Alfatika. You sign in directly on the official ECCP website. An older, separately configured session connection mode can send ECCP session cookies to your authorized Alfatika server; those sessions are stored encrypted there.

Alfabits does not use extension data for advertising, sell it, or send it to an AI service. No third-party analytics are included in the extension. Data is used only to provide the authorized CCP connection and transaction-review features. It is not used or transferred to determine creditworthiness or for lending purposes, and it is not transferred to third parties outside the permitted uses of this integration.

Automatic activity and control

While enabled, the extension performs free connection checks approximately every ten minutes and imports free recent transactions at the same interval. It can reopen a closed ECCP tab in the background and repair its connection. If login is required while you are on the Alfatika connection page, it opens ECCP once for you to sign in. Checks may be delayed while the browser or computer is asleep. Paid statement requests require an explicit action in Alfatika and are never retried automatically. You can pause updates, disconnect this browser, or revoke browser access in Alfatika. Pausing does not delete previous imports.

Retention and deletion

Disconnecting this browser removes its connection token and local connection history. Revoking access in Alfatika invalidates its authorization. Imported business records remain in the connected Alfatika workspace until removed under that workspace’s records policy. Browser connection authorizations initially last 90 days. Successful current account checks renew them for 90 days when fewer than 30 days remain; queued imports cannot renew them. Unused authorizations expire, and revoked authorizations cannot be renewed.

Permissions

Access to ECCP and your approved Alfatika website is required for this connection. Storage remembers your settings; alarms schedule checks; cookie access supports login detection and the older session mode. Tab information is used only on approved sites to open ECCP and return to the Alfatika page that started the connection.

Contact and changes

For extension privacy requests, contact Alfabits at info@alfabits.net. For records in a shop-managed Alfatika workspace, contact the shop administrator. Do not include your ECCP password, session cookies or connection token in a support message. Material changes to this policy will be reflected on this page with a new revision date.

This extension is provided by Alfabits and is not an official Algérie Poste product.