Information you and your business provide
To set up and operate RevenuePack, we may collect a business name, website, owner or staff contact details, service area, hours, services, routing rules, call-forwarding status, greeting, voice and intake preferences, notification choices, and the RevenuePack phone number assigned to the account. We also collect corrections and outcomes that authorized users add to the opportunity record.
When you request a proof, we collect the website address you submit and information the site makes publicly available, such as business name, services, hours, service area, and public contact information. If you continue, we collect the details needed to configure and support the service.
Calls and service records
For calls routed to an approved RevenuePack line, we may process the caller's name, telephone number, service address, service need, urgency, appointment preference, and other information the caller chooses to provide. We also process call direction, dates, times, duration and connection status; recordings and transcripts when the approved setup permits them; AI-generated summaries; follow-up and notification history; and owner-confirmed opportunity outcomes. An appointment preference is a request, not a confirmed booking.
The participating business is responsible for approving its greeting, call notice, recording configuration, staff access, and routing rules, and for meeting consent and recording laws that apply to its callers. The service is not designed to collect payment-card details, passwords, government identification numbers, or sensitive medical information. Callers should not provide that information.
iOS app, account, and purchase information
The iOS app sends the information needed to create or restore a RevenuePack service account and to display that account's line, call records, transcripts, usage, and configuration. We process opaque mobile session identifiers and limited request information needed to authenticate the app, prevent abuse, and diagnose failures. Only a one-way hash of a mobile bearer token is stored in the service database.
For an App Store subscription, Apple sends us purchase and entitlement information such as product, transaction and original-transaction identifiers; an app-account token; purchase, expiration, revocation, renewal, grace-period, and environment status; and server-notification events. We use it to verify access, restore a purchase, prevent fraud, provide support, and keep subscription status current. RevenuePack does not receive your Apple Account password, full payment-card number, or App Store billing credentials. Apple processes the purchase under Apple's own privacy policy.
Support, partner, and website information
If you use support chat or the support form, we collect the question or message, contact details you choose to provide, related support replies, cited help articles, delivery status, and limited technical data used for security and abuse prevention. Network addresses used for public chat limits are stored as purpose-specific keyed hashes rather than raw addresses.
If you apply to or participate in the Partner Program, we collect your application, contact and audience information, acceptance of program terms, referral activity, attributed checkout events, commission and payout records, and information needed for payment and tax reporting. Referral visits are recorded with a purpose-specific keyed network-address hash rather than the raw address. A signed, HTTP-only attribution cookie may remain for up to 90 days.
On the public website, we record the page path, referring host, and a coarse source category for first-party traffic measurement. The iOS app does not include the website page-view beacon.
How we use information
We use information to prepare requested proofs; create and secure accounts; verify subscriptions; configure phone lines and approved call flows; answer and analyze authorized calls; deliver caller records, alerts, and support; show usage and account history; process exports and deletion requests; investigate faults and abuse; and meet accounting and legal obligations. We keep estimated opportunity value separate from outcomes the owner confirms. We do not sell personal information or use customer call content for third-party advertising.
Partner information is also used to review applications, operate referral attribution, prevent fraud, calculate and pay commission, communicate program changes, and meet accounting and tax obligations. Partner dashboards show aggregate funnel and commission outcomes, not referred buyers' contact information or customer call data.
Service providers and disclosures
We disclose only the information needed for a provider to perform an authorized function. These providers include Apple for App Store purchases and subscription events; Retell and its telephony infrastructure for phone numbers, call transport, recording, transcription, and voice automation; hosting and database providers; email and notification delivery services; Stripe for website checkout; and professional advisers or authorities when legally required. We require providers processing information on our behalf to protect it consistently with this notice and applicable law.
The public support guide may send your question, a short recent support history, and selected published RevenuePack help articles to Anthropic to generate a grounded answer. It is deliberately not given payment-card data, portal credentials, full call recordings, prospect website snapshots, or internal operating documents. Do not enter passwords, card numbers, portal links, or private caller information into public support chat.
We may disclose information to comply with law, protect callers or the service, investigate fraud or abuse, or complete a corporate transaction subject to appropriate confidentiality and notice. We do not give an unrelated business its own right to use customer call data.
Retention
Account profile, configuration, provisioned-line, call, recording, transcript, lead, appointment, and usage records are retained while the account is active because they form the service ledger. Retell is configured to retain its service-side call data for no more than 90 days; RevenuePack's authenticated ledger may retain its own copy until the account is deleted. Mobile sessions remain only until they expire or are revoked. The Partner Program attribution cookie expires after no more than 90 days.
After account deletion, we retain only limited records reasonably required for tax, accounting, fraud prevention, dispute resolution, security, and proof that the request was honored. Those records may include minimal StoreKit transaction and deletion identifiers, without the deleted service content. Support, payment, audit, and legal records are retained only for their applicable operational or legal period. Proof material that never becomes an account is removed when it is no longer needed for the requested proof, security, or dispute prevention.
Isolated backup copies age out under the normal backup-retention cycle and are not returned to the live service except for disaster recovery. Deletion from those isolated copies is not instantaneous. They remain access-controlled, are not used to provide the ordinary live service, and are removed through that retention cycle. We use administrative and technical safeguards designed for the sensitivity of the information, but no system can promise absolute security.
Export and account deletion
An authenticated iOS user can request a portable account export from Settings. The export includes the business profile, agent configuration, provisioned number, calls, leads, transcripts, appointments, usage, and subscription metadata associated with that account, but not provider secrets or internal security credentials.
An authenticated user can also initiate deletion of the entire account in Settings. We revoke its mobile sessions immediately and begin removing or anonymizing its service profile and customer call, lead, appointment, deployment, and line data. We aim to complete active-system and provider cleanup within 30 days. The app securely keeps the deletion receipt needed to check completion status after the account session is revoked. A delay may be required where law requires retention or a verified dispute or security investigation is open.
Deleting a RevenuePack account does not cancel an App Store subscription. Apple controls that billing relationship. Cancel first through Apple's Manage Subscriptions page if you do not want it to renew, then complete account deletion in the app. A deleted account is not silently recreated by a later Apple subscription notification; restoring service requires an explicit purchase-restore action.
Your choices and rights
You may use the in-app controls above or ask us for access, correction, export, or deletion. You can change notification permission in iOS Settings and ask RevenuePack support to change an approved call notice or recording configuration. Applicable privacy rights and appeal procedures vary by location. We may need to verify that the requester is authorized for the business account before disclosing or changing its information.
Controller and contact
AMF LLC operates RevenuePack and is the controller. Privacy requests can be sent to privacy@revenuepack.com or mailed to AMF LLC, 112 E B St, Wilkinson, IN 46186, United States. Product and account questions can be sent to support@revenuepack.com.
Changes to this notice
We will update the date above when this notice changes. If a material change affects an active account, we will provide additional notice when required.