Privacy policy

1. Who we are

Treisa Flow (“Treisa”, “we”) operates the platform https://treisaflow.com and the Chrome extension Treisa Session Connector, used to connect WhatsApp Web to a Treisa Flow workspace.

Privacy and support contact: through your Treisa Flow account (settings / team) or the publisher email listed on the extension's Chrome Web Store listing.

2. Scope

This policy covers:

• The Treisa Flow website and web app.

• The Treisa Session Connector extension (Manifest V3) published or distributed to import WhatsApp Web sessions.

WhatsApp / Meta are independent services. Their use is governed by their own terms and policies. Treisa is not an official Meta or WhatsApp product.

3. What the extension does

Treisa Session Connector lets a user with a Treisa Flow account import the technical material of their WhatsApp Web session into their workspace, to operate a line inside the product without manually pasting instance URLs or API tokens.

The flow requires:

• Signing in to Treisa Flow and a single-use connection token.

• WhatsApp Web open in Chrome with an active session.

• An explicit user action (“Start import”).

4. Data the extension handles

Only when the user starts the import:

• WhatsApp Web authentication / session material needed to rehydrate the connection (e.g. data in localStorage and IndexedDB of web.whatsapp.com).

• Single-use connection token issued by Treisa Flow (short-lived, typically minutes).

• Technical job metadata: chunk sizes, SHA-256 hashes, extension version.

The extension is not designed to read the content of your chats for advertising, to resell data, and it includes no third-party ads or analytics SDKs.

5. What is sent to our servers

During the import, session chunks are transmitted over HTTPS only to:

• https://treisaflow.com — API /api/v1/channels/import-session/*

Treisa processes that data to activate the workspace's WhatsApp line on its infrastructure. We don't sell that data to brokers or use it for third-party ads.

6. Data from the Treisa Flow web product

Depending on platform usage, we may also process:

• Account: email, workspace name, team members.

• Operational inbox and automation data the user uploads or generates (contacts, messages from the connected line, flows, sales, configuration).

• Service technical data (logs, IP, user-agent) for security and reliability.

The main basis is providing the service hired / requested by the user.

7. Retention

• Import token: minutes and single-use.

• Temporary upload chunks: the duration of the import process; then discarded from the intake pipeline.

• WhatsApp line and workspace data: for as long as the account / workspace exists or per legal obligations.

Uninstalling the extension does not by itself delete the line already imported into Treisa; that is managed from the dashboard (Connections).

8. Chrome permissions (why)

• activeTab, tabs, scripting: open or work the WhatsApp Web tab and show the connector panel when the user starts the flow.

• storage: minimal local state of the import assistant in the browser.

• Host https://web.whatsapp.com/*: read session material only when importing.

• Host https://treisaflow.com/*: call the Treisa Flow import API.

9. Meta integrations (WhatsApp and advertising)

Treisa Flow integrates with Meta platforms (WhatsApp Cloud API, WhatsApp Business, ad accounts) acting as processor of the data you, as controller, authorize. When you connect an ad account with your system-user token or Meta's OAuth flow, we receive and store encrypted that access token, your platform user identifier, the enabled ad accounts and the campaign metrics we sync for you.

You can disconnect the integration at any time from Connections inside the product: the token is deleted instantly. To request deletion of all data associated with your account, use the data deletion page. If you started the request from Meta, we receive a signed notice and disconnect and delete the integration automatically.

10. Third parties

The extension includes no ad networks or marketing trackers. Infrastructure providers (hosting, database, transactional email where applicable) process data only to operate the service under their own agreements / terms.

11. Security

We use HTTPS, ephemeral tokens and chunk-hash verification. No system is invulnerable: report incidents through your account's support channels.

12. Minors

The product is not intended for those under 16 (or your jurisdiction's minimum digital age).

13. Rights

Depending on your jurisdiction you may request access, correction or deletion of personal data. Write via your account's support or the publisher email on Chrome Web Store. You can also manage much of the data from the Treisa Flow dashboard.

14. Changes

We may update this policy. The “Last updated” date will change. Continued use of the service or the extension after a material change implies, where applicable, acceptance of the current version.