The reviewed source set produced no substantive exact-product editorial review, benchmark, mature software-review corpus or eligible numeric rating for Odella. Five reviewed public source domains were technically inaccessible. Apple App Store and Google Play exact-name searches returned apps associated with a developer named Oriol Della rather than Odella AI; those results were excluded for product-surface mismatch. Other reviewed-source searches returned no relevant exact-product evidence. Missing coverage is not scored as zero, but it reduces confidence.
Outside the main reviewed source set, current third-party evidence is mostly ecosystem and launch corroboration rather than testing. LinkedIn company data identifies Odella as a Sydney software company founded in 2025, and launch posts in August 2026 confirm the current AI-employee positioning. Smokeball's marketplace lists Odella as an integration for legal practices and describes document/process automation against Smokeball data. These sources corroborate identity and use cases but do not independently benchmark output quality.
Privacy documentation is materially more detailed than many early agent platforms. LAIW PTY LTD is identified as the operator. The Privacy Policy says customer data in active systems is deleted within 30 days after account deletion or a valid request, backups ordinarily expire within 90 days, and security/access/operational logs are generally retained up to 24 months. A July 2026 DPA describes Odella as Processor/Subprocessor for customer personal data and incorporates appropriate contractual transfer mechanisms where applicable.
Odella's LLM-training policy deserves precise treatment. Customer Data, Content and AI Agent Traces are not used to train or fine-tune Odella-developed LLMs unless an authorized organization owner expressly opts in. However, the policy separately permits service-improvement processing such as model routing, workflow reliability, safety evaluation and product improvement, and third-party model/API providers can have their own data terms. Organizations with sensitive data should therefore review configured providers and subprocessor terms rather than treating “no training by default” as a blanket no-processing statement.
The security surface includes least-privilege access, isolated worker environments, approval gates, SSO/RBAC-style administration, regional residency options, PII removal claims and audit logs. These are meaningful controls. The remaining evidence gap is assurance: The reviewed public evidence does not include a SOC 2 report, ISO certificate, penetration test or external reliability benchmark during this desk review.