Orchardist

Privacy Policy

Effective date: October 25, 2026

On this page
  1. 1. Connecting to Apple and storing data on your device
  2. 2. Information processed by the notification relay
  3. 3. Optional notification forwarding
  4. 4. Purchases, exchange rates, icons, and support
  5. 5. Service providers and this website
  6. 6. Reasons for processing and international processing
  7. 7. Retention
  8. 8. Your choices, deletion, and other rights
  9. 9. Security, children, and changes

Orchardist is provided by 伟贺 信 (XINWEIHE). This policy explains how we handle information in the Orchardist app, widgets, notification extension, notification relay, official website, and support service. For privacy questions or requests about your personal information, contact hi@mytesla.cc.

Orchardist helps developers understand their App Store business. Your device obtains most reports directly from Apple and stores them locally. Live notifications use a relay hosted on Cloudflare, which processes notification content and stores the device and notification settings needed to provide that service. Orchardist does not require an email and password account, but its notification service uses persistent random device and channel identifiers.

1. Connecting to Apple and storing data on your device

When connecting, you choose to import or paste an App Store Connect private key and provide the corresponding Key ID, Issuer ID, and Vendor Number. You may also provide an In-App Purchase key to query transaction information, subscription status, and notification history available from Apple. Private keys and their related key identifiers are stored in the system Keychain. Your device uses the private keys to sign authorization tokens and contact Apple directly. Orchardist does not upload these Apple API private keys to our notification relay, and we do not ask for your Apple Account password.

Information obtained from Apple may include app and product details, sales and proceeds, downloads, refunds, subscription events, transaction identifiers, purchase and expiration dates, territories, and customer reviews, including reviewer names, ratings, titles, text, and responses. The app uses this information for display, filtering, calculations, offline access, and the management actions you choose, and caches it on your device.

When you submit or delete a review response, the response and relevant review identifier are sent directly to Apple. Codes, offer batches, and local distribution records are stored on your device. If you copy, export, or share information, the recipients you choose handle it under their own terms. Check for customer or business information before sharing.

Widgets and the notification extension share some local information with the main app, such as notification events, app and product names, display snapshots, exchange rates, and preferences. Lock Screen notifications and widgets may display business details or amounts. You can adjust the app's amount visibility settings and the system's notification display settings.

Apple may back up device data according to your system settings. When you enable configuration sync, your App Store Connect and In-App Purchase keys, notification channel, and related settings sync through iCloud Keychain so you can use the same configuration across your devices. System backups and device migration may also affect copies of your data. Uninstalling the app does not remove every Keychain item, backup, or server record.

2. Information processed by the notification relay

When registering a device, the app sends random device and channel identifiers, a push token, an optional widget push token, the device's encryption public key, notification category preferences, quiet hours and time zone, and language and region settings. We also store creation or update times, a digest used to verify access to the channel, and a mapping of product identifiers to standard subscription periods. These details let us identify receiving devices, authenticate requests, select notification delivery modes, and classify events.

After you configure an Orchardist notification URL in App Store Connect, Apple sends signed notifications to the relay. The relay verifies and parses them. It may process notification types and times, app and product identifiers, transaction and original transaction identifiers, prices and currencies, storefronts, purchase and expiration dates, refund, offer, Family Sharing and renewal information, and an appAccountToken supplied by your app. Transaction identifiers and appAccountToken values may relate to your app's customers and are not inherently anonymous.

Before sending an event to a device, the relay encrypts its content using that device's public key and delivers it through Apple Push Notification service (APNs). The relay can process Apple's notification content before encryption. APNs still handles information needed for delivery, including push tokens, delivery metadata, event categories, and fallback notification text. The device decrypts the event and generates the notification or updates local data.

3. Optional notification forwarding

Forwarding is optional. When you enable it and save a destination, the relay sends Apple's original notification body to the HTTPS address you specify. That body may include the transaction information described above and other Apple notification fields that the app does not display. We store the destination address to carry out forwarding.

Only select a recipient you are authorized to use, and review its purposes and privacy practices. You can turn forwarding off and confirm that the app reports the change as saved on the server. Clearing local data, uninstalling the app, or disabling system notifications does not automatically turn off a saved forwarding destination.

4. Purchases, exchange rates, icons, and support

Orchardist Pro purchases. Purchases and restoration use Apple StoreKit. The app uses purchase and entitlement status to unlock features. We do not receive your payment card number or Apple Account password. Apple handles payments and purchase records under its own terms.

Exchange rates and icons. To estimate currency conversions, your device requests public exchange rates from ExchangeRate-API. The request does not include your Apple API keys or business reports. To display app icons, your device sends an app identifier to Apple and downloads the image returned by Apple. These services receive information needed for the network request, such as an IP address and request metadata.

Support. If you email us, we receive your email address, message, and any attachments you choose to send. We use them to respond, investigate a problem, or handle a rights request. Please do not send private keys, notification channel credentials, Apple Account passwords, full notification URLs, or unredacted customer transaction information. We may ask for the minimum additional information needed to address your request.

5. Service providers and this website

Recipient or servicePurpose and information
AppleApp Store Connect and App Store Server API requests, purchases and restoration, push delivery, icon requests, and Keychain synchronization or backups controlled by system settings. See Apple's Privacy Policy.
CloudflareHosting the notification relay, storing necessary notification settings, and delivering this website. Cloudflare processes requests, notification content, and network and operational logs to provide the service, troubleshoot, and prevent abuse. See Cloudflare's Privacy Policy.
ExchangeRate-API, operated by AYR Tech (Pty) LtdProviding public exchange rates and receiving rate queries and connection metadata. See its Terms and Privacy Policy.
Your chosen forwarding recipientReceiving Apple's original notifications only when you enable forwarding. The recipient is determined by the destination you save.

This website serves static pages. It does not embed advertising, visitor analytics, or third-party fonts, and it does not set marketing or analytics cookies. Cloudflare may still process IP addresses, requested URLs, timestamps, browser or client information, response results, and other metadata for delivery and security, and may use security cookies where needed.

The app does not integrate advertising or cross-app tracking tools. We do not sell personal information or use notification and report content for advertising profiles. Necessary operational logging and the functional processing described above still occur. Service logs may contain request paths, times, statuses, event categories, delivery results, and error information. Network providers also process metadata required for operation and security.

6. Reasons for processing and international processing

Under applicable law, we process necessary information to provide features you request, respond to support requests, protect the service, and meet legal obligations. Where processing requires consent, we rely on valid consent. You can withdraw consent or stop the relevant feature as described below. Withdrawal does not affect processing that was lawful before withdrawal. A feature may no longer be available if the information is necessary to provide it.

Apple, Cloudflare, the exchange rate service, and your chosen forwarding recipient may process information outside your country or region. Processing locations depend on their service networks and recipient arrangements; you should not assume all data remains on your device or in mainland China. Where international processing requires additional notice, consent, or other safeguards under applicable law, we will meet those requirements. This policy and acceptance of our Terms do not replace any separately required consent.

The developer data you connect may include information about your customers. You should have authority to enable the relevant processing and meet applicable notice and authorization requirements for your customers. We process this information for the features you enable and remain responsible for our own applicable protection and assistance obligations. Your customers may also contact us about privacy concerns. Following necessary verification, we will coordinate with the relevant developer where appropriate.

7. Retention

Retention depends on the feature and applicable law. There is no single retention period for every category.

Apple, your forwarding recipients, and copies you export, share, or back up are governed by their respective arrangements. Clearing data in Orchardist cannot delete those copies on your behalf.

8. Your choices, deletion, and other rights

You can explore sample data before connecting, choose whether to import keys, use live notifications or enable forwarding, and change relevant settings. System notification controls affect presentation; they do not delete relay settings or stop Apple callbacks and forwarding you have already configured.

The app's “Clear Data” action removes downloaded business records and code caches, Apple API keys, and some local preferences. It also attempts to unregister the current device for push delivery; that attempt may fail without a network connection. It keeps the notification channel and related identity information. It does not delete other devices, server-side product settings, or forwarding destinations, or revoke API keys and notification callbacks in Apple's systems.

To stop the service and remove server-side settings, follow the Support page to disable forwarding, remove or change Apple's callback, revoke keys if needed, and email hi@mytesla.cc with your deletion request. We will verify your authority over the relevant device, channel, or developer data to avoid deleting someone else's information. Verification is limited to necessary information; we do not ask you to email private keys or secret credentials. We will handle the request within the periods required by applicable law and explain the outcome, including any reason we cannot fulfill it in full and available next steps.

Depending on applicable law, you may request access to, copies of, correction, completion, deletion, or transfer of personal information, withdraw consent, restrict or object to certain processing, and complain to a competent authority. The app's CSV export provides selected daily business totals, not a complete copy of all data. You can make other requests by email. Some information is independently managed by Apple or your chosen recipients, so you may also need to contact them.

9. Security, children, and changes

We use measures including HTTPS, system Keychain storage, signing on your device, device public-key encryption, access checks, and system file protection. Protect your device and developer account, and revoke compromised or unused keys promptly. No storage or transmission method guarantees absolute security. If a personal information security incident occurs, we will take remedial, notification, and reporting steps required by applicable law.

Orchardist is intended for developers authorized to manage apps, not children under 14, and we do not intentionally ask children to provide personal information. Contact support if you believe we have processed a child's information without the necessary authorization. Developers whose apps involve children must comply with the applicable protections for children's information.

We will update the effective date when this policy changes. We will give appropriate notice of material changes affecting processing purposes, data categories, recipients, or your rights, and obtain renewed consent where required by law.

Terms of Service · Contact Support · 简体中文