Website enquiries
Your contact details and business context help us understand your request and get back to you. The enquiry form sends your submitted answers to our CRM. Booking a meeting is a separate, optional step.
THE FORENSIC REVENUE TRUST CENTER
Clear about your data.
From the first conversation.
What you share with us depends on the work we do together. Here is how website enquiries, BuyerBuilt projects and Revenue Memory fit into that picture.
BuyerBuilt projects
We agree on the research, materials and business information needed for the project. Confidentiality, access and handling requirements form part of the engagement we define with you.
Revenue Memory
The current analysis workflow uses sales-call transcripts in text and agreed business context. Access to customer information belongs within the customer’s authorized workspace.
Your recordings stay with you.
We work with the text.
The Revenue Memory analysis workflow receives sales-call transcripts. The original audio and video stay in your recording platform.
Keep the recording where it belongs.
Revenue Memory does not need your audio or video files to analyze a conversation.
Share the words and the context.
The workflow uses the transcript, the business context you provide and the relevant account information.
Return to the evidence.
Your team reviews findings, quoted passages and patterns within its authorized customer workspace.
How access is protected.
Customer isolation
Postgres Row-Level Security uses the authenticated session to scope access to customer data.
Encryption at rest
The documented database configuration uses AES-256 encryption, with key management through AWS KMS.
Encryption in transit
The documented architecture uses TLS 1.2+ across application, database, pipeline and API connections, with HSTS enabled.
Server-side credentials
Integration credentials are held in a vault. Decryption is restricted to server processes.
Role-based access
Server-side permissions determine what managers and salespeople can access before information reaches the browser.
Security reviews
Written security reviews use the production database security advisors to identify issues and document the verification of fixes.
The details your team may need.
Open a topic to review the data, providers and commitments behind Revenue Memory.
What information is stored?
Transcripts: the text of meetings supplied by the customer. We treat this as the platform’s most sensitive class of data.
Derived intelligence: per-call briefs, findings with quoted passages, buyer signals, profiles and patterns across conversations.
Operational information: submitted salesperson and account names, platform users and organization metadata.
Customer screens present findings and quoted passages. The documented application and pipeline logging configuration uses internal identifiers without transcript content.
Which providers are involved, and where?
Database and authentication
Supabase, managed on AWS. The documented database region is AWS us-west-2, Oregon, United States.
Web application
Vercel, with a global edge network and functions in AWS regions.
AI analysis
Anthropic’s commercial Claude API, with processing in the United States.
Pipeline orchestration
A self-hosted instance with credential-based separation. The documented execution-log configuration excludes transcript content.
Our infrastructure providers publish their own security and compliance documentation. Those reports belong to the providers; they do not certify Forensic Revenue.
Provider documentation: Supabase · Vercel · Anthropic · AWS.
How is AI used, and does it train on our content?
Analysis uses Anthropic’s commercial API. Under its commercial data policy, inputs and outputs are not used for model training by default. Your content is used to produce intelligence for your account. We do not resell it or use it to supply another customer.
Findings stay connected to the conversation evidence. The product’s evidence standard is to compute counts, percentages and monetary values from the source data, and to show gaps when the available material cannot support a conclusion.
Revenue Memory keeps its intelligence on the server. The conversation interface consults that material and returns answers with quoted evidence from the available calls.
What are the privacy roles and contractual commitments?
Defined roles: for customer conversation data under Brazil’s LGPD, the customer is the controller and Forensic Revenue is the processor. We process it under documented instructions to generate commercial intelligence for the customer.
Data protection agreement: the published framework provides for a DPA with named subprocessors and the ANPD standard contractual clauses for international transfers, under Resolution CD/ANPD No. 19/2024.
Deletion: at the end of the contract, deletion upon request within 30 days, with written confirmation.
Individual rights: a process for access, correction and deletion requests, with FR supporting the controller within the contractual timeframe.
Incident notification: the contractual commitment is to notify the customer within 72 hours of a confirmed incident and provide a written report within 14 days.
Optional pseudonymization: the customer may replace names before submission. The mapping between original and replacement names remains exclusively with the customer.
These are the commitments in the published Revenue Memory framework. Your signed agreement defines the terms for your engagement.
Who is responsible for recording and sharing conversations?
The customer defines its recording program with its legal team, including the lawful basis, participant notices and permission to share transcripts. Applicable requirements depend on the context and jurisdiction.
In Brazil, the published technical reference cites the Supreme Federal Court’s Tema 237 concerning recording by a participant. This does not replace the customer’s assessment of data protection and other requirements for its specific use.
We recommend a clear recording notice at the beginning of the meeting. Revenue Memory receives the text transcript; the participant’s recorded voice stays outside the analysis workflow.
Need a procurement or security review?
A data protection agreement, subprocessor list, architecture details and answers to security questionnaires are available to customers and prospects evaluating the product. Tell us which documents your team needs.
Technical reference: July 19, 2026. Languages and presentation updated September 10, 2026. These dates do not represent a new security audit.
The details, in one place.
Privacy policy
Information we collect, how it is used and how to contact us about it.
Read the details ↗Data handling
Our approach to submitted materials, confidentiality and responsibility.
Read the details ↗Terms of service
The terms for using our website and related services.
Read the details ↗