Uspacy Integration Privacy Notice
1. Roles and scope
The organization operating the Uspacy portal is the controller of call, employee and CRM data it instructs Aelo to process. Auspex Streamline S.L. operates Aelo as processor for that Customer. Aelo is controller for the limited account, security, billing and support data described in the general Privacy Policy.
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.
2. Data read from Uspacy
| Data | Purpose |
|---|---|
| Installer identifier and the current user’s identifier, name, email address and interface language | Verify installation authority, create or link the person’s Aelo account, keep an evidence trail and localize the shell |
| Completed-call event and CRM activity identifiers, direction, status, timestamps, duration, subject, participant phone number and responsible employee identifier | Resolve, route and describe the call |
| Recording link and recording audio | Retrieve the selected recording for transcription and analysis |
| An explicit lead, deal, contact or company binding when Uspacy supplies one | Return the result to the correct CRM card without guessing |
| The portal’s deal funnels with their stages (identifiers, names, order and whether a stage is a closing success or fail stage), and the current stage identifier of a deal bound to a call (Aelo reads the deal and uses only that identifier), read at analysis and, with stage-based evaluation, again on a recurring schedule — only while the organization’s processing instruction is active | Show the stages on the Deal Stages tab, find the funnel and stage of a deal, capture its stage at analysis for stage-based evaluation, determine the phase of a stage from the funnel and stage names (see section 4), apply the sales methodology set for its funnel to the deal state, and keep the deal’s outcome (open, won or lost) and whether it advanced after a call current for the Sales dashboard (see section 4) |
| The leads linked to a deal bound to a call, where the organization has the deal state (Aelo reads them and uses only their identifiers and whether Uspacy marks a lead as converted) — only while the organization’s processing instruction is active | Find the lead the deal was converted from, so that the deal’s state continues that lead’s state (see section 4) |
| The responsible employee’s identifier (the Uspacy field “owner”) of a deal or lead bound to a call (Aelo reads the deal or lead and keeps only that identifier), where the organization has the deal state — only while the organization’s processing instruction is active | Keep it with the deal’s state, so that the task Aelo adds for the deal or lead at a user’s request is assigned to that employee (see section 4) |
| The CRM activities of a deal or lead — their identifiers, bindings, status and description — read when a user asks for a task for that deal or lead, where the organization has the deal state — only while the organization’s processing instruction is active | Find the task Aelo added for the deal’s current state, so that a repeated request adds no second one (see section 4) |
| The portal’s employee directory — each employee’s identifier, name, email address, whether the employee is active and the departments the employee belongs to — and its departments — identifiers, names, parent department and the head the portal names; application bots are left out — read when the organization’s owner imports the org structure in Aelo, only while the organization’s processing instruction is active | Reproduce the organization’s department structure in Aelo, match employees to the organization’s Aelo users by email address and show the organization’s owner the employees who have no Aelo account yet (see section 4) |
| Where the organization connects Uspacy chat conversations to Aelo (not yet available in the Calls Beta): the conversation’s messages, timestamps and participant and responsible-employee identifiers | Analyze the conversation in the same way as a call |
The Calls Beta does not bulk-import historical calls or read arbitrary Uspacy CRM fields: of a deal only its stage identifier, the identifier of the lead it was converted from and the identifier of its responsible employee are used (of a lead, only the identifier of its responsible employee), and Aelo keeps of a deal only its funnel and stage identifiers, the outcome derived from them, that lead’s identifier and the identifier of its responsible employee, and reads no deal title or amount. Of the portal’s employees beyond the installer and the current user, Aelo reads only the directory described above, and only for the org-structure import.
3. Token handling
At installation Uspacy supplies an access token, refresh token and expiry information. Access and refresh tokens are kept in restricted Cloudflare KV secret storage and are not written to the public metadata database. Non-secret installation identifiers, portal domain, credential-health status and webhook subscription identifier are kept in the metadata database. Tokens are rotated when Uspacy refreshes them and deleted when the application is uninstalled.
4. Processing and external providers
- An authenticated Uspacy-originated CRM activity event is received and checked to determine whether it represents a call.
- Aelo checks that the installation is active and that its current processing state is active before queueing or enriching the event.
- Aelo uses the Customer’s Uspacy token to resolve the call and retrieve its recording link.
- The audio is stored and sent to the configured speech-to-text provider. Supported phone, email, payment-card and valid IBAN patterns in new transcripts are redacted on write and before LLM analysis; original audio is not text-redacted.
- The redacted transcript is sent to the configured language-model provider for analysis.
- If the organization has defined criteria — its own questions asked of every conversation — the redacted transcript is sent to the same provider again, in a separate request, together with the text of the criteria that apply to the call. The answer, quotes from the redacted transcript, the model’s short explanation and, when known, the responsible employee’s identifier are stored 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 calls are sent the same way with the draft wording; those answers are shown and not stored. 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 call (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 stored.
- 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 or call recording was disclosed) that are the only place where these checks of what was or was not said are made: the analysis no longer performs them. The redacted transcript is sent to the same provider in a separate request — together with the organization’s criteria, or on its own if it has none — and answered on Aelo’s own account at no charge. The 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 if the organization uses its own provider key, for a short call that receives no analysis, or when an already analysed call is re-analysed (a failed analysis that is retried asks them as usual). Their answers are stored with the record in the same way and deleted together with it, and are shown to the organization, including in the report Aelo adds to Uspacy; if the organization uses its own provider key, built-in criteria are not shown and it has none of these checks on new calls, and if Aelo has switched them off for the organization, they are not shown and the organization has none of these checks.
- If the 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 call 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 stored with the record and deleted together with it. Calls analysed before this was introduced are not processed in bulk; a call the organization re-analyses is processed like a new one. It is made on Aelo’s own account at no charge, or with the organization’s own provider key where it uses one. Where the organization also has conversation themes (Pro plan and above) and its set has an active theme, the same request carries the names and descriptions of those themes (as the 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 call, or that none fits, and, where the call has a subject the set lacks, a short suggested theme, which are stored with the results; calls analysed before a theme entered the set are not processed in bulk.
- When a user 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 user selected, with up to 40 of the stored one-sentence summaries of those questions — masked again for supported phone, email, payment-card and IBAN patterns before they are sent — are sent to the same provider in a separate request to write a draft FAQ with answer templates for the organization to complete. No transcript, quote or call is sent. The draft is shown to that user and is not stored. It is made on Aelo’s own account at no charge, 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.
- When the organization’s owner or an administrator asks for a starter set of conversation themes, the short topic phrases the analysis stored for the organization’s calls of the last 90 days, each with the call category — distinct pairs, up to 1,500 of them, without demo calls and with the calls of the Uspacy portal only while its processing instruction is active — checked again for supported phone, email, payment-card and IBAN patterns before they are sent (a phrase in which the check finds one, or that may contain an identification number, is left out), are sent to the same provider in a separate request to propose up to 25 themes with short descriptions. No transcript, quote, call or person is sent. The proposal and the list of phrases that was sent are stored; 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. It is made on Aelo’s own account at no charge, or with the organization’s own provider key where it uses one.
- Once a week, for an organization with conversation themes whose set has an active theme and that had newly analysed calls in the last 7 days, while its analysis is not paused, up to 300 distinct suggested-theme phrases stored for its calls of the last 30 days, without demo calls and with the calls of the Uspacy portal only while its processing instruction is active (the organization’s calls from its other sources are used either way) — checked again the same way before they are sent (a phrase in which the check finds such a pattern, or that may contain an identification number, is left out) — 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. No transcript, quote, call or person is sent. A candidate that came up in at least 10 calls and 3% of the period’s calls is shown to the owner and administrators with its counts and up to three example calls, to accept into the set or reject. It is made on Aelo’s own account at no charge, or with the organization’s own provider key where it uses one.
- Segments of the redacted transcript — and the text a user types into search, redacted the same way — are sent to the same provider to compute numerical vectors for search by meaning. The vectors are stored in Cloudflare Vectorize with identifiers of the record, project, organization and transcript, the record type and, when known, the responsible employee’s identifier and the call date — without any text. The index region is not pinned. The vector of a search query is used for that search only.
- Where the organization connects Uspacy chat conversations (not yet available in the Calls Beta), their text is processed the same way — redaction, analysis and search vectors — without the audio and speech-to-text steps.
- If the organization has the deal state (Pro plan and above) and Uspacy binds the call explicitly to a deal or lead, the redacted transcript of the call (redacted again before it is sent), a summary of its analysis, the previous state of that deal or lead and the number of days since the previous call 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, by the sales methodology set for the deal’s funnel — the framework chosen for that funnel and the organization’s company rules for it, masked again for supported text patterns before they are sent — or by the standard methodology for a lead and for a deal whose funnel cannot be read. For a deal, Aelo reads from Uspacy its current stage identifier and the portal’s list of deal funnels to find that funnel, and the stage identifier is sent with the request; it also reads the leads linked to the deal and keeps with the deal’s states the identifier of the one lead Uspacy marks as converted, which is not sent. When that lead has a state and the deal has none of its own yet, the deal’s first state continues the lead’s state as of the deal’s first call, and the deal’s card in Aelo names the lead to a user who may open the lead’s card. Aelo also reads the deal or lead itself and keeps with its state only the identifier of its responsible employee (the Uspacy field “owner”); that identifier is not sent to the language-model provider and is not part of the request, and it follows the retention of the deal’s states (section 5). Nothing further is read from Uspacy for it. The states are stored as the deal’s history. This is done on Aelo’s own OpenAI account at no charge, or, where the organization has its own active OpenAI key, with that key; it is not done for a short call that receives no analysis or when a call is re-analysed; calls analysed before the deal state was available are not processed in bulk.
- When a user 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), while the organization’s processing state is active, 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, masked again for supported phone, email, payment-card and IBAN patterns — and the sales methodology set for the deal’s funnel with the organization’s company rules for it, masked the same way (the standard methodology for a lead), are sent to the same provider in a separate request to write one short follow-up message. No transcript, quote, conversation identifier, title, amount, stage or responsible employee is sent. The draft is shown to that user, who can edit and copy it, and is not stored or written to Uspacy; at most 5 requests per minute, 60 per hour and 200 per 24 hours per organization, and 3, 30 and 60 per user. This is done on Aelo’s own OpenAI account at no charge, or, where the organization has its own active OpenAI key, with that key.
- If the organization has switched on stage-based evaluation, 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 not the stages the organization has given a phase itself — 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 Uspacy nor the organization has given a phase. No customer, deal or conversation data is sent. This is done 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; the request then contains the names of all the portal’s funnels and stages. The phase is stored with a hash of the stage’s name, not the name, and is marked as a guess wherever it is shown; a phase the organization sets for a stage always takes precedence. It is made on Aelo’s own OpenAI account at no charge, also where the organization has its own OpenAI key.
- If the organization has switched on stage-based evaluation, Aelo re-reads, on a recurring schedule, the current stage of each Uspacy deal bound to an analysed call and keeps the deal’s outcome — won on its funnel’s closing success stage, lost on its fail stage, otherwise open — with its funnel and stage identifiers and the times it closed and was last checked, to show the outcome of the deals of the period on the Sales dashboard. Uspacy keeps no stage history, so Aelo keeps its own: at each re-check it stores the deal’s funnel and stage identifiers with the times it first and last saw the deal on that stage, and whether the deal advanced, held or regressed after a call is decided from the stage the deal was seen on when the ~7-day window following the call ended, against its stage at the call; a call whose window ended at a time Aelo had not seen the deal at (for example, before stage-based evaluation was switched on, or between two re-checks) gets no result. If the organization also has the Voice of Customer section with its customer questions and decline reasons, a lost deal carries the code of the reason the customer gave in its most recent declined call (a code from a fixed list, without the customer’s words), taken from the stored decline reason. Nothing is sent to a language-model provider for this, and it happens only while the organization’s processing instruction is active.
- When the organization’s owner imports the org structure in Aelo (Settings → Team → Org structure), while the organization’s processing state is active, Aelo reads the portal’s employee directory and departments with the Customer’s Uspacy token. Employees are matched to the organization’s Aelo users by email address. A match by email address makes the employee a member of their departments in Aelo, with the portal’s identifier for the employee stored on the membership, but does not link the employee’s Aelo account to the portal: that link is made only by the employee, from the portal. The department head the portal names receives access to the records of everyone below them in the tree only once that link exists, unless the organization’s owner assigns a head in Aelo, which always takes precedence and survives later imports; a head matched by email address only is recorded as the portal’s suggestion and does not receive that access. An employee with no Aelo account yet is stored with the portal’s identifier, name, email address and departments, and shown to the organization’s owner by name, until an Aelo account for them is linked. Nothing from the directory is sent to a speech-to-text or language-model provider.
- Aelo stores the record, transcript and analysis and appends a summary to the Uspacy call note. If Uspacy states one supported CRM binding explicitly, Aelo may add a comment to that entity. With the deal state, while the organization’s processing state is active and Uspacy is the CRM that receives its call reports, Aelo also adds a separate comment about the state of the bound deal or lead to it after each new state — the date and duration of the call; 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 call in Aelo; the next action with its due date and reason; points for the next contact; 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 added only for a call held within the last 7 days and not for a call analysed after a newer one; the organization can switch these comments off (they are on by default). When a user asks for it in the deal card (deal state, Pro plan and above), while the organization’s processing state is active, Aelo adds one planned task (a CRM activity) to the deal or lead: 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. Where the deal’s latest state knows the identifier of its responsible employee in Uspacy (see item 14), Aelo sets that employee as the task’s responsible employee; otherwise it sets none, and Uspacy assigns the task by its own default. There is one task per deal state: a repeated request finds the task Aelo already added and adds no second one.
Current providers, processing locations and transfer safeguards are listed in the Sub-processors register.
5. Retention
Audio, transcripts, analyses and associated call metadata follow the Customer’s Aelo retention setting: 365 days by default, configurable by an organization owner from 1 to 365 days. Lowering the period removes records already outside the new window. Two operational journals have fixed periods that do not depend on that setting: the ingest log entry for a call event from the portal that was not taken in (rejected, skipped or failed, with the reason, the installation, the project where it is known and the Uspacy identifier of the call or of the activity the event came with) is deleted 90 days after it was written, and the receipt of each call taken in (its external identifier, the time of the call, the installation, a hash of the content and the identifier of the record created, used to recognise a repeated delivery) is deleted 30 days after the call’s intake into Aelo was completed, whether or not the call has been analysed by then; the receipt of a call whose intake has not been completed, and a log entry about that call, are kept until it is. Until then the receipt also keeps the details that came with the call from the portal — the recording link, the Uspacy identifier of the responsible employee, the participant phone number, the call’s direction, duration and subject, its lead, deal, contact or company binding, and whether the call was missed or ended without a recording — so that an interrupted intake can be completed with them; they are removed from the receipt when the intake is completed. Search vectors follow the record: they are removed from the index after the record is deleted — normally within a few hours; while a large volume of deletions is being processed, removal can take several days. Deal states follow the same retention period, counted from the earliest call a state may carry facts from, and are also deleted with their project; a deal state is not deleted when a call it was built from is deleted — its text, quotes and links stay as the organization’s users saw them until the state reaches the end of the retention period. The organization’s set of conversation themes, with a record of who changed it and when, is kept for the duration of its Aelo account (a theme is archived, not deleted); the themes and the suggested theme of a call follow the record. The list of phrases of a starter set is kept until the set 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 is kept 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, and an example call is removed when that call is deleted; these phrases are not linked to a record, so a phrase from a call deleted in the meantime remains until these periods end. The phase determined for a stage, with the hash of the stage’s name, is kept until it is replaced or the organization’s Aelo account is deleted. A deal’s outcome is kept for the duration of the organization’s Aelo account; the stage records of a deal are deleted 90 days after the deal was last seen on that stage, and when the account is deleted; the decline-reason code on a lost deal is removed when the call it was taken from is deleted, including at the end of the retention period, and when Aelo sees the deal reopened or won; the per-call progression result follows the record. Comments already written to Uspacy stay there under the organization’s control. Account, legal-evidence and security records may be retained for the periods stated in the general Privacy Policy, DPA or applicable law.
The org structure imported from the portal — departments, memberships and heads, and the interim records of employees with no Aelo account yet — is kept for the duration of the Customer’s Aelo account. Each import replaces the previously imported structure in full, and an interim record is deleted as soon as an Aelo account for that employee is linked.
6. Pausing, withdrawal, uninstall and deletion
Pausing or withdrawing the organization’s processing instruction blocks new Uspacy intake in Aelo before Aelo attempts to delete the external webhook. A failed Uspacy deletion therefore does not reopen processing. Uninstall also deactivates the installation, removes the webhook where credentials remain usable and deletes stored portal credentials.
Pause, withdrawal and uninstall do not automatically erase records already analyzed. Those records are deleted at the end of the Customer’s retention period or earlier following a valid deletion request. Requests may be sent to privacy@aelo.cloud.
7. Data subject requests and contact
Employees and call participants should normally contact the organization operating the Uspacy portal, which is the controller. Aelo assists Customers with access, correction, export and deletion obligations under the DPA. If the controller cannot be identified, contact privacy@aelo.cloud.
The English text is the governing version. German users are linked to the English version until reviewed German legal text is available.