How Solvren handles information
Effective 5 October 2026. Solvren, Inc., a Utah corporation, operates this service at 1673 East 1860 North, Lehi, UT 84043, United States. Contact support@solvren.com with privacy questions or requests.
Information we collect
Account and team information includes name, work email, authentication identifiers, role, and security events. Product data includes customer and contract identifiers, signed pricing terms, AI usage and outcome metadata, provider cost buckets, report decisions, and support requests. The ingestion schema does not accept prompt or response bodies, documents, or payment-card numbers. Stripe handles payment methods; Solvren stores subscription identifiers and status.
How it is used
We use account data to provide access, secure the service, send necessary messages, answer support cases, and manage billing. We use customer-provided financial and usage data to calculate and explain contract margins, reconcile cost evidence, generate reports, and alert authorized organization users. Aggregate conversion events omit customer names, contract terms, prompts, and raw usage.
Marketing email
If you explicitly subscribe to the AI margin field guide, we store your email, consent wording and time, confirmation status, and email delivery outcomes. We send the guide and occasional product updates only after you confirm. Each marketing email includes an unsubscribe link; you can also ask support to remove your subscription. We use hashed request fingerprints briefly to limit abusive signups. Public company research stores company-level information and source links, not personal contact details.
Who processes it
Infrastructure, authentication and database services, hosting, email delivery, and payment processing support the service. The current categories and providers are listed on the subprocessor page. Solvren does not sell customer data or use customer contract and usage records to train a public AI model.
Retention and control
Normalized events are retained for 13 months by default. Unconfirmed marketing signups expire after 30 days; signup fingerprints after two days, and delivery events after 90 days. We retain unsubscribe status to honor suppression until you request deletion. Organization Owners can export records and request closure in the workspace. Closure revokes access and schedules primary database and private-file deletion within 29 days. A canceled subscription enters read-only access and is scheduled for deletion within 29 days after access ends unless it is reinstated. If infrastructure backup copies exist, they expire according to the provider’s retention schedule.
Requests and security
Use Support for access, correction, export, deletion, or security questions. We verify account authority before disclosing organization records. Transport uses HTTPS in production, and primary stores use managed encryption.