← Back to reception

Draft prepared 20 September 2026 · not yet effective

Terms of service

These proposed terms cover the Reception dashboard, ReceptionKit SDK, APIs and related in-app customer support services. They are intended for business customers and their authorised team members.

1. Who provides the service

Reception is the product name used in these documents. Operator legal name and registration: PLACEHOLDER. Business address and country: PLACEHOLDER. Legal/privacy email: PLACEHOLDER. Final product name and domain: PLACEHOLDER. The customer is the person or organisation identified in the accepted order or account agreement.

You must have authority to act for your organisation. These terms, the agreed order and the Data Processing Agreement govern the service; the DPA prevails for processing customer personal data. A separately signed order prevails for its specific commercial terms.

2. Your account and team

Keep account and billing details accurate and protect your sign-in, project credentials and integration secrets. Assign access only to authorised people, remove access when it is no longer needed and tell us promptly about suspected compromise. Organisation owners control team access and app configuration.

3. What the service does

Reception lets people contact your team within your app. Your team can manage conversations and user details, exchange screenshots, request App Store reviews and configure Apple Push or Telegram notifications and replies.

The service is not an emergency channel, a payment processor for your app’s users, or a guarantee of customer retention, sales, reviews or uninterrupted message delivery. Device settings, networks and third-party platforms affect delivery. Features marked coming soon, including AI integrations, are not part of the available service until released and agreed.

4. Customer content and permitted use

You retain your rights in the messages, images, app information and other material submitted by you or your users. You grant us the limited rights needed to store, transmit and display that material to provide the service and carry out your instructions. We retain rights in our software and service; third-party materials remain their owners’ property.

You are responsible for your apps, your instructions, the legality of your content and the notices or permissions required to collect and share personal data. Use the minimum data necessary. Do not submit passwords, full payment-card details or highly sensitive information that the service has not been agreed to handle.

  • Do not use the service for unlawful, abusive, deceptive or infringing activity, unsolicited messages or malware.
  • Do not bypass access controls, access another customer’s data, disrupt the service or test production security without permission.
  • Do not use review requests to mislead users or violate app-store rules. Any offers, refunds or discounts to your users remain your responsibility.

5. Fees and billing

The standard offer includes $1,000 of App Store revenue per organisation and billing period, then a fee of 0.5% of the amount above that allowance. We sum all covered apps and days before rounding the fee half up to US cents. Negative refund days reduce the total. Revenue means the customer price times units in Apple's daily App Store Connect sales reports for your connected apps and their in-app purchases, after refunds and before Apple's commission; where App Store prices include VAT, so does revenue. Refunds reduce revenue on the day Apple reports them. Each currency is converted to USD at the exchange rate we stored for that day; stored rates are not changed later. A negative billing period has a zero fee and does not create a revenue balance for later periods. Ads, Android, web checkout and sandbox sales are excluded.

Billing starts at the next UTC midnight after the first end-user message from one of your apps, including test messages during setup. Each app joins from the next UTC midnight after its own first message, also when it is connected later; we read the days needed by its unfinished billing periods, as far back as Apple keeps reports. Monthly anniversary periods retain their original anchor day, clamped in shorter months, and include the start but exclude the end. Apps added later join the running period. We finalize a period no earlier than three days after its end, once every day of it has been read; unavailable reports delay finalization. Fees under $1 carry forward until the combined balance reaches $1. A documented individual offer or approved temporary fee waiver continues according to its terms.

You must connect every production app using Reception to the App Store Connect account that sells it, with a key limited to the Sales and Reports role, and keep that access current. We may reasonably audit the underlying aggregate figures and request supporting records under confidentiality safeguards. Missing or incomplete data does not mean zero revenue. Once finalized, later report corrections for those dates do not increase or decrease the fee. Errors in our own calculation or application of these terms remain correctable.

Stripe stores payment methods and collects the agreed fees. Cancellation takes effect at the end of the running period; already incurred fees and carried balances remain due. Deleting support data does not erase required billing records. After an app's first message, you have 7 days to connect it. Other customer-fixable credential or payment issues have a 3-day remediation window. After the window, we may pause replies: messages from your end users keep arriving and remain readable, but replies, paywall/review actions, new apps and agent invitations are unavailable until the issue is resolved; billing, reconnection and deletion remain available. Outages at Apple do not start that window. Applicable service taxes, final operator details and the effective agreement date remain PLACEHOLDER pending legal review.

6. Data and connected services

The Privacy Policy explains our handling of account, security and billing information. The DPA governs personal data we handle on your behalf. You determine the lawful basis for collecting end-user support data and provide appropriate notices.

Enable third-party integrations only when authorised. Telegram recipients can receive message content and identifying details; push notifications may show reply text on a device’s lock screen. Third parties have their own terms and data practices. Disconnecting an integration stops future use but does not erase copies already delivered to it.

7. Availability and changes

We may maintain and improve the service and will give reasonable notice of material changes where practical. Unless a separate agreement says otherwise, no uptime or support-response service level is promised. We may take proportionate protective action without prior notice to address abuse, security threats or legal requirements, and explain the reason when permitted.

8. Ending the service

You may stop using the SDK and request account or workspace deletion through the available controls or the confirmed support contact. Ending billing and deleting data are separate actions. Fees already incurred remain payable; resolve ownership requirements shown by the service before deleting an account.

We may suspend or terminate access for a material breach, unpaid agreed fees or unlawful use. Where practicable, we will explain the issue and allow a reasonable opportunity to fix it. Arrange any required data return before deletion. Closing a conversation does not delete its messages. Deletion and return of customer personal data are governed by the DPA; legally required records may be retained separately.

9. Responsibility and liability

Each party remains responsible for its own breach of these terms and applicable law. Except for express commitments in an accepted agreement and warranties that cannot lawfully be excluded, the service is provided without additional guarantees of fitness for a particular purpose or error-free operation.

No provision excludes liability that cannot legally be excluded, including fraud or other mandatory protections. Any negotiated financial liability cap, indemnity or special service-level remedy must be set out in the accepted order; this draft does not silently impose one.

10. Notices, changes and disputes

We will make material changes available in advance through the service or the confirmed account contact, except where an urgent legal or security change is needed. We will obtain fresh acceptance where required. Changes do not retrospectively alter an agreed charge.

Notice email: PLACEHOLDER. Governing law and dispute forum: PLACEHOLDER, to be confirmed in the final agreement. Mandatory rights under applicable law remain unaffected. Contact details and the effective date will be published when this draft is finalised.