Contents
1. Scope
This policy applies to information processed through the Revana.Money website and platform, including sign-up and login flows, subscription and payment recovery workflows, abandoned checkout recovery, cancellation and offboarding experiences, customer analytics, escrow and milestone management, invoicing, dispute intake, and support interactions.
It also applies to personal data submitted through our SDKs, embedded components, APIs, and integrations when that data is made available to us by a customer or user in connection with these services.
2. Information We Collect
Information you provide directly
- Account data such as name, business name, email address, phone number, login credentials, and role information.
- Billing and commercial data such as subscription details, invoicing information, plan selections, and contract records.
- Communications you send to us, including support requests, onboarding materials, demo requests, feedback, and dispute submissions.
- Escrow and milestone content, including project descriptions, deliverables, attachments, comments, approval decisions, and evidence uploaded in connection with disputes.
Information collected from integrations and platform activity
- Payment and subscription metadata from providers such as Stripe, PayPal, or other configured partners, including payment status, subscription state, invoice references, charge events, refunds, and recovery outcomes.
- Checkout, cart, and cancellation-flow events captured through our SDKs, components, or ecommerce integrations, including product, cart value, checkout stage, offer exposure, and conversion outcome.
- Messaging and engagement data relating to recovery campaigns, such as delivery events, bounce information, opt-out signals, and campaign performance metrics.
- End-user feedback and survey responses collected when a customer deploys our offboarding or recovery components.
Technical and usage data
- Device, browser, IP address, approximate location, operating system, referral source, session timestamps, and log data.
- Security telemetry such as authentication events, suspicious activity indicators, API request metadata, and administrative audit logs.
- Cookie or similar technology data used for core site operation, security, remembering preferences, and analytics where enabled.
We generally do not store full payment card numbers. Those are usually processed directly by the relevant payment service provider.
3. How We Use Information
We use personal data to:
- provide, operate, maintain, and improve the Revana.Money platform;
- authenticate users, secure accounts, prevent abuse, and detect fraud or other harmful activity;
- trigger payment recovery, checkout recovery, retention, and re-engagement workflows configured by our customers;
- generate analytics, performance reporting, and operational insights for customers and internal service improvement;
- administer escrow, invoicing, milestone tracking, dispute review, and evidence handling;
- send service notices, transactional messages, security alerts, and, where permitted, product updates or marketing communications;
- comply with law, enforce our agreements, protect our rights, and manage legal claims.
Where applicable law requires it, we rely on one or more of the following legal bases: contract performance, legitimate interests, compliance with legal obligations, consent, and establishment, exercise, or defense of legal claims.
4. Controller And Processor Roles
Revana.Money may act as either a controller or a processor, depending on the context.
- We act as a controller for data relating to our own website, account administration, direct customer relationships, billing, security monitoring, and product improvement.
- We typically act as a processor or service provider when a business customer uses our platform to process its own customer, subscriber, buyer, client, or contractor data through recovery, checkout, offboarding, escrow, or dispute workflows.
If your personal data was submitted to Revana.Money by one of our customers, that customer may remain responsible for the primary privacy notices, legal bases, and response to certain rights requests. In those cases, we may direct you to the relevant customer.
5. Product-Specific Processing
Payment recovery and churn prevention
We process payment status, subscription state, offer logic, messaging delivery data, and response metrics to help customers recover failed payments, reduce churn, and re-engage users who may otherwise leave.
Checkout drop-off and offboarding components
When customers deploy our SDKs or embedded components, we may process cart details, abandonment signals, cancellation responses, survey answers, offer interactions, and conversion events to power retention experiments and performance reporting.
Escrow, milestone tracking, and disputes
Our escrow features may process project identities, counterparties, invoice references, milestone approvals, deliverable evidence, dispute narratives, communications, and release decisions. This information is used to manage project funds, document fulfillment, detect misuse, and help resolve disagreements.
AI-assisted features
Some workflows may use AI-assisted tools to summarize evidence, detect patterns, recommend recovery actions, score risk, propose next steps, or support dispute triage. These tools are intended to support platform operations and customer decision-making. Material outcomes involving escrow, disputes, fraud prevention, or account restrictions may also involve rules-based controls and human review where appropriate.
7. International Transfers
Revana.Money and its service providers may process personal data in countries other than the country where the data was originally collected. When we transfer personal data internationally, we use appropriate safeguards where required, such as contractual protections, transfer assessments, and supplementary technical or organizational measures.
8. Data Retention
We retain personal data only for as long as needed for the purposes described in this policy, including to provide the service, maintain records, resolve disputes, enforce agreements, prevent fraud, and comply with law. Retention periods vary by data type and product workflow.
- Account, identity, and authentication records: Retained for the life of the account and typically for up to 24 months after closure to support reactivation, security investigations, and audit trails.
- Transaction, invoice, payout, tax, and financial ledger data: Retained for at least 7 years where required for accounting, fraud prevention, legal claims, and regulatory compliance.
- Recovery campaign, checkout recovery, and customer communication event logs: Usually retained for up to 24 months unless a shorter customer-configured retention period applies or longer retention is required for disputes or compliance.
- Escrow, milestone, dispute, and evidence records: Retained for the term of the engagement and commonly for up to 6 years after final resolution because these records may be needed to enforce agreements and resolve later claims.
- Support requests, incident reports, and security logs: Support tickets are typically kept for up to 3 years, while core security and access logs are generally kept for 12 months unless investigation, abuse prevention, or legal obligations require longer retention.
- Backups and disaster recovery copies: Stored on a rolling basis and typically overwritten within 90 days, except where a backup must be preserved for security, legal hold, or recovery purposes.
We may retain data for longer when required by law, when a dispute, investigation, or legal hold is active, or when we need a limited record to prevent repeat abuse, enforce restrictions, or document prior processing.
9. Security And AI-Assisted Workflows
We use administrative, technical, and physical safeguards designed to protect personal data against unauthorized access, loss, alteration, misuse, or disclosure. These safeguards may include access controls, encryption in transit, environment segregation, audit logging, backup procedures, rate limiting, and vendor due diligence.
No service is completely secure. You should also protect your own credentials, use strong passwords, enable additional account security controls where available, and notify us promptly if you suspect unauthorized access.
If AI-assisted tooling is used in connection with a workflow, we aim to keep that use proportionate to the service being provided and aligned with appropriate confidentiality, access control, and review standards.
10. Your Rights And Choices
Depending on your location and the role in which we process your data, you may have rights to access, correct, delete, restrict, object to, or port certain personal data, and to withdraw consent where processing is based on consent.
You may also be able to opt out of non-essential marketing communications by using the unsubscribe link in the message or by adjusting account preferences where available.
If we process your data on behalf of a business customer, we may need to refer your request to that customer so it can be handled by the party that controls the underlying business relationship.
11. Children
Revana.Money is intended for business and professional use and is not directed to children. We do not knowingly collect personal data from children where prohibited by law. If you believe a child has provided personal data to us unlawfully, contact us so we can review and take appropriate action.
12. Changes And Contact
We may update this Privacy Policy from time to time to reflect changes in the service, law, security practices, or operational requirements. When we make material changes, we will update the date at the top of this page and may provide additional notice when required.
For privacy questions, requests, or complaints, contact REVANA MONEY LIMITED at c.marshall.engineer@gmail.com or write to 14 Cairns Crescent, Dunfermline, KY12 9FH.