Инструкция организации на обработку данных Uspacy
С 2026-11-16 эта инструкция входит в Соглашение об обработке данных, раздел 2.1, и отдельно она больше не выдаётся. Текст ниже сохранён в том виде, в каком его приняли.
Ниже приведён английский текст этой версии. В случае расхождений преимущественную силу имеет английская версия.
Documented instruction
By separately confirming this instruction, the authorized representative of the organization operating the identified Uspacy portal instructs Auspex Streamline S.L., through Aelo, to:
- subscribe to Uspacy CRM activity events and determine whether an activity represents a completed call;
- read the call event and the minimum related metadata needed to identify and route it and, for a call bound to a deal, the current stage identifier of that deal and the portal’s deal funnels with their stages, to find the funnel and stage of the deal, and, where the organization has the deal state, the leads linked to that deal, using only their identifiers and whether Uspacy marks a lead as converted, to find the lead the deal was converted from;
- retrieve the call recording made available by the organization through Uspacy;
- store the recording, transcribe it, redact supported text patterns, analyze the redacted transcript and store the resulting transcript, metrics and analysis;
- where the organization defines criteria, put them to the redacted transcript of each call within their scope and store the answers, with quotes from the redacted transcript, the model’s short explanation and the responsible employee’s identifier when known; and, on the organization owner’s request, put a draft wording to up to 20 recent analysed calls without storing the answers; on a user’s request, write a draft wording from the user’s own description of a criterion (masked for supported text patterns), and propose an edit of a draft wording from the answers of its check the user marked as wrong, sending the user’s optional reasons and, for each marked call (up to 10), a fragment of its redacted transcript around the quoted lines, redacted again — showing the draft and the proposed edit to that user without storing them;
- put Aelo’s built-in criteria — standard questions worded by Aelo (for example, whether the company was named, a next contact was agreed or call recording was disclosed) that are the only place where these checks of what was or was not said are made, because the analysis no longer performs them, paused and limited in scope by the organization owner in the Aelo criteria settings within the limits Aelo sets — to the redacted transcript of each call within their scope, in a separate request (with the organization’s criteria, or on their own if it has none), except where the organization uses its own provider key, for a short call that receives no analysis and when an already analysed call is re-analysed (a retried failed analysis asks them as usual), and store the answers in the same way, showing them to the organization (where Aelo has switched built-in criteria off for the organization, they are not shown and the organization has none of these checks; an organization that uses its own provider key has none of them on new calls);
- where the organization has the Voice of Customer section with its customer questions and decline reasons (Pro plan and above), put the redacted transcript of each newly analysed call to the same language-model provider in a separate request to find the questions the customer asked (up to 10) and, for a sales conversation, how it ended and why the customer declined, and store the results, with the customer’s words quoted verbatim from the redacted transcript, with the record — on Aelo’s own account at no charge to the organization, or with the organization’s own provider key where it uses one; where the organization also has conversation themes and its set has an active theme, send with that request the names and descriptions of the active themes (as the organization wrote them, at most with supported text patterns masked), obtain one to three themes of the set for the call, or that none fits, and, where the call has a subject the set lacks, a short suggested theme, and store them with the results;
- where the organization has the Voice of Customer section with its customer questions and decline reasons, on a user’s request, put up to 40 of the stored one-sentence summaries of the questions customers asked in the period and projects the user selected, with their subjects and masked again for supported text patterns, to the same language-model provider in a separate request to write a draft FAQ with answer templates, show the draft to that user and not store it — on Aelo’s own account at no charge to the organization, or with the organization’s own provider key where it uses one; at most 10 drafts per organization and 5 per user in 24 hours;
- where the organization has conversation themes (Pro plan and above), on the request of its owner or an administrator, put the short topic phrases stored for the organization’s calls of the last 90 days with their call categories — distinct pairs, up to 1,500, without demo calls, with the calls of this Uspacy portal only while this instruction is active, checked again for supported text patterns, a phrase in which the check finds one or that may contain an identification number left out, and no transcript, quote, call or person — to the same language-model provider in a separate request to propose up to 25 themes with descriptions, store the proposal and the list of phrases sent (the phrases for at most 30 days) and let the owner and administrators approve it, only approved themes entering the set — on Aelo’s own account at no charge to the organization, or with the organization’s own provider key where it uses one; a new proposal at most once in 24 hours;
- where the organization has conversation themes whose set has an active theme and that had newly analysed calls in the last 7 days, once a week while the organization’s analysis is not paused, put up to 300 distinct suggested-theme phrases stored for its calls of the last 30 days — the calls of this Uspacy portal only while this instruction is active — (checked again for supported text patterns, a phrase in which the check finds one left out, without demo calls, and with no transcript, quote, call or person) to the same language-model provider in a separate request to group them into at most five candidate themes, show a candidate that came up in at least 10 calls and 3% of the period’s calls to the organization’s owner and administrators, with counts and up to three example calls, to accept or reject, and keep the candidate for 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) — on Aelo’s own account at no charge to the organization, or with the organization’s own provider key where it uses one;
- compute numerical search vectors from segments of the redacted transcript, and from the redacted text a user types into search, for search by meaning, and store the segment vectors without text in the search index listed in the Sub-processors register;
- where the organization connects Uspacy chat conversations to Aelo, process them in the same way — redaction, analysis and search vectors — as calls;
- where the organization has the deal state (Pro plan and above) and Uspacy binds a call explicitly to a deal or lead, put the redacted transcript of the call, a summary of its analysis and the previous state of that deal or lead (for a deal with no state of its own yet, converted from a lead that has one, the lead’s state as of the deal’s first call) to the same language-model provider in a separate request — together with the sales methodology set for the deal’s funnel and the organization’s company rules for it, masked for supported text patterns, and, for a deal, its stage identifier — to write the updated state of the deal or lead, with the customer’s words quoted verbatim from the redacted transcript, and store the states as its history, together with the identifier of the responsible employee of that deal or lead (the Uspacy field “owner”), read from Uspacy for that purpose and not sent to the language-model provider, on Aelo’s own OpenAI account at no charge to the organization, or, where the organization has its own active OpenAI key, with that key, except for a short call that receives no analysis and when a call is re-analysed; a deal state is kept for the organization’s retention period and is not deleted when a call it was built from is deleted;
- where the organization has the deal state (Pro plan and above), while this instruction is active, on the request of a user who may see the texts of a deal’s state, put the current stored state of that deal or lead, masked again for supported text patterns and without quotes, conversation identifiers, title, amount, stage or responsible employee, together with the sales methodology set for the deal’s funnel and the organization’s company rules for it, masked the same way, to the same language-model provider in a separate request to write one short follow-up message to the customer, show the draft to that user and not store it or write it to Uspacy — on Aelo’s own OpenAI account at no charge to the organization, or, where the organization has its own active OpenAI key, with that key, at most 5 requests per minute, 60 per hour and 200 per 24 hours per organization and 3, 30 and 60 per user;
- where the organization has switched on stage-based evaluation, send the names of the portal’s deal funnels and of their stages — in their order and with each funnel’s closing success or fail stage marked, but without the stages the organization has given a phase itself and without any customer, deal or conversation data — to the same language-model provider in a separate request, to determine the sales phase (discovery, qualification, proposal, negotiation, closing or post-sale) of each stage that neither Uspacy nor the organization has given a phase; only while stage-based evaluation is on, and only when such a stage is new or has been renamed or an earlier attempt gave no answer for it; keep the determined phase with a hash of the stage’s name, not the name, until it is replaced or the organization’s Aelo account is deleted, and mark it as a guess wherever it is shown; a phase the organization sets for a stage always takes precedence — on Aelo’s own OpenAI account at no charge to the organization, also where the organization has its own OpenAI key;
- where the organization has switched on stage-based evaluation, re-read on a recurring schedule the current stage identifier of each deal bound to an analysed call and store the deal’s outcome (open, won or lost, from the funnel’s closing success or fail stage) with its funnel and stage identifiers and close and check times, store at each re-check the deal’s funnel and stage identifiers with the times it first and last saw the deal on that stage (deleted 90 days after the deal was last seen on that stage, and with the organization’s Aelo account), decide per call, from the stage the deal was seen on when the ~7-day window following the call ended, whether the deal advanced, held or regressed, and, where the organization has the Voice of Customer section with its customer questions and decline reasons, keep on a lost deal the code of the reason the customer gave in its most recent declined call — without any request to a language-model provider;
- on the request of the organization’s owner, read the portal’s employee directory — each employee’s identifier, name, email address, whether the employee is active and the departments the employee belongs to, without application bots — and its departments — identifiers, names, parent department and the head the portal names — to reproduce the organization’s department structure in Aelo: match employees to the organization’s Aelo users by email address, making a matched employee a member of their departments without linking their Aelo account to the portal; give the department head the portal names access to the records of everyone below them in the tree only once that head has linked their own Aelo account from the portal, unless the organization’s owner assigns a head in Aelo, which always takes precedence; store an employee with no Aelo account yet with their identifier, name, email address and departments until an Aelo account for them is linked; replace the previously imported structure in full on each import and keep it for the duration of the organization’s Aelo account — without sending any of it to a speech-to-text or language-model provider;
- return a summary or note to the Uspacy call and, only where Uspacy supplies an explicit supported binding, add a comment to the linked CRM entity; and, where the organization has the deal state, while this instruction is active and Uspacy is the CRM that receives the organization’s call reports, add a separate comment about the state of the bound deal or lead to it, for a call held within the last 7 days, unless the organization switches these comments off; and, where the organization has the deal state, while this instruction is active, on the request of a user who may create a task for a deal, add one planned task (a CRM activity) to that deal or lead, with the next action as its title, its reason and a link to the deal or lead in Aelo as its description, and its due date, assigned to the responsible employee of that deal or lead whom Aelo has kept with the deal’s latest state, and, where none is known, without Aelo setting a responsible employee for it, so that Uspacy assigns it by its own default, reading that deal’s or lead’s activities — their identifiers, bindings, status and description — only to find the task Aelo added for the deal’s current state, so that a repeated request adds no second one; and
- retain and delete the resulting Customer data according to the organization’s Aelo retention setting and valid deletion instructions, except two operational journals with fixed periods that do not depend on that setting: delete the ingest log entry for a call event that was not taken in (rejected, skipped or failed) 90 days after it was written, and the receipt of a call taken in, used to recognise a repeated delivery, 30 days after the call’s intake into Aelo was completed, keeping the receipt of a call whose intake has not been completed, and a log entry about that call, until it is.
Pro Trial: a free (Pay-as-you-go) organization receives the features of the Pro plan once, for 14 days from its next analyzed 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.
Controller confirmations
The organization remains responsible for deciding which calls may be recorded and analyzed; establishing an applicable legal basis; giving required notices to employees and call participants; handling data-subject requests; and ensuring that the person activating, pausing, withdrawing or reauthorizing this instruction has authority to act for the organization.
Duration and changes
The instruction remains active until paused, withdrawn or the application is uninstalled. Aelo records the acting user and, where available, the external Uspacy user identifier, together with installation and portal identifiers, document version, language, canonical URL, authority basis and timestamp. Material changes to the scope require a new version and fresh authorized confirmation.
Pausing or withdrawing blocks new intake before Aelo attempts to remove the external subscription. Existing records remain subject to the configured retention period or a valid earlier deletion request.
Related documents and governing version
This instruction operates with the Aelo Data Processing Agreement, Uspacy Integration Privacy Notice and Sub-processors register. The English text is the governing version; German users are linked to it until reviewed German legal text is available.