Business Revenue Recovery

PRIVACY

Privacy Policy

Effective date: September 24, 2026 · Version 2026-09-24

How to read this policy

This page describes what information Revenue Recovery AI processes, why, who else sees it, and what you can do about it. The prose under each heading is the policy. Boxes marked In plain terms are explanations added so the policy is actually readable; they are explanatory only, the operative wording governs where the two appear to differ, and nothing in an explanation creates or removes a commitment.

Questions this page answers

If the answer you need is not on this page, ask rather than assuming. A policy that is silent on something is silent, not permissive.

Who operates the service

Business Revenue Recovery operates Revenue Recovery AI, software designed to help businesses review authorized financial and commercial records for potential revenue leakage, receivables, refunds, credits, and other recovery opportunities.

Privacy questions may be sent to hello@businessrevenuerecovery.com.

Information we may process

Depending on how the service is used, information may include account and business contact information; customer, vendor, and counterparty contact information; invoices; contracts; accounting exports; payment information contained in business records; extracted fields; analysis results; AI-generated reasoning; findings; recovery cases; recovery actions; follow-up records; invoice and document drafts; email and message drafts; communication recipients and send metadata; reply or thread metadata; message content; delivery events; product feedback; privacy/data requests; subscription status; access-control records; and security or audit events.

Source-document lifecycle

Customers should upload only information they are authorized to provide and only information reasonably necessary for the revenue review.

Source documents submitted for analysis are processed through temporary application storage. The production configuration is designed to use ephemeral temporary storage rather than the application's persistent data disk for new uploads.

After processing completes or fails, the application attempts to remove the temporary source file. The saved Analysis Record does not intentionally retain the original source-file path as the authoritative source document.

Derived information can remain in the service, including extracted fields, findings, recovery records, document hashes, AI-generated reasoning, and user-created drafts, until removed under supported controls or applicable retention processes.

Invoice and document drafts

When a user creates or saves an invoice or commercial-document draft, Revenue Recovery AI may process information from the related business workspace, including customer or vendor identity, contact details, amounts, dates, source-document references, recovery-case information, notes, and user edits.

Draft fields may be marked as unconfirmed when source information is missing or ambiguous. Users are responsible for verifying drafts before use. Revenue Recovery AI is not intended to replace the customer's authoritative accounting or invoicing system.

AI-assisted email and message drafts

Revenue Recovery AI may use authorized workspace information to prepare editable communication drafts. Draft generation does not itself send a message.

If a user chooses to save a draft, the service may retain the recipient, subject, body, case association, editing history or status, and related metadata needed to display and manage that draft, depending on the implemented feature.

Outbound communications

Where an outbound communications feature is enabled, a communications provider may receive the confirmed recipient address, sender information, message subject and body, message identifiers, attachments or links selected by the user, and delivery-related metadata needed to transmit and operate the communication.

Outbound customer or vendor communications are intended to require an explicit human review and send action. Business Revenue Recovery does not use the existence of an AI draft as consent to contact a recipient.

Inbound replies and response monitoring

Where reply monitoring is enabled, the service may receive and process inbound sender and recipient information, reply content, provider message identifiers, thread identifiers, parent-message references, timestamps, delivery or bounce events, and other provider metadata needed to associate a response with the correct tenant and recovery case.

Revenue Recovery AI may surface whether a response is awaiting review, unresolved, or otherwise associated with a case. An inbound message does not by itself prove that an amount is owed, paid, disputed, refunded, credited, or resolved.

The service is designed to correlate replies using tenant-scoped and provider-supplied identifiers rather than relying only on free-form subject lines. Duplicate or mismatched provider events may be rejected or ignored to reduce cross-thread and cross-tenant errors.

Customer and vendor contact information

Customers are responsible for providing or importing contact information they are authorized to use. The service may process customer, vendor, or counterparty names, business names, email addresses, telephone numbers, mailing addresses, account references, and related relationship information when needed for an authorized workflow.

Customers should avoid entering unnecessary sensitive personal information into invoice or communication drafts.

AI processing

Revenue Recovery AI uses OpenAI's API for certain AI-assisted reasoning and generation features. For most features the application sends structured information needed for the requested function rather than attaching a customer's original source file.

Smart upload is different. When you use smart upload, the full text read from each PDF you upload is sent to OpenAI so it can propose the values to review. The PDF file itself is not sent; its text is. Nothing becomes evidence until you confirm it, and you can always enter the details manually instead.

Information sent for AI processing may include the text read from a PDF you upload with smart upload, filenames, extracted invoice or contract fields, financial amounts, findings, accounting-record data, draft context, and other information needed to perform the requested analysis or generation task.

OpenAI states that API Platform business data is not used to train its models by default unless the API customer explicitly opts in. OpenAI also states that standard API inputs and outputs may be retained for service operation and abuse monitoring for up to 30 days by default, and may be kept longer where the law requires it or where it is reasonably necessary to protect the service or others from harm, unless a different eligible retention configuration applies. Business Revenue Recovery does not currently represent its OpenAI configuration as Zero Data Retention.

Application-state storage and abuse-monitoring retention are different things. Application-state storage is what the Responses API keeps so a request can be retrieved afterwards. Abuse-monitoring retention is a separate safety process. Revenue Recovery AI now sends every AI request with application-state storage disabled (store=false), so the provider is asked not to retain that state. Where a request cannot be sent that way, the feature reports that it is temporarily unavailable instead of sending it with storage enabled.

That change does not amount to Zero Data Retention, and this page does not claim it does. Disabling application-state storage does not disable standard abuse-monitoring retention. Zero Data Retention and Modified Abuse Monitoring are separate approved account or project configurations with endpoint limitations, and Business Revenue Recovery continues to make no representation that either is enabled.

Source: OpenAI API data-controls documentation, developers.openai.com/api/docs/guides/your-data. The provider statements above were verified against that page on 2026-09-24 and recorded in our internal change log. Provider policies change; this page states a verification date rather than implying continuous monitoring.

Service providers

Revenue Recovery AI currently relies on providers for specific operational purposes, which may include:

Providers receive information needed to perform their particular function. Provider systems can retain operational information according to their own contracts, security practices, and legal obligations.

Hosting and data location

The primary Revenue Recovery AI web service is configured in Render's Virginia region in the United States. The service uses a Render persistent disk for the application database and application-created database backups.

Third-party providers may process information in other locations according to their infrastructure, contracts, and applicable law.

Security controls

Application controls include authenticated access, business-level tenant separation, Owner, Operator, and Viewer roles, email verification, optional login verification, CSRF protection for state-changing browser requests, security headers, audit events, and human-approval controls for recovery actions.

Communications and response-monitoring features are designed to use tenant-scoped case relationships, explicit recipient confirmation, provider message/thread identifiers, duplicate-event handling, and human review rather than automatically trusting an inbound message or free-form subject line.

These are application controls implemented by Revenue Recovery AI. They are not a representation that Revenue Recovery AI itself has completed an independent SOC 2, ISO 27001, or similar certification or audit.

Additional technical details are available on the Security & Data Practices page.

Privacy and data requests

Signed-in customers can use supported Data & Privacy controls in Revenue Recovery AI to submit an Access, Export, Correction, Deletion, or Other privacy/data request.

Before the application accepts certain privacy requests, the signed-in account may be required to have a currently verified email address or verified phone number. Requests are associated with the authenticated user and business.

Customers can view the status and customer-visible response for requests submitted by their own signed-in account. Other users in the same business do not receive that request history merely because they share the workspace.

Authorized system-level administrators may review and update privacy requests for operational fulfillment. Customer-visible responses are stored separately from internal review notes. Internal privacy-request review notes are not included in the customer JSON data export.

The in-application request workflow is an operational process for handling customer requests. It does not define, expand, or limit rights or obligations that may apply under applicable law or contract.

Deleting an individual analysis

A business Owner can use supported controls to permanently delete an analysis from active application storage after required confirmation. Associated findings, recovery cases, actions, follow-ups, and related data may also be removed according to the application's implemented deletion behavior.

Limited audit information recording that a deletion occurred may remain when reasonably necessary for security, integrity, or operational purposes and when allowed by applicable policy or law.

Deleting a business workspace

A business Owner can request deletion of the business workspace from active application storage through supported controls. The control may require current-password verification and explicit confirmation.

Workspace deletion is designed to remove active business data including users, analyses, findings, recovery records, integration imports, saved drafts and communication records maintained as workspace data, product feedback, privacy-request records, business audit events, and applicable account-security records, subject to technical, legal, billing, security, and backup limitations.

Limited security, fraud-prevention, billing-provider, communications-provider, or operational records that are not maintained as ordinary business workspace records may be retained when reasonably necessary for security, reconciliation, legal obligations, abuse prevention, or dispute handling.

Subscription cancellation is not data deletion

Canceling a subscription does not automatically delete business records. This separation prevents a billing change from unexpectedly destroying customer data.

Backups and deletion timing

Revenue Recovery AI creates application-level SQLite database backups for recovery purposes. The current application policy is configured to prune backup files when they become older than 14 days when the backup cycle runs, while also maintaining a separate backup-count limit.

Information removed from active storage can therefore remain temporarily inside an application-created backup until that backup ages out.

Render also creates provider-managed snapshots of its persistent disks once every 24 hours. Render states that persistent disks and their snapshots are encrypted at rest and that snapshots are available for at least seven days. Because Render describes that period as "at least" seven days, Business Revenue Recovery does not promise that every provider-managed snapshot is erased within a seven-day maximum.

Payments and billing

Stripe processes subscription payments. Revenue Recovery AI may receive billing-related identifiers, subscription state, price information, cancellation state, and payment status needed to operate paid access. Full payment-card credentials are handled by the payment provider rather than intentionally stored in the Revenue Recovery AI application database.

Account communications

Twilio Verify may receive an email address or telephone number and verification-related information when account verification is requested. SendGrid may receive recipient addresses and transactional email content when Revenue Recovery AI sends supported password-reset, team-invitation, or other enabled messages.

Retention of drafts and communications

Saved invoice drafts, email drafts, sent-message metadata, and inbound-reply information may remain associated with the business workspace while needed for the requested workflow, auditability, dispute handling, or supported retention practices. Exact retention can depend on the feature, deletion controls, provider retention, backups, legal obligations, and security needs.

Customers should maintain their authoritative accounting, invoicing, and correspondence records outside Revenue Recovery AI and should not rely on the service as their only archive.

Product feedback

If you submit product feedback, Revenue Recovery AI may store the rating, comments, account association, business association, and submission time to evaluate and improve the service. Feedback is not automatically published as a testimonial.

Customer responsibility and data minimization

Customers are responsible for ensuring they have authority to upload, import, process, and communicate using business records and contact information through the service. Sensitive information that is unnecessary for revenue analysis or communications should not be uploaded or included in drafts.

Revenue Recovery AI is not intended to replace the customer's original accounting, invoicing, contract, email, or recordkeeping systems.

Service discontinuation

If the service is discontinued, Business Revenue Recovery will use reasonable efforts, where practicable, to notify active customers and provide an opportunity to request deletion or export of supported active workspace data before shutdown. Customers should not rely on Revenue Recovery AI as their only copy of business records.

What this policy does not permit

A privacy policy that only lists permitted processing invites the reading that anything unmentioned is permitted too. These are things Revenue Recovery AI does not do. They are stated here as a description of current practice rather than as new commitments. Where a practice would change, this page changes with it and the effective date moves.

Changes to this policy

This policy may be updated as the product, providers, data practices, or legal requirements change. The effective date and version shown above will be updated when the policy changes.

Contact

Existing customers can submit privacy and data requests through supported authenticated Data & Privacy controls in Revenue Recovery AI. General privacy, data-deletion, or security questions can also be sent to hello@businessrevenuerecovery.com.

Please do not send unnecessary invoices, contracts, authentication credentials, or other sensitive customer records by ordinary email when a request can be identified without them.