Privacy Policy — Aelo — AI Call & Chat Analytics
1. What This Policy Covers
This policy describes the Aelo — AI Call & Chat Analytics application ("the Application") published by Auspex Streamline S.L.: what it accesses in your Bitrix24 portal, what it transmits outside it, what it writes back, and how long the resulting data is kept.
The Application is a client for the Aelo cloud service. Processing performed by the service as a whole — including for customers who do not use Bitrix24 — is described in the general Aelo Privacy Policy, the Data Processing Agreement and the Sub-processors register. Where this policy is silent, those documents apply.
Pro Trial: a free (Pay-as-you-go) organization receives the features of the Pro plan once, for 14 days from its next analysed call or chat (Terms of Service, section 9.6). While its Pro Trial lasts, the processing described here for the Pro plan and above also applies to it; when the trial ends, that processing stops for new conversations, and what it already produced is kept and deleted as described here.
2. Who Is Responsible for What
Under the GDPR, the organization that installs the Application on its Bitrix24 portal is the controller of the call, chat and employee data it submits for analysis. Auspex Streamline S.L. is the processor, acting on the controller's documented instructions.
| Responsibility | Party |
|---|---|
| Deciding to install the Application and which data it may access | Portal administrator (Controller) |
| Obtaining consent from call participants before recording | Portal administrator (Controller) |
| Informing employees that their calls are analyzed using AI | Portal administrator (Controller) |
| Processing and storing the data securely | Auspex (Processor) |
| Providing deletion and data-subject-request tooling | Auspex (Processor) |
3. What the Application Reads From Your Bitrix24
The Application requests only the Bitrix24 permissions (scopes) it uses. Each is listed below with the reason it is required.
| Permission | What is read | Why |
|---|---|---|
| Telephony | Call records and their metadata — direction, duration, timestamps, participant phone numbers, the responsible employee, and the location of the recording file | To find the calls to analyze and to retrieve the audio |
| Drive | The recording file for a call being analyzed | Bitrix24 stores call recordings on Drive; the audio itself is the input to the analysis |
| CRM | The call activity and the linked lead, deal, contact or company — names, the deal's pipeline, stage and stage history, the names of your deal pipelines and their stages, and the labels of custom fields. Immediately before writing results back, the current values and type definitions of the fields you designated (see Section 5.1), so that a populated field is not overwritten. With the deal state (Pro plan and above): for the deal or lead an analysed conversation is linked to, its title, amount, currency, pipeline, stage, whether the stage is final and its responsible employee, and, for a deal, the lead it was converted from, so that the deal's first state continues the lead's; and, before creating a to-do for its next action, the deal's or lead's activities are searched for Aelo's own marker | To attach the analysis to the correct record, to select the evaluation scorecard matching the deal stage (and, for a stage without a phase, to have its phase determined from the pipeline and stage names — see Section 4), and to write results without destroying data already in the record. For the deal state: to build it and show the deal in Aelo's deal list, to assign the to-do to the deal's responsible employee, and not to create the same to-do twice. The comment about the deal state and the to-do are written under this permission too (Section 5) |
| Chat / Open Channels | Message history of open-channel conversations, when text-conversation analysis is enabled | Aelo analyzes written customer conversations in the same way as calls, and sends an employee a notification in the portal (section 5) |
| Users (minimal) and company structure | For the person opening the Application: their identifier in your portal and their name — no e-mail address and no other contact detail. For employees linked to analyzed conversations: identifier, name and department membership. On an administrator-initiated import: the portal's department tree and the department heads it names | The identifier in your portal is what identifies the employee's Aelo account, so no address needs to be read to sign them in. Names attribute a conversation to the employee who handled it; the department tree determines which records a department head may open |
| Placement | Nothing is read — this permission is used only to register the “Aelo” tab in the deal, lead, contact and company cards (see Section 5) | To show Aelo inside a CRM card |
| Tasks | Nothing is read — this permission is used only to create tasks (see Section 5) | To create a follow-up task on a flagged conversation. The to-do for a deal's next action is a CRM activity created under the CRM permission, not a task |
The Application also subscribes to the portal events ONCRMACTIVITYADD and ONCRMACTIVITYUPDATE so it learns when a new call appears, and it reads its own installation record via app.info.
4. What Leaves Your Bitrix24
- The recording of a call selected for analysis is downloaded from your portal and stored encrypted (Cloudflare R2, AES-256-GCM server-side encryption) in the Aelo service.
- The audio is sent to a speech-to-text provider (ElevenLabs) to produce a transcript.
- Personal data is redacted from the transcript — phone numbers, e-mail addresses, payment card numbers and IBANs — before the transcript is stored and before it is sent for analysis.
- The redacted transcript is sent to a large language model provider (OpenAI) which produces the analysis: quality score, sentiment, key points, attention flags with their reason, and key moments; a key moment carries a quote and a timecode only where the analysis could ground them in the transcript.
- If your organization has defined criteria — its own questions asked of every conversation — the redacted transcript is sent to the same provider again, together with the text of the criteria that apply to the conversation, to answer them. The answers, their quotes from the redacted transcript, the model's short explanation and — when known — the identifier of the employee who handled the conversation are kept with the record and deleted together with it. When the organization owner checks a criterion's wording before saving it, up to 20 recent analysed conversations are sent the same way with the draft wording; those answers are shown and not kept. A user who describes a criterion in their own words has the description sent to the same provider (with supported text patterns masked) to write a draft wording; a user who marks answers of that check as wrong has the draft wording, the marked answers with their optional reasons and, for each marked conversation (up to 10), a fragment of its transcript around the quoted lines, redacted again, sent to the same provider to propose an edit of the wording. The draft and the proposed edit are shown to that user and not kept.
- Aelo also asks its own built-in criteria — standard questions worded by Aelo (for example, whether the company was named, a next contact was agreed, call recording was disclosed or the employee used profanity) that are the only place where these checks of what was or was not said are made — the analysis itself no longer performs them. The redacted transcript is sent to the same provider in a separate request — together with your organization's criteria, or on its own if it has none — and Aelo does not charge for it. Your organization’s owner pauses them and chooses where they apply in the Aelo criteria settings, within the limits Aelo sets (Aelo may also pause one); they are not asked for a short call that receives no analysis, or when an already analysed conversation is re-analysed (a failed analysis that is retried asks them as usual). Their answers are kept with the record in the same way and deleted together with it, and are shown to your organization, including in the report Aelo writes to your portal; if Aelo has switched them off for your organization, they are not shown and it has none of these checks. Analyses made before this change keep the checks they stored, and those are still shown.
- If your organization has the Voice of Customer section with its customer questions and decline reasons (Pro plan and above), the redacted transcript of each newly analysed conversation is sent to the same provider again, in a separate request, to find the questions the customer asked (up to 10) and, for a sales conversation, how it ended and — when the customer declined — the reason. The results, with the customer's words quoted verbatim from the redacted transcript, are kept with the record and deleted together with it. Conversations analysed before this was introduced are not processed in bulk; a conversation your organization re-analyses is processed like a new one. Aelo does not charge for it. If your organization also uses stage-based scorecard selection, the code of the decline reason — without the customer's words — is also kept next to the outcome of the lost deal the conversation belongs to (see Section 7). Where your organization also has conversation themes and its set has an active theme, the same request carries the names and descriptions of those themes (as your organization wrote them, at most with supported phone, email, payment-card and IBAN patterns masked) and also returns one to three themes of the set for the conversation, or that none fits, and, where the conversation has a subject the set lacks, a short suggested theme; they are kept with the results. Conversations analysed before a theme entered the set are not processed in bulk.
- When an employee asks for a draft FAQ in the Voice of Customer section, the most frequent subjects of the questions customers asked in the period and projects the employee selected, with up to 40 of the kept one-sentence summaries of those questions — masked again the same way before they are sent — are sent to the same provider in a separate request to write a draft FAQ with answer templates for your organization to complete. No transcript, quote or call is sent. The draft is shown to that employee and is not kept. Aelo does not charge for it; at most 10 drafts per organization and 5 per employee in 24 hours.
- When your organization's owner or an administrator asks for a starter set of conversation themes, the short topic phrases the analysis kept for your organization's conversations of the last 90 days, each with the call category of the conversation — distinct pairs, up to 1,500 of them, without demo conversations — are sent to the same provider in a separate request to propose up to 25 themes with short descriptions. The phrases are checked again the same way before they are sent, and a phrase in which the check finds such a pattern, or that may contain an identification number, is left out. No transcript, quote, call or person is sent. The proposal and the list of phrases that was sent are kept; the owner and administrators edit and approve it, and only approved themes enter the set. A new proposal at most once in 24 hours per organization. Aelo does not charge for it.
- Once a week, for an organization with conversation themes whose set has an active theme and that had newly analysed conversations in the last 7 days, up to 300 distinct suggested-theme phrases kept for its conversations of the last 30 days, without demo conversations, are sent to the same provider in a separate request to group them into at most five candidate themes, each with a name and a short description. The phrases are checked again the same way before they are sent, and a phrase in which the check finds such a pattern, or that may contain an identification number, is left out. No transcript, quote, call or person is sent. A candidate that came up in at least 10 conversations and 3% of the period's conversations is shown to the owner and administrators with its counts and up to three example conversations, to accept into the set or reject. It is not done while your organization's analysis is paused. Aelo does not charge for it.
- Segments of the redacted transcript — or of a redacted chat conversation — are sent to the same provider to compute numerical vectors for search by meaning, after a contextual masking of a passport or other identity-document number, a tax number, a date of birth, bank account details and an address that follows a label such as “address” and a colon, a dash or “is” (a labelled address also where it continues after a line break within one turn), and of an address written as a street word from a fixed list (“street”, “avenue”, “calle”, “avenida” and the like, in English, Spanish, Ukrainian and Russian), the street’s name, a comma and a house number (such as “calle Mayor, 7” or “avenida Diagonal, 12”) in addition to the redaction above; an address or a date of birth without such a label or form is not detected (for example “my address 123 Broadway”, with no colon, dash or “is” after the label, or “Hauptstraße 12”, with no comma), and names are not removed. Vectors computed before release 26.50.0 were computed after the redaction above only and are replaced when the record is transcribed again and its vectors are built, or when the index is rebuilt. Only the vectors are kept, with identifiers of the record, project, organization and transcript, the record type and the segment’s length, and — when known — an identifier of the employee who handled it (their Bitrix24 user ID, or their ID in the connected telephony or in Aelo) and the record’s date, without the text. The text a user types into search, and an AI assistant question matched against the search index, are sent to the same provider, redacted the same way, to compute a vector used for that search only.
- When an employee asks the AI assistant (Pro plan and above) a question — about one call, about a CRM deal, lead, contact or company across its linked calls and chats, or about all the analysed calls and chats the employee may see — the question, redacted the same way and, before it is kept, checked by the same provider in a separate request for personal data the redaction missed (what it finds is masked; a question whose check fails is not accepted), is sent to the same provider together with the redacted transcripts and analyses the answer is built from. For a question about all records, the question is first matched by meaning against the search index (its vector is not kept), up to 12 of the closest records are used, and the filters it was asked under — period, record type, category, customer name — are sent with it. Before the answer is written, the transcripts and analyses it will be built from, with the earlier questions and answers of the same conversation, are sent to the same provider in a separate request to find personal data the redaction missed — such as an address, a date of birth, an identity or tax number, card or account details, a phone number or an email, also where it is split between turns or spelled out in words — and what it finds is masked; the answer is checked the same way, with the question, before it is kept and shown, and a record whose check fails is left out of the answer, and when the check of the answer or of every record fails, no answer is given. Only records the employee may see are ever used. The question and its answer are kept for the employee to return to for your organization's retention period, and are deleted with any record the answer was built from.
- If your organization has the deal state (Pro plan and above) and an analysed call or chat is linked to a deal or lead, the redacted transcript of that conversation (redacted again before it is sent), a summary of its analysis, the previous state of that deal or lead, the sales methodology of the deal's pipeline with your company's rules for it (a lead gets the standard methodology), the number of days since the previous conversation and the deal's stage, amount and currency are sent to the same provider in a separate request to write the updated state: status, chance of closing, what changed, the reason with the customer's words quoted verbatim from the redacted transcript, the next action, points for the next contact, commitments, objections, what is known of budget, decision maker, need and timeline, and the customer's interest. The title of the deal or lead and its responsible employee are not sent. The states are kept as the deal's history together with what was read from your portal (Section 3). Aelo does not charge for it; it is not done for a short call that receives no analysis or when a conversation is re-analysed; conversations analysed before the deal state was available are not processed in bulk.
- When an employee who may see the texts of a deal's state asks for a draft message to the customer in the deal card (deal state, Pro plan and above), the current stored state of that deal or lead — status, chance of closing, the reason for the status, the next action, points for the next contact, what the latest conversation changed, commitments, objections, what is known of budget, decision maker, need and timeline, and the customer's interest, with those texts masked again the same way — and the sales methodology of the deal's pipeline with your company's rules for it (a lead gets the standard methodology) are sent to the same provider in a separate request to write one short follow-up message. No transcript, quote, conversation identifier, title of the deal or lead, amount, stage or responsible employee is sent. The draft is shown to that employee, who can edit and copy it, and is not kept or written to your portal; at most 5 requests per minute, 60 per hour and 200 per 24 hours per organization, and 3, 30 and 60 per employee. Aelo does not charge for it.
- With stage-based scorecard selection on, the names of your deal pipelines and their stages (not of the stages your organization has given a phase itself), in their order and with Bitrix24’s own mark of the won and lost stages, are sent to the same provider in a separate request to determine the sales phase (discovery, qualification, proposal, negotiation, closing or post-sale) of each stage that neither Bitrix24 nor your organization has given one — no customer, deal or conversation data. This happens when a call at such a stage is analysed, when an employee opens the deal stages settings or clears the phase of a stage there, and when Aelo gives a phase to calls recorded before stages had one; other screens that show the stages send nothing; it is asked when a stage is new or has been renamed, or an earlier attempt gave no answer for it, and the request then contains the names of all your pipelines and stages. A phase your organization sets for a stage always takes precedence. Aelo does not charge for it.
- To evaluate the quality of the analysis, Aelo measures how accurately it answers on samples of conversations: the kept redacted transcripts of a sample are sent to a language model that labels them without seeing the analysis’s answers or checks the kept analysis against its transcript, and the analysis a candidate model or wording produces on them is compared with the current one; depending on the measurement, the analysis or answers of those conversations and the wording being measured are sent too. These requests go to OpenAI and, from 2026-12-03, to Anthropic; the redaction does not remove names. The results are used to decide changes to the analysis, are not shown to your organization and are not used to make decisions about the people in the conversations.
- CRM context needed to interpret the conversation — the linked record's identifier, the deal's pipeline and stage, the employee's name — accompanies the analysis inside the Aelo service.
- When the Application is installed in a portal that has no Aelo organization yet, the portal’s address and the new organization’s name and identifier are recorded as a lead in Aelo’s own Bitrix24 portal, so that our team can follow up. Aelo does this for its own purposes, as controller (Privacy Policy, Section B.6); no data of your conversations or CRM records is involved.
Every third party involved, the data each receives, its location and the transfer safeguard applied are listed in the Sub-processors register, which we update at least 30 days before adding a new sub-processor.
5. What the Application Writes Back
Results are returned into your portal so that they are usable where your team already works:
- A comment or note on the CRM record's timeline carrying the verdict of the analysis.
- An item in a dedicated smart process ("Call data") holding the full breakdown. On first use the Application creates this smart process and its custom fields on the CRM module. It does not create or modify custom fields in employee profiles.
- Values in the CRM fields you designate. You decide, per data source, which output of the analysis goes into which field of your lead, deal, contact or company — for example the transcript into one custom field and the summary into another. The Application writes only into the fields you have mapped.
- The transcript attached to the call in Bitrix24 telephony.
- A task for the responsible employee when a conversation triggers a rule that calls for follow-up.
- With the deal state (Pro plan and above), a separate comment about the state of the deal or lead on its timeline after each new state: the date of the conversation and, for a call, its duration; the status and chance of closing and what they were before; what changed; the reason with the customer's verbatim quote and a link to the conversation in Aelo; the next action with its due date and reason; points for the next contact and the methodology; the commitments without who made them; the objections by their standard names; which of budget, decision maker, need and timeline are known, without the facts; the customer's interest; and a link to the deal or lead in Aelo. It is written only when Bitrix24 is the CRM that receives your call reports, only for a conversation held within the last 7 days and not for a conversation analysed after a newer one; your organization can switch these comments off (they are on by default).
- With the deal state, when an employee asks for it, a to-do (CRM activity) in the deal or lead, assigned to its responsible employee: the next action as its title, its reason and, except when it is created from the Aelo tab in the card, a link to the deal or lead in Aelo as its description, and its due date.
- The “Aelo” tab in the deal, lead, contact and company cards: the Application registers it (
placement.bind) when it is installed and when a data source is reconnected, or the Aelo team does so for an existing installation. The Application removes it when the data source is disconnected in Aelo. - A notification to an employee about new coaching feedback — a note, an annotation or a review that a supervisor, an administrator or the owner left on their work — when the employee’s Aelo account is linked to their user in the portal: the author’s name, the kind of feedback and a link that opens the Application on the conversation (a call at the moment the feedback is about), never the feedback text. One per author and conversation within 30 minutes; the employee can mute it in the portal’s own notification settings.
- Any other notification or chat message inside the portal, when in-portal delivery is configured.
5.1 How existing values are treated
Before writing, the Application reads the record's current field values and field definitions so that it never silently destroys data. Per field:
- an empty field receives the new value;
- a filled text field keeps its content and the new value is appended below it;
- a filled non-text field (number, date, list, and similar) is left untouched and the value is not written.
One exception, stated plainly: if that read of the current values fails — for example the portal is unreachable at that moment — the Application cannot tell which fields are populated. In that case values extracted from the conversation (Section 5.2) are discarded entirely, while the fields you designated for Aelo's own output are written directly and may replace what was in them. Fields you never mapped are unaffected either way.
5.2 Filling empty fields from the conversation (optional, off by default)
Your administrator can additionally enable auto-fill of empty CRM fields and choose which fields are eligible. When this is on, the language model is asked to extract values for those specific fields from the conversation itself — for instance a delivery address, a budget or a requirement that the customer stated out loud — and the Application writes them into your CRM.
Two limits apply to this mode and are enforced in code, not by policy alone:
- Extracted values are written only into fields that are empty. A field that already holds a value is never overwritten or appended to by auto-fill.
- Only the fields your administrator selected are eligible. If the Application cannot determine which fields are already populated, or if delivery was redirected to a different CRM record than the one the conversation belongs to, auto-fill is skipped entirely rather than applied on a guess.
This setting is disabled by default. Enabling it means content spoken by a call participant may be stored in your CRM's structured fields, so the decision — and informing the participants about it — rests with you as controller.
6. What the Application Does Not Do
- It does not create, invite, modify or deactivate users in your Bitrix24.
- It does not read or write custom fields in employee profiles.
- It does not read employees' personal contact details at all — no e-mail addresses, personal phone numbers, addresses or birthdays. If you choose to give Aelo an address so it can send you reports, you type it into the Application yourself; it is never read from your portal.
- It does not delete CRM records, calls or files in your portal.
- It does not sell, rent or share your data with advertisers or data brokers.
7. Storage and Retention
| Data | Retention |
|---|---|
| Audio recordings retrieved from your portal | 365 days, then deleted together with the transcript |
| Transcripts (with personal data redacted) | 365 days |
| Analyses, metrics and conversation metadata | Follows transcript retention |
| Search vectors (no text) | Rebuilt from the current transcript when the call is transcribed again (if that build fails, the earlier vectors stay until the next index rebuild) or the index is rebuilt; removed from the index after the record is deleted — by a user, at the end of the retention period or together with its project — normally within a few hours; while a large volume of deletions is being processed, removal can take several days |
| Conversation themes (organizations with the Voice of Customer section with its customer questions and decline reasons): your organization's set of themes with a record of who changed it and when; per conversation, the themes of the set and a suggested theme; a starter set proposal with the list of phrases that was sent; weekly suggestions with their counts, phrases and up to three example conversations | The set and the record of its changes: duration of the account (a theme is archived, not deleted). The themes and the suggested theme of a conversation are deleted together with it. The list of phrases of a starter set: until it is approved or a new one is requested, and at most 30 days; the proposed themes stay until a new starter set replaces them. A weekly suggestion: at most 30 days after the last week in which it reached the threshold; a rejected one 90 days after the decision, without its phrases, which are erased when it is accepted or rejected; an example is removed when that conversation is deleted. The phrases are not linked to a call, so a phrase from a call deleted in the meantime remains until these periods end |
| Decline-reason code on a lost deal (organizations with stage-based scorecard selection and the Voice of Customer section with its customer questions and decline reasons): a code from a fixed list taken from the most recent conversation of the deal's current loss cycle that ended in a decline, without the customer's words | While the deal stays lost and that conversation exists: removed when the conversation is deleted, including at the end of the retention period, and when the deal is reopened or won; replaced or removed when a newer conversation of the same loss cycle ends in a decline or when the conversation's analysis no longer confirms the reason. With stage-based scorecard selection switched off, the deal is not re-checked and the code stays until the conversation is deleted |
| Deal states, with the title, amount, currency, pipeline, stage and responsible employee read from your portal and, for a deal converted from a lead, the identifier of that lead | Your organization's retention period, counted from the earliest conversation a state may carry facts from; also deleted with its project or the account. Not deleted when a call it was built from is deleted — its text, quotes and links stay as your employees saw them until the state reaches the end of the retention period. Comments and to-dos already written to your portal stay there under your control |
| Phase of a deal stage determined from the pipeline and stage names: the phase, the model that determined it and a hash of the stage’s name (not the names) | Until it is replaced (a renamed stage is asked again) or the account is deleted; the row of a stage removed from your portal stays until then |
| Ingest activity log: for each incoming event from your portal, the decision on where to route it, with its reason, the routing rule that matched and the external identifier of the call or chat | 90 days after the entry was written, whatever your organization’s retention period; the entry of a call or chat still waiting to be processed is kept until it is |
| Ingest receipts: for each call or chat taken in for processing, its external identifier, the installation, a hash of the content and the identifier of the record created, used to recognise a repeated delivery | 30 days after it was processed; a receipt still waiting to be processed is kept until it is |
| Employee accounts and the imported department tree | Duration of the account; the tree is replaced in full on each import |
| OAuth tokens for your portal | Marked inactive the moment the Application is removed — Bitrix24 revokes them at that point, so they cannot be used afterwards. The installation record itself is erased on request, or together with the account |
Data is stored on Cloudflare and Neon infrastructure; the database and the audio storage are in the EU. The search index (numerical vectors with record and employee identifiers, no text) and Cloudflare's processing state, queues, logs, caches and coordination state are not pinned to the EU; some of them hold call transcript and chat text while a conversation is processed and for a few days after. The full security description is in the Aelo Privacy Policy and the DPA.
8. Removing the Application and Deleting Data
Removing the Application from your Bitrix24 stops all access to your portal: its event subscriptions are cancelled and its installation record is deactivated, so no further data is read.
Removal does not by itself erase data already analyzed. Recordings, transcripts and analyses remain in your Aelo account and are deleted on the retention schedule above. To have them erased sooner, request deletion of your Aelo account or of specific records by writing to privacy@aelo.cloud. We act on such requests without undue delay and within the periods required by applicable data protection law.
9. Rights of Employees and Call Participants
Employees whose conversations are analyzed, and customers who took part in them, are data subjects. Because the organization operating the portal is the controller, requests to access, correct, delete or object should be addressed to that organization, which uses Aelo's tooling to fulfil them.
If you cannot identify or reach the controller, write to privacy@aelo.cloud and we will help route the request.
10. Changes to This Policy
We may update this policy as the Application changes. Material changes affecting what is read from your portal or what leaves it will be communicated to customers by e-mail at least 30 days before they take effect.
11. Contact
Publisher / Processor:
Auspex Streamline S.L.
C.I.F.: B56341829
Calle Velarde 13, 4B
35010 Las Palmas de Gran Canaria
Canarias, Spain
Privacy inquiries: privacy@aelo.cloud
Application support: support@aelo.cloud
Document ID: PP-Aelo-B24-2026-001 · Version: 1.26