Data Practices

ClaimSage is owned and operated by the company owner. The application runs on Polsia infrastructure — meaning Polsia provides hosting (Render), database (Neon PostgreSQL), deployment pipelines, and AI proxy services — but Polsia is an infrastructure provider, not a co-owner of the business.

Think of it like using AWS or Heroku: the infrastructure is managed, but the business, its content, and its customers belong to the owner.

The business owner owns all of the following:

• Application source code — the ClaimSage codebase lives in a GitHub repository owned by the company owner's account.
• Database records — all user data, EOB analyses, appeal letters, usage events, and email queue data belong to the owner.
• Generated documents — AI-generated appeal letters, cost estimates, and benefit summaries are the owner's intellectual property.
• Collected email leads — email addresses captured through ClaimSage's lead gates are the owner's data. Polsia does not use them for its own purposes.
• User-uploaded files — documents uploaded by end users are processed on behalf of the business owner and are subject to the owner's privacy policy with those users.

Polsia retains no ownership interest in the application, its content, its data, or its intellectual property.

Uploaded EOBs follow this path:

• Image files are sent to OpenAI's API for OCR (optical character recognition) to extract text. They are processed in memory and not permanently stored on ClaimSage's servers.
• Extracted text is passed to the Polsia AI proxy (backed by Anthropic's Claude) for analysis — claim parsing, denial explanation, and summary generation.
• Analysis results (provider name, amounts, denial codes, summaries) are saved to the database so users can reference them. Raw document content is not stored.

Email addresses collected through ClaimSage's lead capture gates are stored in a PostgreSQL database hosted on Neon (a managed cloud database provider). The data is encrypted in transit and at rest.

Access is restricted to:

• The ClaimSage application itself (for sending nurture emails)
• Polsia infrastructure for database management and backups
• The business owner via the admin dashboard or direct export

Email addresses are not shared with, sold to, or accessible by any third party for marketing or other purposes. They are used solely to deliver the nurture email sequence you have configured.

Yes. A full export is available on request and includes:

• Source code — the complete GitHub repository
• Database dump — all tables: leads, email queue, EOB analyses, appeal letters, usage events, users
• Generated documents — any stored AI outputs
• Task and execution logs — history of agent activities

To request an export, email support@polsia.com. Exports are delivered as a zip archive containing the repository and a database dump in standard PostgreSQL format (.sql).

Polsia charges a 20% platform fee on payments processed through the Polsia Stripe integration. This fee applies only while the subscription is active and covers the infrastructure, AI proxy usage, and platform services.

After cancellation:

• The owner retains all code, data, and content — no restrictions
• Polsia retains no license or continuing rights to the company's intellectual property
• Polsia does not retain access to the owner's data after the account is closed
• The owner may continue operating the application independently on any hosting provider

This page is meant to be accurate and complete. If any answer here doesn't match your actual experience or agreement with Polsia, please flag it immediately:

ClaimSage: claimsage@polsia.app

Polsia platform support: support@polsia.com