# Oculus Inc. > Clarifo company profile — qualitative business description generated from > the company's filings. Financial statements, charts and ratios are > available on Clarifo (https://www.clarifo.com/fi/companies/Oculus Inc.). ## Overview Oculus Inc. is a U.S.-listed technology company focused on cybersecurity, data privacy, and data protection software for enterprise customers. Its product set includes cloud-based document protection, privacy compliance tools, and data governance software delivered through its ComplyTrust and Forget-Me-Yes platforms, with operations and headquarters in Vancouver, Canada. ## Products & services • Forget-Me-Yes® data privacy SaaS platform • ComplyTrust® SaaS Suite for data protection • ComplyScan® compliance validation tool • Cloud-DPS digital document protection • C-DPS authentication and tamper-proofing technology - **Data privacy SaaS** (35%) — Software tools that help organizations manage deletion, access, and privacy compliance workflows. - **Data protection and governance** (30%) — Cloud-native tools for protecting enterprise data and managing governance controls. - **Document security and watermarking** (20%) — Digital document protection and tamper-proof authentication using watermarking technology. - **Compliance validation tools** (15%) — Software that checks privacy and data-handling processes against regulatory requirements. - Forget-Me-Yes® data privacy SaaS platform - ComplyTrust® SaaS Suite for data protection - ComplyScan® compliance validation tool - Cloud-DPS digital document protection - C-DPS authentication and tamper-proofing technology ## Customers The company sells primarily to enterprise business customers that need software for privacy compliance, data governance, and document protection. Its use cases are tied to organizations operating under privacy regimes such as GDPR, CCPA, LGPD, and similar laws, including cloud users and data controllers. The products are also relevant to software partners and OEMs that may integrate privacy APIs or microservices into their own offerings. - **Enterprise business customers** (primary) — Buy SaaS tools for privacy compliance, governance, and document protection to reduce manual compliance work. - **Cloud platform users** (primary) — Use cloud-native tools to manage data protection across public cloud environments. - **Software partners and OEMs** (secondary) — Integrate FMY APIs and microservices into third-party applications and partner solutions. - **Organizations subject to privacy regulation** (primary) — Adopt products to address GDPR, CCPA, LGPD and similar data rights requirements. - Enterprise organizations needing privacy compliance automation - Cloud customers managing data protection and governance - Data controllers handling deletion and access requests - Software partners integrating privacy APIs and microservices - OEMs seeking embedded compliance functionality ## Geography Oculus is headquartered in Vancouver, British Columbia, and its disclosures describe a Canadian-based company with a U.S. operating and reporting footprint. Its target market is global, with products positioned for privacy and data-protection regimes in North America, Europe, Latin America, and other jurisdictions. The business is therefore exposed to cross-border regulatory adoption and cloud-market demand rather than a single domestic market. - Headquartered in Vancouver, British Columbia, Canada - U.S.-listed and reporting through SEC filings - Products designed for global privacy regimes - Targets customers in North America, Europe, and Latin America - Regulatory scope includes GDPR, CCPA, LGPD and similar laws ## Strategy The company is focused on building and commercializing a suite of privacy and data-protection products around its proprietary watermarking and cloud software capabilities. Near-term priorities include proving product-market fit, adding database connectors and API integrations, and positioning the platform for recurring sales and support revenue. It is also seeking recognition for its differentiated compliance and authentication tools in enterprise cloud environments. - **Commercialize core privacy SaaS products** (short-term) — The business needs repeatable enterprise use cases to convert development work into revenue. - **Expand integrations and connectors** (medium-term) — Broader database and software connectivity increases product utility and adoption. - **Position cloud-native compliance tools** (medium-term) — AWS and enterprise cloud workflows are a natural channel for automated governance software. - Commercialize privacy and data-protection SaaS products - Expand FMY with DBaaS connectors and API microservices - Demonstrate ComplyTrust in AWS-based enterprise workflows - Build recurring sales and support revenue streams - Differentiate through watermarking and tamper-proofing technology ## Risks The company faces execution risk typical of development-stage software businesses, including product validation, customer adoption, and the need to fund ongoing development. Its products also depend on evolving privacy regulations and enterprise cloud adoption, so changes in law, customer behavior, or competitive offerings can affect demand. As a smaller reporting company with limited disclosed operating history, it also carries financing and commercialization risk. - **Commercialization and adoption risk** [high] — The company is still building and proving its privacy and data-protection products in the market. - **Regulatory dependence** [high] — Demand is tied to privacy laws such as GDPR, CCPA, LGPD and similar regimes. - **Financing and liquidity risk** [high] — Development-stage software businesses often require ongoing external funding before scale is reached. - **Competitive pressure** [medium] — Enterprise privacy and security software markets include larger vendors with broader platforms. - Development-stage execution risk and uncertain commercialization - Dependence on privacy regulation adoption and enforcement - Competition from larger compliance and security software vendors - Funding risk for product development and working capital - Customer adoption risk for new SaaS and API products ## Accounting The company appears to be in an early commercialization phase, so revenue recognition, capitalization of development-related costs, and the valuation of any intangible assets are key areas to watch. With limited or no sales disclosed in the excerpts, period-to-period results may be dominated by operating expenses and judgmental estimates rather than recurring revenue. Investors should also monitor whether any acquired or internally developed technology requires impairment testing or other fair-value judgments. - **Revenue recognition** — Could affect reported revenue timing and deferred revenue balances - **Capitalized development costs and intangible assets** — Could affect amortization expense and impairment charges - **Impairment testing** — Could lead to non-cash write-downs - Revenue recognition is important if SaaS and licensing contracts expand - Development-stage spending may affect expense timing and capitalization - Intangible asset and technology impairment risk - Estimates and judgments may drive reported results more than revenue - Quarterly comparability may be limited by minimal sales activity --- *Last updated: 2026-04-29T04:42:25.697711+00:00*