How Recoupex handles your data

Recoupex is a revenue-recovery workspace. The data we hold is the data you load or generate inside the product — we do not collect end-user data from your customers’ own customers beyond what you put in.

• Leads — name, contact details (email, phone), source, status, and any notes or tags you attach.
• Contacts — the people surfaced from your CRM imports, with their contact history and prior conversation state.
• Segments — the filters and rules you define to group leads for outreach (e.g. “dormant 60+ days, US”).
• Message drafts — outbound copy generated or edited by the AI, plus the human edits you apply on top.
• Account & billing — sign-in email, profile, subscription tier, and receipt metadata from our payment processor.

Everything else — your CRM, billing system, calendar — stays in your stack. Recoupexconnects to them through read-only or operator-approved integrations; we copy the minimum needed to run the workflow.

The model drafts outreach from inputs you supply — the lead row, the segment spec, and any earlier draft history you ask it to learn from. Prompts are routed through the Polsia AI proxy; Recoupex does not call model providers directly and never holds a provider key.

Drafts are scoped per tenant. One customer’s inputs are not visible to another’s drafts or model calls, and we do not use your drafts or leads to train any shared model.

Drafts are drafts: nothing is sent until you approve or schedule it. You can edit any line before it goes out, and the original draft is preserved for audit.

Auth. Sign-in issues a session through our auth provider. The session cookie scopes every /api read and write to the signed-in user, and is HttpOnly. No third-party tracking cookies are set.

Locale. If the locale module ships, a cookie stores your language preference. It is purely functional — used only to render the UI — and is not used for analytics.

No advertising or analytics cookies. Recoupex does not run third-party ad pixels, retargeting tags, or analytics scripts on the marketing or app surface.

Access. Every record in the product — segments, leads, message drafts, message history — is visible to you from the workspace and is yours to inspect.

Export. Leads, segments, and quotes can be exported as CSV or XLSX from the corresponding page. If you need the rest of the data (auth logs, billing history) on demand, write to the address below.

Deletion. Account deletion cascades — segments, leads, message drafts, and message history scoped to that user are removed within the time stated in the deletion confirmation flow. For a hard-delete outside the in-product flow, email the address at the bottom of this page and we will action it manually and confirm in writing.

• Transport. All traffic is served over HTTPS; the database is reached over TLS.
• Per-tenant scoping. Every query is filtered with where: { userId: user.id }; one tenant cannot read another tenant’s rows.
• Secret hygiene. API keys and database URLs are injected by the platform. They are not committed to the repo and they are not sourced from the front end.
• Session hygiene. The session cookie is HttpOnly and scoped to the product domain; there is no shared admin password and no custom admin cookie.

We update the effective date at the top of this page whenever the policy changes. Material changes are also announced in-product and on the Recoupex blog, and you will get a reasonable heads-up before they take effect.

Non-material changes (typos, clarifications, formatting) update silently with the effective date bumped at the top.

For anything privacy-related — a data request, a deletion ask, a question about a processor, or a complaint — write to recoupex-ni4aa2@polsia.app. We reply from the same address and aim to acknowledge within two business days.

This policy is offered in English. If translations are added later, the English version here stays the source of truth.