Privacy Policy

If Subscription Integrity is available in your workspace, its check compares Stripe account, subscription, subscription-item and attached Price facts with an access snapshot you choose to provide. Availability is shown in your workspace; a Stripe connection alone does not establish a completed or healthy check. The check does not change Stripe subscriptions or your application's access.

Provide only the workspace reference, Stripe customer identifier, optional subscription identifier, active or inactive access state, access tier and observation time requested by the snapshot template. Do not include customer names, email addresses, passwords, card details or secret keys. Recovra uses the normalized rows, your confirmed rules and bounded Stripe facts to produce the attributable comparison.

Snapshot contents are available for at most 7 days from acceptance, or less when withdrawn, replaced or expired. Withdrawal remains available to the active workspace owner after Stripe disconnect. Withdrawal or expiry makes the source contents and dependent rules and customer-level comparison details unavailable; it does not extend a previous result's freshness.

Backups may contain older source contents. A restored database must replay the verified current withdrawal/deletion journal before it is safe to serve traffic. Minimal source revision, digest and deletion references support integrity and recovery without retaining snapshot contents. Existing commercial and case records keep their separate purpose and retention rules.

Access Snapshot notice version: integrity-access-snapshot-v1.

For a later accepted case, the intended verified merchant may select relevant findings from earlier delivered Recovra Plans in the same workspace and confirm that they concern the same legal business. Recovra reviews their relevance before using them to prepare that case. This does not authorize ongoing provider collection or account changes.

Permission to use a selection ends after 30 days, or sooner when withdrawn or the destination case closes. Review does not restart that period. Original source expiry and deletion continue to apply. The index stores source references and a minimal selection and review history, rather than copies of files or messages. Withdrawal hides the previous values from the later case; original case and audit records retain their existing purpose and retention rules.

Where private continuation is enabled, you may add relevant business messages, links, screenshots, CSVs and PDFs that you are authorized to share. Remove unrelated personal information, card details, passwords and secret keys first. Files are checked before they become available for review.

We use this material to understand the situation, identify missing information, prepare a person-approved initial review and, where appropriate, propose a scoped service. Providing material does not create a paid engagement or authorize changes to your Stripe account.

Your private request is available for 30 days from creation. Its expiry is shown in the request; adding material does not extend it. You can remove individual sources earlier. At expiry, private request details, source contents and initial-review contents are removed from the active system.

Backups may temporarily contain older copies. Source deletions are reapplied before restored data can serve traffic. Minimal deletion references, containing no source contents, are retained until 30 days after request expiry. Agreed commercial records follow their separately documented retention requirements.

Use a private access link to return to the request. Essential cookies protect access; these private pages do not run our website analytics. Hosting and service-email providers help operate this service. Contact support@recovra.de for privacy requests.

Private request notice version: private-intake-2026-09-13.

Payment Triage information: the payment-health problem you select, your description of the situation, optional website URL, relevant Stripe-message or deadline context, active-dispute context, business name and type, payment model, work email, and whether you can make or share the business decision.

Commercial-offer information: the founder-selected package, recommendation rationale, scope, exclusions, price snapshot, intended business email, offer status, scope-acceptance confirmations, accepted terms and privacy versions, and related timestamps.

Payment information: Stripe Checkout session identifiers, payment status, paid amount, tax amount where reported, currency, payment-intent identifier where available, and verified Checkout event identifiers. Recovra does not receive or store full card numbers through its own Checkout flow; Stripe processes payment credentials.

Secure-case information: case status, account or merchant binding, access state, findings, plans, implementation or testing state, outcome-learning records, and evidence or files you later choose to provide within the secure case boundary.

Account and security information: email address, account or workspace identifiers, authentication and session records, login timestamps, access events, and limited operational or security logs needed to protect the service.

Optional Google sign-in: when this method is available and you choose it, Google shares your account identifier, email address and verification status, name and profile-image URL. Recovra uses these facts to authenticate and display your account and to protect provider linking. Recovra does not receive your Google password or request access to Gmail, Drive or Calendar. Signing in does not connect Stripe or authorize changes to your sources.

Connected-provider information: if an existing workspace or an accepted future scope uses a separately authorized Stripe connection, Recovra may process the bounded account, dispute, payment, customer, charge, event, or other provider data permitted for that integration and required for the authorized work.

Triage information is used to understand the request, protect the intake from abuse, contact the merchant, and support founder judgment about fit and the smallest responsible next step. Payment Triage does not automatically diagnose the merchant or select a package.

Commercial information is used to prepare and preserve the exact offer, recommendation rationale, accepted scope, price, legal-version confirmations, checkout state, and payment truth for an engagement.

Case and evidence information is used to perform the accepted Payment Health work, preserve provenance, explain findings, coordinate actions, verify implementation where included, and record bounded outcome learning.

Account and operational data is used for authentication, access control, support, security, reliability, auditability, and communication about the service or case.

We do not sell personal data and do not use merchant case data for third-party advertising or cross-site advertising profiles.

Where the GDPR applies, we process inquiry and agreement data as necessary to take steps you request before an engagement or to perform that engagement (Article 6(1)(b)).

For business contact persons, service security and abuse prevention, we rely on our legitimate interests in responding to business requests and operating a reliable, protected service (Article 6(1)(f)), balanced against the person's rights. Supply only relevant information you are authorized to share and redact unnecessary information about other people.

Optional public-website analytics relies on consent (Article 6(1)(a)). Private request material is not used for advertising or consent-based website analytics.

Payment Triage is a public intake and should contain only the minimum relevant business and Stripe context. Do not submit card numbers, passwords, secret API keys, webhook secrets, authentication cookies, or other credentials through the Triage form.

Recovra applies validation, rate limiting, a honeypot control, and checks for card-shaped numbers and common live-secret formats before durable Triage storage. These controls reduce obvious unsafe submissions but cannot guarantee that every sensitive value will be detected.

If more sensitive evidence is reasonably needed later, Recovra should request it through the appropriate secure case or explicitly authorized channel rather than through the public Triage form.

Recovra may distinguish Merchant Supplied information, Publicly Observed information, Connected Provider Data, Official Guidance, and Recovra-Generated Artifacts so the origin of evidence remains visible.

Findings may also distinguish direct facts, derived facts, interpretations, hypotheses, and unknown information. Recovra does not claim that missing information or private provider logic is known.

Where files or screenshots are accepted, you should provide only material you are authorized to share and should remove unnecessary credentials, card data, personal data, or unrelated sensitive information before uploading whenever possible.

Some existing Recovra workspaces retain a separate Stripe Connect OAuth or Stripe App permission path built for dispute workflows. Payment Triage and the current founder-led Payment Health entry do not require that connection.

When Stripe Connect OAuth is used, Recovra stores encrypted OAuth tokens and uses only the provider data and writes needed for the authorized connected workflow. The separate Stripe App path uses its named permissions rather than the broad Connect read_write scope.

Recovra does not use those connections to move payouts, transfer funds, issue refunds, change bank details, use customer payment methods, or silently expand a merchant's accepted Payment Health scope.

Recovra currently uses third-party Railway cloud infrastructure in a United States region for production services and the database. Production backups are encrypted before they are written to backup storage.

Commercial and case records may be retained where needed to preserve the accepted agreement, payment and invoice history, security and audit trails, evidence provenance, claims handling, or other documented legal, contractual, or operational purposes.

Selected mutable personal-data fields in legacy dispute records are anonymized only after the dispute is terminal and the applicable retention conditions are met. Immutable evidence provenance, decision history, submission outcomes, and financial-result records may be preserved where deleting them would weaken integrity or audit protections.

Raw monitoring evaluator runs are kept for 30 days. Expired or consumed one-time authentication capabilities and expired sessions are removed after a 30-day operational grace period; currently valid sessions and capabilities are preserved.

Railway and our service-email provider, Resend, publish Data Processing Addenda covering their processing roles, security duties and international transfers. Their terms include applicable EU Standard Contractual Clauses for transfers that require them. Contact support@recovra.de for information about the safeguards applicable to your request.

The precise legal classification and retention of commercial history remain separate from the limited private-intake period. This policy does not assign every commercial record an unverified statutory retention category.

We do not sell your data and do not share merchant case data with third parties for their marketing.

Data may be processed by providers used to operate Recovra, such as hosting and database infrastructure, Stripe for payment processing and authorized Stripe integrations, and email or communications providers used for account, security, or service messages.

If you consent to analytics, public website usage data is also processed by Google as the analytics provider described in the Cookies section. Analytics consent does not authorize advertising use of merchant case data.

Recovra may also disclose information where reasonably required to comply with applicable law, enforce rights, protect users or the service, investigate abuse, or respond to a valid legal process.

Depending on applicable law and the relevant record, you may request access to personal data, correction of inaccurate personal data, deletion, restriction, objection, or other available data-protection rights.

A deletion request may not require Recovra to erase records that must or may legitimately be retained for legal, contractual, security, claims, fraud-prevention, payment, audit, or integrity purposes. Where deletion is not appropriate, Recovra should explain the applicable boundary when responding to the request.

You can revoke a separately authorized Stripe connection from Stripe. Revocation stops future access through that connection but does not automatically erase records already retained for a legitimate purpose.

Contact support@recovra.de for privacy or data requests.

You may also lodge a complaint with a competent data-protection supervisory authority.

We use essential cookies or equivalent browser storage for authentication, session management, security, and other functions required to operate the service. These functions are not used for advertising.

With your consent, we also use Google Analytics, provided by Google Ireland Limited, to understand how visitors use the public website. Analytics may process information such as pages viewed, referrer, device or browser information, and approximate location derived from network information.

Analytics cookies are set only after you accept them in the cookie banner. If you decline, analytics cookies are not intentionally set by Recovra's consent-controlled analytics path. You can revisit your choice through the Cookie preferences control in the public footer.

We do not use advertising, remarketing, or cross-site behavioral advertising cookies.

We may update this policy as Recovra evolves. A paid commercial offer records the privacy-policy version accepted for that offer. Material changes affecting an active account or engagement may be communicated by email, workspace notice, or another appropriate channel.