Data collection statement · Updated 8 October 2026

Data collection.
Purpose and access.

1. Responsibility and scope

RentBoy.rent is the public-facing service responsible for the records described here. Data requests and questions go to info@rentboy.rent. This statement covers account, content, booking, support and payment-verification records handled through the service. It supplements the Privacy Policy rather than asserting an unverified company address, legal incorporation or data-controller registration.

2. Records actually collected

The application stores account names and emails, password hashes, email verification and sessions; provider profile text, age and country; photos/videos and moderation states; conversations and read/presence timestamps; preferences, favourites, availability, booking briefs and acceptances; commission/deposit references and verification states; reviews, reports, costs, subscriptions and audit records. Registration records include recorded request IP and delivery state where available.

The current application does not collect card numbers, PayPal passwords, passport numbers, national identity numbers, mobile-device telephone numbers or government-ID images as registration fields. Private verification may require separate evidence handling; explain the purpose and collection method before requesting it. Public galleries and complaints forms must not be used to collect ID-document copies.

3. Purposes and grounds

Records support requested accounts and bookings, authentication, moderation, fraud prevention, receipts, dispute handling, recordkeeping and service operation. Optional newsletter/alert consent is separate from essential service processing. Where applicable, relevant grounds may include performing the requested contract, legal obligations, legitimate interests and consent. Consent to marketing is not inferred merely from viewing the site.

4. Access and security

Access is restricted by role, ownership and moderation permissions. Passwords are hashed, verification codes expire, and authenticated endpoints enforce account checks. Public APIs omit sensitive fields; legal reports have a separate restricted review path. Authorized processors may include hosting, transactional email and payment providers. Security measures reduce risk but do not make every transfer or server invulnerable.

5. Access, correction and deletion requests

Email info@rentboy.rent to ask what data is held, request a copy, correct inaccuracies, request deletion or restriction, object to applicable processing, or withdraw optional consent. Verification should be proportionate to the request; a notarized power of attorney is not routinely required. RentBoy.rent will respond within applicable statutory periods, explain a lawful refusal or extension, and identify escalation options. A universal fourteen-day response is not promised for every jurisdiction.

6. Disclosure and transfers

Personal information is not public merely because it is stored. Necessary processors and authorized support personnel may receive it for stated purposes. Disclosures to authorities require a valid legal basis or reporting duty. Business transfers must address applicable notice, safeguard and retention requirements. Hosting and vendors may involve international processing; no unverified assertion is made that all servers are in Germany or exclusively in the EU.

7. Retention, backups and review

Data is retained for operation, disputes and applicable recordkeeping, with review of deletion requests. Removing live data does not instantly rewrite every backup. Backups and restores should be controlled and tested; this statement does not claim a particular thirty-day schedule unless it is actually implemented. New processing should be assessed before deployment and disclosures updated when practices change.