Умови інтеграції з Uspacy
Нижче наведено чинний англійський текст. У разі розбіжностей англійська версія має переважну силу.
1. Scope and parties
These supplemental terms govern the Aelo Calls Beta application installed in a Uspacy portal. They form part of the Aelo Terms of Service. “Customer” means the organization that controls the Uspacy portal; “Auspex” means Auspex Streamline S.L., the provider of Aelo.
The person activating the integration represents that they are authorized to act for the Customer and accepts, on the Customer’s behalf, these terms, the Aelo Terms of Service and the Data Processing Agreement. The processing the integration carries out for the Customer’s portal is described in the Data Processing Agreement, section 2.1, which replaced the separate organization processing instruction.
2. Calls Beta service
After authorized activation, Aelo subscribes to Uspacy CRM activity events and checks whether they represent calls. For a completed call, Aelo resolves the corresponding call event, retrieves the recording link and relevant call metadata, transcribes and analyzes the recording, stores the resulting record under the Customer’s Aelo workspace, and writes a summary or note back to Uspacy. When a call has an explicit supported CRM binding, Aelo may also add a comment to that linked lead, deal, contact or company. Where the Customer uses stage-based evaluation or the deal state, Aelo also reads the portal’s deal funnels with their stages and the current stage of a deal bound to a call.
The Beta does not bulk-import historical calls, modify structured CRM fields, or create Uspacy users. Delivery depends on the Uspacy APIs and event payloads made available to the application.
3. Customer responsibilities
The Customer decides which conversations may be recorded and analyzed and is responsible for an applicable legal basis, required notices to employees and call participants, and any consent required by local law. Aelo’s AI output is an analytical aid, not a legal determination or a substitute for human review.
The Customer must ensure that only an authorized representative activates, pauses, reauthorizes or withdraws the integration’s processing.
4. Access and security
Uspacy provides an access token and rotating refresh token when the application is installed. Aelo stores those credentials in restricted secret storage, not in the public application database. The embedded application uses the current Uspacy user session to read that user’s profile; activation is permitted only when the profile identifier matches the installer identifier recorded by Uspacy, unless a separately documented and verified administrator role mechanism is introduced later.
5. Fees, availability and Beta changes
Aelo plan limits and current pricing are published on the pricing page. The Calls Beta may change as Uspacy’s integration contract evolves. Changes to these terms follow the Terms of Service and the Data Processing Agreement (section 12); a new version is published as a new document version.
6. Suspension, removal and termination
An authorized organization owner or administrator may pause or withdraw Uspacy processing in Aelo settings. Aelo blocks new intake before attempting to remove the Uspacy webhook subscription. Removing the application from Uspacy disables the source and deletes stored portal credentials, but does not withdraw the acceptance: when the same Customer installs the application again, processing resumes without a new acceptance (Terms of Service 1.12, section 7; Data Processing Agreement, section 2.1). Neither pausing, withdrawing nor removing the application automatically deletes analyses already stored in Aelo; those records follow the Customer’s configured retention period or an earlier valid deletion request.
7. Privacy and order of documents
The Uspacy Integration Privacy Notice describes the integration-specific data flow. Processing on the Customer’s behalf is also governed by the Data Processing Agreement and the Sub-processors register. If these supplemental terms conflict with the general Terms solely about this integration, these supplemental terms control; the DPA controls for processing of personal data.
8. Contact and governing version
Support: support@aelo.cloud. Privacy and legal inquiries: privacy@aelo.cloud.
The English text is the governing version. Ukrainian and Spanish page labels and notices are provided for accessibility; reviewed translations may replace the English body in a later version. German users are linked directly to this governing English version until reviewed German legal text exists.