SSolarc Labs

App Store privacy information

Solarc Booking Companion Privacy Notice

Updated 11 September 2026. This notice covers the current Solarc Booking Companion iPhone app and its Today widget. It is separate from the privacy notice for the Solarc Labs website and other products.

Operator

SOLARC GOODS LIMITED · Company Registration No. 16998296 · England and Wales

Privacy and app-support contact: enoch@solarclabs.com

1. Merchant authentication and security metadata

The app requires an existing Solarclab Booking merchant account. When you sign in, the merchant identifier and passcode you provide are sent over HTTPS to the booking service for authentication. The iPhone app does not intentionally persist the merchant passcode after authentication.

The current service retains short-lived authentication-abuse and rate-limit state that combines the merchant/account identifier with caller network metadata such as IP address for the active 15-minute window. This is used for app functionality, authentication, security and abuse prevention, not advertising or cross-company tracking.

2. Booking data displayed on the iPhone

After authentication, the service can return booking information such as customer name, contact details, service, appointment time, timezone, booking reference and status. Those records already exist in the Solarclab Booking service and are downloaded so the merchant can view the operational schedule.

The current iPhone release is read-only for booking operations. It does not use the app to create payments or make the iPhone a separate booking system of record.

3. Local cache, widget and notifications

The app keeps a limited local cache so recent operational information can remain useful when the network is unavailable. The Today widget uses an App Group to share a deliberately reduced snapshot with the widget extension. Customer email and phone are not intended to be stored in the offline SwiftData cache, widget snapshot or local-notification payload.

Optional local reminders are scheduled through Apple platform notification APIs. You can deny or revoke notification permission without blocking the core booking-list workflow.

4. Data categories and tracking boundary

The current release does not intentionally include an advertising SDK, analytics SDK, session-replay SDK or cross-app tracking system. It does not request the advertising identifier and the app privacy manifest declares tracking as disabled.

App Store privacy disclosures for the shipping build include the account/user identifier and the security/network metadata retained for authentication and abuse prevention where Apple's collection definition applies. The exact App Store privacy answers are re-audited against the production service and release binary before publication.

5. System contact actions

When available, customer phone or email can be opened through Apple system contact actions such as the telephone or mail handler. Using those system actions does not by itself create Solarc advertising or analytics collection. The destination service or carrier applies its own terms and privacy practices.

6. Support, retention and deletion

If you contact Solarc for support, we receive the contact information and content you choose to send. Do not send merchant passcodes, payment-card data, API keys or real customer records unless genuinely necessary and authorised. Redact personal information where possible.

Local app data follows the app's operational lifecycle and device controls. Server-side booking records, authentication records and security state follow the retention rules of the Solarclab Booking service and applicable legal, accounting, security or contractual requirements.

7. Changes and questions

This notice must be reviewed before a release materially changes authentication, server collection, analytics, advertising, local caching, widget content or notification behavior. Questions or privacy requests can be sent to the contact above.