Privacy Policy

The product is InboundX. In this policy, “we” and “us” mean REOM LLC, a Wyoming LLC, 1712 Pioneer Avenue, Cheyenne, Wyoming, USA, the operator of InboundX.

General questions: hello@inboundx.io. Privacy requests: support@inboundx.io.

The InboundX app for ChatGPT is published by Tony Msonza for REOM LLC.

This policy covers two surfaces:

• The marketing site at inboundx.io.
• The product at app.inboundx.io, including workspaces, the buyer browser, the publisher portal, and call records.

Workspaces are separate. One customer’s buyers, publishers, and calls are not visible inside another customer’s workspace. Each workspace is sealed from the others at the database level.

Callers, buyers, and publishers usually deal with the operator’s brand: the operator’s subdomain, logo, and email. This policy still describes what the platform does with that data. Notices the operator gives those people are the operator’s responsibility.

If a workspace agreement says something more specific about data, that agreement controls for the product where the two conflict.

Marketing site. If you email us or message @inboundx on Telegram, we keep the message and the address it came from so we can reply. The marketing site loads Vercel Web Analytics to count page views. That tag does not run in development. We do not use it to build advertising profiles, and this site does not run an advertising tag manager. You do not create an account on the marketing site itself.

Workspace account. When an operator opens a workspace, we process the account and brand details they submit, such as name, email, company name, logo, colours, and subdomain, and the settings they change later. An audit log records changes and who made them, including when platform support acts on the operator’s behalf.

Calls. The product handles call metadata (who was routed, when, duration, and outcome), two-channel recordings, live and stored transcripts of both sides, summaries, qualification verdicts, and the words those verdicts used. Recordings are stored privately and kept for a year by default. The product does store transcripts. A buyer can read the live transcript during the call.

Pings and routing. Every publisher ping is kept with its answer and the reason, including the ones you turn down. Each buyer check is kept with the first check that failed, such as offline, outside hours, state not selected, or balance low.

Going online. Before a buyer takes calls, the product can run a device check for microphone, speaker, echo, and network, and can require a training course or a campaign compliance sheet. Those checks are part of the workspace the operator configured.

Billing. The operator’s plan uses a card. Minutes are billed from a prepaid call balance. Buyers top up through the operator’s own payment processor, and the platform does not hold that money. Buyers can be asked to sign a payment agreement under the operator’s brand before the first top-up. Identity checks are a switch the operator controls; when the switch is on, the product collects what that check requires. We keep ledger rows for charges, credits, and publisher earnings. This policy does not name the card processor for the operator’s plan, and it does not claim we store full card numbers for buyer top-ups.

Disputes. The recording, the transcript, and the decision are kept so the operator can resolve a charge inside the window they set.

• To run the platform: ping, reserve, ring, transcribe, qualify, and bill.
• To show each role only what that role is allowed to see.
• To keep recordings, transcripts, summaries, and a printable evidence pack.
• To operate wallets, the prepaid call balance, invoices, and dispute credits.
• To secure workspaces, investigate abuse, and keep the audit log.
• To answer support and sales mail.
• To count page views on the marketing site.
• To meet a legal duty that actually applies to an account.

We do not sell personal information. We do not use one customer’s calls to advertise another customer’s product.

The operator runs the network under their brand. They choose the campaigns, the qualification criteria, and what they tell their buyers, publishers, and callers.

InboundX provides the platform that stores and processes that workspace’s data in order to deliver the service. In privacy-law terms, the operator is often the party that decides why call data is collected, and InboundX processes it to provide the platform. Which legal role applies depends on the campaign and on the law that covers it. The workspace agreement is where that is confirmed.

Buyers and publishers are the operator’s users. They do not receive a separate InboundX workspace unless they are also operators.

• People inside the operator’s workspace, limited to what that role can see.
• The operator’s payment processor, for buyer top-ups the operator configures.
• Infrastructure providers that host the service, carry telephone calls, transcribe speech, and send email, and the provider that processes the operator’s plan payment.
• Vercel, for marketing-site page-view analytics.
• A court, regulator, or other authority when the law requires it.

We do not publish a named list of telephony, transcription, or hosting subprocessors on this page. That list stays off the page until it is confirmed, rather than being filled with guesses. We do not share one workspace’s calls with another customer.

InboundX does not claim SOC 2, HIPAA, or a similar certification on this site.

Recordings are kept for a year by default. Transcripts, ping logs, ledger rows, and the audit log are kept while the workspace is open and for as long as we need them to operate billing, disputes, security, and any legal duty that applies. A refund is a new ledger row, not an edit, so billing history is not rewritten.

When a workspace ends, we do not promise that every record disappears the same day. Recordings follow the one-year default unless we honor a deletion request or a longer hold is required for a dispute or a legal duty. You can ask what we still hold.

Email support@inboundx.io to ask for access, correction, or deletion, or to ask a privacy question. Name the workspace and the address you use there so we can find the record.

If you are a caller, a buyer, or a publisher, we may need to involve the operator of that workspace, because you dealt with their brand. We will say so if a record has to stay for a dispute, for security, or for a legal duty. This policy does not state a statutory response deadline, because it does not choose a jurisdiction.

The service may process data in countries other than where an operator, buyer, or caller is located. This page does not name those countries until hosting locations are confirmed for publication. The workspace agreement is where those terms belong once counsel confirms them.

InboundX is a business product. It is not directed at anyone under 18. Operators must not use it to knowingly collect personal data from children.

We post updates on this page and change the date above. If a change materially reduces what an operator can expect, we will also email the workspace address we have on file.

Privacy requests go to support@inboundx.io. Everything else goes to hello@inboundx.io. Postal address: REOM LLC, a Wyoming LLC, 1712 Pioneer Avenue, Cheyenne, Wyoming, USA. The Terms of Service sit beside this policy.