Subprocessors

1. Growth Assistant — OpenAI

Growth Assistant is optional. When the user consents to data sharing and starts an analysis, the OpenAI API is used to produce a concise daily briefing and prioritized suggestions from business records. Opening a saved analysis alone does not start a new OpenAI analysis.

• Data shared: visit intervals, package usage, available appointment slots, appointment trends, staff workload, service amounts and, where available, period-based cost estimates for individual staff members. Known customer, staff and service names are replaced with codes before transmission. Stored phone numbers and email addresses, private notes and individual wage rates are excluded from the analysis input. Coding does not mean the data is fully anonymous.
• Ordiva storage: the last successful analysis, its date and a snapshot of its supporting records are stored in the database by business, account owner and language. This snapshot may contain customer and staff names. A new successful analysis replaces the previous record for the same scope; without a new analysis, the record is retained without automatic expiry. When account deletion is completed, the associated saved analyses are also deleted. Business ownership and plan access are checked when it is accessed.
• OpenAI processing: API data is not used for model training by default. store:false does not guarantee zero retention. Provider abuse-monitoring logs may be retained for up to 30 days by default, or longer for legal or security requirements. Processing may occur abroad.
• User control: this feature does not offer free-text questions or chat. Suggestions and any message drafts are presented for user review; the assistant does not automatically send messages or change appointment or staff records. The business checks the necessary permissions before contacting customers.

2. Mobile subscriptions — RevenueCat

Ordiva uses RevenueCat to verify Google Play and App Store subscriptions, restore purchases, manage plan access and provide subscription analytics. This involves your Ordiva account ID, your account email address where available, store transaction and purchase records, product/plan identifiers, and subscription status and dates. Your full payment card number or security code is not sent to Ordiva or to RevenueCat through this integration; the relevant store processes store payments. Before account deletion is completed, deletion of the associated RevenueCat customer record is also requested. The stores have their own transaction records and retention obligations.

3. Mobile notifications — Expo and platform providers

When you enable mobile notifications, delivery uses Expo Push Service together with Firebase Cloud Messaging (Google) on Android or Apple Push Notification service on iOS. Device/app installation identifiers, push tokens, app/project and platform information may be processed, together with notification titles, content and navigation data when a notification is sent. The notification token is linked to your account. You can disable notifications in Ordiva settings or device permissions while keeping your Ordiva account. Notification records and necessary delivery information are processed to operate the service and investigate issues.

4. App updates — Expo EAS Update

When the Ordiva mobile app starts, it checks Expo EAS Update for compatible software updates. These requests transmit a randomly generated app installation identifier, app/project and version information, and operating system information; the IP address may also be processed as part of the network request. This data is used to deliver the correct update, measure distribution and operate the update service. Update checks are independent of notification permission; disabling notifications does not stop this technical request.

5. Scope

Subprocessors are technical vendors that provide hosting, database, email, security, error monitoring, support, or integration services on behalf of Ordiva. The list is updated according to production usage.

6. Hosting and infrastructure

Render or similar cloud infrastructure providers may be used for application servers, API, static web deployment, and runtime logs. Data categories may include account, business, appointment, customer, and technical log data.

7. Database and storage

Managed PostgreSQL and related storage services may be used to store appointment, customer, business, staff, package, finance, and consent records.

8. Email and notifications

Resend or similar email services may be used to send verification, appointment, support, reminder, system, and permitted marketing messages.

9. Integrations and auxiliary services

Cloudflare DNS/security/email routing, Google Maps, Google Calendar, AI insight services, analytics, error monitoring, and support tools may process limited technical data when the relevant feature is enabled.

10. Changes

When a new subprocessor is added or a material change occurs in the nature of processing, this page is updated. Businesses should reflect such changes in their own notices where they act as data controller for their customers.