Launched this week
Thrive Financial
Divorce financial analysis and asset tracing, simplified.
8 followers
Divorce financial analysis and asset tracing, simplified.
8 followers
Thrive Financial is divorce financial analysis software for hidden assets, discovery, and settlement planning. Parse statements, tax returns, affidavits, legal filings, and business records, trace transfers, analyze marital financials through numerous financial analytical tools, and export court-ready evidence for a fraction of the time and cost of an external firm.
@crmcguire74 Do you redact sensitive information from the documents before parsing the documents with Gemini?
Additionally, are SOC 2, AES-256 encryption, quarterly penetration testing claims already performed/implemented in the app?
Do you have any Free lifetime codes for the initial users of the application?
@crmcguire74 Additonally, how well does this software take into account community vs non community states for settlement negotiations?
@shooooooo
The AI Settlement Proposal and Proposal Assessor modules are coded to assess the state or country of proceedings and account for the laws appropriate to those territories (equitable, 50/50). In addition, the settlement module has been trained to use territory laws and guidance, but also advocate on behalf of the user (spouse, pro se litigant, attorney for the spouse), outputting a fair settlement proposal grounded in the extracted financial information, red flag findings and concerns, and providing explicit descriptions to proposals that favor a party.
@shooooooo
Hi there...let me tackle each of the questions below:
AES-256 Encryption
Plaintext SHA-256 (Currently in production)
How it worked: The app serialized the case into a clean JSON string, generated a standard SHA-256 digest, and appended it to the file. Upon import, the app re-computed the hash to verify that the file hadn't been modified or corrupted.
AES-256-GCM Encryption (Development cycle finished, releasing in the next day)
All private case data stored locally in your browser's database is encrypted at rest using AES-256-GCM. Additionally, when you export a .thrive backup file, it is secured as a password-protected binary container using AES-256-GCM and PBKDF2 hashing.
SOC 2 Compliance (In Progress):
While we have built the platform with strict security and privacy controls, formal compliance to SOC 2 Type 1 standards are in progress and a formal SOC 2 Type I readiness assessment and SOC 2 Type II audit are currently on our future roadmap.
Quarterly Penetration Testing (Not Yet Implemented):
No. Independent, third-party penetration testing has not yet been performed, but it is planned as part of our upcoming security program roadmap aligned with the SOC Type I readiness
Free lifetime codes for the initial users of the application
Their is a free tier that gives users access to 3 initial AI credits, the document parser, asset/debt manager, settlement negotiator modules forever. No credit card is required to access the Starter Tier, and it allows users to view demo functionalities given to higher tiers.
Several initial users during a beta testing phase have been granted system access to vet out the functionality.
Redaction of Information
No, Thrive Financial does not automatically redact sensitive information (such as account numbers or SSNs) from your documents before sending them to the AI for parsing. Redacting documents, such as images that need to be scanned, would be difficult and additionally block the analysis portions of the app to dig into the details.
With that said, your data remains secure due to our enterprise privacy controls:
No Model Training: The financial data transmitted to Google Gemini for parsing is strictly used for your active session and is not used to train Google's foundational AI models.
Anonymization Tooling: While we do not redact pre-parsing, Thrive Financial does feature a "Generate Anonymized Demo File" tool. This feature replaces identifying names, banks, account numbers, and addresses, which is perfect for sharing workflows safely or testing the system without exposing real client data.
The backend relies on a paid, enterprise-bound architecture via Firebase and Vertex AI, and data falls squarely under Google's strict corporate privacy terms:
For Vertex AI & Paid Gemini API Traffic: Section 17 ("Training Restriction") of the official Google Cloud Service Specific Terms explicitly states: "Google won't use your data to train or fine-tune any AI/ML models without your prior permission or instruction."
For Gemini API Developer Terms: The Gemini API Additional Terms of Service ("Paid Services" clause) mandates: "When you use Paid Services... Google doesn’t use your prompts (including associated system instructions, cached content, and files...) or responses to improve our products..."