Third-Party Services Register
OneCoreHive believes customers should understand not only how our products work, but also which trusted third-party services may support their operation. This register provides a transparent overview of external providers that may be used across the OneCoreHive ecosystem.
Third-party services are selected based on their security, reliability, operational maturity and ability to support our commitment to privacy and responsible software development.
The use of a third-party service depends on the specific product, deployment model and features enabled by the customer. Not every product relies on every provider listed below.
Our Selection Principles
Before integrating a third-party service, we evaluate it against several criteria:
- security and privacy practices;
- service reliability and availability;
- regulatory compliance;
- technical maturity;
- long-term sustainability;
- operational necessity;
- vendor reputation;
- customer impact.
Where practical, we minimize external dependencies and favor local processing to reduce unnecessary data exposure.
Current Third-Party Services
| Provider | Purpose | Customer Data Processed | Status |
|---|---|---|---|
| Google Play | Android application distribution and updates | Limited account and download information managed by Google | Active |
| Apple App Store | iOS application distribution | Limited account information managed by Apple | Planned |
| Supabase | Authentication, database, optional cloud synchronization | Account and application data, depending on product configuration | Active |
| Google Firebase | Push notifications, analytics and crash reporting (where enabled) | Limited technical diagnostics and notification identifiers | Optional |
| Cloudflare | DNS, CDN, DDoS protection and website performance | Network metadata necessary to deliver web services | Planned |
| GitHub | Source code management and version control | Internal development data only | Active |
| Stripe | Subscription billing and payment processing | Payment information processed directly by Stripe | Planned |
Infrastructure Philosophy
OneCoreHive is designed with an Offline-First architecture whenever technically feasible. This approach allows many product functions to operate entirely on customer-controlled devices without requiring continuous communication with external services.
Cloud services are introduced only when they provide a clear operational benefit, such as:
- secure account synchronization;
- software licensing;
- encrypted backups;
- collaboration features;
- product updates.
Data Sharing
OneCoreHive does not sell customer data to third parties.
We do not share personal information with external providers for advertising or marketing purposes.
Where third-party services are required to deliver functionality, only the minimum information necessary for that service is processed.
Customer Choice
Whenever possible, organizations can choose whether to enable optional third-party integrations. Examples may include:
- cloud synchronization;
- push notifications;
- diagnostic reporting;
- analytics features.
Optional services can typically be disabled without affecting core functionality.
Security Review
Third-party providers are periodically reviewed to assess:
- security posture;
- operational reliability;
- service continuity;
- contractual commitments;
- relevance to OneCoreHive products.
Providers that no longer meet our standards may be replaced or removed.
Subprocessors
Where OneCoreHive acts as a Data Processor on behalf of customers, applicable subprocessors are identified in the relevant Data Processing Agreement (DPA) and associated documentation.
Customers requiring additional contractual information may contact us using the details below.
Service Availability
Third-party providers operate independently of OneCoreHive. Temporary interruptions or outages affecting external providers may impact specific features that rely on those services.
Where practical, OneCoreHive designs products to minimize dependency on any single external provider.
Future Providers
As the OneCoreHive ecosystem evolves, additional providers may be introduced to support new capabilities, including:
- enterprise identity providers;
- cloud hosting platforms;
- payment gateways;
- communication services;
- AI infrastructure;
- monitoring and observability tools.
All new providers undergo the same evaluation process before integration.
Change Management
This register is reviewed whenever:
- a new third-party service is introduced;
- an existing provider is replaced;
- the purpose of an integration changes;
- significant security or compliance updates occur.
Material changes will be reflected in the latest published version of this register.
Contact
For questions regarding third-party services, subprocessors or data processing practices, please contact:
- Generalcontact@onecorehive.com
- Privacyprivacy@onecorehive.com
- Securitysecurity@onecorehive.com
Every external dependency is a trust decision.
OneCoreHive carefully evaluates each third-party service before integration, striving to minimize external dependencies while ensuring that our products remain secure, reliable and transparent. We are committed to informing our customers about the services that support our ecosystem and the role they play in delivering our products.