Privacy policy

This document describes two independent data flows:

• Account data — what you tell us yourself: email, the password as a hash, company name, the contents of contact forms.
• Extension telemetry — the pseudonymised signals the edge SDK collects in the browsers of users of connected extensions.

Separate rules, described below, apply to the second flow: it is designed so that personal data does not enter it.

When you register and use the portal we store:

• the email address — the account identifier and the contact channel;
• the password hash (bcrypt) — the original password is not available to us and cannot be recovered;
• the company name;
• a technical action log: sign-in, sign-out, password change, plan request, with the IP address and user agent — for investigating security incidents;
• the contents of the contact forms you send.

Sessions are held in an HttpOnly cookie carrying a refresh token; only its hash is in the database. The access token exists solely in tab memory and is never written to localStorage.

The SDK builds an event out of the technical metadata of a visit. The field list is published in the data schema and covers the cleaned URL, the root domain, the extracted search query, the browser language, the device type and the country code.

Filtering runs on the device before anything is sent:

• query parameters that look like identifiers, tokens, emails or phone numbers are stripped;
• events from the domains of banks, payment systems, mail services, and medical and government portals are discarded entirely;
• authentication, password recovery and payment pages are discarded;
• the session identifier is turned into an irreversible HMAC hash, anon_uid.

We neither read nor set cookies of extension users. Page content, typed text, passwords and files are not collected in any form.

Account data is processed to perform the contract with you, and on the basis of our legitimate interest in keeping the service secure.

Extension telemetry is processed solely on the basis of the user's explicit consent (GDPR art. 6(1)(a); for storage on the device, ePrivacy art. 5(3)). The SDK shows the consent prompt when the extension is installed or in its popup, and collects, stores and sends nothing until the user presses “Allow”. Declining does not limit how the extension itself works.

Withdrawing consent. Consent can be withdrawn at any time in the extension settings. After withdrawal collection stops, and unsent events and the installation identifier are deleted from the device. Withdrawal does not affect the lawfulness of processing carried out before it. Pseudonymised data already transferred is deleted once the retention periods below expire; a request can be sent to privacy@intentd.net.

The user's decision is stored only in their browser. When the consent text changes — because new data categories appear, for example — consent is requested again.

The extension publisher is responsible for invoking the consent prompt in their interface and for disclosing the collection in the store listing.

[LEGAL REVIEW NEEDED]

• Account data — while the account is active, and 12 months after it is deleted.
• Action log — 12 months.
• Pseudonymised deliveries — 30 days in hot storage, up to 90 days in the archive.
• Contact form messages — 24 months.

Pseudonymised deliveries are passed to data partners under the terms of use, which include an outright ban on re-identification.

We do not sell your account data and do not pass it on for advertising. Transfer is possible only to infrastructure processors (hosting, storage) and on a justified request from an authorised body.

Sub-processor list: [PLACEHOLDER].

You can request access to your account data, its correction, deletion or export, and you can withdraw consent to mailings. Send the request to privacy@intentd.net from the address on the account.

For the telemetry stream, deleting a specific record is technically impossible: it carries no field that would tie an event to a person. That is a consequence of the design, not a refusal to honour the right.

A data processing agreement (DPA) is provided on request — mention it in the contact form.

• passwords are stored as bcrypt hashes;
• refresh tokens are stored as hashes and revoked when the password changes;
• every API call is rate limited and logged;
• delivery access is granted through separate per-tenant keys.

Report a suspected leak to privacy@intentd.net.

Data controller: [PLACEHOLDER]

Address: [PLACEHOLDER]

Data protection contact: privacy@intentd.net