Identity verification disclosure
Learn when Rentino requests identity verification and how verification affects trust, payouts, and platform safety.
Chapters
10
Key points
44
Reading mode
Structured sections with sticky chapter navigation
Use the chapter rail to jump quickly, but read the full section before relying on a rule.
Start with the summary or opening notes, move through the matching chapter, then confirm the date or update note before acting.
2
Short sections, numbered points, and sticky chapter links
Before you rely on this page
- Check the effective date and last update.
- Read the full chapter, not just the heading.
- Use support when the policy does not clearly answer your case.
- 1Rentino Inc. (“Rentino,” “we,” “us,” “our”) operates Rentino (rentino.org).
- 2This KYC / Identity Verification Disclosure (“Disclosure”) explains how identity verification works on Rentino (rentino.org). It applies primarily to Owners (people who list items and receive payouts). This Disclosure is part of Rentino’s Terms, Privacy Policy, and Payments & Fees Policy.
Why Rentino requires identity verification
Key points and requirements in this section.
Rentino requires identity verification (“KYC”) to:
- 1enable payouts to Owners and reduce fraud
- 2comply with payment network and financial compliance requirements
- 3protect Renters and Owners from scams and chargebacks
- 4support dispute resolution and trust/safety enforcement
Who performs verification
Context and explanation for this part of the policy.
Rentino uses Stripe to perform identity verification and payout onboarding for Owners (including Stripe’s verification services and related providers). Stripe’s handling of verification data is governed by Stripe’s own policies and agreements.
When KYC is required
Key points and requirements in this section.
KYC may be required:
- 1before an Owner can approve booking requests
- 2before an Owner can receive payouts
- 3when risk signals require additional verification (for example: unusual activity, large transaction volume, repeated disputes, chargebacks, or account changes)
- 4If KYC is required and not completed, your account may be restricted (for example, you may not be able to approve booking requests or receive payouts).
What information may be collected
Key points and requirements in this section.
Depending on Stripe’s requirements and your account activity, verification may involve collecting or confirming:
- 1legal name, date of birth, address, phone number, email
- 2payout details (e.g., bank account information)
- 3government-issued ID information (such as driver’s licence, passport, or other ID)
- 4a selfie or liveness check (where required by Stripe)
- 5business-related information (if business accounts are enabled in the future)
- 6device and security signals (to prevent fraud)
- 7Not every Owner will be asked for the same information. Requirements may change over time based on compliance rules and risk.
How verification works (high level)
Key points and requirements in this section.
- 1You submit the requested information through Rentino’s verification flow (powered by Stripe).
- 2Stripe reviews the information and returns a verification status (for example: verified, pending, needs more information, or failed).
- 3Rentino uses that status to decide whether listings and/or payouts can be enabled.
What Rentino receives vs what Stripe stores
Key points and requirements in this section.
- 1Stripe collects and stores the identity verification information you provide as part of their processing and compliance obligations.
- 2Rentino typically receives limited information such as verification status and basic account details needed to operate the Platform (for example, whether you are verified, and whether payouts can be enabled).
- 3Rentino does not store full payment card numbers and does not need to store full copies of identity documents to operate payouts.
How verification data is used
Key points and requirements in this section.
Verification information may be used to:
- 1confirm identity and eligibility for payouts
- 2prevent fraud, account takeovers, and suspicious activity
- 3comply with legal, regulatory, and payment processor requirements
- 4support investigations related to disputes, chargebacks, prohibited items, or safety issues
Decisions, restrictions, and enforcement
Key points and requirements in this section.
If verification is:
- 1Pending: your payouts and/or listing ability may remain restricted until completed.
- 2Needs more information: you must submit additional details within the timeframe shown.
- 3Failed or rejected: Rentino may disable listing and payout features and may suspend or terminate the account if required for safety/compliance.
- 4Rentino may also restrict accounts if it believes there is fraud risk, policy violations, or attempts to bypass platform rules.
How long information is kept
Key points and requirements in this section.
Retention depends on:
- 1Rentino’s operational needs (fraud prevention, disputes, accounting records), and
- 2Stripe’s legal/compliance retention requirements for identity verification and financial transactions.
- 3Where feasible, Rentino will delete or anonymize information it no longer needs. Some records may need to be retained for legal or security reasons.
Your choices and access requests
Key points and requirements in this section.
- 1If you do not want to complete KYC, you may still use some parts of the Platform, but Owner features that depend on verification, including approving booking requests and payouts, will not work.
- 2You can request access/correction of your personal information held by Rentino by contacting [email protected].
- 3Because KYC is processed by Stripe, some KYC-related requests may need to be handled by Stripe as well; Rentino can guide you.
Navigator
On this page
- 1Why Rentino requires identity verification
- 2Who performs verification
- 3When KYC is required
- 4What information may be collected
- 5How verification works (high level)
- 6What Rentino receives vs what Stripe stores
- 7How verification data is used
- 8Decisions, restrictions, and enforcement
- 9How long information is kept
- 10Your choices and access requests
Reading guide
Before you rely on a section
- Check the effective date and latest update.
- Read the full chapter, not just the heading.
- Use the related product flow only after reviewing the rule.
