Privacy Policy

Effective August 16, 2026; updated August 17, 2026. This product is under active development; this policy must be reviewed with qualified counsel before a broad commercial launch.

What Revenue Rescue processes

Revenue Rescue processes account and workspace identity, workspace memberships and invitations, configuration, connected-provider identifiers, normalized revenue events, opportunities, recovery-case history, channel delivery records, audit records, and billing data needed to provide the service.

Account and session security data

For authenticated-session security, Revenue Rescue may store a truncated browser user-agent string, session creation and last-activity timestamps, the active workspace and role, and session expiry. Raw IP addresses are not stored in the session record. When the workspace operator configures a dedicated session-security salt, Revenue Rescue stores only a one-way HMAC-SHA256 fingerprint derived from the network address for security correlation. Workspace invitation tokens, password-reset tokens, verification tokens, and session bearer tokens are not stored in plaintext; only cryptographic hashes are retained where applicable.

Workspace invitation records may include the invited email address, requested role, inviter identifier, expiry and acceptance/cancellation state, and system-email delivery metadata. Invitation links expire and are one-time use.

Google and Gmail data

The Gmail integration requests send-only authorization. Revenue Rescue does not request Gmail inbox-reading scopes. We store the authorized Google account identifier, mailbox email, encrypted OAuth credentials, and delivery metadata such as the Gmail message ID needed to audit a recovery action.

Revenue Rescue's use and transfer of information received from Google APIs will comply with the Google API Services User Data Policy, including its Limited Use requirements.

WhatsApp Business data

The WhatsApp Business integration stores the business's Meta access token encrypted by workspace, safe account metadata, the approved recovery template configuration, customer WhatsApp consent/opt-out state, and transport metadata such as WhatsApp message IDs and delivery status. Inbound message bodies are not copied into the ChannelMessage recovery ledger; the webhook records message type, transport identifiers, timing, and explicit opt-out state needed to govern recovery communication.

Businesses are responsible for establishing an appropriate lawful basis and permission for customer messaging. Revenue Rescue requires recorded WhatsApp consent before proactive recovery delivery and honors channel opt-outs independently from the global Contact Hold.

Provider credentials

OAuth and provider access credentials are encrypted before database storage. Credentials are isolated by workspace and are not presented back to users after connection. Disconnecting a provider removes Revenue Rescue's local ability to use its credentials and requests provider-side revocation where supported or documents when provider-level shared subscriptions must be managed separately.

Purpose limitation

Connected data is used to identify, prepare, govern, execute, reconcile, and audit revenue-recovery workflows requested by the business. Account and session metadata is used for authentication, access control, security review, and abuse prevention. Revenue Rescue does not sell connected-account data to advertisers.

Retention and deletion

Expired sessions and security tokens are cleaned automatically. Consumed authentication tokens are retained briefly for replay protection, expired rate-limit buckets are retained with a short safety grace period, and old accepted, cancelled, or expired workspace invitations are periodically removed. Businesses should be able to disconnect providers and request account/workspace deletion. Production backup deletion windows and statutory retention exceptions must be finalized before public launch.

Security

The application uses tenant isolation, encrypted provider credentials, hashed bearer and invitation tokens, session controls, membership revalidation, webhook authentication, request tracing, idempotent audit events, and policy/approval gates. No internet service can guarantee absolute security.

Contact

Operational privacy contact details must be configured on the production domain before provider verification and public launch.